The bid goes out. The sub returns a number. Buyout closes. Then, six months into the job, someone finds a clause that no one read — and now you're absorbing a cost you never priced.
That's not bad luck. That's a process failure.
Arcadis data from 2026 puts the average U.S. construction dispute at $60.1 million. Errors and omissions in contract documents have been the single biggest dispute cause for 6 of the last 9 years. The same disputes. The same clause types. Different projects.
This guide covers how experienced GC estimators actually analyze contract risk before they sign — and the specific clauses that keep showing up on the wrong side of a change order.
Most GCs treat contract review as a legal function. Send it to counsel, get a redline back, sign. That approach misses the field exposure hiding inside perfectly legal language.
A lawyer will catch unenforceable indemnification clauses. They won't flag that "base plate grouting by others" is sitting inside a structural steel scope with no "other" defined. That's an estimator's catch — if they're looking for it.
Pre-construction contract analysis is about translating legal language into dollar exposure. It's not about what the clause says. It's about what it costs if things go sideways.
The firms that do this well run it as a checklist process, not a read-through. One pre-construction lead at a top-ENR Canadian GC put it plainly: "If you miss anything, they'll bill it."
These aren't hypothetical risk categories. They're the clauses that come up in disputes — again and again — on commercial ICI projects across North America.
Start here. Every subcontract scope needs to be traceable to a specific drawing sheet, spec section, or addendum — not "as per plans and specs."
That phrase — as per plans and specs — is the most cited anti-pattern in GC pre-construction. It sounds complete. It isn't. It transfers risk to whoever interprets it on a bad day.
A hospital project absorbed a $300,000 cost for lead-lined glass in an imaging suite. The spec reference existed. The scope sheet didn't call it out by name. The sub's number didn't include it. The GC held the bag under "readily inferable" language.
For every trade in your buyout, verify that:
The Scope Gap Playbook chapter on subcontract language covers how to write scope references that hold up — and the specific phrases that don't.
Watch for contract language that requires you to provide work that is "reasonably inferable" from the documents — even if it isn't explicitly shown.
This is increasingly common on CM-at-risk and design-build work. And the definition of "inferable" expands the moment a change order dispute hits.
One senior PM at a Canadian ICI GC described the pressure this creates: "Our construction management clients expect us to find the scope gaps in the design too now. They expect us to be designers and engineers."
If your contract contains "readily inferable" language, document your design assumptions at bid time. That documentation becomes your defense later.
Change orders average 8–14% of project cost on commercial work, according to Navigant data cited by the AIA. On projects with weak scope definition, that number climbs past 25%.
Your contract analysis needs to verify:
Broad-form indemnification clauses require you to indemnify the owner even for the owner's own negligence. Many states have anti-indemnity statutes that limit this — but enforcement requires you to know they apply.
Check your project's jurisdiction. Know which state statutes govern. Flag any indemnity language that goes beyond your own acts and omissions — and get legal input before signing, not after a site incident.
Insurance clauses are often copied from previous contracts without updating limits or endorsement requirements. The risk is double: you may be under-insured for this project, and you may be passing requirements to subs who can't meet them.
For every subcontract, confirm that:
Liquidated damages (LD) clauses are binary. You're either on time or you're paying — often $5,000 to $50,000 per day on commercial projects. The analysis question isn't whether LDs are fair. It's whether your schedule is realistic given the contract milestone dates.
Check the substantial completion definition. Check whether weather delays and owner-caused delays are excluded. Confirm your sub milestones align with your prime milestones — or price the float risk.
Most contracts specify a claims process: written notice within X days, then escalation, then mediation, then arbitration or litigation. Miss any step and you may waive your right to recover.
This is particularly important for recurring costs — like generator field conditioning — where the cost compounds across the job but no one submits a formal notice at the first occurrence. By the time the dispute materializes, the notice window is long closed.
Map the dispute escalation path before the project starts. Put the notice periods in your project controls calendar.
This one gets missed because it doesn't look like a contract clause. But buried in site-logistics language is often the answer to who is responsible for material damage after delivery.
On one project, a glulam beam was destroyed in a lay-down yard. Nothing in the subcontract required material protection on site. The cost — and the dispute — were avoidable with one line of contract language.
If your project has long-lead specialty materials — mass timber, curtainwall, elevator cabs — make sure the subcontract specifies who is responsible for storage, protection, and handling from delivery to installation.
A read-through is not a review. Experienced pre-con teams run structured checklists against every prime contract and every major subcontract. The checklist doesn't replace judgment — it makes sure judgment gets applied to every clause, not just the ones that stand out on a first read.
Here's a functional contract risk review checklist for GC pre-construction teams:
Run this against the prime contract first. Then run it against each major subcontract in buyout. The gaps between what the prime requires and what you've passed to subs are where your exposure lives.
Most contract risk doesn't come from exotic clauses. It comes from habits that feel efficient but aren't:
The firms that keep margin protect it through process, not relationships.
Manual contract review at bid volume doesn't scale. A 2,000-page project set, a 14-day bid window, and three active pursuits running at once — something gets skimmed.
Purpose-built AI tools for GC pre-construction can help close that gap — but not all tools are equal. Generic AI like ChatGPT can summarize language. It doesn't flag the clause type, map it to your checklist, or surface the interaction between a "readily inferable" clause and your scope sheet gap.
Provision's Risk Review runs a structured checklist against construction contracts and specifications — with 99.5% accuracy on pre-built risk checklists and 97%+ on custom checklists. It's reviewed more than $100 billion in project value across 66,000 documents. That's the kind of track record that earns trust from a VP of pre-construction, not a sales deck claim.
Provision has also processed over 1,000,000 risks across real project documents — so the checklist coverage reflects what actually shows up in disputes, not a theoretical framework.
Provision's Chat Agent lets estimators query specs, contracts, addenda, and drawings in under 20 seconds — with cited answers. If you need to know what the contract says about motor starters or who owns the trench, you don't have to manually search a 600-page spec book. You ask and get the reference.
The goal isn't to replace the pre-con team's judgment. It's to make sure the checklist actually gets run on every pursuit — not just the ones with enough time.
See how the EllisDon team used Provision to cut contract and spec review time by 80% without reducing the quality of their risk catch.
There's a right time and a wrong time for contract risk analysis.
The wrong time: after you've committed to a GMP or signed a subcontract. At that point, analysis identifies exposure you can't escape — only manage.
The right time: before you set your number. Contract risk affects contingency. It affects how you structure subcontract language. It affects whether you pursue the project at all.
Run contract risk analysis as a checkpoint in your pursuit process — after you receive bid documents, before you set strategy. The pre-issue scope review checkpoint is one of the Eight Habits that separates high-margin pre-con teams from the rest. You can read about all eight in the Scope Gap Playbook's chapter on subcontract language.
The firms with the best margins do this consistently. Not on their biggest jobs. On every job.
Construction contract risk analysis is a structured review of prime contracts and subcontracts to identify clauses that create financial exposure — including scope ambiguity, change order limitations, indemnification requirements, and liquidated damages. It's done before bid commitment to inform contingency and scope decisions.
The most common risk areas are: scope of work gaps (especially "as per plans and specs" language), "readily inferable" implied-scope clauses, change order notice period requirements, broad-form indemnification, and liquidated damages without owner-delay exclusions. Errors and omissions in contract documents have been the #1 construction dispute cause for 6 of the last 9 years, per Arcadis.
Purpose-built AI tools — like Provision's Risk Review — run structured checklists against construction contracts and specs, flagging risk clauses with cited references. This reduces manual review time by up to 80% and maintains 99.5% accuracy on pre-built risk checklists. Generic AI tools like ChatGPT lack the construction-specific context and structured output GC workflows require.
Before you set your bid number. Contract risk affects contingency, scope structure, and subcontract language. Reviewing a contract after committing to a price means you're managing exposure, not preventing it. The pre-issue scope review checkpoint — before numbers are finalized — is the highest-leverage point for contract risk analysis.
"Readily inferable" language requires the GC to provide work that is reasonably implied by the contract documents — even if it isn't explicitly shown or specified. This clause expands scope risk significantly on CM-at-risk and design-build projects. Document your design assumptions at bid time to establish a baseline if the clause is later disputed.
A scope gap is missing work coverage between trades — nobody priced the base plate grouting, the trench, or the motor starters. A contract gap is missing or ambiguous language that determines who is responsible when scope disputes arise. Both cost money. Contract gaps are often harder to recover from because they affect your legal position, not just your buyout number.
Start with the eight highest-risk clause types: scope definition, implied scope, change order rights, indemnification, insurance flow-down, liquidated damages, dispute resolution procedures, and material protection. Run the checklist against your prime contract first, then against each major subcontract. Flag gaps between what the prime requires and what you've passed down to subs — that gap is your exposure.
Risk Review runs a structured checklist across your contracts and specs — 99.5% accuracy, results in under an hour.
See Risk ReviewMore Articles