You're two months into a commercial project. RFIs are piling up. The sub says the scope didn't cover it. The scope letter says "as per plans and specs." Nobody wins.
Here's the part that frustrates most project managers: those RFIs were written before ground broke. They were written the day someone copied last project's scope letter, swapped the trade name, and sent it out with the bid package.
This guide is for PMs who are tired of fighting fires they didn't start. It explains why scope letters produce RFIs, what the specific failure patterns look like, and what you can do at buyout to stop it.
Most RFI root-cause analysis stops at the symptom: a sub asked a question, the answer wasn't in the documents, so someone had to respond. That's not root cause. That's triage.
True root cause sits in pre-construction. Specifically, it sits in scope letters that were written too fast, copied from the wrong project, or never cross-referenced against the actual drawing set.
A Director of Pre-Construction at a mid-market Southeast GC put it directly: "Pre-con is working in the scope sheet world and project management is working in the scopes of work." That gap — between what pre-con thought they wrote and what the field team receives — is where RFIs are born.
When the handoff from pre-con to project management is clean, RFI volume drops. When it's not, you spend the back half of a project arguing over what was "clearly inferable."
These aren't hypothetical failure modes. They're the patterns that show up repeatedly when GC teams trace RFIs back to their origin documents.
This is the single most common anti-pattern in subcontractor scope letters. It's also the most expensive.
When a scope letter defers to the full document set without specifying what's included and what's excluded, you've created an interpretive void. The sub fills that void with their lowest-cost reading. You fill it with your understanding of the design intent. Neither of you is wrong — you just disagree.
That disagreement becomes an RFI. Or a change order. Or a dispute.
A Pre-Construction Lead at a top-ENR Canadian GC described it 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.'"
Generic incorporation language is not a scope. It's a placeholder that defers conflict instead of resolving it.
Every GC does this. The logic is sound: why rewrite a scope letter for a trade you've scoped a hundred times?
The problem is that scope letters carry embedded assumptions from their source project. Site conditions differ. Drawing details differ. Spec sections differ. When you copy a scope letter from a hospital project into a school project, you inherit those assumptions — and none of them have been validated against the current document set.
The $45K stone-depth conflict described in The Scope Gap Playbook — a mismatch between civil, structural, and architectural drawings on a single slab — came from exactly this pattern. Nobody checked whether the copied scope reflected what was actually on the new drawing set.
Most scope letters are better at listing exclusions than at defining what's actually included. "Elevator not included" is clean. "Mechanical rough-in as per spec section 15000" is not — especially when Section 15000 has twelve sub-sections and only three of them apply to this trade package.
Exclusions protect you from scope creep. But they don't tell the sub what they're expected to build. That requires clarifications — specific, affirmative statements about what's in scope, tied to drawing numbers and spec sections.
The Estimating Manager at a Canadian ICI GC said 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 reading your scope letters more carefully than they used to. Your clarifications need to match that level of scrutiny.
A scope letter written from specs alone — without checking the drawings — will miss coordination issues. Every time.
Drawings and specs don't always agree. Architectural drawings show one thing. Structural drawings show another. The spec says a third. If your scope letter is built from specs and the sub prices from drawings, you have a conflict that hasn't surfaced yet. It will surface. Usually as an RFI, sometimes as a claim.
The $300K lead-lined glass gap on a hospital imaging suite — absorbed by the GC under "readily inferable" language — started here. The spec referenced radiation protection requirements. The scope letter didn't. The drawings showed the room type but not the wall assembly. Nobody connected the three.
For PMs inheriting a project from pre-con, this is the hardest gap to spot. The scope letter looks complete. The problem only becomes visible when you compare it against the full drawing set line by line.
This isn't a soft problem. The financial exposure is real and well-documented.
The Arcadis 2024 Global Construction Disputes Report puts the average North American dispute value at $60.1 million. Errors and omissions in contract documents rank as the leading cause of those disputes in North America. That's not a design problem or a field problem — it's a pre-construction documentation problem.
A 2018 PlanGrid and FMI study projected that $31.3 billion in annual U.S. rework traced back to miscommunication and bad project data. Of that, 26% was attributed to communication breakdowns and 22% to bad project data — nearly half of all rework costs tied to information problems that start before construction begins.
On commercial work, change orders typically run 8–14% of project cost (Navigant/AIA). On projects with weak scope definition, that number exceeds 25%.
Those aren't abstract statistics. They're the budget overruns PMs spend the second half of every project explaining to owners.
The good news: PMs don't have to accept scope letters as-given. There are specific, repeatable steps you can take at buyout — and before buyout — to reduce RFI volume.
Pull the scope letter for each trade. Open the relevant drawing sheets. Check whether what the scope letter says aligns with what the drawings actually show.
Flag every instance where the scope letter defers to a spec section without referencing the drawing detail. Those are your highest-risk items.
This takes time. But it's time you spend once at buyout, not repeatedly across four months of RFIs.
One of the eight habits documented in The Scope Gap Playbook is front-loading the buyout conversation. That means bringing subs in early — before they've priced the job on their own interpretation — and walking them through the scope letter section by section.
The goal isn't to intimidate. It's to surface disagreements while they're still cheap. A phone call to clarify whether a sub included motor starters costs nothing. A change order after mobilization costs real money.
Scope letter templates exist for a reason. They capture standard trade scopes, required inclusions, and baseline exclusions. Use them.
But treat them as a starting point. Every project has unique conditions — site constraints, spec deviations, drawing conflicts, addenda changes. Those conditions need to be reflected in the scope letter, not overridden by the template.
If a scope letter would make sense for any commercial project your firm has built in the last five years, it's not specific enough for this one.
Before any scope letter goes to a sub for buyout, it should pass through a review — ideally by someone who has read the drawing set, not just the spec.
This is the pre-issue checkpoint habit. It doesn't need to be a formal process. It can be a 30-minute call between the PM and the estimator. The question to ask: "Does this scope letter reflect what's actually on the drawings?"
That question, asked consistently, catches a significant share of the gaps that become RFIs.
Most PMs track RFI volume. Fewer track RFI origin. Start doing both.
For every RFI that results in a scope interpretation, note which scope letter clause it connects to. After 20 or 30 RFIs, you'll see patterns. The same trade packages, the same clause types, the same gaps will repeat.
That data is a feedback loop for pre-con. It tells your estimating team which scope letter sections are producing the most field conflict — and where the next project's templates need to change.
Manual scope letter review is slow. A senior estimator reviewing a full scope package against a 2,000-page drawing set takes 30–40 hours per bid. That's before addenda, before RFI prep, before buyout calls.
That's the problem Scope Agent was built to solve. It reads the full project set — drawings, specs, and contracts together — and generates a complete, trade-by-trade scope package in under 60 minutes. Every item is cited to the exact document and section it came from. That citation trail is what makes the scope letter defensible when a sub disputes it in the field.
Provision has reviewed over $100 billion in project value and processed more than 100,000 documents. The EllisDon case study shows what that looks like in practice: a GC using Scope Agent to catch gaps that would otherwise surface as change orders or RFIs months later.
Technology helps with document volume. It doesn't replace the PM's judgment on what matters for this project, this sub, this owner relationship. The two work together — better data from pre-con, better decisions in the field.
If your team is reviewing contracts and specs for risk as part of buyout prep, Risk Review cuts that time by 80%. Every risk is cited to the exact clause and page. That same precision — clause-level citation — is what closes the gap between what a scope letter says and what a sub can dispute.
For PMs who need fast answers from a 1,500-page spec book mid-project, Chat Agent returns cited answers in under 20 seconds. It reads drawings, specs, contracts, RFIs, and addenda — the full project set, not just the spec book.
The common framing is that scope letters are a pre-con deliverable. PMs receive them; they don't write them.
That framing is part of the problem. Scope letters govern the subcontracts that PMs spend the next 18 months managing. If the scope letter has gaps, the PM deals with the consequences — in RFIs, in change orders, in field disputes, in owner conversations.
PMs who engage with scope letters at buyout — who read them against the drawings, who walk subs through the clarification items, who build a pre-issue checkpoint — consistently see lower RFI volume and cleaner project delivery.
If you want to see how firms are building that discipline into their pre-construction process, the Scope Gap Playbook is worth reading. It's built from 200+ interviews with GC teams across North America. The patterns it documents are the same ones showing up in your RFI log right now.
To see how Scope Agent produces the cited, trade-by-trade scope packages that close these gaps before buyout, request a demo.
Most RFIs trace back to scope letter ambiguity written during pre-construction — not to field conditions or sub errors. The most common triggers are generic incorporation language ("as per plans and specs"), scope letters copied from prior projects without being checked against the current drawing set, and missing cross-references between drawings and specs.
A scope letter creates RFIs when it leaves room for multiple interpretations. If the scope says "mechanical rough-in per spec section 15000" without specifying which sub-sections apply and which drawing details govern, the sub and the GC will read it differently. That disagreement surfaces in the field as an RFI — or a change order.
At buyout — before subcontracts are executed. That's the last point where scope gaps can be closed without a cost impact. A scope clarification at buyout is a conversation. The same clarification after mobilization is a change order negotiation.
Trade coordination gaps — where drawings from two different disciplines conflict and the scope letter doesn't resolve which governs — tend to produce the largest RFIs. The $300K lead-lined glass gap and the $400K missed roof cover board documented in The Scope Gap Playbook both came from this pattern: the spec implied the work, the drawings didn't show it clearly, and the scope letter didn't call it out.
AI tools like Scope Agent reduce RFI risk by reading the full project set — drawings, specs, and contracts together — and generating scope packages where every item is cited to its source document. That citation trail is what makes scope letters defensible when subs dispute them. It doesn't replace PM judgment, but it catches document-level gaps before they reach the field.
Pre-con writes scope letters. PMs manage the consequences. In practice, the firms with the lowest RFI volume treat scope letter review as a shared responsibility — pre-con produces the draft, PMs validate it against the drawings at buyout before subcontracts are signed. That one checkpoint catches a large share of the gaps that otherwise become field disputes.
Log each RFI against the subcontract trade and the specific clause — or absence of a clause — that the RFI is interpreting. Over 20–30 RFIs, patterns emerge: the same trade packages, the same clause types, the same gap categories. That data feeds back to pre-con as a template improvement priority for the next project.
See how Scope Agent builds cited, trade-by-trade scope packages in under 60 minutes.
See Scope AgentMore Articles
