Change Orders: How to Document Scope Changes Without Disputes

No construction project finishes exactly as drawn. Owners change their minds, field conditions surprise everyone, materials get substituted, weather intervenes. The question is never whether the scope will change — it is whether each change gets documented before the work happens. A change order is the tool for that: a written, signed amendment recording what changed in the scope, the price, and the schedule. Projects that use them consistently rarely end in payment fights. Projects that run on verbal go-aheads often do.

What a change order actually is

A change order is a mini-contract layered on the original one. Once signed by both parties, it amends the agreement itself: the contract sum becomes the new sum, the completion date becomes the new date, and the described work is officially in (or out of) scope. That is also why most construction contracts require changes to be authorized in a signed writing — and why courts take those requirements seriously, with exceptions that vary by state.

What every change order should contain

• A reference to the original contract — parties, date, project — and a sequential change-order number.
• A clear description of the change: what work is added, removed, or modified, specific enough that a stranger could price it.
• The reason for the change — owner request, concealed condition, design revision, code requirement.
• The cost impact: the amount added or deducted, and the new total contract sum after this change.
• The schedule impact: days added to (or removed from) the completion date, even if the answer is zero — silence invites arguments later.
• Signatures from someone authorized on each side, dated before the changed work begins.

The process that prevents disputes

1. Identify and notify. When a potential change surfaces, flag it in writing right away — many contracts set notice deadlines for claiming extra costs, and missing them can waive the claim.
2. Price it before doing it. Prepare the description, cost, and time impact as a proposed change order. If pricing must be time-and-materials, agree in writing on rates and a not-to-exceed figure first.
3. Get signatures before mobilizing. This is the discipline that decides everything. Work performed on a handshake is work you may argue about forever.
4. Log it. Keep a running change-order log — numbers, status, amounts, cumulative total — reconciled against every pay application.
5. Bill it visibly. Carry approved change orders as their own lines on the schedule of values so payment and paperwork stay in sync.

Pricing a change order

Most changes are priced one of three ways. A lump sum fixes the cost of the change up front — cleanest for everyone when the work is well defined. Time and materials bills actual labor and material costs, usually at rates listed in the contract, and works when the extent of the work is genuinely unknowable in advance; pair it with a not-to-exceed cap so the number cannot run away. Unit prices apply pre-agreed rates to measured quantities — common for earthwork and repetitive scope. Whichever method applies, check what the contract says about markup: many agreements cap the overhead and profit a contractor may add to change-order work, and some cap the markup a GC may add on top of a sub's change. Pricing disputes are much easier to avoid when the method and the markup were agreed before the work.

When the other side says 'just do it, we'll paper it later'

Sometimes the schedule genuinely cannot wait for paperwork. Many contracts anticipate this with a construction change directive or field order: the owner can direct the work to proceed while price and time get resolved afterward, through an agreed process. If your contract has that mechanism, use it — it preserves your claim. If it does not, at minimum send a same-day written confirmation ('per our conversation, you directed us to…, we will proceed and submit a change order for the cost and time impact'). An unanswered contemporaneous email is far better evidence than a memory.

Watch the cumulative picture

Individual change orders can each look reasonable while the project drifts badly. Track the cumulative effect: the total contract sum, the total days added, and the pace of change relative to progress. A project that is 30% complete with forty change orders has a scope-definition problem no individual form will fix — that conversation should happen at the project level, early.

The owner's side of the same discipline

Everything above protects owners too. A written change order is how an owner knows what a change costs before authorizing it, keeps the contract sum reconciled against the budget, and prevents end-of-job surprise invoices for work nobody remembers approving. Owners should insist that no changed work proceeds without their signature, that deductive changes (work removed from scope) get papered just as promptly as additions, and that the change-order log is reviewed at every pay application. The form is mutual protection, not a contractor's tool.

Habits that hold up later

• Photograph and document conditions before and after changed work.
• Use consistent numbering and never reuse a number, even for voided change orders.
• State schedule impact on every change order, including 'no change to contract time.'
• Reconcile the change-order log against every pay application before submitting it.
• Check who has authority to sign — a change order signed by someone without authority may bind no one. Requirements and exceptions vary by state.

None of this is exotic. It is the same rule applied over and over: get the change in writing, signed, before the work. This guide is general information, not legal advice — for a live dispute over unpaid changed work, talk to a construction attorney in your jurisdiction.