Errors and omissions don't show up on bid day. They show up at buyout — or worse, in the field. By then, the lump sum price is locked and the GC owns the gap.
Arcadis ranked "errors and omissions in contract documents" as the top cause of construction disputes in North America in its 2024 Global Construction Disputes Report. The average dispute value for that year: $60.1 million. That's not a rounding error. That's a company-altering number.
This guide breaks down how errors and omissions create lump sum exposure, what a disciplined review process looks like, and where technology is changing what's possible before bid day.
In a cost-plus or GMP structure, errors in the documents can often be treated as a change. In a lump sum, the baseline price is fixed. If the drawings miss a system, the GC typically eats it.
"Readily inferable" language makes this worse. Contracts often require GCs to include work that a competent contractor "should have known" was needed — even when it's missing from the drawings. Courts and arbitrators have interpreted this clause broadly. One Senior PM at a Canadian ICI GC put it plainly: "Our construction management clients expect us to find the scope gaps in the design too now. They expect us to be designers and engineers."
That's the real risk in a lump sum. You're not just pricing what's shown. You're pricing what's implied.
The big ones rarely announce themselves during bid review. They hide in drawing-to-spec conflicts, in scope sheets that reference the wrong revision, and in trade packages that rely on what the last sub "assumed."
Here are real examples from GCs interviewed for The Scope Gap Playbook:
These aren't catastrophic project failures. They're the slow bleed that erodes margin across a portfolio — one scope gap at a time.
The standard lump sum contract review process at most mid-market GCs looks something like this:
The problem isn't effort. It's throughput. A 2,000-page project manual reviewed under a two-week bid schedule — by two estimators already running three other pursuits — will miss things. Every time.
A 2018 study by PlanGrid and FMI found that poor project data and communication breakdowns drove $31.3 billion in annual U.S. rework costs, with those two causes accounting for 48% of all rework. The documents were the source of the problem then. In 2026, the documents are bigger, the bid windows are shorter, and the teams haven't grown.
Across 200+ interviews with GCs conducted for The Scope Gap Playbook, the firms with the tightest margins did the same things consistently. They weren't doing more work. They were doing the right work earlier.
Start with what's actually shown. The drawings reveal what the spec assumed. Boilerplate templates reveal what a different project assumed — often on a different building type.
Scope sheets that say "as per plans and specs" are the single most-cited anti-pattern in lump sum disputes. Name the drawing number. Name the spec section. If you can't cite it, you can't enforce it.
The worst time to discover a sub's scope assumption is during buyout. The second-worst time is during a change order dispute. Surface sub interpretations before bid day — in writing.
Scope templates are a starting point. A Pre-Construction Lead at a Top-ENR Canadian GC described it as 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.'"
Use the site walk to verify what the drawings show. Site conditions regularly conflict with drawing assumptions on renovation and phased work. Document every discrepancy.
A sophisticated mechanical sub needs different scope language than a small drywall shop. As one 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." Tailor your package to what that sub will exploit.
An exclusions list tells the owner what you're not doing. A clarifications section tells them what you assumed. Both matter. Most scope sheets have the first. Few have the second.
Before the scope goes to subs, someone who didn't draft it reads it against the drawings. Ten minutes of review here prevents ten weeks of RFIs later.
Some trades carry disproportionate scope-gap risk on lump sum projects. The following are the highest-frequency gaps documented in The Scope Gap Playbook's trade-specific chapter.
Geotech compaction requirements, the five-foot transition zone between structural and non-structural fill, and excavator unit-rate language are chronic sources of scope disputes. If the geotech report and the civil drawings don't agree, the GC is usually holding the difference.
Base plate grouting, slab assembly conflicts between structural and architectural drawings, and concrete pumping requirements (who supplies the pump?) are frequently unassigned in lump sum packages.
Embeds and anchor bolts (cast-in vs. post-installed), hoisting and rigging responsibilities, and miscellaneous metals scattered across multiple spec sections are common omission sites.
Generator field conditioning costs have generated "millions" in disputes across multiple projects at GCs interviewed for the playbook. Add fire-rated louvres, motor starters, and lighting controls to the list of MEP items that routinely fall between trade scopes.
The $400K roof cover board example cited above came from the envelope trade. Add masonry-to-storefront flashings, interior vs. exterior caulking, and fire-stopping in penetrations — all of which regularly appear in neither the envelope sub's scope nor the GC's self-perform package.
Lead-lined glass in medical imaging rooms, curtainwall mock-up requirements, and mass-timber material protection (the $10K glulam destroyed in a lay-down yard with no contractual protection clause) represent the long tail of specialty scope exposure.
Manual contract review is bottlenecked by time and attention span. A reviewer who has read 600 pages of spec by hour four is not the same reviewer who read page one. That's not a failure of competence. It's a failure of throughput.
Provision's Risk Review runs a structured risk checklist against the full contract and spec package — every clause, every section, every page. It flags risks and cites the exact location. Accuracy on pre-built checklists is 99.5%. Review time drops by 80% compared to manual review.
That's not a replacement for legal counsel or pre-construction judgment. It's a first pass that ensures nothing gets buried in page 847 of the spec book.
For scope packages, Scope Agent reads the full project set — drawings, specs, and contracts together — and generates trade-by-trade scope-of-work packages in under 60 minutes. Internal validation shows 97% accuracy on scope item extraction. A manual estimator doing the same exercise on the same documents typically runs at 91.3% accuracy — and takes four days instead of one hour.
Provision has reviewed over $100 billion in project value and processed more than 100,000 documents. The patterns across those projects — the gaps that repeat, the trades that hide scope, the clauses that generate disputes — are what the models are trained to find.
If you want to see how GCs are using Provision in pre-construction today, the EllisDon case study is a concrete starting point. Their team used Provision to identify $1.8M in risk exposure before bid day.
A practical review checklist for lump sum contract risk covers five areas. This isn't exhaustive — your legal team should review indemnification and insurance provisions — but it's the framework that matters most during pre-construction.
The VPs of pre-construction with the cleanest project handoffs share one habit: they don't let scope sheets reach subs until the drawings have been read, not skimmed.
One Director of Pre-Construction at a mid-market Southeast GC described the organizational gap this way: "Pre-con is working in the scope sheet world and project management is working in the scopes of work." The translation failure between those two documents is where scope gaps become change orders.
A VP-level standard for lump sum risk review looks like this:
If your pre-con team is running four pursuits simultaneously and doing this manually, they aren't doing all four of these things on all four jobs. That's not a criticism. That's math.
Tools like Provision's Chat Agent let estimators ask direct questions about the project documents — drawings, specs, contracts, RFIs, addenda — and get cited answers in under 20 seconds. That's not a search function. It's a way to close the gap between a 2,000-page project manual and a two-week bid window.
To go deeper on scope language, sub-specific tailoring, and the anti-patterns that produce disputes, read the full Scope Gap Playbook chapter on subcontract language and scope.
Errors and omissions refer to mistakes, conflicts, or missing information in contract documents — drawings, specs, and scope packages. In a lump sum contract, the GC typically absorbs the cost of these gaps because the price is fixed at award. Arcadis has ranked this category as the top cause of construction disputes in North America.
In most lump sum structures, the GC bears primary risk for errors and omissions in the documents they priced. "Readily inferable" contract language extends this further — requiring GCs to include work that a competent contractor should have anticipated, even when it's not explicitly shown in the drawings.
The primary defenses are pre-bid document review, drawing-to-spec conflict identification, specific document references in scope sheets, and written clarifications submitted with the bid. Catching gaps before bid day is the only reliable protection. After award, options are limited.
Readily inferable language requires a GC to include work that is implied by the contract, even if not explicitly shown. Courts and arbitrators have interpreted this broadly. A $300,000 lead-lined glass omission in a hospital imaging suite — not shown on drawings — was absorbed by a GC under this clause in a documented case from The Scope Gap Playbook.
The highest-frequency gaps appear in MEP (generator field conditioning, motor starters, lighting controls), envelope (roof cover boards, masonry-to-storefront flashings, fire-stopping), concrete (base plate grouting, pumping responsibilities), and specialty trades (lead-lined glass, curtainwall mock-ups). These regularly fall between trade scopes in lump sum packages.
AI tools like Provision's Risk Review run structured checklists against the full contract and spec package, flagging risks at the exact clause or page. Accuracy on pre-built checklists is 99.5%, with an 80% reduction in review time. This allows pre-construction teams to cover more ground — faster — without relying on a single estimator's attention span across a 2,000-page document set.
Individual scope gaps on commercial projects range from $10,000 (material protection omissions) to $400,000 (missed roof cover board) to over $300,000 (lead-lined glass in a hospital imaging suite). Across a portfolio, these add up to margin erosion that compounds year over year — often without appearing as a single, visible line item.
Risk Review flags errors and omissions at the exact clause — 80% faster than manual review.
See Risk ReviewMore Articles
