The Construction Change Order Process: How to Maintain One Source of Truth

What a change order actually is

A construction change order is a written modification to the original contract — it adjusts scope, price, schedule, or all three. It becomes part of the contract the moment it's signed by the owner, the contractor, and (where applicable) the design team.

The document itself is simple. The process is not: a single change can touch estimating, procurement, the field schedule, subcontractor commitments, the billing SOV, and the owner's project budget. Every one of those systems has to move together or the project loses its single source of truth.

The three types you'll actually see

• Owner-directed. Scope added, changed, or removed by the owner. Priced against the contract's unit rates or lump sum, then approved.
• Constructive. The owner or design team does something (or fails to) that materially changes the work — differing site conditions, delayed decisions, defective drawings. Documented as a change even without an explicit direction.
• Contractor-initiated. Value engineering, substitutions, or field-detected coordination issues that the contractor proposes and the owner approves.

The six-stage lifecycle

Every change — regardless of type — runs through the same six stages. The friction shows up in the handoffs between them.

1. Trigger. RFI response, field condition, owner directive, or design revision.
2. Scope capture. Written narrative of the added, changed, or deleted work — with references to drawings and specs.
3. Pricing. Labor, material, equipment, subcontractor quotes, overhead, and fee — priced against the contract's markup rules.
4. Time impact. Schedule analysis: is this a critical-path activity? How many days? Concurrent delay?
5. Approval. PCO → CO. Owner sign-off, design review where required, and internal cost engineer approval.
6. Execution. Budget updated, schedule updated, subcontractor change orders issued, billing SOV amended.

Why one write matters

In most stacks, executing an approved change order is not one action — it's five. Someone updates the budget in the accounting system. Someone else redlines the schedule. A third person cuts a subcontractor CO. A fourth amends the SOV in the pay app. A fifth (if you're lucky) files the signed document.

Every one of those steps is a chance for the numbers to disagree. The owner's budget report says one thing, the schedule says another, the sub believes a third, and the next pay app catches it — badly.

The one write discipline: when a change order is approved, the same record updates the budget, schedule, subcontractor commitments, and billing in a single transaction. There is only one version of "what changed" — and it's the signed one.

Six pitfalls that quietly drain margin

• Work-before-signature. Field crews execute on a verbal directive. If the CO is later denied or negotiated down, the labor is unrecoverable.
• Cumulative impact ignored. Each CO priced in isolation. The compounded schedule and productivity impact is never claimed.
• Sub CO lag. Owner CO signed; subcontractor commitment isn't updated. The next sub pay app doesn't match.
• SOV drift. The billing schedule of values is amended by hand and stops reconciling to the contract sum.
• Contingency invisibility. Contingency is drawn down on internal spreadsheets. The owner report shows the wrong remaining balance.
• Lost paper trail. The signed PDF lives in someone's inbox. Six months later, no one can prove what was approved.

The pre-signature checklist

Before any change order is routed for signature, confirm each of the following. If any answer is "no", the change is not ready — regardless of schedule pressure.

• Scope narrative references the specific drawing revisions, RFIs, or directives that triggered it.
• All labor, material, equipment, and sub pricing is attached and matches the contract's markup rules.
• Time impact analysis is present — even if the answer is zero days.
• Subcontractor change orders are drafted and ready to issue on approval.
• Budget line, contingency drawdown, and SOV amendment are prepared, not deferred.
• The signature block matches contract requirements (owner, contractor, and A/E where applicable).

Change order template — fields

A defensible construction change order captures the same fields every time. Use this as the schema for your CO form, whether it lives in your platform or a PDF template.

• Header. Project, contract number, CO number, date, prior CO total, revised contract sum.
• Trigger reference. RFI, directive, ASI, bulletin, or field condition ID.
• Scope of change. Added, changed, or deleted work — in plain language, with drawing/spec references.
• Cost breakdown. Labor, material, equipment, subcontractors, overhead, fee, and taxes — each on its own line.
• Time impact. Days added to contract completion, critical-path analysis, and revised substantial completion date.
• Signatures. Owner, contractor, architect/engineer as required by the prime contract.