عContact us
← Back to the blog

Workflow

Contractor → Consultant → Owner: The Approval Chain

Why this is the default approval workflow, and how it shapes document management and contractual correspondence.

By Mutamad TeamPublished 9 July 2026

On most construction projects, there is a default approval ordering: the contractor creates and submits the document, the consultant reviews and signs, the owner gives final approval when the document falls outside the consultant’s authority. This ordering is second nature to practitioners, but absent from most global document management systems.

Why the consultant is the signer

In this model, the consultant is the project’s engineer of record: they write the specification, they pre-qualify the contractor, and they stamp every technical submittal. Their role is not just review — it carries technical and legal consequences. A document is not complete until the consultant signs.

When does the owner step in?

The owner enters in specific cases:

  • When a change order exceeds a threshold (usually defined by the contract).
  • For time extensions or additional budget approvals.
  • For strategic documents (overall design, façades, major systems) that could affect delivery terms.
  • When contractor and consultant disagree, the owner’s decision is binding.

The trap: systems that do not understand this ordering

Most global document management systems treat approval as a two-party operation: creator and approver. To implement this chain, you need a full workshop configuration: custom roles, routing rules, exceptions. The result is high integration cost, and the team usually falls back to email and Excel to bridge the gaps.

How Mutamad implements this by default

  1. On document creation, it is auto-assigned to the contractor (creator) then routed to the consultant.
  2. The contractor cannot bypass the consultant to the owner — a rule enforced by roles.
  3. On consultant approval (code A), the system opens the next procedure automatically (inspection request, payment claim, phase).
  4. When owner involvement is needed, the document is routed to the owner’s task inbox with the full correspondence history as context.
  5. Every step is recorded in the immutable audit trail.

This ordering is not configured — it is the default. Read about native document types and how to choose document management software, or start a trial.