A construction change order is a written amendment to the contract that adjusts scope, cost or schedule, and it only becomes binding once the owner and contractor sign it. The single workflow that keeps this process under control runs in five stages: request, assess, approve, document and reconcile. Skip any one of them and you risk disputed payments or unrecoverable costs.
TL;DR:
- Most delays in change order processing stem from signature routing issues rather than estimation or drafting time.
- A standardized approval matrix and single referencing system can significantly reduce approval bottlenecks and disputes.
- Only the owner and contractor can sign and enforce a change order, while architects and engineers advise and document but cannot approve amendments.
- Proper documentation should include detailed scope, cost breakdown, schedule impact, and signatures, with supporting evidence stored alongside revisions.
- Proactive scope definition, clear approval thresholds, and mapped workflows can prevent many change orders and accelerate approval timelines.
Table of Contents
- How the change order lifecycle actually flows
- The step-by-step change order process you can copy
- Who signs, who advises, and who just documents
- What a complete change order document needs to contain
- Reducing avoidable change orders before they happen
- Measuring your workflow and shortening approval time
- A governance-first example worth borrowing
- Why governance failures keep repeating on site
- How Videra supports mapped, auditable change order workflows
- Sources
- FAQ
How the change order lifecycle actually flows
Every change order starts somewhere, and spotting the trigger early is what separates a smooth approval from a stalled one. The common triggers are:
- Unforeseen site conditions discovered once work begins
- Owner-initiated changes to scope, finishes or programme
- Design clarifications that alter what was originally drawn
- Regulatory or code changes affecting compliance
- Material or equipment substitutions
Once a trigger appears, the workflow moves through fixed stages: trigger, request or proposal, estimate and schedule impact, approval routing, execution, payment reconciliation, and close-out. Each stage has a decision gate, and each gate has an owner. The project manager or architect typically screens the initial request, the commercial lead assesses cost and time impact, and the owner or their delegate holds final sign-off authority above a set value threshold. Below that threshold, a project manager or superintendent may approve directly, provided the contract allows it.
The gates matter more than the stages themselves. A change order that skips the approval gate and proceeds on a verbal instruction is the single most common source of payment disputes later in the project.
Pro Tip: Map your approval matrix before the project starts, not after the first disputed invoice arrives.
The step-by-step change order process you can copy
This is the sequence a project manager can lift directly into their own project controls system. It assumes a standard private or commercial contract using forms similar to the AIA's change order guidance, which treats the change order as a formal contract amendment rather than an informal instruction.
- Capture the trigger. Log the date, a unique reference number, photos and any field ticket the moment the issue is identified.
- Prepare the request or proposal. Write a concise scope description and cite the relevant contract clause or drawing reference.
- Estimate cost and schedule impact. Break the cost down by labour, materials, plant, overhead and fee, then update the Schedule of Values to reflect the change.
- Route for approval. Use a defined approval matrix and obtain signatures before work proceeds, except where a formal construction change directive authorises interim work.
- Update drawings and documentation. Revise drawing revision blocks and confirm the document control index reflects the new version.
- Reconcile payment. Align the change order with the updated Schedule of Values, add the payment line item, and confirm the final reconciled amount at close-out.
A few habits make this sequence reliable rather than aspirational:
- Never let field work start on a change without at least a preliminary written estimate.
- Assign one reference number that follows the change order from request through to the final payment application.
- File supporting evidence, photos, RFIs and field tickets, against that same reference number.
The FHWA's review of change-order processing found that delays cluster overwhelmingly around signature routing rather than estimation or drafting, which is why step four deserves more attention than most teams give it.
Who signs, who advises, and who just documents
Ambiguity over authority is what turns a routine change into a dispute. Only the owner and contractor can approve a binding contract modification: their signatures are what make the change enforceable. The AIA's guidance on change order fundamentals is explicit that architects and engineers advise and document but cannot bind cost or schedule changes without the owner's written consent.
- Owner and contractor: the only parties who can sign and bind a change to the contract.
- Architect or engineer: documents the change, recommends a course of action, and prepares supporting paperwork.
- Project manager: packages the request, routes it for approval, tracks status and archives the record.
- Commercial lead or quantity surveyor: negotiates and verifies the cost breakdown.
- Field staff: document conditions and instructions but never sign or authorise a change themselves.
Verbal directives are the biggest source of confusion on site. Nominate one named approver for verbal instructions, and require that person to confirm in writing within 24 hours.
Pro Tip: Publish your approval matrix on the site noticeboard, not just in the project management system nobody opens under deadline pressure.
What a complete change order document needs to contain
An incomplete change order slows every downstream approval, so it pays to standardise the fields from day one. A workable template needs the following:
| Field | Purpose |
|---|---|
| Project ID and change reference | Unique identifier linking the change to payment and Schedule of Values |
| Description of work | Plain scope statement, no ambiguity |
| Drawing and specification references | Ties the change to the exact document it alters |
| Reason for change | Supports justification and, on federally funded work, eligibility review |
| Cost breakdown | Labour, materials, plant, overhead and fee, itemised |
| Schedule impact | Days added or removed, tied to the master programme |
| Schedule of Values and cost codes | Keeps payment lines traceable to the change |
| Signatures and dates | Owner and contractor, the only binding step |
- Attach supporting evidence: photos, RFIs and field tickets referenced by the same change order number.
- Keep a revision block on every affected drawing, with the document control index updated the same day.
- Archive the signed change order alongside its Schedule of Values update, not in a separate folder.
Good document control practice treats the revision history as part of the audit trail, not an afterthought filed at project close-out.
Reducing avoidable change orders before they happen
Most change orders are preventable, and the fix starts long before the first shovel hits the ground. A 1996 study using the Project Definition Rating Index found that projects scoring below 300 on scope definition averaged 18% of budget in change orders, while those scoring above 300 averaged 119%: a stark gap that traces directly back to how well scope was defined before construction began.
- Run a PDRI or equivalent scope-definition exercise during preconstruction, not after mobilisation.
- Set contingency allowances based on realistic risk, not a flat percentage carried from the last project.
- Standardise change order forms and routing across every project so approvers know exactly what to expect.
- Require a preliminary cost estimate before any field work proceeds on a suspected change.
- Keep a payment-tied log where the change order, Schedule of Values update and payment line share one identifier.
- Train site teams on approval thresholds and insist on written confirmation for anything that touches cost or schedule.
Pro Tip: Treat scope definition as a budget line item, not a formality. It's the cheapest insurance on the project.
Better risk management in preconstruction consistently reduces the volume of changes that reach the approval stage at all.
Measuring your workflow and shortening approval time
Tracking a small set of metrics tells you exactly where your process is losing time. Average approval time, the percentage of contract value consumed by change orders, average cost impact per change, and the number of changes per 1,000 work hours are the four worth watching monthly.
| Benchmark | Figure |
|---|---|
| Average total change order processing time | About nine working days (FHWA review) |
| Share processed within five working days | 60% (FHWA review) |
The FHWA's review of 159 change orders traced most of the variance in that nine-day average to signature delays at higher approval levels, not to estimating or drafting time. If your own numbers run longer, the bottleneck is almost certainly routing, not paperwork.
- Run a short root-cause analysis on your five slowest approvals from the last quarter.
- Set a 30, 60, 90 day experiment: target the single longest approval leg and measure whether a revised routing rule shortens it.
This kind of bottleneck diagnosis works whether you run it manually or through a workflow platform.
A governance-first example worth borrowing
Mapped workflows work because they force every change order, Schedule of Values line and payment entry to share a single traceable identifier, closing the gap where disputes usually start. Keystone's own Pareto-based procurement approval workflow applied this principle to internal approvals and cut administrative time by 40%, according to internal data, by focusing routing rules on the small number of approval steps causing most of the delay.
- Assign one identifier per change from request through to final payment reconciliation.
- Route by exception, escalating only the changes that breach a defined threshold.
- Capture evidence, photos, signatures, cost breakdowns, at the point of approval, not after the fact.
You can apply the same logic with a spreadsheet and a disciplined numbering convention. A platform simply removes the manual chasing.
Why governance failures keep repeating on site
The recurring problem isn't missing paperwork, it's verbal approvals nobody writes down until the invoice dispute. Two fixes worth testing this week: name one verbal-directive approver per site, and refuse payment applications that don't cite a signed change order reference.
— Peter
How Videra supports mapped, auditable change order workflows
Chasing signatures across e-mail threads and spreadsheets is exactly the kind of admin that a mapped workflow removes. Videra Construction maps your change order stages into a stage-gated workflow, routes each request to the correct approver automatically, and keeps every cost breakdown, signature and drawing revision tied to one auditable record.
- Routing rules mirror your approval matrix, so nothing reaches an owner before it has cleared the right internal checks.
- Every change order links automatically to its Schedule of Values update and payment line, closing the gap where disputes usually start.
- Reporting is audit-ready by default, which matters when a funder or client asks for the full change history at handover.
If your current process relies on someone remembering to chase a signature, a diagnostic conversation with Keystone's consultancy team is a practical next step, or you can look at the Videra Construction page directly to see how the workflow maps to your own project structure.
Sources
- PDRI assessment (1996) — scope definition and project outcomes
- The fundamentals of change orders in construction — AIA Contracts Learning
FAQ
What are the steps involved in the construction change order process?
The process runs from trigger through request, cost and schedule estimation, approval routing, execution, and payment reconciliation. Each step needs a clear owner and a written record, since the FHWA's review found most delays occur at the approval routing stage rather than in drafting or estimating.
Can you provide an example of a change order in construction?
A typical example is a request to substitute a specified material after a supply shortage, with an itemised cost breakdown for labour, materials and plant, a schedule impact statement, and signatures from both the owner and contractor. The AIA's change order guidance treats this kind of document as a formal contract amendment rather than a site instruction.
What is the difference between a PO and a change order?
A purchase order authorises a specific purchase against an existing budget line, while a change order formally amends the construction contract itself, adjusting scope, cost or schedule. Only the owner and contractor can approve a change order, whereas a purchase order can often be issued by a procurement or commercial role.
What is a PCI in construction change order workflows?
A PCI, or potential change item, is a preliminary flag raised when a possible change is identified but before cost and schedule impact have been assessed or approved. It becomes a formal change order only once it passes through estimation and approval, following the same request-to-approval sequence described in the AIA's fundamentals guidance.