Errors and omissions in contract documents are not a new problem. They have been the leading cause of construction disputes in the U.S. for six of the last nine years, according to the Arcadis 2025 Global Construction Disputes Report. That's not a trend. That's a pattern.
And the stakes are rising. The average U.S. construction dispute hit $60.1M in 2024. When a project ends up in arbitration or litigation, the root cause is almost always traceable to something that was wrong — or missing — in the original contract documents.
This guide is written for chief estimators and VPs of pre-construction at GC firms who are tired of discovering errors after they've already become claims. It covers where these gaps hide, what they actually cost, and how to build a document review process that catches them before bid day.
Design documents are produced under budget pressure and time pressure. Coordination between disciplines is imperfect. Specifications get copied from previous projects. Addenda get issued days before bid close.
The result is a project set that contains conflicts, gaps, and ambiguities — and a contract that typically assigns the risk of those gaps to the GC through "readily inferable" language.
That language is the real problem. Once you sign, a court or arbitrator may find you responsible for work that was implied by the documents — even if it wasn't explicitly specified. As one Senior PM at a Canadian ICI GC put it: "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 expectation has teeth. A $300K lead-lined glass scope item was once absorbed by a GC under exactly this kind of language — the hospital imaging suite required it, the specs didn't explicitly call it out, and the "readily inferable" clause did the rest.
Not all errors are the same. Understanding which type you're dealing with changes how you find it and how you price the risk.
These happen when two drawings say different things. The architectural plan shows a wall in one location. The structural drawing shows a beam that conflicts with it. The MEP routing assumes a ceiling height that doesn't exist in the civil model.
A $45K stone-depth discrepancy on a single slab — caught during pre-construction at a mid-market GC — came from a conflict between the civil/structural drawings and the architectural documents. Two disciplines, two assumptions, one gap that would have landed on the GC at field.
Spec sections that reference a product type but don't define the standard. Sections that list materials without installation requirements. Division 01 language that overrides Division 03 without a clear hierarchy.
MEP work is especially prone to this. Generator field conditioning costs have become a recurring dispute point on projects where the mechanical spec doesn't explicitly assign responsibility. The same pattern shows up with motor starters, fire-rated louvres, and lighting controls. For more detail on trade-specific gaps, see the trade-specific scope gap chapter of Provision's Scope Gap Playbook.
Work that the drawings show and the specs describe — but that no one is contractually assigned to do. This is where scope gaps are born.
A $400K roof cover board scope gap on a $50M project existed because the specs described the assembly and the drawings showed the roof build-up, but no sub was explicitly required to include the cover board in their scope. The GC absorbed it. They recovered through a relational concession from the sub — not through contract language.
That is not a risk management strategy. That is luck.
"As per plans and specs" is the most dangerous phrase in construction. It sounds complete. It isn't. It pushes interpretation downstream — to a sub who will interpret it in their favor, to a PM who will interpret it in yours, and eventually to a claims consultant who will charge both of you to figure out who was right.
The GCs with the tightest margins have moved away from this language. They write specific document references into scope packages: not "as per plans and specs" but "as per Structural Drawing S3.02 Rev 2 and Specification Section 03 30 00."
The FMI Construction Disconnected report puts annual U.S. rework costs from miscommunication and bad project data at $31 billion. That figure is not abstract — it's built from real project losses that started in pre-construction.
Here's where the exposure concentrates on a typical commercial GC project:
Change orders on commercial projects typically run 8–14% of total project cost, according to Navigant research republished by the AIA. On projects with weak scope definition, that number climbs above 25%.
The GCs that keep change orders at or below budget don't do this by accident. They have a review process that runs from bid receipt to sub-scope issuance. It's systematic, not heroic.
This sounds obvious. It isn't standard practice. Most estimating teams divide the documents by trade, review only what's relevant to their scope, and miss the inter-discipline conflicts that live in the gaps between those silos.
Someone on the pre-construction team — a senior estimator or pre-con manager — needs to read across disciplines. Structural against architectural. MEP against civil. Specifications against drawings. That cross-read is where errors surface.
The pre-bid walk is not a courtesy. It's a scoping tool. But you can only use it as one if you've already read the documents carefully enough to know what questions to ask.
Walk the site with a discrepancy log in hand. Note conditions that don't match the drawings. Ask the architect or owner's rep about conflicts on-site. Get answers in writing — through addenda if possible, through email if not.
The anti-pattern that shows up most consistently in GC risk reviews: scope packages drafted from a template for a previous similar project, not from the actual drawings in front of you.
As one Pre-Construction Lead at a Top-ENR Canadian GC described it: "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.'"
Templates are a floor, not a ceiling. Start with your standard structure. Then rewrite every scope item against the actual drawings and spec sections for this project. Reference specific drawing numbers and specification sections. Do not copy-paste from the last hospital or the last office build.
For a structured starting point, Provision's scope of work template is built around this drawing-first approach.
Before scope packages go out, run a structured risk review. This means checking every scope against a pre-built checklist of known contract language traps: notice provisions, warranty terms, delay clause exposure, indemnification scope, and payment condition triggers.
This is where most GCs lose time. Reviewing 200-page spec books and 50-page subcontract templates manually takes hours per pursuit. On a busy bid calendar, it often doesn't happen at all — or it happens in five minutes before bid close.
Provision's Risk Review runs this checklist automatically against your actual project documents. It covers pre-built risk items at 99.5% accuracy and custom checklist items at 97%+. Across more than $100 billion in project value reviewed, it has surfaced over 1,000,000 risks that manual review missed or skipped.
Before sub scopes go out — not after — have a senior pre-construction team member review each scope package for completeness. Check that every trade is covered, every drawing reference is correct, and every clarification from the pre-bid walk is reflected.
This is the last gate before scope gaps become contract gaps. It takes 30 minutes per trade if your scope packages are well-structured. It saves multiples of that in RFIs and change orders.
Construction document review has a volume problem. A commercial project set can run 2,000 pages of specifications, 500+ drawings, plus addenda, RFIs, and supplementary conditions. No estimator reads all of it. The parts they skip are where errors hide.
Purpose-built construction AI can change the economics of this review. Not by replacing experienced estimators — by making it possible to review the full document set, not just the parts one person has time for.
Provision's Chat Agent answers specific questions about drawings, specs, contracts, and addenda in under 20 seconds — with cited answers drawn from the actual documents. It has answered over 50,000 queries across real project sets. It doesn't replace the judgment call. It eliminates the manual search that eats the time that judgment call needs.
For scope package generation, Scope Agent reads the full project set and produces a complete scope-of-work package in under 60 minutes. That's 30–40 hours of manual work compressed into one. The packages are drawn directly from the project's drawings and specifications — not from a generic template.
For a closer look at how this plays out on a real project, the EllisDon case study shows how one of Canada's largest GCs used Provision to surface $1.8M in risk that traditional review missed.
The best pre-construction teams treat errors and omissions review as a standing process — not a bid-specific scramble. They have a checklist. They assign ownership. They set a deadline before bid day, not on it.
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." The subs are sharper. The GCs need to be sharper too.
The firms with the tightest change order rates share a few consistent practices, drawn from the research behind Provision's Scope Gap Playbook:
These are not expensive practices. They are disciplined ones. The GCs that adopt them consistently outperform their peers on margin — because they catch errors before those errors become disputes.
Errors and omissions are mistakes, conflicts, or missing information in a project's drawings, specifications, or contract language. They can include drawing conflicts between disciplines, incomplete spec sections, unassigned scope items, or ambiguous language that leaves responsibility unclear. They are the leading cause of U.S. construction disputes, according to the Arcadis 2025 Global Construction Disputes Report.
Responsibility depends on the contract. Design errors typically fall on the owner or their design team. But "readily inferable" language in many GC contracts shifts some or all of that risk to the GC. This is why pre-construction review matters: you need to know what you're taking on before you sign.
When a gap or conflict in the documents surfaces during construction, someone has to pay for the fix. If the contract assigns that risk to the GC, or if the GC failed to raise it before bid close, the cost comes out of the GC's contingency or margin. That is how a document error becomes a change order — or a claim.
"Readily inferable" clauses require the GC to include work that a reasonable contractor should have recognized as necessary — even if it wasn't explicitly specified. It is a major source of scope gap risk. The $300K lead-lined glass omission referenced in this article was absorbed under exactly this kind of clause. Understanding how it applies to your project set is a core part of contract document review.
The most effective approach is a structured pre-bid document review that cross-checks drawings against specifications, assigns all scope items explicitly, and uses specific document references — not generic "as per plans and specs" language. Running a formal risk checklist before scope packages go out adds a second layer of protection.
Manual review of a full commercial project set — drawings, specifications, addenda, and subcontract language — typically takes 30 to 40 hours per pursuit for an experienced estimator. Purpose-built AI tools like Provision's Risk Review and Scope Agent compress that work significantly, allowing teams to run thorough reviews on more pursuits without adding headcount.
MEP trades consistently generate the most scope gap disputes — generator field conditioning, motor starters, trench responsibility, and fire-rated louvres are recurring problem areas. Envelope and specialty trades (elevators, curtainwall, lead-lined glass) follow closely. Site and earthwork scopes also carry high gap exposure, particularly around geotech compaction and excavation unit rates.
Risk Review checks your project documents against 99.5%-accurate risk checklists in a fraction of manual review time.
See Risk ReviewMore Articles
