Most GCs don't lose margin because they got the takeoff wrong. They lose it because someone missed a clause buried in the supplementary conditions — or assumed the owner's standard spec language was standard.
The average U.S. construction dispute now carries a value of $60.1 million, according to the Arcadis 2025 Global Construction Disputes Report. Errors and omissions in contract documents have been the top cause for 6 of the last 9 years. That's not a design problem. That's a pre-construction problem — and it's preventable.
This guide gives estimators and pre-construction leads a repeatable process for identifying contract risk in construction specs before you sign anything.
Most GCs treat contract review and spec review as separate exercises. They're not — at least not from a risk standpoint.
The general conditions set the rules. But the specs — particularly Division 1 and the supplementary conditions — define the scope, shift responsibilities, and quietly expand your obligations. A requirement buried in a spec section can be just as binding as a clause in the contract itself.
The classic trap: a GC receives a 2,000-page project manual. Estimators pull the trade sections they need for takeoff. Nobody reads Section 01 50 00 in full. Nobody flags the sentence that makes the GC responsible for third-party commissioning services. By the time the project is awarded, that cost isn't in anyone's number.
That's how a $300K lead-lined glass package gets missed on a hospital imaging suite. The GC absorbed it under "readily inferable" language — language that was in the spec, not the contract. (Source: The Scope Gap Playbook, Provision, 2026.)
The supplementary conditions are the highest-risk document in almost any project set — and the most frequently skimmed.
They modify the general conditions. That means every deviation, addition, or deletion to the standard contract terms lives here. Owners and their lawyers use this document to shift risk. It's the section that:
Read these line by line. Flag anything that adds scope, limits your rights, or introduces a financial penalty. Don't delegate this to a junior estimator — this document requires someone who knows what standard looks like so they can spot what isn't standard.
Division 1 is where owners hide operational requirements that have real cost implications. Most estimators treat it as boilerplate. That's the mistake.
A Pre-Construction Lead at a Top-ENR Canadian GC put it plainly: "If you miss anything, they'll bill it."
Division 1 sections that carry the most cost and scope risk include:
Don't just read these sections. Check whether they conflict with what the trade specs say. Conflicts between Division 1 and a trade section almost always resolve in favor of the more stringent requirement — and that's a cost you need to catch before bid day.
Risk in construction specs rarely lives in one place. It's distributed — a requirement mentioned in the structural drawings, modified in the civil specs, and re-stated differently in Division 1.
This is where scope gaps form. The Scope Gap Playbook research found a $45K stone-depth mismatch between civil/structural and architectural drawings on a single slab. Neither document was wrong in isolation. The conflict only appeared when someone read them side by side.
A Director of Pre-Construction at a Mid-Market Southeast GC described the systemic problem: "Pre-con is working in the scope sheet world and project management is working in the scopes of work." The handoff is where the risk hides.
For GCs managing large project sets, Provision's Chat Agent can search across drawings, specs, contracts, RFIs, and addenda in under 20 seconds — with citations to the exact page and clause. That's useful when you need to verify whether a Division 1 requirement appears anywhere else in the document set.
These two phrases are the most expensive words in construction contracts. They shift scope onto the GC without specifying what that scope is.
"Readily inferable" language holds the GC responsible for work that a competent contractor should have anticipated — even if it's not explicitly shown or called out. Courts and arbitrators have consistently upheld this interpretation. The practical result: you own the gap.
A Senior PM at a Canadian ICI GC described the current environment: "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 $300K lead-lined glass package mentioned earlier was absorbed under exactly this kind of language. The spec referenced the imaging suite. The drawings showed the room. Nobody connected the two until the sub's exclusion list came in after award.
When you find this language, stop and ask: what work could this clause pull in that isn't explicitly priced? If you can't answer that question, you have a risk item that needs a clarification or exclusion before you submit.
For a deeper look at how this language shows up in subcontract scope, see Chapter 5 of The Scope Gap Playbook.
Generic risk reviews produce generic findings. The most useful spec reviews are organized by trade — because the risks cluster differently depending on what you're looking at.
Based on patterns identified across hundreds of project reviews, these are the trade sections that consistently hide contract risk:
Check who bears the risk for subsurface conditions. Look for compaction specs that conflict with geotech recommendations. Watch for the "five-foot transition" clause — the grey zone between the site contractor's scope and the structural backfill spec. That gap has cost GCs real money.
Who pays for concrete pumping? Is grouting of base plates explicitly included in the structural steel spec or the concrete spec — or neither? Slab assembly conflicts between the structural and architectural drawings are common and expensive.
Generator field conditioning is one of the most consistently disputed MEP items. The spec often calls for it. The sub rarely includes it. The GC is usually stuck in the middle. Also check: motor starters, fire-rated louvres, lighting controls, and who owns the trench between trades.
These trade-specific patterns are documented in detail in Chapter 5 of The Scope Gap Playbook.
Roof cover board is a recurring gap — a $400K miss on a $50M project is documented in the Scope Gap Playbook research. Fire-stopping at the envelope interface is another. Caulking scope — interior vs. exterior, who owns the masonry-to-storefront transition — creates disputes at buyout every time it's not explicitly assigned.
A structured checklist beats a narrative review every time. Checklists are faster, auditable, and don't rely on one person's memory or expertise on a given day.
The categories your checklist should cover:
Provision's Risk Review runs this kind of structured check automatically — flagging every risk item with a citation to the exact clause, section, and page. It covers 99% of pre-built checklist items and cuts contract and spec review time by 80%. Every finding is traceable. Nothing is paraphrased.
That matters because a paraphrased risk summary can introduce errors. A citation doesn't.
Finding a risk item is only useful if you do something with it. That means documenting every flagged item in a format that survives the handoff from pre-con to project management.
A risk log should include:
This log becomes your pre-bid risk summary for leadership review. It also becomes the starting point for your subcontract scope packages — so the risks you flagged at the spec review stage get addressed at buyout, not in a change order six months later.
That's the connection most GCs miss. The spec risk review and the scope package are not separate documents. They should inform each other. If you want to see how Provision handles that workflow end to end, book a demo and we'll walk through a live project set.
Even experienced teams fall into habits that undermine the spec review process. The most common ones, drawn from 200+ GC interviews in The Scope Gap Playbook:
Construction contract risk in specs refers to clauses, language, or scope definitions that expose the GC to unpriced cost, legal liability, or schedule penalties. It appears most often in supplementary conditions, Division 1, and trade-specific spec sections that include ambiguous scope language or risk-shifting terms.
According to the Arcadis 2025 Global Construction Disputes Report, errors and omissions in contract documents have been the #1 dispute cause for 6 of the last 9 years. The average U.S. dispute value in 2026 is $60.1 million. Most of these disputes originate in pre-construction document review failures.
"Readily inferable" language holds the GC responsible for work that a competent contractor should have anticipated — even if it's not shown on the drawings or called out in the specs. It's one of the most common sources of scope gaps and change order disputes. Any contract containing this language requires a detailed scope cross-check before bid.
The supplementary conditions carry the highest risk overall. In the spec book, Division 1 — especially sections covering summary of work, temporary facilities, quality control, and closeout — is where owners embed operational requirements with real cost implications. Trade sections for MEP, envelope, and earthwork consistently produce the most costly scope gaps.
A thorough manual review of a mid-size commercial project spec book takes 30 to 40 hours per bid. That's the baseline. AI-assisted tools like Provision's Risk Review cut that time by 80% — covering the same checklist items with citations to the exact clause and page, so estimators spend time on decisions, not document hunting.
A contract review focuses on the legal and commercial terms — indemnification, payment, termination, insurance. A spec risk review focuses on scope obligations and cost exposure embedded in the technical documents. Both are required. Doing only one leaves risk on the table. The two reviews are most effective when done in parallel and cross-referenced at the end.
Build a risk register with five fields for every flagged item: source document and clause, nature of the risk, estimated dollar exposure, recommended action, and owner with a deadline. This log becomes your bid-day summary for leadership and your starting point for subcontract scope packages at buyout.
Risk Review flags every contract risk with a citation to the exact clause and page. 80% less review time.
See Risk ReviewMore Articles
