Risk allocation is the real subject
Most infrastructure agreements are less about the asset itself than about who absorbs surprises over a long timeline. Unforeseen site conditions, changes in law, permitting delays, supply-chain disruption, and force majeure each need a home in the contract, and the price usually reflects where they land. The structure matters as well: design-build, engineering-procurement-construction, and operations-and-maintenance contracts place design and performance responsibility in different hands. Where a government body is the owner, procurement rules and approval steps add a layer that private projects do not face. Lenders often review the contract closely and may insist on step-in rights or direct agreements before they fund.
Keeping the project record
Once work starts, the documents that decide later disputes are created every day. Keep the tender documents, technical specifications, baseline schedule and each update, change orders, and the correspondence around every request for more time or money. Daily logs, meeting minutes, and dated photographs prepared at the time usually carry more weight than summaries assembled after a disagreement surfaces. Many infrastructure contracts require written notice of a claim or delay within a set period, and a late notice can defeat a claim that was otherwise sound. Subcontracts and supply agreements should be checked to see whether they pass the same risks down the chain on matching terms.
Questions we work through early
Whether you are negotiating an infrastructure agreement or already in a dispute under one, we start with the allocation of the risks most likely to materialize on your project rather than with boilerplate. We review the dispute-resolution ladder, which in large projects may run from project meetings to a dispute board or mediation and then to arbitration, and whether each step must be completed before the next. If a public entity is involved, we check for special claim procedures and funding limits. The aim is a contract, or a claim strategy, that keeps the project moving while protecting your position if the relationship becomes adversarial.
