A scope gap doesn't announce itself. It hides in a set of bid documents — between a drawing note and a spec section nobody cross-referenced. By the time it surfaces on site, it's already a change order, a dispute, or a relationship problem with a sub you need on the next job.
The numbers in 2026 are hard to ignore. Construction Executive pegs the average scope dispute at $340K per affected project. Arcadis puts the average U.S. construction dispute value at $60.1M — and "errors and omissions in contract documents" has been the single largest cause for six of the last nine years. FMI estimates that miscommunication and bad project data drive $31 billion in annual rework costs across U.S. construction.
None of this is bad luck. Scope gaps are caused — by specific habits, specific document patterns, and specific pre-construction shortcuts. Here's how they compound, and what the best GCs do differently.
Most GC teams treat scope gaps as a field problem. They're not. They're a pre-construction problem that gets paid for in the field.
The gap is created the moment a scope of work document doesn't reflect what the drawings actually show — or assumes a sub will "figure it out." By bid day, it's already in the estimate. By award, it's in the subcontract. By the time a sub raises it on site, the GC is on the hook.
As one Pre-Construction Lead at a Top-ENR Canadian GC put it: "If you miss anything, they'll bill it."
The mechanics are straightforward. A scope sheet uses boilerplate language — "as per plans and specs." A sub prices what they see in their typical scope of work. The gap between those two assumptions is where the change order lives.
Some subcontracts include language that requires subs to perform work "reasonably inferable" from the contract documents. GCs lean on this language when a dispute surfaces. But in practice, it rarely holds the way they expect.
One of the clearest examples from Provision's research: a hospital imaging suite where $300K in lead-lined glass was omitted from the mechanical sub's scope. The GC argued it was inferable from the drawings. The sub disagreed. The GC absorbed the cost.
A Senior PM at a Canadian ICI GC described the shift happening across the industry: "Our construction management clients expect us to find the scope gaps in the design too now. They expect us to be designers and engineers."
The expectation is rising. The tolerance for "we missed it" is dropping. See the full breakdown of how contract language creates scope exposure in Chapter 6 of the Scope Gap Playbook.
Provision's research across 200+ GC interviews identified a consistent set of behaviors that produce avoidable scope gaps. None of them are exotic. Most are habits that feel efficient in the moment.
The most common anti-pattern. It feels complete. It isn't. It transfers zero actual scope information to a sub and creates maximum ambiguity at buyout. When the dispute comes, nobody can prove what was included.
Every project has a different document set. Copying a scope from a previous hotel job for a new hotel project feels like a time saver. It's a risk loader. The drawings are different. The spec sections are different. The trade breakdown may be different. What you miss is project-specific — and that's always where the gap is.
A scope sheet gets reviewed by a PM at 3:00 PM on bid day — an hour before submittals close. Nobody has time to find the $45K stone-depth conflict between the civil and architectural drawings. Nobody catches the missing roof cover board. The scope goes out with the gaps still in it.
Longstanding sub relationships are an asset. But the market has changed. As one Estimating Manager at a Canadian ICI GC observed: "We have less subs who just kind of have a gentleman's agreement… they've become more quick to clarify that we're not including that one piece of scope."
Subs are protecting their margins too. Assuming they'll absorb scope ambiguity is a budgeting error.
Scope sheets are for describing work. When PMs add liability language, indemnification terms, or payment conditions to a scope document, the result is a hybrid that does neither job well — and creates conflict at execution.
Industry averages are useful. Project-level examples are more useful. These are real gaps documented across GC teams in the Provision research base.
Each of these was avoidable. Each started in pre-construction. The $400K roof cover board wasn't a construction mistake — it was a scope document that never described the full roof assembly.
Change orders aren't random. They follow a pattern. The scope of work produced at bid — and refined during buyout — is the template for everything that follows. When that template has gaps, change orders are predictable.
The Arcadis data supports this. "Errors and omissions in contract documents" drives more disputes than any other cause. Not site conditions. Not owner-directed changes. Documents. Which means the solution is also in documents — in how thoroughly you read them before bid day.
FMI's breakdown puts 26% of rework cost on communication breakdowns and 22% on bad project data. That's nearly half of $31 billion in annual rework tied to information problems — most of which originate in pre-construction document review.
There's a specific failure mode that shows up at buyout. A Director of Pre-Construction at a Mid-Market Southeast GC described it plainly: "Pre-con is working in the scope sheet world and project management is working in the scopes of work."
Pre-con builds a scope sheet for estimating. The PM writes a subcontract scope of work for execution. If those two documents don't match — if the estimating assumptions don't translate — you have a gap between what was priced and what's now contractually required. That gap is a change order waiting to happen.
The fix isn't more meetings. It's better handoff documents — scope packages that include specific drawing and spec references, trade-specific assumptions, and explicit exclusions. Not just "as per plans and specs."
From 200+ GC interviews, Provision identified the consistent practices of firms that hold margin and minimize change order exposure. These aren't complex. They're disciplined.
The scope document should reflect this project's drawings — not a template modified from a previous job. Every scope line should trace back to a specific drawing or spec section. If it can't, it's probably wrong.
Replace "as per plans and specs" with "per Structural S-201, Sheet 14, Grid 5-C." Specific references survive disputes. Boilerplate doesn't.
Don't wait until post-award to start sub conversations. The pre-bid walk isn't a courtesy — it's a scoping tool. Walk subs through scope assumptions before bids close. Identify gaps before they're locked into the estimate.
Exclusions tell a sub what's not included. Clarifications tell them how you're reading a contested scope item. Both matter. Most scope documents only have one.
Before a scope goes out — to a sub or into a subcontract — have someone review it specifically for gaps, not just errors. A checklist-based review against the actual document set takes less than an hour. It's the cheapest insurance in pre-construction.
The full framework for all eight habits is documented in The Scope Gap Playbook, built from 50+ in-depth GC interviews.
Manual scope review at the depth needed to catch a $300K lead-lined glass gap takes time most pre-con teams don't have. On a competitive bid with a two-week window, a Chief Estimator running three pursuits simultaneously can't spend 30-40 hours reading a 2,000-page document set for a single project.
That's the actual tradeoff. Not "should we review the docs?" — everyone knows the answer. It's "how do we review them thoroughly when we're bidding six jobs at once?"
Provision's Scope Agent generates complete scope-of-work packages directly from construction documents — drawings, specs, and addenda — in under 60 minutes. It replaces 30-40 hours of manual takeoff and scope drafting per bid. More importantly, it surfaces the kind of cross-discipline conflicts — slab assembly discrepancies, unassigned specialty scopes, missing spec callouts — that produce six-figure change orders when they go undetected.
The Risk Review product applies pre-built checklists to contract documents with 99.5% accuracy. Provision has reviewed over $100 billion in project value and processed more than 66,000 documents. Across those documents, the platform has identified more than 1,000,000 individual risks — scope gaps, contract exposures, and document conflicts that would otherwise reach the field.
For teams that need to query a 2,000-page spec book fast, Chat Agent pulls cited answers from the full project document set in under 20 seconds. That's the tool that answers "is roof cover board spec'd in Division 07?" before bid day — not after.
You can see how these tools work together in the EllisDon case study, where the team avoided $1.8M in project exposure using Provision's pre-construction workflow.
A Pre-Construction Lead at a Top-ENR Canadian GC uses a simple standard to evaluate a scope document: "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.'"
If a sub can read a scope item and still have a reasonable question about what's included, the scope isn't done. That's the standard. It's also the standard that prevents most avoidable change orders.
Not every gap can be closed by better writing. Some come from document conflicts the author didn't know existed. That's where a systematic document review — either manual or AI-assisted — becomes the differentiator between firms that hold margin and firms that absorb change orders.
If your firm is bidding commercial ICI work in 2026, here's a practical checklist before the next scope package goes out:
The $340K average dispute cost is a real number. The $300K lead-lined glass and the $400K roof cover board are real projects. The good news is that both were preventable — with the right process, the right document review, and the right tools.
If you want to see how Provision's Scope Agent performs on a live project set, request a demo and we'll run it against your documents.
A scope gap is work that's shown in the drawings or specs but not assigned to any trade in the subcontract scope of work. It's a missing line between what the documents require and what any sub has been contracted to deliver. Scope gaps become change orders when the work shows up on site and no sub owns it.
A sub prices what their scope document says. If the drawings require more work than the scope describes, the sub stops, raises the issue, and submits a change order. The GC either pays the change or disputes it. Either way, margin is at risk and schedule is affected.
Construction Executive pegs the average scope dispute at $340K per affected project. Arcadis puts the average U.S. construction dispute at $60.1M — with "errors and omissions in contract documents" as the top cause for six of the last nine years.
MEP work generates the most scope disputes — particularly generator conditioning, motor starters, fire-rated louvres, and lighting controls. Specialty items like lead-lined glass, curtainwall mock-ups, and elevator allowances are also frequently unassigned. Structural-architectural conflicts around slabs, embeds, and anchor bolts are common in concrete and steel scopes.
Start scope documents from drawings — not boilerplate. Use specific drawing and spec references instead of "as per plans and specs." Run a pre-issue review checkpoint before any scope goes to a sub. Front-load buyout conversations with subs before bids close. Write clarifications, not just exclusions.
AI tools like Provision's Scope Agent read the full construction document set — drawings, specs, and addenda — and generate structured scope packages in under 60 minutes. They surface cross-discipline conflicts and unassigned scopes that manual review misses under time pressure. The result is fewer gaps entering the estimate and fewer change orders during construction.
Many subcontracts require subs to perform work "reasonably inferable" from the contract documents. GCs use this clause when a disputed scope item wasn't explicitly described. In practice, it rarely resolves disputes in the GC's favor — as the $300K lead-lined glass example shows. Explicit scope coverage is more reliable than relying on inferred obligation language.
Scope Agent generates complete scope packages from your project documents in under 60 minutes.
See Scope AgentMore Articles
