# Construction Change Orders: From Request to Approved Cost and Time

> A practical guide to the change order cycle: how a change request differs from a site instruction, a change order, and an extension of time, what the record must contain, and how unrecorded changes are prevented.

Published: 2026-10-20 · [Full version (HTML)](https://mutamad.net/en/blog/construction-change-order-workflow/)
Keywords: construction change order, variation order, change order approval workflow, time extension of time, construction change management

---

Change on a construction project is not the exception; it is the rule. A detail is missing from the drawings, an authority imposes a new requirement, or a material choice changes after approval. The risk is not change itself, but change that is executed before it is priced, priced without approval, or approved without reaching the programme. Once that gap accumulates, the end-of-project claim stops being a technical discussion and becomes an argument about memory.

A change order is not a form signed at the end. It is a record linking the reason for change to scope, price, and time. Every missing link becomes a question later: who asked for this, on what basis was it priced, who approved it, and when did work start?

## Change request, site instruction, change order, extension of time

Conflating these terms is the first reason traces disappear. A change request (CR) raises a need or an idea, from the owner, the consultant, or the contractor. A site instruction (SI) requires immediate work or clarifies design intent, and does not by itself approve money. A change order (CO or VO) approves scope, price, and time impact after evaluation. An extension of time (EOT) is a separate decision about programme, even though most change orders call for both.

**Who starts what in the change cycle**

| Step | Document | Usually raised by | What it produces |
| --- | --- | --- | --- |
| Raising the need | Change request | Owner, consultant, or contractor | Initial discussion and preliminary estimate |
| Pricing the impact | Cost and time estimate | Contractor | A provisional figure for review |
| Urgent execution | Site instruction | Consultant within delegated authority | Preserves the right to price later |
| Approving the impact | Change order | Owner or delegate | Binding scope, price, and time |
| Extending time | Extension of time request | Contractor | Revised programme and completion dates |
| Updating the record | Contract and budget revision | Project management | A new governing version of the work |

Each step produces its own document, and the links between them are what give the documents meaning. A site instruction without a change order is an open commitment; a change order without a programme update is a number on paper. Worse than either: a change executed on site with no document at all, leaving the gap between approved and built impossible to prove.

## Why change orders stall in practice

Most projects have the form. The failure is in when it is used:

- Executing before pricing: the owner wants progress, the work is done, and the price is negotiated with no reference — after execution, that number is always higher.
- Estimating without detail: a lump sum with no quantities, rates, or clause reference cannot be reviewed or compared.
- Separating time from cost: price is approved, time impact is forgotten, and the extension is requested near handover with no parallel record.
- No owner of the decision: nobody knows who may approve once a threshold is crossed, so the change sits between departments.
- Change by email: a drawing or specification revision arrives in a conversation and is built, leaving the register with no number and no revision.

## The practical path from request to approval

1. Record the request under its own number with description, location, technical reference, and reason for change.
2. The consultant assesses feasibility and alternatives before pricing, and recommends whether the change is necessary.
3. The contractor submits a detailed estimate: quantities, rates used, and the effect on existing items.
4. Time impact is assessed against the programme: what is affected, by how many days, and whether the item is critical.
5. The owner or delegate approves scope, price, and time under the authority matrix, or rejects, or returns it for revision.
6. Issue the approved change order linked to every prior document, and update the contract, budget, and programme versions.
7. Notify every affected party — quality, safety, procurement — from the same record, not from a separate message that can be missed.

## What a change order must contain

- A precise scope statement: what is added, removed, or replaced, and where.
- The originating request and the document that triggered it (RFI, submittal, or site observation).
- Quantities and rates used, and their contractual source.
- The net price and its effect on original items where relevant.
- The time impact: days, affected activity, and critical-path status.
- Attachments: approved drawings, photographs, samples, or inspection reports.
- Approval state: who agreed, when, and any expiry on the instruction to proceed.

Where the contract prescribes a form or approval thresholds, those govern. The system’s job is to make the prescribed form workable day to day, not to replace it with one of its own.

## How change orders connect to RFIs and submittals

A change often begins with an RFI that exposes a drawing conflict, a submittal returned as non-compliant, or a site observation. In every case the change order must cite the document that started it; otherwise it becomes a financial decision with no documented cause — the first thing questioned in a claim review.

Keeping one chain is therefore simpler than keeping three: [RFI](/en/blog/construction-rfi-workflow), then [technical submittal](/en/blog/construction-submittals-workflow), then change request, change order, and programme update. For the evidence side, read [what gives a project record evidentiary weight](/en/blog/construction-audit-trail-legal-weight).

## Preventing unrecorded change

- No work without a number: any scope outside the approved baseline starts with a numbered request, even if pricing comes later.
- A weekly open-change list: requests without a price, requests without a decision, and approved requests not yet reflected in the programme.
- Contractual settlement points: review pending requests at defined milestones instead of letting them accumulate to handover.
- Contingency tracking: every approved change draws down the allowance, so consumption is visible before it runs out.

None of this needs a complex system, but it needs one register that contractor, consultant, and owner all trust at the same time. When a contractor can see that their request actually entered the record, they stop reaching for email.

## The record that survives a claim

At handover nobody asks how many changes there were. They ask for the full history of each one: who requested it, why, who estimated it, on what basis, who approved it, and when it was executed. A project that can answer from the register negotiates with confidence; one that relies on meetings and memory pays for the doubt.

## Frequently asked

### What is the difference between a change order and an extension of time?

A change order approves scope and price; an extension of time approves the programme impact. Many changes require both, but agreeing the price does not automatically grant time, and granting time does not accept the price. The two decisions stay separate but linked to the same request.

### Can work proceed before a change is approved?

It can, where the contract or a site instruction gives the owner the right to require urgent work, but urgent execution is not price approval. Record the work as a site instruction linked to the change request, and keep the price open until approved, or the negotiation happens after execution with no reference.

### Who approves a change order?

The contract and authority matrix decide, not the size of the change alone. Typically the consultant approves the technical assessment, while the owner or delegate approves cost and time, with value thresholds moving the decision up a level. What matters is that the approver is identifiable in the record before work starts.

### How does a change order affect the programme?

Through a time-impact assessment that identifies the affected activity and whether it lies on the critical path — not through a global extension request at the end. A good record shows the cause, duration, and date of delay, which lets the extension be discussed with dates rather than estimates.

Change orders are not an exception managed on the margins; they are part of contract administration. Read the [construction document management guide](/en/blog/construction-document-management), the [approval chain](/en/blog/contractor-consultant-owner-approval-chain), or [book a working demo](https://calendly.com/yousuf-mutamad/30min) to review the change process on your project.

## Continue reading

- [Construction RFI Workflow: From Question to Closure](https://mutamad.net/en/blog/construction-rfi-workflow/)
- [Construction Submittals: MIR, SUB, NCR, COR Explained](https://mutamad.net/en/blog/construction-submittals-workflow/)

---

*Markdown mirror of a Mutamad blog post, intended for AI agents and crawlers. Full version: https://mutamad.net/en/blog/construction-change-order-workflow/*