Where Infrastructure Projects Break Down
EPC contracts are among the most commercially consequential agreements in international business. A single contract may govern a project worth hundreds of millions of dollars, running over several years, involving multiple subcontractors, lenders, and regulatory bodies across different jurisdictions. The risks embedded in that contract, and the question of which party bears them, will determine not just the economics of the project but whether it can survive the disruptions that almost always arise in large infrastructure and construction work.
The disputes that emerge from failed EPC contracts are correspondingly complex, involving detailed technical records, competing expert evidence on delay causation and cost attribution, and financial claims spanning years of project execution. In international arbitration, EPC disputes consistently rank among the largest and most protracted proceedings by both claim value and duration. They are also among the most preventable, not because projects do not face genuine disruption, but because the contractual framework governing risk allocation is frequently inadequate to handle that disruption when it arrives.
For project sponsors, contractors, and the lenders and investors who finance large infrastructure and energy projects, understanding where EPC contracts most commonly generate disputes is an essential input into how these agreements are negotiated. This note examines four areas where risk allocation in EPC contracts most consistently fails.
Scope Definition and the Performance Obligation Problem
The most fundamental source of EPC disputes is a mismatch between what the sponsor believed it was buying and what the contractor believed it was obligated to deliver. This mismatch almost always originates in the scope definition provisions of the contract, and it almost always surfaces when something unexpected happens mid-project.
EPC contracts typically impose a single-point responsibility on the contractor: to design, procure, and construct a facility that meets specified performance criteria, on time and within budget. The contractor’s obligation is outcome-focused rather than input-focused, which in principle protects the sponsor from the risk of design errors, procurement failures, and construction deficiencies. In practice, the breadth of that obligation depends entirely on how precisely the performance criteria and the scope of work are defined.
Where the employer’s requirements are drafted broadly, as they frequently are in early-stage projects where the design has not been fully developed, the contractor will argue that work falling outside the literal description of the scope is a variation entitling it to additional time and cost. The sponsor will argue that the contractor’s single-point obligation encompasses everything necessary to achieve the specified performance outcome, regardless of whether it was individually itemised. This disagreement, replicated across dozens or hundreds of individual scope items over the life of a project, generates the variation and change order disputes that dominate EPC arbitration.
The legal position under most governing laws is that the contractor’s obligation is defined by the contract documents read as a whole, including the employer’s requirements, the technical specifications, and any agreed design documentation. Where those documents are inconsistent or incomplete, tribunals must interpret the parties’ intentions from the contractual matrix, which is an exercise that routinely produces outcomes that neither party anticipated at the time of signing.
For project sponsors and their advisors, the commercial lesson is that the employer’s requirements document is as commercially important as the pricing mechanism. An underspecified technical scope, accepted at contract execution in the interest of meeting a commercial deadline, will generate cost and time claims throughout the project life. For contractors, the equivalent lesson is that a scope accepted without adequate technical due diligence, on the basis that the single-point obligation can be managed through aggressive variation claims, is a strategy that creates as much dispute risk as it seeks to manage.
Liquidated Damages and Liability Caps: The Provisions That Determine Financial Exposure
Two provisions in every EPC contract determine the financial boundaries of dispute: the liquidated damages clause and the overall liability cap. Both are negotiated intensively at contract execution. Both are frequently structured in ways that create more uncertainty than they resolve.
Liquidated damages (LDs) for delay are intended to pre-agree the sponsor’s loss arising from late completion, providing certainty for both parties and removing the need to prove actual loss in the event of a dispute. In principle, a well-calibrated LD clause benefits both parties: the sponsor has a quantified remedy, and the contractor has a defined and capped exposure for delay. In practice, LD clauses generate disputes on multiple fronts.
The first is whether the delay is the contractor’s responsibility at all. Most EPC contracts distinguish between contractor-caused delays, which attract LDs, and employer-caused or neutral delays, which entitle the contractor to an extension of time and, depending on the contract, to additional cost recovery. Where multiple causes of delay operate concurrently, the question of which party bears responsibility for the critical path delay, and in what proportion, is one of the most technically and legally complex questions in construction arbitration. The outcome depends on a detailed analysis of the project programme, the contractor’s delay notices, and expert evidence on delay causation, none of which the LD clause itself resolves.
The second issue is the relationship between the LD cap and the overall liability cap. Most EPC contracts limit aggregate contractor liability to a defined percentage of the contract price, typically between ten and thirty percent. Where the LD cap and the overall liability cap are not clearly coordinated, disputes arise about whether LDs paid or accrued count toward the overall cap and what remedy the sponsor has if LDs are exhausted but losses continue to accrue. For sponsors of large infrastructure projects, an LD structure that is exhausted early in a prolonged delay period may provide far less protection than it appeared to at the time of negotiation.
For project sponsors and lenders who rely on EPC contracts to underwrite financial projections, the strategic implication is to model the LD structure against realistic delay scenarios before contract execution, not after. A cap set at ten percent of contract price against a project with a leveraged financing structure and committed revenue obligations may be wholly inadequate to cover actual loss in the event of significant delay. For contractors, the equivalent discipline is to understand exactly what conduct triggers LD liability and to ensure that the notice and extension of time machinery is followed precisely, since procedural failures in delay notification are a recurring basis on which contractors lose extension of time entitlements that are factually justified.
Variation and Change Order Mechanisms: Where Claims Accumulate
Variation claims are the most common source of cost escalation and relationship breakdown in EPC projects. They arise when the contractor performs work that it considers to fall outside the contractual scope, or when the sponsor instructs changes to the design, specification, or programme. How the contract handles those claims, procedurally and commercially, determines whether they are resolved efficiently or accumulate into a dispute that overshadows the project itself.
Most EPC contracts require the contractor to submit variation claims within a defined notice period after becoming aware of the event giving rise to the claim. Failure to give timely notice, under many standard forms including the FIDIC suite, operates as a bar to the claim entirely, regardless of its substantive merit. Time-bar provisions are strictly enforced in international arbitration, and the consequences for contractors who have performed significant additional work without complying with notice requirements can be severe.
The commercial problem is that notice obligations are frequently treated as administrative formalities rather than substantive contractual requirements. Project managers focused on delivery may not prioritise contractual notices. Claims may be informally flagged to the sponsor’s representative without meeting the formal requirements of the contract. By the time a formal dispute arises, the contractor may have accumulated months of additional work that is contractually time-barred, regardless of whether the sponsor was substantively aware of the issue.
For contractors operating under EPC contracts in infrastructure and energy projects, the discipline of contemporaneous claims management, maintaining a live record of potential variation events, issuing notices promptly and in compliance with contractual requirements, and quantifying claims as they arise rather than at project completion, is not a legal nicety. It is the foundation of the contractor’s financial recovery. For sponsors, the equivalent consideration is whether the variation mechanism is structured to encourage early resolution of disputed claims or to defer them to end-of-project negotiations where positions have hardened and the commercial relationship has deteriorated.
Force Majeure and Change in Law: The Provisions That Are Rarely Read Until They Are Needed
Force majeure and change in law provisions are among the most negotiated and least understood clauses in EPC contracts. They are typically reviewed carefully by lawyers at the drafting stage, accepted with relatively minor amendments, and then rarely revisited until a major disruption event occurs and both parties discover that the clause does not perform as either expected.
Force majeure in EPC contracts typically entitles the affected party to an extension of time and, in some contracts, to cost recovery, where performance is prevented by events outside the parties’ control that could not reasonably have been anticipated or mitigated. The definitional question is critical: what events qualify? Most EPC contracts include a list of qualifying events, which may or may not encompass the specific disruption that has actually occurred. The experience of the Covid-19 pandemic generated a substantial body of arbitral decisions on the interpretation of force majeure clauses in infrastructure contracts, and the consistent lesson from that jurisprudence is that the breadth of the qualifying event definition, and the specific language used to describe causation, determines outcomes in ways that neither party appreciated at drafting.
Change in law provisions address the separate question of what happens when regulatory, tax, or legal changes after contract execution alter the economics or practicality of the contractor’s obligations. In infrastructure projects with long construction periods, regulatory change is not a theoretical risk. Environmental regulations, import duties, labour laws, and planning requirements can and do change materially over a five or seven year project timeline. Where the contract does not clearly allocate the risk of post-execution regulatory change, the dispute that follows requires tribunals to engage with complex questions of contractual interpretation, applicable law, and financial quantification simultaneously.
For project sponsors and contractors negotiating EPC contracts in cross-border infrastructure and energy projects, force majeure and change in law provisions deserve the same commercial attention as pricing and performance mechanisms. The qualifying event list should be reviewed against the specific risk profile of the project and jurisdiction, not accepted as boilerplate. The distinction between events entitling the contractor to time only and events entitling it to time and cost should be clearly specified. And the procedure for invoking these provisions, including notice requirements and the mechanism for agreeing or disputing relief, should be workable in practice, not merely theoretically coherent.
Strategic Implications for Sponsors, Contractors, Lenders, and General Counsel
EPC disputes are not primarily caused by bad faith. They are caused by contracts that distribute risk in ways that neither party fully modelled at execution, and that do not provide adequate mechanisms for resolving disagreements when disruption occurs.
For project sponsors and their general counsel, the most important discipline is to treat the EPC contract negotiation as a risk allocation exercise, not a procurement exercise. The commercial pressure to reach financial close and begin construction often creates an environment where contractual risk is accepted without adequate analysis of what it means under realistic project scenarios. Provisions that appear reasonable under optimal conditions may be wholly inadequate when the project faces the disruptions that large infrastructure projects routinely encounter.
For contractors, particularly those operating in new jurisdictions or under unfamiliar governing laws, claims management from day one is as commercially important as the technical execution of the work. A contractor that delivers a technically excellent project but fails to manage its contractual entitlements through inadequate notices, failure to quantify claims contemporaneously, or reliance on informal communications, may recover significantly less than its actual cost and time entitlements.
For lenders and investors financing EPC-based infrastructure projects, the risk allocation provisions of the underlying contract are a direct input into project risk. Where the EPC contract transfers risk to the contractor that the contractor cannot practically manage, the consequence of a major disruption event is contractor financial distress, not sponsor protection.
When EPC disputes do arise, they are typically complex, expensive, and slow to resolve. They involve detailed delay analyses, competing expert evidence, and documentary records spanning years of project execution. Arbitration is almost always the preferred forum for large international EPC disputes, both for the technical expertise available through arbitrator selection and for the enforceability of awards across jurisdictions. The quality of that arbitration depends directly on the quality of the contemporaneous record maintained during the project. Claims that were properly noticed, quantified, and documented at the time they arose are significantly more recoverable than those reconstructed after the relationship has broken down.
Closing Thoughts
The provisions that determine outcomes in EPC disputes are almost always the ones that received the least attention during contract negotiations. Scope definition, LD calibration, variation notice requirements, and force majeure qualifying event lists are treated as standard form provisions to be accepted with minor amendments, not as the commercial mechanisms that will govern the parties’ rights and obligations when the project faces genuine disruption.
For project sponsors, contractors, lenders, and the general counsel and advisors who support them, the investment made at the drafting stage in understanding how each risk allocation provision will actually operate under realistic project scenarios is invariably less costly than the arbitration that follows when those provisions fail. The EPC contract is not just the document that gets the project started. It is the document that determines how the project ends.
