If I lose control of change orders, I lose control of the job. For owners, the fix is simple in concept: lock down the contract, force written notice, require cost backup, test every time claim, and never let field direction change the deal.
Here’s the whole playbook in plain English:
What this means for me is straightforward: good change-order control is not about stopping every change. It is about stopping scope creep, thin backup, late claims, and time extensions without proof.
A few rules carry most of the load:
If I apply those rules the same way every time, I keep more control over budget, milestones, contingency, and claim risk.
Scope creep almost never shows up as one giant surprise. More often, it piles up through small calls made over time - a late user request here, a coordination miss there - until the contract price no longer matches the work in the field.
One of the biggest traps is the reasonably inferable issue. A contractor may charge for items that are not shown on the drawings but are still needed for a working system, like wiring or backing.[1] That puts pressure on the owner to spell out what is included before the contractor prices the gap.
Coordination problems make this even harder. If mechanical ducts run into fire sprinkler piping, the fix can turn into a priced change, and the owner often pays for it. On GMP jobs, margin may be buried in loaded labor rates and material pricing before markup is added.[1]
Once unclear scope starts pushing costs up, the contract becomes the owner's first line of defense.
Schedule risk from change orders is easy to miss because it often hits sideways. One change can break the planned sequence, stall downstream trades, and force crews to come back later.
On mission-critical projects, less float means a change on the critical path can lead to a time extension, acceleration, or both.[1] At that point, the owner is no longer just talking about cost. Now time is on the table too.
There's another risk here. If an owner rejects a valid time extension and doesn't have the records to back that up, the contractor may claim constructive acceleration. In plain English, the contractor adds labor to make up lost time, then comes back and charges the owner for being forced to do it.[1]
Also pay close attention to RFIs that start as technical questions and slowly turn into direction requests. That's often a sign that the file is being built for a claim, not just to fix a jobsite issue.[1]
When float gets thin, tighter notice rules and approval steps matter a lot more.
Weak documentation can wipe out owner leverage in a hurry. Once work starts based on verbal direction, pricing and scope control start slipping away.[1] And if the backup is thin or missing, it becomes much harder to challenge the scope, the price, or the claimed delay.
"Never - not once - allow work to proceed without your written authorization. Give in once and you open the floodgates." - DeVore Consulting [1]
That isn't just tough talk. Verbal direction can turn unapproved work into a direct project loss.
The same thing happens when owners accept lump-sum change order pricing without line-item backup. Without that detail, there is no clean way to separate base cost, markups, or schedule-related cost.[1]
That's why each change needs a clear intake process, pricing support, and an approval path on paper.
These risks are controlled first through contract terms, then through disciplined review.
Contract language is the owner's first line of defense against change-order drift. On mission-critical projects, weak terms can turn scope changes into lost money and lost time fast. Design changes, plus errors and omissions, account for 56.5% of cost overruns and 40% of delays [2]. That’s why the contract has to do more than describe the job. It has to spell out the rules the owner will use when changes show up.
A tight notice clause gives the owner real leverage. The contract should require the contractor to provide written notice within 7 to 14 days after spotting a potential change. It should also say, in plain terms, that if the contractor misses that deadline, it gives up the right to extra money or extra time.
That kind of deadline matters. If the notice rule is fuzzy, contractors can bring claims months later, when memories are thin, records are spotty, and the owner has little chance to confirm what happened in the field.
The contract should also make one thing crystal clear: only the named owner representative can approve changes to scope, cost, or schedule. Field talks, casual emails, and verbal direction should not bind the owner.
A Construction Change Directive (CCD) gives the owner another useful tool. It allows work to keep moving while pricing is still being worked out. That helps avoid project slowdowns without giving up control over cost.
The contract should block lump-sum change order proposals. Instead, require itemized pricing for labor, materials, and equipment, backed by invoices and agreed rates. If a subcontractor is involved, the general contractor should pass through the subcontractor’s original backup documents, not just a rolled-up summary. That makes it much harder to hide markups inside the sub’s base number.
It also helps to lock in labor rates and unit prices during the bidding phase, when pricing pressure is at its highest. For common unforeseen conditions, like rock excavation or contaminated soil, the contract should include pre-set unit prices. That cuts down on the chance of inflated mid-project pricing.
Many colleges and universities cap total markup at 10%, with a separate 5% cap on subcontractor work [2]. An owner can use that same approach to keep pricing from drifting.
The contract should also include an explicit right to audit clause. That gives the owner the power to check claimed costs against canceled checks and supplier invoices instead of taking list prices at face value.
If a change order request affects time, the contractor should have to submit a Time Impact Analysis (TIA) tied to the current schedule update. A broad claim that the change added time is not enough. The TIA needs to show where the change hits the critical path and what it does to float.
Without that proof, the owner is left guessing. And that’s where padded time claims can slip through.
The contract should also set minimum documentation standards up front. At a minimum, require:
Those records let the owner test both entitlement and cost against what took place on the project, instead of relying on the contractor’s version of events.
Weather claims need the same level of detail. The contract should define the expected weather baseline using NOAA 10-year average data for the project location. Time extensions should apply only to days that go beyond that stated baseline.
Once these rules are in the contract, the owner has a much stronger hand during review, approval, and dispute control.
Change Order Review Workflow: Owner's Step-by-Step Defense Process
Contract language only matters if owners use it the same way every time. This workflow turns notice, pricing, and document rules into day-to-day control. Instead of relying on one person's judgment in the moment, it gives you a system for budget, schedule, and leverage decisions.
Every possible change should come in through one intake form and get logged right away. That log is your audit trail. Each entry should include the date received, the contractor who sent it, the change category, and the claimed cost and time exposure. One intake point helps limit scope creep, and clear routing keeps budget and schedule calls from drifting.
Triage should sort each item into one of three buckets: owner scope, unforeseen conditions, or design errors. That label shapes who pays and how much review the item needs. From there, route the change based on dollar amount and risk. Your construction manager (CM) should handle scope definition and tracking, your project manager (PM) should watch the budget, an estimator should check cost, and a scheduler should review any claimed effect on the critical path.
Use this matrix to route changes by risk, backup, and review depth.
| Change Type | Typical Risks | Required Documentation | Recommended Review Depth |
|---|---|---|---|
| Design Revisions (E&O) | Betterment vs. waste disputes; coordination clashes | RFI history, original vs. revised drawings, architect and PE validation | High: Requires architect and PE validation |
| Unforeseen Conditions | Standby equipment gouging; schedule slippage | Photos, geotechnical reports, daily logs, actual supplier invoices | Moderate: CM and estimator review against pre-bid unit prices |
| Owner Scope Changes | Schedule ripple effects; remobilization costs; lost productivity | Written request, narrative of the change, updated Schedule of Values | Moderate: PM review focused on hidden downstream costs |
| Code/Regulatory Changes | Unplanned cost; interpretation disputes | Code official notices, revised permit sets, inspector notes | High: PE review to confirm technical necessity |
Once a change is routed, review it in this order: entitlement first, then cost, then time.
Before talking about price, answer the key question: Is the contractor entitled to this change at all? Check the contract's order of precedence, review the RFI history, and ask whether a capable contractor should have spotted the issue during bidding. If the issue was reasonably visible before award, reject the claim unless the contract clearly placed that risk elsewhere. This is the point where notice rules, backup rules, and approval authority start doing real work.
If entitlement is confirmed, move to pricing. Reject any lump-sum submission right away. Ask for a line-item breakdown of labor, materials, and equipment. Watch for inflated loaded labor rates, and require actual supplier invoices instead of list prices [1].
"Change orders aren't expensive because of the thing being changed. They're expensive because of the momentum being lost." - DeVore Consulting [1]
For time claims, require a TIA that shows exactly how the change affected the critical path. If the contractor only used up float on non-critical activities, that does not justify a time extension.
Set tiered approval authority based on dollar value and total exposure to date. Every approved change order should trigger an immediate update to the budget log and the project schedule records.
Run a monthly trend report showing approved changes, pending items, and projected exposure. That report helps you spot a shift early, before exposure hardens into a claim. If a change is disputed, issue a CCD so the work keeps moving while price and entitlement are worked out. If direct negotiation stalls, move the issue through your internal review path before it turns into a formal claim.
With a clean review record, negotiation usually gets faster and less reactive. The next move is to use that data to negotiate faster and build the owner-side team that can hold the line.
Once intake, pricing, and schedule review are set up, the owner's next edge is negotiation discipline. Going into a change-order negotiation without outside cost data puts the owner in a weak spot. Use current market benchmarks like RS Means and the Lee Saylor Index to check the contractor's proposal line by line [3].
The point isn't just to debate one price. It's to see the pattern. Research shows that when change-order hours go past 6% of planned project hours, productivity drops across the project [3].
"On projects with less than six percent of hours spent on changes, productivity was better than planned." - Construction Industry Institute [3]
That changes the frame of the conversation. Owners aren't only pricing a single item; they're managing the combined effect of repeated changes. If critical-path MEP or process equipment work is stuck while pricing gets sorted out, use a CCD to keep the work moving and settle cost later.
That kind of discipline only works if the right people are in place to carry it out. An experienced project executive can enforce notice rules and written approvals. A trade-savvy estimator can spot padded labor burdens - if the burden is more than 70% of the base wage, that can point to an inflated labor burden [1]. A scheduler can test delay claims. An MEP specialist can decide whether the scope is actually new work or something that was reasonably inferable from the original drawings. Without those roles, owners tend to do one of two things: overpay or slow down change decisions.
"The project manager who writes everything down usually wins the fight. But the project manager who is fair and reasonable prevents the fight from becoming a lawsuit." - DeVore Consulting [1]
Owner certainty comes from strong contract terms, disciplined process, and skilled reviewers.
Stop the work at once and require written approval before anything moves forward. Ask for a Construction Change Directive (CCD) or a signed change order that authorizes the work and spells out the pricing method.
Do not accept verbal instructions or let work continue without paperwork. If the owner won’t sign a proper change order, make sure you’ve met all contract notice and documentation rules, and consider mediation or arbitration.
Review the change order documentation with care. A valid request should spell out why the change is needed, the exact work to be done, and what’s not included. If any of that is vague or missing, there’s a good chance it isn’t legitimate extra work.
Then stack it against the original contract scope and cost breakdown. If the work already seems covered, has no clear backup, or is being rushed through for approval without support, treat it with caution.
Use a Construction Change Directive when work needs to move NOW, but the parties still haven't agreed on the cost or the schedule impact.
It usually makes sense when a delay would slow the project down or hit the critical path. It's also common when the owner directs a change but pricing is still in dispute. A CCD allows the work to keep moving while the cost and schedule are sorted out later.
