Change orders feel like a field problem. A sub claims extra work. The owner pushes back. The project manager spends two weeks pulling emails. But by the time that fight starts, the damage was done weeks — or months — earlier, in a bid room.
If your team is seeing the same change order patterns project after project, that's not bad luck. It's a system producing predictable outcomes. This article breaks down the root causes and where pre-construction teams have the most leverage to stop them.
Change orders on commercial construction projects average 8–14% of total project cost, according to Navigant research republished by the AIA. On projects with weak scope documentation, that number climbs past 25%.
The Arcadis 2025 Global Construction Disputes Report puts the average U.S. construction dispute value at $60.1 million. The most common cause? Errors and omissions in contract documents — for 6 of the last 9 years running.
FMI's Construction Disconnected report puts annual U.S. rework costs at $31 billion. Communication breakdowns account for 26% of that. Bad project data accounts for another 22%.
These aren't abstract industry statistics. They describe what's happening on your projects right now.
The most common scope anti-pattern in commercial construction is also the most costly: "As per plans and specs."
That phrase appears in thousands of subcontract scope sheets. It sounds reasonable. It's actually a gap-generator. It pushes the interpretation burden onto the sub — and when they interpret differently than you intended, the change order follows.
A Pre-Construction Lead at a top-ENR Canadian GC described the standard this way: "It's descriptive — bread, put it on a plate, use the open jar… You have to get to that level of detail or else they'll just be like, 'you didn't tell us that.'"
The peanut-butter test. If your scope sheet doesn't pass it, you're exposed.
Other language patterns that generate change orders:
The subcontract language chapter of the Scope Gap Playbook goes deep on the specific clauses that generate the most disputes — and how to rewrite them.
Most change orders don't come from a single bad spec. They come from conflicts between documents that no one caught at bid time.
Consider a real example from the playbook: a $45,000 stone-depth mismatch on a single slab — caused by a conflict between civil/structural and architectural drawings. Neither drawing set was wrong in isolation. Together, they were a problem. No one caught it until the concrete was poured.
A $300,000 lead-lined glass scope gap on a hospital imaging suite is another. The requirement appeared in the spec. It didn't appear in the scope sheet. The GC absorbed it under "readily inferable" language.
These aren't exotic edge cases. They happen because full document review — drawings plus specs plus addenda — takes 30–40 hours per bid. Teams under backlog pressure cut that time. Something gets missed.
In 2026, with pre-construction teams stretched thin across more pursuits, that pressure is only higher.
Scope gaps often surface at buyout — when the sub reads the subcontract for the first time and sees what they're actually agreeing to. By then, the GC has already committed to the owner.
An Estimating Manager at a Canadian ICI GC put it plainly: "We have less subs who just kind of a gentleman's agreement… they've become more quick to clarify that we're not including that one piece of scope."
Subs are sharper on scope exclusions than they were five years ago. If you're not having the buyout conversation before bid day, you're discovering scope gaps when it's most expensive to fix them.
The Pre-Construction Lead quoted earlier added: "If you miss anything, they'll bill it."
Front-loading buyout conversations is one of the eight habits that separates high-margin pre-construction teams from the rest. See the full list in The Scope Gap Playbook.
Scope templates exist for good reasons. They enforce consistency. They prevent wheel-reinvention on every bid. They give junior estimators a starting point.
But templates become a liability when they're treated as a complete scope — when the estimator fills in the blanks and ships it without project-specific review.
The $400,000 missed roof cover board on a $50 million project is a template failure. The cover board was project-specific. It wasn't in the template. No one added it. The GC recovered it only through a relational concession from the sub — not a contractual right.
The pattern is consistent across trade types. A previous job's MEP scope doesn't account for this project's generator field conditioning requirements. A previous concrete scope doesn't flag the concrete pumping question on a job with a different site constraint. Copy-paste is a change order factory.
Even when pre-construction does the work correctly, change orders still happen — because the scope package doesn't make it to the field intact.
A Director of Pre-Construction at a Mid-Market Southeast GC described it this way: "Pre-con is working in the scope sheet world and project management is working in the scopes of work."
That's two different documents, two different vocabularies, and two different interpretations of what was agreed. When a PM issues a subcontract with scope language that drifts from what was bid, the change order potential is baked in before the project starts.
This is a systems problem, not a people problem. The scope sheet needs to be the source of truth — and it needs to survive the handoff.
Some scope gaps are project-specific. Others are structural — they happen in the same trades, in the same document sections, on almost every job. Knowing where to look cuts your exposure significantly.
Geotech compaction specs buried in the soils report. The five-foot transition zone between disciplines. Excavator unit-rate language that experienced subs exploit on measured work.
Grouting base plates — who owns it, and under what spec section. Slab assembly conflicts between structural and architectural. Concrete pumping when the site doesn't allow direct pour.
Embeds and anchor bolts — specified by structural, installed by others. Hoisting and rigging on heavy steel packages. Miscellaneous metals scattered across a dozen spec sections that no single sub is tracking.
Generator field conditioning: a recurring dispute across multiple projects in the playbook research, described as costing "millions" in the aggregate. Motor starters — specified in electrical, needed by mechanical. Fire-rated louvres that neither trade claims. Lighting controls fragmented across spec sections.
Roof cover board: specified in the roofing section, missed by the estimator who only read the membrane spec. Masonry-storefront flashings that fall between trades. Interior vs. exterior caulking scope. Fire-stopping responsibility at penetrations.
Lead-lined glass in hospital imaging suites. Curtainwall mock-up costs not in any budget. Mass timber material protection on site — a $10,000 glulam beam destroyed because no clause required coverage.
For a full breakdown by trade, see the trade-specific chapter of the Scope Gap Playbook.
The firms with the best margins aren't just lucky. They follow a consistent set of habits — and they apply them on every pursuit, not just high-stakes ones.
The eight habits identified across 200+ GC interviews in the Scope Gap Playbook research are:
These habits aren't new. What's new is the ability to execute them consistently, across every pursuit, without adding headcount.
The root cause of most change orders is incomplete information at bid time. The challenge is that complete information takes time — 30 to 40 hours of document review per bid, across a project set that may include 2,000 pages of specs, drawings, addenda, and supplementary conditions.
That's where purpose-built pre-construction tools change the equation.
Provision's Scope Agent reads the full project set — drawings and specs together — and generates a complete scope-of-work package in under 60 minutes. It surfaces trade gaps, document conflicts, and missing callouts that manual review typically misses under time pressure.
The Risk Review tool runs a structured risk checklist against contracts and specs, flagging the clauses — "readily inferable," "including all related work," "as required" — that generate change orders downstream. It operates at 99.5% accuracy on pre-built risk checklists.
And for teams that need to pull specific information from a large document set during bid assembly, Chat Agent returns cited answers from drawings, specs, and addenda in under 20 seconds.
A Senior PM at a Toronto mid-market developer framed the value simply: "If we could catch three scope gaps or three missed items on every scope of work, then this thing pays for itself."
That math holds on almost any commercial project. Three missed items at even $50,000 each is $150,000 in change order exposure. The cost of a tool that catches them is a fraction of that.
See how GCs are using Provision to reduce change order exposure — start with the EllisDon case study, where the team identified $1.8M in risk on a single project review.
Change orders have always damaged margin. In 2026, with pre-construction teams managing higher backlog on leaner staffing, they're more damaging than ever.
Every unresolved scope gap is a potential change order. Every change order is a negotiation. Every negotiation costs project management time that doesn't exist. And if the change order turns into a dispute — the average U.S. construction dispute is now $60.1 million, per Arcadis — the cost is orders of magnitude higher than what it would have taken to write a clear scope sheet at bid time.
The firms that win in this environment aren't just faster at bidding. They're more precise. They catch what others miss. They write scope packages that hold up — not just to the owner, but to the sub, to the PM, and to the contract.
That starts in pre-construction. And it starts before bid day.
Ready to see what a thorough scope review looks like? Book a demo and see Scope Agent work on a live project set.
Errors and omissions in contract documents are the leading cause — ranking #1 in construction disputes for 6 of the last 9 years, according to the Arcadis Global Construction Disputes Report. Most trace back to incomplete scope language, missed document conflicts, or late buyout conversations during pre-construction.
Change orders average 8–14% of total project cost on commercial work, per Navigant research republished by the AIA. On projects with weak scope documentation, that figure can exceed 25%. The average U.S. construction dispute — many of which start as disputed change orders — was $60.1M in 2024, per Arcadis.
A scope gap is work that needs to happen on a project but isn't clearly assigned to any party in the contract or scope sheet. It typically surfaces during construction, when a sub claims the work is extra and the GC disputes it. Scope gaps are caused by incomplete spec reviews, conflicting drawings, and vague scope language at bid time.
The highest-impact actions are: writing drawings-specific (not boilerplate) scope language, resolving buyout questions before bid day, running structured document reviews that cross-reference drawings and specs, and creating a pre-issue scope review checkpoint before packages go to subs. These habits are detailed in The Scope Gap Playbook.
MEP, envelope, and specialty work generate the highest change order frequency in commercial construction. Common gap zones include generator field conditioning, roof cover board, lead-lined glass, miscellaneous metals, and fire-stopping — all areas where scope responsibility falls between trade sections or document sets.
"Readily inferable" is contract language that requires a sub or GC to include work that's logically implied by the documents — even if not explicitly stated. GCs who rely on this clause to cover scope gaps are taking a risk. Courts and arbitrators interpret it narrowly. Writing explicit scope is always more defensible than arguing inferred intent.
Yes — when they're built for construction workflows. Purpose-built tools like Provision's Scope Agent read full project sets (drawings and specs together) and flag trade gaps, document conflicts, and missing callouts in under 60 minutes. Generic AI tools like ChatGPT lack the construction context and structured output formats that pre-construction teams need to produce bid-ready scope packages.
See how Scope Agent reviews your full project set and flags missing scope in under 60 minutes.
See Scope AgentMore Articles
