Lump sum contracts are the dominant delivery format on commercial ICI work in North America. Owners like them because the price is fixed. GCs accept them because they know how to price risk — or think they do.
The real exposure isn't in the number you bid. It's in the scope you didn't see.
On a cost-plus or GMP contract, a missed scope item becomes a conversation. On a lump sum contract, it becomes your invoice to absorb. That difference in contract structure is the single biggest reason scope gaps are a margin problem — not just a documentation problem.
According to the Scope Gap Playbook, the average U.S. construction dispute was worth $60.1 million in 2024 (Arcadis 2025 Global Construction Disputes Report). "Errors and omissions in contract documents" has been the number one dispute cause for six of the last nine years. That pattern doesn't start on site. It starts in pre-construction, when the scope package gets assembled under time pressure with incomplete documents.
"Readily inferable" is the phrase in most lump sum contracts that keeps GC lawyers busy. The clause typically reads something like: the contractor shall provide all work reasonably inferable from the contract documents as being necessary to complete the work.
In plain English: if a reasonable contractor should have known it was needed, you're on the hook for it — even if nobody drew it or specified it.
Here's what that looks like in practice. A hospital imaging suite required lead-lined glass in the partition system. The spec section for glazing referenced it obliquely. The drawings showed it only in a small-scale partition detail. The glazing sub didn't include it. The GC absorbed $300K under "readily inferable" language — because a reasonable contractor working on a hospital imaging suite should have known lead-lined glass was required.
That's not a fringe scenario. That's a documented gap from the Scope Gap Playbook, drawn from 200+ interviews with GC pre-construction and estimating professionals.
"Our construction management clients expect us to find the scope gaps in the design too now. They expect us to be designers and engineers."
— Senior PM at a Canadian ICI GC
That's the direction the market is moving. Owners are putting more scope discovery burden on the GC at bid time — and lump sum contract language is the mechanism.
Not all lump sum contracts carry equal risk. The difference is in specific language patterns. These are the ones that create the most exposure.
This is the most-cited anti-pattern from the Scope Gap Playbook. It shows up in scope sheets, subcontract schedules, and bid scopes. It looks like coverage. It isn't.
"As per plans and specs" doesn't tell the sub what they're doing. It tells them to go figure it out. When the documents conflict — and on most commercial projects they do — each sub reads the ambiguity in their favor. You end up with gaps between trades and no clear ownership.
Language like "contractor shall perform all work as described in Division 01 through Division 33" sounds thorough. But it leaves every trade gap, every cross-division conflict, and every spec-to-drawing discrepancy unresolved. The GC holds the residual.
Specific document references — section numbers, drawing numbers, revision dates — are harder to write but much easier to defend.
Many GCs use a boilerplate inferred-scope clause listing 20-30 items that are "included" by convention. The problem: these lists were written for a different project type, in a different market, with different trade norms. They don't reflect the actual documents.
A Pre-Construction Lead at a Top-ENR Canadian GC put it plainly: "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.'"
That's the peanut-butter test. If your scope sheet could apply to three different projects, it's not a scope sheet. It's a liability.
Scope gaps aren't random. They cluster in predictable places by trade and by document zone. Understanding the pattern is the first step toward catching gaps before bid day.
These examples come directly from the trade-specific scope gaps chapter of the Scope Gap Playbook.
A $400K roof cover board was missed on a $50M project. It wasn't in the roofing spec. It wasn't called out in the roof assembly details. The GC recovered the cost only through a relationship concession from the sub — not through contract language.
Masonry-storefront flashings, exterior caulking vs. interior caulking, and fire-stopping at penetrations are recurring gaps in envelope packages. Each trade reads the spec differently. The GC absorbs whatever falls between them.
Generator field conditioning is one of the highest-frequency MEP gaps on commercial projects. The equipment spec describes the generator. Nobody owns the temporary conditioning of the space during commissioning. "Millions" in disputed costs have recurred across multiple projects for the same firm.
Motor starters, fire-rated louvres, and the trench between the mechanical and electrical work are other consistent gap zones. On lump sum work, each one is a potential change order that doesn't get approved.
Grouting base plates sits in a gap between structural steel and concrete. Both subs assume the other includes it. A $45K stone-depth mismatch between civil, structural, and architectural drawings on a single slab is a documented example — caught only because someone cross-referenced all three document sets before bid day.
Anchor bolts, embeds, and miscellaneous metals scatter across three or four spec sections and rarely have a single clear owner.
Elevators, curtainwall mock-ups, lead-lined glass, and mass-timber material protection are common specialty gaps. On the mass-timber example: a $10K glulam beam was destroyed in a lay-down yard because no clause required material protection on site. Small in isolation. Multiplied across a large project, these add up fast.
The GCs with the best lump sum margins don't just bid better. They run their pre-construction differently. The Scope Gap Playbook identifies eight habits that separate low-gap firms from high-gap firms. Five of them directly reduce lump sum exposure.
Scope sheets assembled from last project's template miss what's unique about this project. The documents for this job — drawings, specs, addenda — are the only source of truth. Templates are a starting point, not a finish line.
Every scope item should cite the drawing number or spec section it comes from. Not "as per architectural drawings." Specifically: A-201, A-202, Spec Section 08 80 00. When there's a dispute, specific references win. Generic references don't.
If you wait until after award to resolve scope ambiguities with subs, you negotiate from a weak position. The subs know you need them. Front-loading buyout conversations — before you're under contract — is where you can still adjust pricing or scope coverage.
"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."
— Estimating Manager at a Canadian ICI GC
A large mechanical contractor reads a detailed spec and knows exactly what you mean. A smaller specialty sub may not. Scope descriptions need to match the reader. Assume nothing about what a sub will "obviously" include.
Before scope packages go out, run a cross-trade review. Look specifically for items that live between two spec sections, two trades, or two drawing sets. That's where the gaps are.
Provision's Scope Agent does this systematically — reading the full project document set (drawings, specs, addenda) and generating a complete scope package in under 60 minutes. It flags cross-trade conflicts and missing scope callouts that manual review typically misses under bid-day time pressure.
There's a growing temptation to paste spec sections into ChatGPT and ask it to find scope gaps. The output looks plausible. It isn't reliable.
Generic AI tools don't read drawings. They can't cross-reference a spec section against a drawing detail to find a conflict. They don't know that "miscellaneous metals" in Division 05 and "architectural metals" in Division 08 often overlap on the same project. They have no awareness of what trade typically owns the trench between MEP subs on a hospital project.
Provision's Risk Review is built specifically for construction documents. It has processed over 66,000 documents across $100 billion in project value. Its pre-built risk checklists run at 99.5% accuracy — verified against real project documents, not synthetic test sets. That's the difference between purpose-built and adapted.
A $300K scope gap is bad. But the real cost is higher.
When you absorb a scope gap on a lump sum job, you don't just lose the dollar amount. You lose the margin on that dollar amount. On a job running at 4% net margin, absorbing $300K costs you the profit on $7.5M in work.
FMI's Construction Disconnected report puts annual U.S. rework costs from miscommunication and bad project data at $31 billion. Twenty-six percent of that rework comes from communication breakdowns. Another 22% comes from bad project data. Both are preventable — but only if the gap is found before the contract is signed.
"If we could catch three scope gaps or three missed items on every scope of work, then this thing pays for itself."
— Senior PM at a Toronto mid-market developer
That's the math. Three gaps per job. Lump sum. Pre-construction is the only place where those gaps are still your choice to fix — not your obligation to absorb.
The best-performing GCs on lump sum work treat scope management as a pre-construction discipline — not a contract administration function. Here's what that looks like in practice.
Each of these steps reduces the number of scope items that survive into the lump sum contract as "readily inferable" risk.
For teams running multiple pursuits simultaneously, Scope Agent accelerates the scope package assembly step — turning 30–40 hours of manual work into under 60 minutes per bid. That's not a convenience feature. On lump sum work, it's a margin protection tool.
For teams that need to review contract language and risk clauses against the full project document set, Risk Review surfaces the specific clauses — "readily inferable," broad incorporation language, undefined scope boundaries — that create lump sum exposure. It has answered over 50,000 queries across real construction documents, with 95% verified accuracy.
If you want to see both tools applied to a real project set, request a demo and we'll walk through a document set from your pipeline.
A lump sum contract scope gap is a work item that was not explicitly included in the bid or subcontract scope but is required to complete the project. On lump sum contracts, the GC absorbs the cost of these gaps. The owner's price stays fixed.
"Readily inferable" is contract language that requires the contractor to perform all work a reasonable contractor would understand to be necessary — even if it isn't explicitly shown or specified. It is one of the most common mechanisms by which GCs absorb scope gaps on lump sum projects without recourse.
MEP (mechanical, electrical, plumbing), envelope, structural steel, and specialty trades carry the highest scope gap frequency on commercial lump sum work. Gap-prone items include generator field conditioning, roof cover board, lead-lined glass, grouting base plates, and miscellaneous metals. These items sit between spec sections or between two sub scopes.
The most effective prevention happens in pre-construction. Start scope writing from drawings, not boilerplate. Use specific document references — not "as per plans and specs." Run a cross-trade gap check before scope packages go out. Front-load buyout conversations before the prime contract is signed.
Generic AI tools can't read drawings, cross-reference spec sections against drawing details, or flag trade-boundary conflicts. Provision's Scope Agent and Risk Review are built specifically for construction documents. They process drawings, specs, addenda, and contracts together — which is what end-to-end scope gap analysis requires.
The average U.S. construction dispute was worth $60.1 million in 2024 (Arcadis 2025 Global Construction Disputes Report). Individual scope gaps on commercial ICI projects range from tens of thousands to several hundred thousand dollars per item — with the $300K–$400K range documented frequently in real GC pre-construction experience.
Pre-construction — before the prime contract is signed. Once you're under a lump sum contract, scope gaps become your cost. The only time you have leverage to price them, exclude them, or require clarification is during the bid and pre-award phase.
Scope Agent reviews your full document set and flags trade-boundary gaps in under 60 minutes.
See Scope AgentMore Articles