When RFI volume spikes on a project, the instinct is to look at the field. Maybe the super isn't coordinating well. Maybe the subs are fishing for change orders. Maybe the design team is slow to respond.
Those things happen. But they're rarely the root cause.
Most high-RFI projects trace back to a single failure point: scope that wasn't defined clearly enough at bid. The field is just where the gap surfaces. The gap itself was created weeks or months earlier — in the estimate room, in the scope package, in the subcontract.
This article breaks down how that happens and what pre-construction teams can do to stop it.
A scope gap is any work required to complete the project that isn't clearly assigned to a responsible party. It's not always missing work. Sometimes it's work that two subs both think the other is doing. Sometimes it's work that the spec references but no scope package captures. Sometimes it's work that's "readily inferable" — and your subcontract language just handed it to you.
Scope gaps come in three forms:
All three end up as field RFIs. And all three were preventable at bid.
Here's the chain reaction most pre-con teams know but rarely map out explicitly:
A Pre-Construction Lead at a Top-ENR Canadian GC put it plainly: "If you miss anything, they'll bill it."
That billing starts with an RFI.
These aren't hypotheticals. They're anonymized examples drawn from over 200 GC interviews conducted for The Scope Gap Playbook.
A hospital imaging suite required lead-lined glass. The spec called for it. The drawings showed it. Nobody's scope package explicitly assigned it. The GC absorbed the cost under "readily inferable" language in the subcontract. One RFI, one scope gap, $300K out of pocket.
On a $50M project, roof cover board wasn't captured in the envelope scope package. The gap was discovered in the field. The GC recovered the cost only through a relational concession from the sub — not because the subcontract gave them any leverage.
Civil, structural, and architectural drawings disagreed on slab stone depth. Nobody reconciled them at bid. The discrepancy surfaced as a field RFI. The resolution cost $45K and two weeks of coordination time.
Each of these started as a scope gap at bid. Each ended as a field problem — an RFI, a change order, or a dispute.
For more trade-specific examples like these, see the trade-specific scope gaps chapter of The Scope Gap Playbook.
It's the most common anti-pattern in scope writing. The scope package says "as per plans and specs." The sub prices it that way. Nobody checks whether the plans and specs actually align — or whether they contradict each other.
This phrase doesn't define scope. It defers it. And deferred scope becomes an RFI the moment the field needs an answer.
A Director of Pre-Construction at a Mid-Market Southeast GC described the disconnect this way: "Pre-con is working in the scope sheet world and project management is working in the scopes of work."
The gap between those two worlds is where RFIs live.
The Pre-Construction Lead at a Top-ENR Canadian GC calls 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.'"
Most scope packages don't pass that test.
Based on the same 200+ GC interviews, The Scope Gap Playbook identifies the habits that consistently produce high-RFI projects. These aren't edge cases — they show up across firm size, geography, and project type.
Each of these habits produces ambiguity. Ambiguity produces RFIs.
The firms with the lowest RFI volume on delivery don't manage RFIs better in the field. They prevent them in pre-con. Here's what they do differently.
Scope packages built from templates carry the previous project's assumptions. Scope packages built from the actual drawing set reflect what this project actually requires. The difference shows up in field RFI counts.
Review the drawings first. Build the scope to match. Then apply the template as a floor — not a starting point.
Don't write "as per plans and specs." Write "per Structural Drawing S-301, Rev 2, and Spec Section 03300." Specific references leave no room for interpretation disputes. They also make RFI responses faster when questions do arise.
Scope gaps between bid and buyout are a major RFI driver. When what the sub priced doesn't match what the GC's scope package says, the field pays for it. Front-loading buyout conversations — before award, not after — closes those gaps while there's still budget flexibility to address them.
A national mechanical contractor reads scope differently than a regional HVAC shop. The level of detail required in the scope package should match the sub's sophistication — and their history of RFI and change order behavior on past projects. Generic scope packages ignore this entirely.
Before the scope package goes out, someone who didn't write it should read it against the drawings. Not for grammar. For gaps. This is the checkpoint most teams skip — and it's the cheapest place to catch a $300K problem.
These five habits map directly to the Eight Habits framework in The Scope Gap Playbook, which covers the full set of practices that separate low-gap from high-gap pre-construction teams.
Not all trades produce equal RFI volume. Some scope areas are structurally more prone to gaps — because the work crosses trade boundaries, because the spec language is ambiguous, or because the drawings from different disciplines conflict.
MEP is particularly high-risk. Generator field conditioning costs alone have generated "millions" in disputed claims, recurring across multiple projects at the same firms. The pattern is consistent: the scope doesn't assign it, both parties assume the other owns it, and the field RFI turns into a change order battle.
See the full breakdown in the trade-specific scope gaps chapter.
The firms taking RFI reduction seriously in 2026 are attacking it at the source — in pre-con, not in the field.
A few specific shifts are happening:
Tools like Scope Agent are part of this shift. Scope Agent reads the full project set — drawings, specs, and addenda — and generates a complete scope-of-work package in under 60 minutes. It surfaces cross-discipline conflicts, flags missing trade coverage, and produces structured outputs that estimators can review and refine. That's work that used to take 30–40 hours manually — and often didn't happen at all on smaller pursuits.
Teams using Provision have reviewed over $100 billion in project value and processed more than 66,000 documents. The scope gaps that surface aren't edge cases — they're consistent, trade-specific patterns that repeat project to project.
If your team is managing RFI volume reactively — tracking them in a log, managing response time, escalating to the design team — you're working the symptom. The fix is earlier. It's in the scope package, at bid, before award.
A Senior PM at a Toronto Mid-Market Developer put it this way: "If we could catch three scope gaps or three missed items on every scope of work, then this thing pays for itself."
That math works. Every scope gap you close at bid is an RFI you never have to write, a change order you never have to fight, and margin you don't have to give back.
For a deeper look at how scope gaps form and how to close them systematically, read The Scope Gap Playbook — built from 200+ GC interviews and organized around the habits that separate low-gap firms from high-gap ones.
To see how Scope Agent works on a real project set, book a demo with the Provision team.
Most high-RFI projects trace back to scope gaps created during bid. When scope packages are vague, built from templates rather than drawings, or use language like "as per plans and specs," ambiguity gets baked in. That ambiguity surfaces in the field as RFIs — often weeks or months after the gap was created.
A scope gap leaves work unassigned or ambiguously assigned. When that work needs to happen in the field, the team issues an RFI to get a direction or establish responsibility. If the subcontract mirrors the vague scope package, that RFI often turns into a change order dispute.
MEP, concrete, steel, and envelope work consistently generate the most scope-gap-driven RFIs. Interface work — where two trades share a boundary — is especially high-risk. Generator field conditioning, base plate grouting, roof cover board, and masonry-storefront flashings are common examples where scope falls through the cracks.
Many subcontracts include language requiring subs to perform work that is "readily inferable" from the contract documents — even if it isn't explicitly called out in the scope package. In practice, this means the GC absorbs cost for anything the documents imply but the scope doesn't assign. The $300K lead-lined glass example is a real case of this playing out on a hospital project.
Five habits have the biggest impact: starting scope packages from drawings rather than templates, using specific document references instead of "as per plans and specs," front-loading buyout conversations, tailoring scope detail to sub sophistication, and running a pre-issue scope review before the package goes out.
Scope Agent is Provision's AI tool for general contractors. It reads the full project set — drawings, specs, and addenda — and generates a complete scope-of-work package in under 60 minutes. It surfaces cross-discipline conflicts, flags missing trade coverage, and produces structured outputs that replace 30–40 hours of manual scope writing. Fewer scope gaps at bid means fewer field RFIs after award.
According to the Arcadis 2025 Global Construction Disputes Report, the average U.S. construction dispute value is $60.1M. "Errors and omissions in contract documents" has been the #1 dispute cause for 6 of the last 9 years. FMI estimates $31 billion in annual U.S. rework costs tied to miscommunication and bad project data — scope gaps are a primary driver of both.
See how Scope Agent builds complete scope packages from your drawings in under 60 minutes.
See Scope AgentMore Articles
