You didn't write the scope letter. You didn't run the bid. You weren't in the pre-construction meeting when the sub asked whether roof cover board was included and someone said "check the spec."
But now it's your dispute to manage.
That's the reality for most project managers on commercial and ICI work. Scope gaps are produced upstream — in pre-construction, during buyout, in the language of the subcontract. But they surface on your project, on your schedule, on your margin.
And when subs push back, they're usually right. The scope letter didn't say it clearly enough.
According to the Arcadis 2025 Global Construction Disputes Report, the average U.S. construction dispute was worth $60.1 million in 2024. For six of the last nine years, the number-one cause was errors and omissions in contract documents.
Not weather. Not design changes. Not owner interference. Scope documents that didn't say what they needed to say.
By the time a PM is managing the project, the scope letter is already signed. The subcontract is executed. The budget is locked. The only leverage left is relational — and subs know it.
As one Pre-Construction Lead at a Top-ENR Canadian GC put it: "If you miss anything, they'll bill it."
That's not cynicism. That's the market in 2026.
The construction subcontractor landscape has changed. Subs are running leaner. Margins are tighter. And they've gotten more precise about what they're pricing.
An Estimating Manager at a Canadian ICI GC described it directly: "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."
That shift puts PMs in a difficult position. If the scope letter is ambiguous, the sub's exclusion looks reasonable. And without a clear written record that the scope was discussed and agreed, the PM has no leverage to push back.
The paperwork wins. And the paperwork was written in pre-construction.
These are the patterns that create scope disputes. Most PMs recognize them immediately — because they've fought through the consequences.
This is the most-cited anti-pattern in scope writing. It sounds complete. It isn't. When the plans and specs conflict — and they often do — the sub will take the interpretation that costs them less. And they'll be right to do so, because the scope letter never resolved the conflict.
A $45,000 stone-depth mismatch between civil/structural and architectural drawings is a real example from the field. The discrepancy existed in the documents. The scope letter said "as per plans." The PM had no ground to stand on.
Templates save time. But a template built around a previous office building doesn't account for the hospital imaging suite you're building now. That's how a $300,000 lead-lined glass scope gap ends up absorbed by the GC under "readily inferable" language — because the scope sheet came from a file that didn't contemplate shielded environments.
The sub never included it. The scope letter never called it out. The PM is left holding the change.
Scope letters that list trades without tying them to specific drawing sheets and spec sections are disputes waiting to happen. When a sub says "we didn't include that," the PM needs a citation — a specific reference that puts the item in scope. Without one, there's nothing to point to.
Scope letters reviewed at the last minute don't get fixed. They get sent. And the gaps that would have taken 20 minutes to close during pre-construction take weeks to resolve on site — at a cost that's usually absorbed by the GC.
A $400,000 missed roof cover board on a $50-million project was recovered only through a relational concession from the sub. There was no contractual basis to require it. The scope sheet didn't mention it. The PM had to call in a favor.
This is perhaps the most common failure mode. The scope letter was written by an estimator. It references a 2,000-page spec book and a set of drawings that may have been revised three times since bid. By the time the PM is running the project, they don't know exactly what's in scope and what isn't — and neither does the sub.
A Director of Pre-Construction at a Mid-Market Southeast GC described the structural problem clearly: "Pre-con is working in the scope sheet world and project management is working in the scopes of work."
Those two worlds need to speak the same language. Most of the time, they don't.
FMI's Construction Disconnected report puts annual U.S. rework costs from miscommunication and bad project data at $31 billion. Twenty-six percent of that rework comes from communication breakdowns. Twenty-two percent from bad project data.
Those numbers are abstract. The field examples aren't:
Change orders on commercial projects average 8–14% of project cost, according to Navigant data republished by the AIA. On projects with weak scope documentation, that number exceeds 25%.
The scope letter isn't administrative. It's financial.
The best pre-construction teams — and the PMs who work with them — do a small set of things consistently. These habits come directly from interviews with 200+ general contractors and are documented in The Scope Gap Playbook.
Scope letters built from the project drawings catch trade gaps that boilerplate misses. The drawings show what's actually being built. They're where the $45K stone-depth conflict lives, or the lead-lined glass that isn't in the standard hospital template.
Starting with drawings means starting with this project, not the last one.
Every scope item should tie to a sheet number, a spec section, or a detail. "Concrete work as per plans" creates a dispute. "Concrete work as per Structural S-101 through S-114 and Spec Section 03 30 00" creates a record.
One Pre-Construction Lead at a Top-ENR Canadian GC called this 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.'"
Scope gaps close fastest when they're discussed before the sub prices the work. By the time a sub has submitted their bid, they've committed to an interpretation. Changing it costs money — their money. They'll fight to keep it.
The conversation has to happen earlier. What's in. What's out. What "readily inferable" means for this project. Before bid day, not after.
Scope letters are full of exclusions. Good ones also have clarifications — explicit statements about what is included and why. Clarifications close the ambiguity that exclusions leave open.
If concrete pumping is included, say it. If fire-rated louvres are in the mechanical scope and not the envelope scope, say it. If the trench is in civil and not MEP, say it. Every clarification is a future dispute that doesn't happen.
Before the scope letter goes to the sub, one person reads it against the current drawing set. Not the drawings from six weeks ago. The current set. This catches addenda changes that didn't make it into the scope, conflicts between drawings and spec, and items that were discussed in pre-construction but never written down.
This is the checkpoint that prevents the five-minutes-before-bid review from becoming the only review.
Scope dispute prevention is fundamentally a documentation problem. The more specific, current, and complete the scope letter, the fewer disputes reach the PM's desk.
That's where tools built for pre-construction can help. Scope Agent reads the full project set — drawings, specs, addenda — and generates a complete scope-of-work package in under 60 minutes. It replaces 30–40 hours of manual work per bid. And because it's built on the actual documents, it surfaces trade gaps that boilerplate templates miss.
Provision has reviewed more than $100 billion in project value and processed more than 100,000 documents. In a published head-to-head using live hospital drawings, Scope Agent captured 145 line items at 91.7% verified accuracy with zero fabricated entries. That kind of document coverage is what closes scope gaps before they become field disputes.
For PMs trying to interrogate a scope letter mid-project, Chat Agent answers questions about drawings, specs, contracts, and RFIs in under 20 seconds — with citations. If a sub says "that's not in our scope," you can check the documents immediately, not after an hour of searching a 2,000-page spec book.
And for contract and subcontract risk, Risk Review runs a 99% accurate risk check on every clause — with every risk cited to the exact section. It cuts contract and spec review time by 80%. If there's a "readily inferable" trap buried in the supplementary conditions, Risk Review finds it before the sub does.
These tools don't replace judgment. They give PMs and pre-construction teams the document coverage they need to make better calls, faster.
If you're a PM inheriting projects with thin scope letters, you can't rewrite pre-construction. But you can reduce your exposure.
Most PMs treat the scope letter as supporting documentation. Subs treat it as the contract. That gap in perspective is where disputes are born.
When a sub says "we didn't include that," they're reading the scope letter. When a PM says "it's obviously in scope," they're reading the drawings. If the scope letter doesn't match the drawings, the sub wins — because the scope letter is what was agreed.
Fixing that requires investment upstream. Better scope letters. More specific document references. Earlier buyout conversations. A pre-issue review that catches gaps before they become signed subcontracts.
It also requires tools that can read a full project set and tell you what's missing — before the sub's exclusions list tells you first. That's what Scope Agent is built to do.
The dispute you prevent in pre-construction is the one you never have to manage in the field. That's the only scope dispute worth having.
Most scope disputes come from vague or incomplete scope letters — documents that reference "plans and specs" without specifying which drawings or sections. When subs and GCs read the same documents differently, the sub's interpretation usually wins because the scope letter didn't resolve the ambiguity. According to the Arcadis 2025 Disputes Report, errors and omissions in contract documents have been the top dispute cause for six of the last nine years.
Subcontractors are running leaner margins and less willing to absorb items that weren't clearly priced. The informal "gentleman's agreement" that once covered scope gaps is largely gone. Subs now clarify exclusions early and specifically — which means vague scope letters create disputes faster than they used to.
A strong scope letter ties every work item to a specific drawing sheet, spec section, or detail. It includes clarifications — not just exclusions — for ambiguous items. It resolves known conflicts between drawings and specs. And it reflects the current document set, not the set from six weeks ago. The Eight Habits framework in The Scope Gap Playbook covers this in detail.
Start by reading the scope letter against the current drawing set. Flag ambiguous items and document any clarifications agreed with the sub before work starts. Build a written clarification log and attach it to the subcontract file. Use tools like Chat Agent to quickly check what the project documents actually say — without searching through thousands of pages manually.
"Readily inferable" language in subcontracts requires subs to include work that a reasonable contractor would infer from the documents — even if it isn't explicitly called out. Subs increasingly challenge this language, and GCs absorb the cost when their scope letters don't support the inference. A $300,000 lead-lined glass scope gap on a hospital project is a real example of this exposure.
Scope Agent reads the full project set — drawings, specs, addenda — and generates a complete scope-of-work package in under 60 minutes. It surfaces trade gaps and document conflicts before buyout, so scope letters reflect the actual project documents rather than boilerplate templates. The result is fewer ambiguities for subs to exploit, and fewer disputes reaching the PM's desk.
Scope gaps range from thousands to hundreds of thousands of dollars per incident. Real examples include a $200,000 wood-flooring gap on a luxury condo, a $300,000 lead-lined glass omission on a hospital project, and a $400,000 missed roof cover board recovered through a relational concession. Change orders on commercial work average 8–14% of project cost — and exceed 25% on projects with weak scope documentation.
See how Scope Agent builds complete scope packages from your project documents in under 60 minutes.
See Scope AgentMore Articles
