A subcontractor scope letter used to be a handshake on paper. Everyone knew the work. Everyone knew the unwritten rules. If something fell in a grey area, the sub picked it up and the relationship stayed intact.
That dynamic has changed. And GCs who still write scope letters the old way are paying for it — in RFIs, change orders, and margin erosion that compounds across every project.
This article explains why vague scope letters create disputes, what the numbers actually look like, and what writing a tight scope letter requires in practice.
The Arcadis 2025 Global Construction Disputes Report puts the average U.S. construction dispute value at $60.1M. For six of the last nine years, the top cause has been the same: errors and omissions in contract documents.
That is not a design problem. That is a scope-writing problem.
FMI's Construction Disconnected report estimates $31 billion in annual U.S. rework costs tied to miscommunication and bad project data. Twenty-six percent of that rework traces back to communication breakdowns. Another 22% to bad project data — meaning work performed against the wrong version of scope.
The average scope dispute on a mid-market commercial project now runs around $340K. That is not a catastrophic project failure. That is a normal project with a few unresolved scope questions — and no paper trail to resolve them.
One of the clearest signals from Provision's research — drawn from interviews with more than 200 general contractors — is a shift in subcontractor behaviour over the last several years.
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 exclusions. They read scope letters looking for what is missing. If it is not in writing, it is not in their price.
A Pre-Construction Lead at a Top-ENR Canadian GC said it even more directly:
"If you miss anything, they'll bill it."
This is not a subcontractor problem. It is a rational response to a construction market where margins are thin and project complexity is high. But it puts the burden squarely on the GC to write scope letters that leave no room for interpretation.
The most common scope-writing anti-patterns are easy to spot — once you know what to look for. They show up on every project type, across every trade.
This is the single most-cited anti-pattern among experienced estimators. It feels complete. It is not. "As per plans and specs" passes the ambiguity downstream. When the sub's interpretation of the drawings differs from yours, you have no written anchor to resolve it.
The Scope Gap Playbook's chapter on subcontract language documents this pattern in detail. It is the phrase that sounds thorough and creates the most disputes.
Scope letter templates are valuable. Using last project's scope letter verbatim is not. Every project has different documents, different subs, and different drawing conflicts. A scope letter built for a $40M office tower does not protect you on a $70M mixed-use with a different structural system and a different envelope sub.
Scope sheets are for scope. When project managers embed contract language — indemnity clauses, warranty terms, insurance language — inside a scope letter, it creates confusion about which document governs. Subs notice. Their lawyers notice more.
A junior estimator under bid-day pressure will use whatever source material is available. If that source material is a scope from two years ago on a different building type, you get scope letters that reference wrong specs, wrong drawing sets, and wrong trade divisions.
Scope letters reviewed at the end of bid day — after numbers are locked — are not reviewed. They are rubber-stamped. Any gap in the scope letter at that point goes to contract. You will not catch it until the field team calls.
Industry averages are useful. Project-level examples are more convincing. These are drawn from Provision's research with GC operators — all anonymized by role and firm segment.
Flooring scope was written in general terms. The drawings called out a specific luxury wood product. Neither the flooring sub nor the GC's scope letter referenced the product spec by name. At buyout, the sub priced a standard product. The owner expected the specified product. The GC absorbed the difference.
The glazing scope letter said "glass as per drawings." The imaging suite drawings called for lead-lined glass with specific shielding specifications. The glazing sub priced standard curtainwall glass. The GC absorbed the $300K delta under "readily inferable" contract language — meaning the owner's contract required the GC to deliver it regardless of whether the sub included it.
The roofing scope letter did not reference the cover board specification. The sub excluded it. The GC caught the gap after award. Recovery came through a relational concession from the sub — not a contract right. On the next project with a different sub, there is no concession to ask for.
Civil, structural, and architectural drawings showed different stone depths on a single slab assembly. The scope letter referenced "stone as per architectural drawings." The conflict between drawing sets was never flagged. The GC paid to resolve it in the field.
These are not edge cases. They are the predictable output of scope letters written without direct document references. For more trade-specific examples, the Scope Gap Playbook's trade-specific chapter covers common gaps across MEP, envelope, drywall, and specialty scopes.
GCs with consistently tight buyout do not use better templates. They follow a consistent set of habits at every stage — bid, scope letter, and buyout. These habits come directly from Provision's operator research.
A Director of Pre-Construction at a Mid-Market Southeast GC described what happens when these habits break down:
"Pre-con is working in the scope sheet world and project management is working in the scopes of work."
When pre-con writes scope letters in isolation from the project documents — and PMs receive them without context — the gap between what was priced and what needs to be built shows up in the field. That gap becomes RFIs. RFIs become change orders.
There is a practical test for scope letter specificity. A Pre-Construction Lead at a Top-ENR Canadian GC called it 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.'"
Applied to a scope letter, the test is simple: can a subcontractor's PM — who has never spoken to your estimator — read this scope letter and know exactly what is in scope, what is not, and where to find the governing specification?
If the answer is no, the scope letter will generate an RFI. Usually within the first three weeks of construction.
The specific versions take longer to write. They take far less time than an RFI cycle or a change order negotiation.
The bottleneck in writing specific scope letters is not knowledge. Most estimators know what to include. The bottleneck is time. On a $50M commercial bid, reviewing 2,000 pages of drawings and specs to catch every spec reference, drawing conflict, and trade interface takes 30 to 40 hours per pursuit.
Provision's Scope Agent reads the full project document set — drawings, specs, addenda — and generates scope-of-work packages in under 60 minutes. It flags trade interfaces, conflicting drawing references, and spec callouts that are commonly missed. The output is a structured scope package your team can review, adjust, and issue — not a first draft that still needs full reconstruction.
Provision has processed more than 66,000 documents and reviewed over $100 billion in project value. The accuracy on pre-built risk checklists runs at 99.5%. That is not a replacement for an experienced estimator's judgment. It is the document review that frees up that estimator to focus on judgment — not page-turning.
If your team is also reviewing contract language for risk exposure, Risk Review runs a structured checklist against your subcontract documents and flags missing protections before you sign. And when your team needs fast answers from a 2,000-page project set — which spec section governs, which drawing sheet shows the detail — Chat Agent returns cited answers in under 20 seconds.
For general contractors building out their pre-construction workflow, the Provision platform for GCs ties these tools into a single pre-con workflow.
A Senior PM at a Toronto mid-market developer put the business case simply:
"If we could catch three scope gaps or three missed items on every scope of work, then this thing pays for itself."
Three scope gaps per project. At a $340K average dispute cost, that is over $1M in avoided losses per project — before you count the RFI cycles, the schedule impact, and the sub relationship cost.
The firms with the best margins do not have better luck. They have tighter habits. The Scope Gap Playbook documents those habits in detail, drawn from 200+ GC operator interviews. If your team is writing scope letters the same way it did five years ago, that playbook is worth an hour of your pre-con team's time.
You can also start with Provision's scope of work template — a structured starting point built for GC teams handling multiple simultaneous pursuits.
A subcontractor scope letter is a written document issued by a GC that defines exactly what work a specific subcontractor is responsible for on a project. It outlines inclusions, exclusions, and references to governing drawings and specs. It forms the basis of the subcontract agreement and is the primary document used to resolve scope disputes during construction.
RFIs are generated when a subcontractor encounters work in the field that their scope letter does not clearly address. If the scope letter uses generic language like "as per plans and specs" without specific document references, the sub has no written authority to proceed — so they issue an RFI. That RFI triggers a response cycle that can take days or weeks and often results in a change order.
The average U.S. construction dispute sits at $60.1M according to the Arcadis 2025 Global Construction Disputes Report. At the project level, individual scope gap disputes on mid-market commercial work commonly run $200K–$400K. The $340K average scope dispute figure reflects real project data from GC operator interviews, not modeled estimates.
"As per plans and specs" is the single most-cited anti-pattern among experienced estimators. It appears thorough but delegates all interpretation to the subcontractor. When the sub's interpretation differs from the GC's intent, there is no written anchor to resolve the dispute. Specific drawing sheet and spec section references are the only reliable substitute.
Reference every major scope item by spec section number and drawing sheet number. List both inclusions and exclusions explicitly. Identify trade interfaces — where one sub's work ends and another's begins. Apply the "peanut-butter test": can a sub's PM who has never spoken to your estimator read this letter and know exactly what is in scope? If not, add detail.
Yes — when the AI is built for construction documents. Provision's Scope Agent reads the full project set (drawings, specs, addenda) and generates structured scope packages in under 60 minutes. It surfaces spec callouts, drawing conflicts, and trade interfaces that are commonly missed in manual review. The output is a reviewed scope package, not a raw draft that still needs full reconstruction by your team.
Readily inferable is contract language that requires a GC to deliver work that a competent contractor "should have known" was necessary — even if it was not explicitly shown in the drawings or specs. This language shifts scope gaps from the owner to the GC. When GC scope letters fail to catch those gaps and pass them to subs, the GC absorbs the cost. The $300K lead-lined glass example is a direct result of this clause operating in practice.
Scope Agent reads your full project set and flags trade gaps, conflicting drawings, and missing spec callouts in under 60 minutes.
See Scope AgentMore Articles