Federal infrastructure investment is rising. Canada recently committed $405 million to the Mackenzie Valley Highway. Major bridge, highway, and utility programs are moving into procurement across North America. That means more GCs are picking up infrastructure contract packages that look familiar on the surface but carry risks that standard commercial checklists were never built to find.
Infrastructure work is different. The documents are thicker. The public-owner clauses are more aggressive. The scope is harder to bound because conditions change underground and in the field. And the disputes, when they come, are expensive. The average North American construction dispute was worth $60.1 million in 2024, according to the Arcadis Global Construction Disputes Report. "Errors and omissions in contract documents" has ranked as the leading cause of disputes in North America across multiple reporting periods.
This checklist is built for GCs doing pre-construction review on infrastructure contracts. Work through it before bid day. Each section names the clause group, what to look for, and the questions your team should be able to answer before you commit to a price.
This is the clause that separates infrastructure from most ICI commercial work. Underground conditions are unknowable until you dig. The contract has to say who carries that risk when the geotechnical report turns out to be wrong.
If the contract is silent on differing site conditions, assume you own everything below grade. Price it accordingly or raise an RFI before bid close.
Infrastructure specs are often produced by multiple engineering disciplines over years. Conflicts between civil, structural, mechanical, and electrical drawings are common. The contract needs to say clearly how conflicts get resolved and who pays for the resolution.
Provision's RFI Agent reads drawings and specs against each other and surfaces conflicts before tender closes. It flagged more than 100 potential issues from a document set in a single hour on one recent project. That is the kind of pre-bid review that changes what you put in a qualification letter.
Infrastructure owners use liquidated damages aggressively. Public-sector clients often set LD rates that far exceed the owner's actual daily cost of delay. Review every LD clause for the following.
When the owner directs work outside the contract scope, force account provisions govern how the GC gets paid. Infrastructure contracts often include force account rate schedules established at bid time. Those rates can lock you into rates that do not cover your actual cost by the time the work happens.
Infrastructure owners can direct acceleration to recover schedule. The cost of acceleration, additional shifts, premium time, out-of-sequence work, is real and large. The contract needs to say clearly when acceleration is a compensable event.
Infrastructure contracts frequently include holdback structures, payment milestone schedules, and lien holdback rules that differ by jurisdiction. Cash flow risk on a multi-year infrastructure project can be as damaging as scope risk.
Infrastructure prime contracts typically require the GC to flow specific obligations down to every subcontractor and supplier. Gaps between what you agreed to with the owner and what your subcontract says are a direct financial exposure.
A Pre-Construction Lead at a Top-ENR Canadian GC put it directly: "If you miss anything, they'll bill it." The subcontract is your protection. Generic scope language is not protection. For a deeper look at how to write scope that holds up at buyout, the Scope Gap Playbook chapter on subcontract language covers the specific habits that separate firms with tight buyout from those that absorb change orders.
Public-sector infrastructure contracts nearly always include termination for convenience provisions that give the owner broad rights to stop the work. These clauses need careful review before you price mobilization and preliminary costs.
A manual review pass through a 400-page infrastructure contract package takes days. Provision's Risk Review ingests drawings, specs, and contracts together and surfaces clause-level risks with 99% accuracy on risk identification. It cut contract review time by 80% across the document sets it has processed, covering more than $100 billion in project value.
Every finding is backed by an exact citation: the clause, section, and page number. Risk Review flags severity levels, generates RFI text for owner clarification, and can re-run instantly when addenda arrive. For infrastructure teams managing long tender periods with multiple document updates, that re-run capability alone changes the workload on bid day.
Provision's pre-built Tariff Checklist and Go/No Go review types are built for exactly the kind of go-or-no-go decision a VP of Pre-Construction makes at first document review. Infrastructure teams can also build custom checklists that map to their own standard of care on public-sector work.
The eight sections above cover the clause groups that consistently drive infrastructure disputes. But every project has its own wrinkles. Before you finalize your review, add rows for the following project-specific items:
Use Provision's Risk Review to run a custom checklist against your infrastructure document set. Firms that use it on pre-construction review have cut review time by 80% and found risks that manual review missed on more than a million risk findings to date.
If you are starting your infrastructure pre-construction process and want a broader picture of scope gap risk by trade, the Scope Gap Index shows what Scope Agent flagged across 1,290 scope packages from 24 projects. The findings on Division 33 (Utilities) and Division 31 (Earthwork) are directly relevant to infrastructure work.
Infrastructure contracts include clause groups that rarely appear in commercial work: differing site conditions provisions, force account rate schedules, owner-directed acceleration rights, and public-sector termination for convenience language. Standard commercial checklists miss these. Infrastructure review requires a separate pass built around those clause types.
A differing site condition (DSC) clause allocates risk when underground or hidden conditions differ from what the contract documents represent. Without a DSC clause, the GC typically owns every subsurface condition regardless of what the geotechnical report showed. DSC clauses are the primary protection for GCs pricing earthwork and underground utility scopes on infrastructure projects.
Readily inferable language requires GCs and subs to include work that a reasonable contractor would infer is necessary, even if the drawings and specs never explicitly call it out. One GC absorbed a $300,000 lead-lined glass scope gap on a hospital project under this language. On infrastructure work, the same exposure appears in utility connections, excavation support, and environmental handling.
"Errors and omissions in contract documents" has ranked as the leading cause of North American construction disputes across multiple Arcadis reporting periods. The average North American dispute was worth $60.1 million in 2024. Getting the contract review right before bid day is the highest-leverage pre-construction activity a GC can invest in.
Yes. Provision's Risk Review ingests drawings, specs, and contracts together and flags clause-level risks with 99% accuracy on risk identification. It supports custom checklists, so infrastructure teams can build review templates tailored to public-sector contracts. Every finding is cited to the exact clause and page. Risk Review has processed more than $100 billion in project value across its platform.
Force account work is owner-directed extra work outside the contract scope, paid based on actual cost plus a fixed markup. Infrastructure contracts often set those markup rates at bid time. If the rates are too low, the GC absorbs overhead and equipment costs on extra work. Review force account markup rates and notice requirements before you sign the contract.
Provision's Risk Review handles contract and spec review for infrastructure work. The RFI Agent finds drawing-to-spec conflicts before tender closes. The Scope Gap Playbook chapter on subcontract language covers flow-down clause best practices. The Scope Gap Index shows real-world scope flags by MasterFormat division.
Risk Review flags clause-level exposures in your full document set, cited to the exact page.
See Risk Review