Documenting change order quantities so they get paid
How to build a defensible change order quantity package: baseline versus revised measurement, plan references, marked-up sheets and the delta shown clearly.
5 min read
Key takeaways
- A change order needs a baseline quantity, not just a new one.
- Show the delta as measured-then versus measured-now with both references.
- Marked-up sheets from both revisions end most disputes quickly.
- Archived bid-day takeoffs are what make this possible at all.
Change orders are won or lost on documentation, not on whether the extra work happened. The owner is not disputing that you installed 340 more feet of pipe; they are disputing that it was not in the original scope. Proving that requires the original scope in measurable form.
The three-part package
| Part | Contains | Purpose |
|---|---|---|
| Baseline | Bid-day quantity, sheet and revision | Establishes what was priced |
| Revised | Current quantity, sheet and revision | Establishes what is required now |
| Delta | Difference, with unit and derivation | The claim itself |
Each part needs a marked-up sheet. Two drawings side by side, each with the traced measurement visible, make the change self-evident in a way that a table of numbers never does.
What makes a delta defensible
- Both quantities measured with the same condition definition and unit.
- Both measured at a verified scale, stated on the package.
- The plan revision cited for each, with dates.
- The specific drawing change identified — cloud, note, addendum number.
- Derived quantities recomputed from the same factors as the bid.
Changing the condition definition between baseline and revised invalidates the comparison. If the bid measured curb to face-of-curb, the revised measurement must too, even if you now prefer back-of-curb.
Common weak claims and why they fail
- "The quantity increased" with no baseline reference — unverifiable.
- A field-measured revised quantity against a plan-measured baseline — different bases.
- A delta computed after the factors changed — mixes scope change with estimating change.
- A quantity from a sheet revision that predates the bid — that was already priced.
- A claim with no marked-up sheets — puts the burden of proof on the reviewer, who will decline.
The archive is the prerequisite
None of this works retroactively. If the bid-day takeoff was overwritten, or lived in a spreadsheet that has since been edited, there is no baseline to point at. That is why archiving the frozen takeoff with its plan revision at submission time is worth the two minutes: it is the difference between a change order that gets approved on the first submission and one that becomes a negotiation.
Contractors with clean quantity records tend to submit fewer change orders and get more of them approved — because the ones they submit are documented well enough that there is nothing to argue about.
Doing this work in TakeoffAI? Versioned quantities.
Related guides
Handling addenda and revised sheets without redoing the takeoff
A method for absorbing addenda late in a bid: comparing sheet lists, isolating affected conditions, re-measuring selectively and reissuing sub packages.
5 min readPricing & reportingExportable estimate reports owners and subs can actually use
What to include in exported takeoff and estimate reports: scope breakdowns, marked-up sheets, assumptions, exclusions and formats that travel well.
5 min readPricing & reportingFrom takeoff to bid: a workflow that holds up on bid day
A step-by-step civil bid workflow from plan intake through quantity handoff, pricing, review and submission, with the checkpoints that prevent bid-day scrambles.
6 min read