In 2026, GC-sub scope disputes are not a back-office nuisance. They are a margin problem. A project delivery problem. And increasingly, a legal problem.
The average U.S. construction dispute is now worth $60.1 million, according to the 2025 Arcadis Global Construction Disputes Report. "Errors and omissions in contract documents" has been the single most common dispute cause for six of the last nine years. That phrase — errors and omissions — covers a lot of ground. But at the GC-sub interface, it usually starts with one thing: a scope letter that did not say enough.
At the same time, the dynamic between GCs and subs has shifted. The informal understandings that used to smooth over ambiguity are disappearing.
"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," said an Estimating Manager at a Canadian ICI GC — one of more than 200 general contractors interviewed for The Scope Gap Playbook.
When subs sharpen their pencils, GCs absorb the gaps. The question is whether those gaps were visible before buyout — or only after the change order lands.
Most GC pre-construction teams know their scope letters could be tighter. Few realize how much tighter they need to be.
Here is what vague looks like in practice — drawn from real projects:
These are not edge cases. They are the predictable output of scope letters written from boilerplate rather than from the actual project documents.
The Scope Gap Playbook identifies a set of recurring habits that produce scope ambiguity. Construction professionals call them anti-patterns — approaches that feel efficient but generate cost downstream.
This is the most common anti-pattern cited across 200+ GC interviews. It transfers risk to the sub in theory. In practice, it creates disputes — because subs interpret plans and specs differently. When there is a conflict between drawings and specs, "as per plans and specs" resolves nothing.
A hospital is not an office tower. An ICI fit-out is not a multi-res build. Scope letters copied from previous projects carry the assumptions of that project — different drawings, different sub roster, different site conditions. When those assumptions are wrong, the gap is real money.
Tenured estimators know what to look for. Junior staff often do not. When a junior estimator copies a previous scope and does not cross-reference current drawings, the result is a scope letter that matches last year's project, not this one.
Pre-bid scope reviews are standard practice at most GC firms. What is less standard is the time allocated. A scope review done at 3:45 PM on bid day catches formatting errors. It does not catch a missing trade, a conflicting spec callout, or a sub that excluded grouting under base plates.
Some GCs use boilerplate "generally includes" language to push scope onto subs. Subs have learned to read these lists carefully — and to exclude anything not explicitly shown in the drawings they received. Generic inclusion language does not hold at arbitration the way specific document references do.
"If you miss anything, they'll bill it," said a Pre-Construction Lead at a top-ENR Canadian GC. The relationships that used to buffer scope disputes have been replaced by tighter estimating practices on the sub side. GCs that still rely on informal understandings are carrying the risk alone.
The GCs with the best buyout margins share a common practice: they treat scope letters as construction documents, not bid summaries. Specificity is not a courtesy — it is protection.
The Scope Gap Playbook identifies eight habits that separate these firms from those chasing change orders through closeout. Here are the five that matter most for scope letter disputes:
Start with the actual drawings for this project. What does the architectural set show? What does the structural set show? Where do they conflict? A scope letter written from the drawings catches gaps that boilerplate never will.
Instead of "as per plans and specs," reference the specific drawing numbers, sheet revisions, and spec sections that govern each line item. "Per A-301 Rev. 2 and Spec Section 09 64 00" is defensible. "As per plans" is not.
Most scope letters list exclusions. Fewer list clarifications — explicit statements about how ambiguous scope was interpreted. Clarifications are more valuable than exclusions in a dispute. They show the GC's intent at bid time, which is harder for a sub to dispute than a line missing from an exclusions list.
The best pre-con teams have scope alignment conversations with key subs before the subcontract is issued — not after. "Pre-con is working in the scope sheet world and project management is working in the scopes of work," said a Director of Pre-Construction at a mid-market Southeast GC. Bridging that gap early is how high-margin GCs prevent field disputes.
Before a scope letter goes to a sub, it goes through a structured review. Not a five-minute check — a systematic comparison against the drawings, specs, and the sub's bid to confirm alignment. This checkpoint catches gaps while the cost to fix them is zero.
Scope gaps are not randomly distributed across trades. Certain items appear repeatedly in GC-sub disputes — and they appear because they live in the grey zone between trades, between drawing sets, or between spec divisions.
The following table lists the highest-frequency scope gaps by trade, drawn from the trade-specific chapter of the Scope Gap Playbook:
These gaps do not appear because subs are careless. They appear because the scope letter did not address them. Subs price what they see. If the letter is silent on cover board, the sub excludes cover board.
A 200-page spec book is manageable. A 2,000-page project set — drawings, specs, addenda, RFIs, supplementary conditions — is not. Most pre-con teams are operating with too many pursuits and not enough time to read everything for every bid.
That is where scope gaps originate. Not from negligence — from volume.
FMI's Construction Disconnected report puts the annual U.S. cost of rework driven by miscommunication and bad project data at $31 billion. Twenty-six percent of that rework comes from communication breakdowns. Another 22 percent comes from bad project data. Scope letters are both: a communication tool and a data source. When they are vague, they produce rework.
Some GC pre-con teams are now using Scope Agent to process full project sets — drawings, specs, and addenda — and generate complete, trade-specific scope packages in under 60 minutes. That replaces 30 to 40 hours of manual scope extraction per bid. It also surfaces the conflicts between drawing sets that produce the gaps in the first place.
The Chat Agent gives estimators a faster way to query specific spec sections, RFIs, and addenda without searching manually through thousands of pages. A question that used to take 20 minutes to answer now takes under 20 seconds.
Provision has processed over 66,000 construction documents and reviewed more than $100 billion in project value. The accuracy on scope extraction and risk identification — across real project documents — is 95%.
Many GC contracts include language that makes subs responsible for scope that is "readily inferable" from the contract documents. In practice, this language is harder to enforce than it reads.
Subs have legal counsel too. What a GC considers "readily inferable," a sub's lawyer may call "not shown on the drawings provided." The $300,000 lead-lined glass example above was absorbed by the GC under exactly this argument — the spec existed, but the sub never received the relevant division during the bid process. "Readily inferable" did not hold.
"Our construction management clients expect us to find the scope gaps in the design too now," said a Senior PM at a Canadian ICI GC. "They expect us to be designers and engineers." That expectation is increasingly being pushed down the chain — from owners to GCs to subs. The scope letter is where that expectation gets formalized, or falls apart.
The Risk Review tool flags contract language like this — conditions where standard boilerplate creates unintended exposure. It runs a structured checklist against the full contract set, not just the scope letter, and identifies clauses that shift risk in ways the GC may not have priced.
One pre-construction lead at a top-ENR Canadian GC described the required level of scope detail using what the Scope Gap Playbook calls the "peanut-butter test":
"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.'"
That standard feels extreme until you absorb a $400,000 change order because the scope letter said "roofing as specified" and did not mention cover board.
The GCs closing buyout within budget are not writing longer scope letters for the sake of it. They are writing specific ones. Every line item that could be disputed gets a drawing reference, a spec section, and an explicit statement of inclusion or exclusion. No grey zone. No assumption of shared understanding.
For teams managing multiple simultaneous pursuits, that level of specificity is only achievable with a structured process. The Scope Agent generates scope packages at that level — trade-by-trade, drawing-referenced, built from the actual project documents — in a fraction of the time manual review requires. See how it works for general contractors who are already using it to close buyout gaps before they start.
Vague language is the primary cause. Phrases like "as per plans and specs" leave room for different interpretations. When a GC and sub read the same letter differently, the gap becomes a dispute. Drawing-specific references and explicit clarifications prevent most of these disagreements before they start.
Real-project examples from 200+ GC interviews range from $45,000 for a single drawing conflict to $400,000 for a missed roofing component on a $50M project. The Arcadis 2025 Global Construction Disputes Report puts the average U.S. dispute value at $60.1 million — scope ambiguity is a leading trigger.
"Readily inferable" clauses make subs responsible for scope that a competent contractor should have anticipated — even if it is not explicitly stated. In practice, these clauses are hard to enforce when the relevant spec section was missing from the bid set or the drawing conflict was not visible. GCs often absorb the cost anyway.
Start from the drawings, not from boilerplate. Reference specific drawing numbers and spec sections for every line item. Include clarifications — not just exclusions. Have a structured pre-issue review that compares the scope letter against the sub's bid. Use templates as a floor, not a ceiling.
Yes — when the tool is built for construction. Provision's Scope Agent reads full project sets (drawings, specs, addenda) and generates trade-specific scope packages with document references in under 60 minutes. That replaces 30 to 40 hours of manual work and surfaces drawing conflicts before the scope letter is drafted. Generic AI tools like ChatGPT lack the construction context to produce bid-ready scope packages.
Margins are tighter. Legal counsel is more involved. And informal "gentleman's agreement" relationships between GCs and subs have weakened over the past decade. Subs now price what they see in the scope letter — and exclude everything else. GCs that rely on historical relationships to fill scope gaps are increasingly absorbing costs that used to be shared.
Start with trade interfaces — where one sub's scope ends and another's begins. Concrete-to-steel, MEP-to-drywall, envelope-to-roofing, and civil-to-structural are the highest-risk zones. Also review any scope item that appears in only one location in the project documents. Single-mention items are the most commonly missed. The trade-specific chapter of the Scope Gap Playbook maps the most common gaps by trade.
See how Scope Agent builds drawing-referenced scope packages before subs find the gaps.
See Scope AgentMore Articles