A $340K dispute doesn't start with a angry sub or a contested change order. It starts three months earlier — in a scope package that nobody read closely enough.
That's the finding from Construction Executive's analysis of scope dispute costs across commercial GC projects. And it lines up with what Arcadis reported in its 2025 Global Construction Disputes Report: the average U.S. construction dispute is now worth $60.1 million. Scope-related errors and omissions have been the leading dispute cause for six of the last nine years.
The pattern is consistent. Scope gaps form during pre-construction. They survive bid day. They surface in the field — as change orders, back-charges, or formal disputes.
This article breaks down where those gaps come from, which trades carry the most risk, and what the highest-margin GCs do differently.
Most estimating teams attribute scope disputes to sub behavior — a sub who low-balled to win work and is now billing extras. That's part of the picture. But it's not the root cause.
FMI's Construction Disconnected report puts $31 billion in annual U.S. rework costs on two factors: communication breakdowns (26%) and bad project data (22%). Both are pre-construction problems.
The gap between what the GC scoped and what the sub priced starts in the scope package. Vague inclusions, missing document references, and copy-pasted language from a prior job all create room for interpretation. And interpretation — at buyout — costs money.
"If you miss anything, they'll bill it." — Pre-Construction Lead, Top-ENR Canadian GC
That's not cynicism. That's a description of how subcontract relationships have changed. The same market that drove up material costs and compressed sub availability also changed sub behavior. Gentlemen's agreements don't survive tight margins.
"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." — Estimating Manager, Canadian ICI GC
This is the environment GCs are operating in. Scope disputes are the predictable result of scope packages that weren't built to handle it.
Based on 200+ GC interviews — documented in The Scope Gap Playbook — a small set of habits produce most scope gaps. They show up across firm size, project type, and geography.
This is the most-cited anti-pattern in the playbook. It feels like complete scope language. It isn't. It gives subs maximum room to exclude anything they didn't price. When a dispute arises, the GC has no document anchor to stand on.
Every project has a different drawing set, a different structural engineer, and different spec sections. A scope package from a similar job last year was calibrated to last year's documents. Carrying it forward without revision means missing everything that changed.
A $45K stone-depth conflict between civil, structural, and architectural drawings on a single slab — cited in the playbook — was a direct result of this habit. Nobody re-read the new drawing set against the old scope template.
When the scope package gets reviewed for the first time in the hour before bids are due, gaps don't get caught — they get accepted. At that point, the choice is to go out with a flawed scope or miss the bid. Most teams go out with the flawed scope.
Scope sheets should scope work. When PMs add contract-style language — risk allocation, liability clauses, warranty terms — without legal review, they create scope-contract conflicts that are expensive to untangle. The scope sheet and the subcontract need to be consistent. They often aren't.
Some estimating teams assume a sophisticated sub will flag what's missing. Some will. Many won't — especially when they're trying to win the work. The GC's scope package is the GC's responsibility. Counting on a sub to complete it is a margin transfer.
Scope gaps aren't evenly distributed. Certain trades generate disputes at disproportionate rates — usually because their scope sits at the intersection of multiple drawing sets or spec sections.
The trade-specific chapter of the Scope Gap Playbook documents the recurring gaps by trade. Here's a summary of the highest-risk areas:
The $400K roof cover board gap is worth examining. It wasn't caught during bid. It wasn't caught during buyout. It surfaced in the field — and the GC recovered it only through a relationship concession from the sub. That kind of recovery isn't a process. It's luck.
One phrase drives more scope disputes than any other: readily inferable.
Most standard form contracts — AIA, CCDC — include language requiring the contractor to perform work that is "reasonably inferable" from the contract documents, even if not explicitly specified. Owners and designers use this as a backstop. GCs inherit the risk.
The $300K lead-lined glass gap in the hospital imaging suite is the clearest example. The GC's scope package didn't explicitly include it. The owner's position was that it was readily inferable from the spec section and the room's function. The GC absorbed the cost.
"Our construction management clients expect us to find the scope gaps in the design too now. They expect us to be designers and engineers." — Senior PM, Canadian ICI GC
Protecting against "readily inferable" risk requires one thing: explicit scope language that either includes or excludes the item in question. Vague scope packages don't provide that protection. Specific, drawing-referenced scope packages do.
For a deeper look at how subcontract language interacts with scope gaps, see the subcontract language chapter of the Scope Gap Playbook.
The firms with the best margins aren't necessarily the fastest estimators. They're the ones who build scope packages that hold up — through buyout, through construction, and through project closeout.
The Eight Habits framework from the Scope Gap Playbook captures what these firms do consistently. Five of them have the highest impact on dispute prevention:
Start every scope package by reading the drawing set for this project. Don't open last year's template first. Boilerplate is a floor — it needs to be built on top of current documents, not used as a substitute for reading them.
Every scope item should tie back to a specific drawing number, spec section, or addendum. "As per plans and specs" is not a scope reference. "Per Structural S-201, dated Rev 3" is. The difference matters in a dispute.
Don't wait until after award to align with subs on scope boundaries. The GCs who win this are the ones having scope alignment conversations during bid — not after. It takes more time up front. It saves a multiple of that time at buyout.
A sophisticated mechanical sub doesn't need the same level of detail as a smaller specialty trade. But a smaller sub — or a new sub relationship — needs explicit scope language at a level of detail that leaves no room for interpretation.
"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.'" — Pre-Construction Lead, Top-ENR Canadian GC
Before the scope package goes to subs, someone who didn't write it reads it against the drawing set. This is not a five-minute review. It's a structured check: are all trades covered? Are the document references current? Are there conflicts between drawings that haven't been resolved?
This checkpoint is where most gaps get caught — if it exists. On too many bids, it doesn't.
The pre-issue scope review checkpoint is the most valuable step in this process. It's also the most time-consuming — and the one most likely to get cut when bid day pressure spikes.
That's the exact problem Scope Agent was built to solve. It reads the full project set — drawings, specs, addenda — and generates a complete scope-of-work package in under 60 minutes. A task that takes an experienced estimator 30 to 40 hours manually.
The output isn't a summary. It's a bid-ready scope package, structured by trade, with document references pulled from the actual project set. Subs get scopes tied to specific drawing callouts — not boilerplate language that leaves room for exclusions.
Provision has reviewed over $100 billion in project value and processed more than 66,000 documents. The EllisDon case study shows how this translates in practice: $1.8M saved on a single project.
If your team is spending 30+ hours per bid building scope packages from scratch — and still sending out packages with gaps — that's a process problem, not a people problem. Tools like Scope Agent and Risk Review exist specifically to close that gap before bid day, not after.
For GCs who want to see how this works on a real project set, book a demo and bring your own documents.
Change orders on commercial projects average 8 to 14% of project cost, according to Navigant data republished by the AIA. On projects with weak scope packages, that number climbs above 25%.
On a $20M project, the difference between 10% and 25% in change orders is $3 million. Not in dispute — in margin erosion. Most of that $3M was preventable in pre-construction.
The $340K dispute figure is the average. It includes the small disputes — a $45K stone-depth conflict, a $200K flooring gap — and the large ones. The pattern across all of them is the same: the gap existed before bid day. Nobody caught it.
The firms that win this aren't the ones who are better at resolving disputes. They're the ones who build scope packages that don't create them.
The Scope Gap Playbook — built from 200+ GC interviews — documents exactly how they do it. It's free, and it's specific enough to put to work on your next bid.
According to Construction Executive, the average scope dispute costs $340K per project. Arcadis data puts the average U.S. construction dispute — which often includes scope-related claims — at $60.1 million in 2024. The gap between those figures reflects the difference between project-level disputes and formally escalated claims.
Scope gaps most often form when teams rely on boilerplate language, copy scope packages from prior jobs without revising against current drawings, or skip the pre-issue review checkpoint due to bid day time pressure. Each habit leaves room for subs to exclude work the GC assumed was included.
MEP, envelope, structural steel, and specialty trades generate the highest-value disputes. These trades sit at the intersection of multiple drawing sets and spec sections, making it easy for scope items to fall between trades or get claimed by neither side. Real examples include a $400K roof cover board gap and $300K in lead-lined glass absorbed by a GC.
Most standard contracts require contractors to perform work that is "reasonably inferable" from the contract documents — even if not explicitly specified. This language creates dispute risk when the GC's scope package doesn't explicitly address the item in question. Explicit, drawing-referenced scope language is the best protection against this exposure.
The highest-impact steps are: tying every scope item to a specific drawing or spec reference, running a structured pre-issue scope review before packages go to subs, front-loading buyout conversations during the bid phase, and avoiding generic language like "as per plans and specs." These habits are detailed in the Eight Habits framework from the Scope Gap Playbook.
Yes — specifically for the scope package generation and review process. Provision's Scope Agent reads the full project set and produces a complete, trade-organized scope-of-work package in under 60 minutes. It replaces 30 to 40 hours of manual work and generates scope items tied to specific document references — the same references that protect GCs in a dispute.
Most change orders trace back to scope gaps — items that weren't explicitly assigned to a trade in the original package. On commercial projects, change orders average 8 to 14% of project cost. On projects with weak scope packages, that figure climbs above 25%. Closing scope gaps in pre-construction directly reduces change order volume in the field.
See how Scope Agent builds trade-specific scope packages from your drawings in under 60 minutes.
See Scope AgentMore Articles
