Most teams treat RFIs as a field problem. They're not. By the time a sub sends an RFI, the real damage happened weeks earlier — in the scope package.
When a scope package is vague, ambiguous, or missing trades, subcontractors fill the gaps themselves. Each sub fills them differently. The result: conflicting assumptions, disputed work, and a stream of RFIs that slow down every project.
According to the Arcadis 2025 Global Construction Disputes Report, the average U.S. construction dispute is now worth $60.1M. "Errors and omissions in contract documents" has been the single biggest cause for six of the last nine years. That's not a field execution problem. That's a pre-construction problem.
The good news: scope package quality is controllable. This guide breaks down exactly how.
A scope gap is any item of work that's present in the construction documents but absent — or ambiguous — in the scope package. The sub either misses it or prices it differently than the GC intended.
Here's what that looks like in practice:
Each of those starts as a scope gap. Each ends as an RFI — or worse, a change order.
As one Pre-Construction Lead at a Top-ENR Canadian GC put it: "If you miss anything, they'll bill it."
For a deeper breakdown of how these gaps form and compound by trade, the trade-specific scope gap chapter of the Scope Gap Playbook is worth reading before your next buyout.
Firms with the best margins don't just catch scope gaps — they prevent them. Here's the framework, drawn from 200+ interviews with GC estimators, pre-construction managers, and VPs across North America.
Boilerplate scope templates are a starting point. They are not a scope package. Every project has unique conditions — conflicts between disciplines, addenda changes, site constraints — that a generic template won't capture.
High-performing teams read the drawings first. They build the scope package from what's actually in the documents, then layer in the template language.
Phrases like "as per plans and specs" are the most cited anti-pattern in scope writing. They don't tell the sub what's in scope. They invite every sub to draw their own line.
The better approach: reference specific drawing numbers, spec sections, and addenda. If a sub disputes the scope, you have a cited document — not an argument about what "plans and specs" means.
The best time to resolve a scope question is before the sub signs the contract — not after they've started work. Teams that front-load buyout conversations close scope gaps before they become RFIs.
This means meeting with key subs early, walking the scope, and confirming assumptions in writing. It's slower on the front end. It's much faster on the back end.
A scope template is the minimum. Every project should push past it based on the actual documents. Junior estimators who copy-paste previous scopes verbatim — without checking the current drawings — are one of the most common sources of recurring scope gaps.
The pre-bid walk is not a courtesy. It's where GCs catch what drawings don't show: existing conditions, access constraints, material storage limitations. Teams that use the pre-bid walk as a scoping exercise write tighter packages and submit fewer change requests later.
A tier-1 mechanical sub reads documents differently than a small specialty trade. The level of detail in your scope package should match who's reading it.
As one Pre-Construction Lead at a Top-ENR Canadian GC described it — what he called the "peanut-butter test" — the scope has to spell out every step: "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.'"
Exclusion lists tell subs what's not in scope. Clarification sections tell them what is — and how you expect it to be executed. Both matter. Teams that rely only on exclusions leave too much room for interpretation.
Before any scope package goes to a sub, it should go through a second set of eyes. This isn't a five-minute review. It's a structured check against the drawings, specs, and prior addenda to confirm nothing was missed.
The firms with the lowest RFI volumes treat this checkpoint as non-negotiable — not something they do when they have time.
For every habit that reduces RFIs, there's a corresponding bad habit that produces them. These are the patterns that show up most often in pre-construction shops with chronic scope problems:
As an Estimating Manager at a Canadian ICI GC noted: "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."
The days of a vague scope package holding together through mutual goodwill are over. Subs are reading documents more carefully. GCs need to write packages that hold up to that scrutiny.
Not all trades produce the same RFI risk. These are the areas where scope packages are most likely to have gaps — and where the downstream RFI volume is highest:
The trade-level detail in your scope packages is where RFI prevention actually happens. For a full breakdown by trade — including specific gap patterns and dollar examples — see the trade-specific chapter of the Scope Gap Playbook.
One of the most common structural problems in GC pre-construction is a hand-off gap between the estimating team and the project management team.
As a Director of Pre-Construction at a Mid-Market Southeast GC described it: "Pre-con is working in the scope sheet world and project management is working in the scopes of work."
Those two documents should tell the same story. When they don't, the field fills the gap — with RFIs, change orders, and disputes.
The fix is structural: scope packages need to be detailed enough that they survive the hand-off intact. That means PMs can read the scope and know exactly what was and wasn't included — without calling the estimator.
FMI's Construction Disconnected report puts annual U.S. rework costs at $31 billion. Twenty-six percent of that rework traces back to communication breakdowns. Twenty-two percent traces back to bad project data. Most of that originates in pre-construction.
The eight habits above are the right approach. The problem is time. Most pre-construction teams are running too many pursuits with too few people to execute them consistently.
A manual scope package takes 30–40 hours per bid. That's not a realistic timeline when you're tracking six pursuits simultaneously. Something gets rushed. Usually the scope review.
Provision's Scope Agent generates complete scope-of-work packages from construction documents in under 60 minutes. It reads the drawings, specs, and addenda together — not just one document at a time — and surfaces trade conflicts, missing scope items, and spec callouts that manual review misses under time pressure.
A Senior PM at a Toronto Mid-Market Developer put it directly: "If we could catch three scope gaps or three missed items on every scope of work, then this thing pays for itself."
Provision has reviewed over $100 billion in project value across 66,000+ documents. The EllisDon case study shows what that looks like in practice — $1.8M in identified risk on a single project.
For GCs managing RFI volume and contract risk simultaneously, Risk Review runs a structured risk checklist across your contracts and specs — with 99.5% accuracy on pre-built checklists — flagging the ambiguous language that generates disputes before it reaches the field.
And when the field does send an RFI that requires finding a specific clause in a 2,000-page spec book, Chat Agent returns a cited answer in under 20 seconds. It doesn't replace the scope package — but it removes the delay when questions still come in.
RFI volume is a proxy for scope package quality. But the real metric is margin.
Change orders on commercial projects average 8–14% of project cost (Navigant, republished by AIA). On projects with weak scope packages, that number climbs past 25%.
The difference between a 10% change order rate and a 15% change order rate on a $20M project is $1M. Most of that difference is recoverable — in pre-construction.
Better scope packages don't just reduce RFIs. They protect margin at buyout, reduce dispute exposure, and give PMs a document they can actually use to manage the field.
That's the business case. If your pre-construction team is spending 30–40 hours per bid on manual scope writing, see how Scope Agent changes that timeline.
Most RFIs trace back to scope gaps in the pre-construction documents — ambiguous scope packages, missing trade assignments, and conflicts between drawings and specifications that weren't resolved before subcontracts were issued. The Arcadis 2025 Global Construction Disputes Report found "errors and omissions in contract documents" has been the top dispute cause for six of the last nine years.
A detailed scope package defines exactly what each subcontractor is responsible for — by reference to specific drawings, spec sections, and addenda. When subs know precisely what's in scope and what isn't, they have fewer questions during construction. Fewer ambiguous assumptions means fewer RFIs.
Manual scope packages typically take 30–40 hours per bid. That's the core bottleneck. Provision's Scope Agent generates complete scope packages from construction documents in under 60 minutes — covering drawings, specs, and addenda together.
MEP, envelope, and specialty trades consistently generate the highest RFI volumes. These trades have the most interdependencies with other scopes — and the most ambiguous hand-off points in typical scope packages. Steel-concrete interfaces and roofing assembly ownership are two of the most common recurring triggers.
Readily inferable is a contract standard that holds subcontractors responsible for work that a skilled contractor should infer from the documents — even if it isn't explicitly stated. In practice, what's "readily inferable" is frequently disputed. Vague scope packages push more items into that gray zone, which increases RFI and change order exposure. See the Scope Gap Playbook chapter on subcontract language for specific examples.
Yes — but only if the tool is purpose-built for construction documents. Generic AI tools like ChatGPT don't have the construction context or structured output formats that pre-construction workflows require. Provision's Scope Agent reads the full project set — drawings, specs, and addenda — and surfaces conflicts and gaps that manual review misses under time pressure.
Change orders average 8–14% of project cost on commercial work. On projects with weak scope packages, that number climbs past 25%. The difference between those two rates on a $20M project is more than $1M. Most of that difference is addressable in pre-construction — before the first sub mobilizes.
Scope Agent builds complete scope packages from your documents in under 60 minutes.
See Scope AgentMore Articles