Change Order Management: Stop Doing Work You Won't Get Paid For

What actually counts as a change

A change is any deviation from the scope, schedule, or conditions you priced in your contract. That includes the obvious things — an owner adds a wall, a design revision lands, a spec gets upgraded — but it also includes the quiet ones: a differing site condition you hit while excavating, an RFI answer that adds work, an out-of-sequence directive that hurts your productivity, or an acceleration request to make up time.

The trap is that a lot of changes do not arrive labeled as changes. They show up as a casual instruction from the superintendent, a redline on a drawing, or a one-line answer to an RFI. If you treat those as just part of the job, you have agreed to do the work for free. The first discipline of change management is recognizing a change the moment it occurs and flagging it.

The change lifecycle, step by step

A clean change moves through a predictable sequence. Skip a step and you create either a dispute or a write-off:

• •Event: something changes — a directive, an RFI answer, a field condition, a design revision. Note the date, who directed it, and what triggered it.
• •Notice: most contracts require written notice within a set number of days (often 7, 14, or 21). Blowing the notice deadline can waive your right to recover, even when the change is legitimate.
• •PCO (potential change order): you price the impact — labor, material, equipment, subs, markup, and any schedule or productivity effect — and submit it for review.
• •Negotiation and approval: the owner or GC reviews, negotiates, and either issues a formal change order adjusting the contract sum and time, or rejects it.
• •Execution and billing: only after approval do you build it, and the new value flows into your schedule of values so it shows up on the next pay application.

Why doing the work first is so dangerous

The most expensive words in construction are "just go ahead, we'll sort the paperwork later." Once the work is in place, your leverage is gone. The owner has the wall, the upgraded fixture, the extra footing — and now you are negotiating from behind, trying to prove what something cost after the fact instead of agreeing on a price before anyone swung a hammer.

There is one legitimate exception: a Construction Change Directive (CCD) or a documented emergency where stopping is not an option. In those cases you proceed under written direction and track every hour and every dollar on time-and-material tickets, signed daily by the owner's rep, so the eventual price is defensible. That is very different from doing changed work on a handshake and hoping.

The rule of thumb is simple. If a change is small and obviously approvable, get the signature anyway — it takes minutes. If a change is large, the price is exactly why you must agree before you build, not after.

Pricing methods: lump sum, unit price, and T&M

How you price a change depends on how well you can define it before the work happens:

• •Lump sum: a single fixed price for fully defined scope. Best when the change is clear and you can estimate it confidently. You carry the risk if you underbid it, so build it like a mini-estimate with real quantities and a margin you can defend line by line.
• •Unit price: a price per unit (per cubic yard, per linear foot, per fixture) when the type of work is known but the quantity is not. The owner pays for the actual installed quantity. Ideal for added excavation, additional rebar, or repetitive scope.
• •Time and material (T&M): you bill actual labor, material, and equipment plus agreed markups. Used when scope cannot be defined up front, often for emergency or investigative work. T&M lives and dies on daily signed tickets — without them, the cost is unprovable.

Track the cumulative impact, not just each change

Individual changes are easy to track. The number that gets lost is the running total. Your original contract sum plus every approved change equals your current contract sum, and that revised number is what your budget, your schedule of values, and your final billing all have to reconcile against. Lose track of it and your pay applications stop tying out.

Tie every change back to its source, too. When an RFI answer creates added work, link the resulting change to that RFI so the paper trail is unbroken from question to answer to PCO to approved CO. In Field PM, RFIs and change orders live in the same workflow, so a CO carries its originating RFI with it and the approved value flows straight into job costing and the schedule of values — no double entry, and nothing falls through the cracks between the field and the back office.

The contractors who get paid for changes are not the ones with the best arguments at closeout. They are the ones whose documentation makes the change undeniable: dated notice, priced PCO, signed approval, and a contract sum that everyone agrees on at every step.