2026 Guide to Construction Change Orders: Safeguarding Your Profits

A Change Order is the cleanest way a change gets paid. It's a signed contract amendment, not a handshake or an email chain.

Think of it like a bank wire. You need authorization (written direction), a reference number (a tracked ID), and a receipt (the signed Change Order). Missing any one of those three, and the money never lands.

Change (field change)

A real shift from the original scope. Added smoke dampers on a revised mechanical plan. A ceiling height change that forces rework. Something that wasn't in the documents you bid.

Claim

A demand for time and/or money under the contract, backed up with records, because the change was not in your bid price or schedule.

PCO and COR

PCO (Potential Change Order) is the tracked "maybe" with a unique ID. COR (Change Order Request) is the priced package you submit for approval: scope, cost, time impact, and backup.

CO and CCD

CO (Change Order) is the signed contract change. CCD (Construction Change Directive) is written direction to proceed before price is agreed. You convert it to a CO once cost and time are settled.

Who does what at each step

Every change document has exactly one party who creates it, one who reviews it, and one who approves it. Most changes stall or die because those roles are blurred. The table below maps every step from the field event through billing.

Figure: Field event → billed CO

Worked walkthrough: field event to billed SOV line

Say you're running a $2.4M tenant fit-out. On a Tuesday, the GC superintendent spots that the architect's revised reflected ceiling plan drops the ceiling height by 8 inches across 4,200 sq ft of open office. That forces the mechanical sub to reroute 320 linear feet of ductwork and add six fire dampers.

Day 1 (Tuesday). The GC superintendent logs the field event in the daily report with photos and tags the RFI response that triggered the ceiling change. The GC project engineer opens PCO-009 with $0 pricing and a scope narrative: "Includes: duct reroute, six fire dampers, revised hangers. Excludes: ceiling grid changes, controls reprogramming."

Day 2. The architect issues CCD-003 directing the GC to proceed so the schedule holds. The Owner signs it. No agreed price yet, so the mechanical sub starts T&M tracking under PCO-009's number. Every labor hour, material receipt, and equipment charge gets coded to PCO-009.

Day 5. The mechanical sub PM sends the GC a sub COR: $38,400 in labor and material, plus a 3-day time extension. The GC project manager reviews backup, adds GC general conditions impact ($4,200 for extended superintendent coverage over the weekend push) and the contractual markup (10% on sub work, $3,840, per AIA A201 §7.3.7 language in this contract). Total COR: $46,440 with a 3-day extension. The GC submits COR-009 to the architect and Owner's rep.

Day 12. The Owner approves. The architect issues CO-005 amending the contract sum by $46,440 and extending Substantial Completion (the point at which the Owner can occupy the space) by 3 days. Both the GC and Owner sign.

Month-end pay app. The GC project manager adds SOV line 22A "CO-005: Ceiling revision, duct reroute" to the Schedule of Values at $46,440. The work is 60% complete, so $27,864 appears on Pay App #4. The architect certifies, and the Owner pays (less retainage, the percentage held back until final completion).

In Archdesk, each PCO number works as a cost container: subcontractor quotes, T&M sheets, PO commitments, and the signed CO all attach to one record inside the change order management workflow. When the GC project manager builds Pay App #4, the $27,864 billed against CO-005 reconciles automatically against committed and actual cost, no manual spreadsheet lookup required.

The previous section covered the lifecycle of a single change: field change → PCO → COR → signed Change Order. That lifecycle assumes everyone agrees on cause, cost, and time. Not every field issue lands neatly in a Change Order. The first job is to figure out the commercial bucket: who pays, and how the cost gets accounted for. Get it right on Day 1 and you protect your margin. Get it wrong and you eat costs that belong to someone else.

Think of a restaurant bill. An upgrade costs more because you asked for it. A kitchen mistake gets comped because the restaurant caused it. A broken plate gets charged to whoever broke it. And if you get food poisoning and the restaurant won't cover the medical bill, you file a formal complaint. Same event at the table. Totally different outcome at the register. Each one is a different commercial bucket, not a different piece of paperwork.

Five commercial buckets: who pays, and how it's accounted for

These buckets describe the commercial reality, not the form you fill out. The form (a Field Work Order, a Change Directive, a Change Order, a Notice of Claim) is the paperwork instrument used to document and authorize the bucket. Name the bucket first. Then pick the right instrument.

Change Order (the bucket)

The Owner pays for new or changed scope. Both sides agree on cause, cost, and time before signing. Owner requests, design revisions (changes to drawings or specs after contract award), and RFI scope adds all land here when there's no dispute. The cost flows into the contract sum and gets billed on the next pay application (the monthly request for payment).

Backcharge

The party who caused the problem pays. A backcharge is a deduction for damage, rework, or cleanup caused by another trade or party. It's cost recovery, not added scope. You need documented notice and photos before you deduct a dollar.

Allowance

The Owner pays, but only if actual cost exceeds a pre-set dollar placeholder already in the contract, like "$15,000 allowance for door hardware." No new approval is needed until the reconciliation (the true-up of actual vs. budgeted cost) shows a variance above or below the allowance amount.

Contingency

The Owner or GC absorbs the cost from a set-aside budget held for unknowns. Spending contingency still needs written direction and coding to a specific scope event. It covers risk that was anticipated but not priced, like soil conditions within a known range.

Claim

The payer is disputed. A claim is a formal demand for additional money or time under the contract's dispute provisions when the other side says "no." Under AIA A201 §15.1 (depending on the edition and your contract's modifications), a claim generally must be initiated by written notice within a specified period (often 21 days) of the event. Under ConsensusDocs 200, the window is typically 14 days. Miss the notice deadline and you may forfeit the right in whole or in part, regardless of merit.

How to sort an issue into the right bucket

The sorting question isn't "what happened on site?" It's "who caused it, who should pay, and do both sides agree?" Walk through these three questions in order.

A claim is not a different kind of work. It's what a change order becomes when agreement fails. Say you hit concealed asbestos behind a demoed wall on a $1.2M tenant fit-out. You issue a PCO for $38,000 in abatement and two weeks of delay. If the Owner signs, the bucket is "change order." If the Owner argues the abatement report was in the bid documents and refuses to pay, the same $38,000 lands in the "claim" bucket the moment you file formal written notice.

Why the bucket matters, with a real cost consequence

Take a worked example: on that same $1.2M fit-out, a coordination clash triggers three days of T&M labor for two workers at $85/hour. That's roughly $4,080 before anyone agrees on cause or payer. If it turns out to be a backcharge or a GC-absorbed means-and-methods issue, that $4,080 comes straight out of fee.

Wrong-bucketing hurts even more on claims. That $38,000 asbestos PCO, if you miss the contractual notice window, doesn't just stay disputed. It may become impossible to recover, depending on the contract and applicable law. You eat the full $38,000 plus the schedule cost. On a two-week slip with $6,200/week in prelims (site-level overhead like supervision, welfare, and temp power), that's another $12,400 gone.

Next, we'll pick the paperwork instrument, the Field Work Order, Construction Change Directive, Change Order, or Notice of Claim, that documents and authorizes the bucket you've just named.

You know the four commercial buckets and the rule: name the payer on Day 1. This story shows what goes wrong when work starts before the change has a number, a scope, or a paper trail.

Situation

A 45-person GC in central Texas, roughly $40M annual revenue, mostly healthcare fit-outs. The project was a $25M outpatient surgery center inside a live hospital campus under AIA A201. Fourteen-month schedule, monthly pay apps with an SOV and 10% retainage.

Week 14 had a hard constraint: the Owner needed a wing open for a licensing inspection. Night shifts were already baked in, so float was close to zero.

What happened

Week 6, the mechanical sub found an above-ceiling coordination clash in a 12-foot corridor run above a 9-foot finished ceiling. A new med-gas zone valve box sat right where the duct main was drawn, and the structural steel was lower than the model showed. The only buildable fix: revised duct routing plus new hangers and seismic bracing.

Day 1, the superintendent gave a verbal "keep going, we can't stop the floor." The sub started that same shift on T&M and burned 160 labor hours over three days. No COR went to the Owner. No change cost code was opened. The time hit the base "HVAC rough-in" code.

Day 14, the PM finally sent a COR for $180k and 8 calendar days. Backup was thin: a few photos, but no marked-up plan, no before-and-after sketch, no clean tie to an RFI response or revised sheet. The Owner's rep came back in writing: "Means and methods. You should have coordinated above-ceiling." They offered $90k, zero days, and asked the GC to waive "impact costs."

Week 8 pay app, the mechanical sub billed the rework inside their normal progress line because that's where the labor had been coded. The GC paid it to keep the schedule and the relationship intact. The project now carried $180k of real cost, but the change still had no signed Change Order and no agreed story.

The decision / the lesson

The GC stopped arguing and rebuilt the record in 48 hours. They produced a one-page narrative, a ceiling conflict sketch, dated photos, and a labor log split by foreman and journeyman. Then they moved the already-booked hours and materials into a dedicated change cost code so the overrun stopped looking like base-scope blowout.

The turning point was making the scope measurable. The COR was rewritten from "reroute duct" to "add 84 linear feet of 24x18 duct, add 26 hangers, add 12 seismic braces, demo and reinstall 18 ceiling tiles for access." Pricing became checkable. The Owner had less room to call it "means and methods."

They still took a hit. The final signed Change Order landed at $140k and 3 days. The unrecovered $40k traces back to two control failures you can spot early: no written direction inside 72 hours, and letting labor and material disappear into base cost codes before the change had an ID and a defined scope. In Archdesk, that discipline maps to change order management, where a PCO can be opened the same day so T&M tickets, quotes, and cost entries stay in a separate container instead of contaminating the base budget.

The decision tree tells you which document to reach for and how fast to move. This section locks in the weekly rhythm that keeps every open item moving from PCO to signed CO, with the dollars landing on the next pay app, not drifting into a reconciliation mess three months later. One cadence, three hard gates: same-day notice logged, 72-hour change pack issued, pricing submitted or escalated within seven days.

30-minute change huddle agenda

Pin this to the same day and time every week. No slides. Tracker on a screen, the right people in the room: PM, superintendent, project engineer, lead estimator.

Required tracker fields, defined

• Change ID, a unique sequential number (e.g., PCO-027). Don't reuse numbers, and avoid skipping them. If you do skip one, note the reason in the log so your audit trail stays clean.
• Source, what triggered the change: Owner request, RFI, or concealed condition (something hidden that only showed up once work started).
• Instrument, the document stage from the decision tree in the previous section: PCO, COR (Change Order Request, the formal ask with pricing), CCD, or CO.
• Status, one of five states only: Draft, Submitted, Under Review, Approved, Rejected.
• $ ROM, Rough Order of Magnitude. Your best guess within 48 hours, accurate to ±30%. Think of it as an early weather forecast: useful for planning even though it'll sharpen later.
• Forecast final, the number you expect on the signed CO after sub quotes, markups, and schedule impact land. This replaces the ROM once real pricing is in hand.
• Days open, calendar days since the PCO was logged. Over 14 days is aging. Over 30 is a problem.
• Next action owner, one person's name, not a company or role. "John Torres, sub quote due 6/12" beats "waiting on HVAC sub."

Escalation email template

Copy and send this the same day any item trips a trigger: over $25k, touches Substantial Completion (the contractual milestone when the Owner can occupy the building), or requires long-lead material (anything with a procurement lead time beyond 6 weeks).

Action checklist

• Publish three service levels on every job: log same-day, issue the 72-hour change pack, submit pricing or escalate by Day 7.
• Run one tracker only, with all eight required fields locked: Change ID, source, instrument, status, $ ROM, forecast final, days open, next action owner.
• Write a two-sentence scope stub on Day 1 for every item: "what changed" and "what stays in base scope."
• Hold the 30-minute weekly change huddle using the four-segment agenda above. End by reading back every assigned action aloud.
• Send the escalation email the same day any item trips a trigger: over $25k, touches Substantial Completion, or needs long-lead material.
• Reserve an SOV line for each approved Change Order before the next pay app. "Approved" doesn't mean "billable" until the SOV line exists.
• Track retainage (the percentage the Owner withholds from each payment until project end) on change value, not just the base contract. A $60k CO with 10% retainage is $6k you won't see until release. Your cost controls need to show that holdback the same week the CO is signed.
• Give every change its own cost code before any cost hits. In Archdesk this sits inside change order management, so T&M tickets, sub quotes, and PO commitments stay isolated and your weekly cost view doesn't bury change spend inside base scope.

What to learn next

• Time Impact Analysis (TIA): schedule fights get won on logic and critical-path proof, not on "we lost days" stories. Learn how to model delay before you argue it.
• Retainage mechanics and release triggers: approved changes can still leave you cash-tight for months on AIA A201 jobs with 10% retainage. Understand when and how that money comes back.
• Pay apps and SOV coding discipline: a signed Change Order still misses payment if it isn't slotted, coded, and billed on the right line before cutoff. Tighten the last mile.

That central Texas outpatient surgery center only leaked $180k because the team worked in the gaps between field direction, paperwork, and cost coding. Close those gaps every week and change control becomes routine operating discipline, the same as weekly safety walks and lookaheads. Your margin stops depending on someone's memory at final account.