Introduction
A government infrastructure project may begin with a fixed budget, an ambitious completion date and a carefully negotiated contract. Yet years later, the contractor may be claiming additional costs while the government insists that the contractor must honour the original price and timeline.
The real legal question is often not simply who caused the delay. It is who had agreed to bear the consequences of that delay under the contract.
Background
Infrastructure projects depend upon several moving parts, including land availability, statutory approvals, utility shifting, financing, design approvals and coordination between different authorities.
A contractor may have the manpower, machinery and technical capability to complete a project but still be unable to proceed because the required site or approval has not been made available. Conversely, delays may arise from inadequate mobilisation, poor planning or failure by the contractor to meet contractual milestones.
Court's Findings / Legal Analysis
Infrastructure contracts commonly contain provisions dealing with extensions of time, variations, force majeure, compensation events and termination. The interpretation of these provisions can determine whether a delay gives rise merely to additional time or also to a monetary claim.
Force majeure cannot automatically become a defence for every unexpected event. The event must fall within the contractual framework and satisfy the applicable requirements concerning notice and causation.
Why the Judgment Matters
Infrastructure disputes demonstrate why risk allocation can be more important than the headline value of a contract. A poorly allocated risk can transform an otherwise profitable project into years of litigation.
The problem becomes particularly difficult where several delays overlap. A project may experience land delay, design changes and contractor inefficiencies simultaneously. Determining which event actually caused the delay can then become a major evidentiary exercise.
Key Takeaways
Contractors should maintain contemporaneous records of delays, instructions, approvals and site conditions.
Government authorities should clearly allocate responsibility for land, approvals, utilities and design changes.
Contracts should distinguish between employer-caused delay, contractor-caused delay and genuinely uncontrollable events.
Conclusion
Infrastructure contracts are ultimately contracts for managing uncertainty. The strongest contract is not necessarily the longest one, but the one that answers a basic question before construction begins: if something unexpected happens, who bears the consequence?
