Skip to content
Approvals and audit history

Put supported decisions in one permission-controlled queue.

Review DPR, expense, material, payment and report records with their evidence, current state and recorded decision history.

NIYAM Approvals centre with pending expense and material decisions
Curated reference product screen showing the intended NIYAM workflow.
The decision gap

An approval is weak when the source and current state are unclear.

Decision-makers need the record, evidence, permitted action and prior state together—not a message asking for an unexplained yes or no.

The working sequence

A clear path from capture to responsible action.

Each step keeps the record, its context and the next responsibility visible.

  1. 01

    Create the source record

    Use the canonical DPR, expense, material, payment or report workflow.

  2. 02

    Submit for decision

    Move the valid supported record to the permitted approval state.

  3. 03

    Review context

    Inspect evidence, money, site, status and history where supported.

  4. 04

    Decide explicitly

    Approve or reject with confirmation and retain the recorded outcome.

Inside the feature

What construction approvals covers.

Focused capabilities for the complete workflow, described within their supported operating boundaries.

Unified attention queue

See supported pending record types without duplicating them.

Evidence beside decision

Review available source material in the decision context.

Permission control

Expose only the actions allowed for the current role and state.

Recorded history

Retain supported decisions and workflow state changes.

NIYAM Finance Inbox with expenses, approvals, payments due and vendors
Curated reference product screen showing the intended NIYAM workflow.
Canonical decisions

Expense and material decisions appear in the same attention centre.

The current evidence shows pending expense and material records while the Finance Inbox retains its own operational composition.

  • No duplicate source record
  • Permission- and state-aware actions
  • Recorded decision history
Who does what

A useful record has a responsible next person.

The feature supports the handoff without blurring who records, reviews or receives the information.

01

Owner or Admin

Decide the supported high-responsibility records permitted to the role.

02

Project manager

Review supported site and material decisions in context.

03

Accountant

Submit and follow supported finance records without bypassing approval.

Decision responsibility

An audit trail is useful evidence; it is not a compliance certification.

NIYAM records supported decisions and states. The authorised person remains accountable for the decision and its organisational consequences.

  • No autonomous approval
  • Duplicate decisions are protected
  • Only supported record types participate
Common questions

Questions about construction approvals.

Straight answers about scope, review and responsibility.

Which records can use Approvals?

Supported DPR, expense, material, payment and report records can enter their current permission-controlled decision paths.

Can a direct URL bypass the approval permission?

No. The current server and route guards continue to enforce role, workspace and record-state access.

Does recorded history certify compliance?

No. It provides operational evidence of supported state and decisions, not a compliance certification.