Self-Induced Frustration Across Interdependent Construction Contracts: A Need for Doctrinal Expansion under Section 56

The doctrine should evolve from a narrow contract-specific inquiry into a broader doctrine of commercial causation.

The doctrine of frustration occupies a foundational place in contract law because it recognises that contractual obligations are undertaken on the assumption that certain essential circumstances will continue to exist. Where a supervening event fundamentally alters those circumstances and renders performance impossible, unlawful, or radically different from what the parties originally contemplated, the law may discharge the parties from further performance. In India, this principle is codified under Section 56, Contract Act, 1872.

At the same time, the doctrine has always been subject to an equally important limitation. The event relied upon as frustrating the contract must arise independently of the conduct of the party invoking it. If the impossibility is caused, contributed to, or materially influenced by that party’s own conduct, the doctrine ceases to apply. This limitation is known as the doctrine of self-induced frustration, and it reflects a basic rule of contractual fairness: No party should be allowed to create the obstacle to performance and then rely upon that obstacle as a source of legal advantage.¹

The origins of this doctrine are firmly rooted in English common law. In Maritime National Fish Ltd. v. Ocean Trawlers Ltd.², the Privy Council held that frustration cannot be invoked where the alleged impossibility arises from the claimant’s own commercial election. The significance of the decision lies in its emphasis on causation. The law does not merely ask whether performance became impossible. It asks why performance became impossible, and whether the party seeking relief materially contributed to that impossibility.

This principle has also found modern recognition in Indian jurisprudence. In Boothalinga Agencies v. V.T.C. Poriaswami Nadar³, while interpreting Section 56, Contract Act, 1872, the Supreme Court recognised that the doctrine of frustration cannot be invoked where the alleged impossibility is substantially caused by the conduct of the party seeking to rely upon it. The court made it clear that Section 56 is intended to protect parties only against genuine external impossibility, and not circumstances which are brought about, directly or indirectly, by their own actions.

A similar approach can be seen in more recent Indian jurisprudence. In NCC Ltd. v. Elecon EPC Projects Ltd.⁴, the Telangana High Court dealt with a dispute arising out of the short-closure of a principal contract and the consequences of one party continuing to perform without being informed of that development. The court found that the party having knowledge of the short-closure continued to derive commercial benefit from the work being performed, while failing to disclose the material change in circumstances to the performing party. In that context, the court expressly observed that self-induced frustration of a contract would itself amount to breach.

While the doctrinal foundation is well established, its application in India has largely remained confined to disputes involving a single contract and a single chain of obligations. Most judicial decisions examine whether a party contributed to impossibility under that particular agreement. Modern infrastructure and construction disputes, however, present a more complex commercial reality. Large projects are rarely governed by one contract alone. Instead, they are structured through multiple agreements relating to civil works, supply of equipment, erection and commissioning, operation and maintenance, technical services, and financing. These agreements may be separately drafted, separately priced, and even performed through different legal structures such as joint ventures, consortiums, or affiliates. Yet commercially, they often form one integrated project structure.

It is within this framework that an important doctrinal gap emerges. Consider a composite infrastructure project in which an employer enters into multiple contracts forming part of one project package. One contract relates to civil and foundation works and is executed by Contractor A. A second contract relates to erection and commissioning and is executed through a joint venture between Contractors A and B. A third relates to operations and maintenance after commissioning. Although these contracts are formally distinct, the technical sequencing of the project makes them commercially interdependent. The erection works cannot commence unless the civil foundations are completed, tested, and certified. All parties are aware of this sequencing at the time of contracting.

Now assume that Contractor A fails to complete the foundation works within the required period. As a result, heavy imported machinery intended for erection remains idle for an extended period. During this delay, external regulatory circumstances arise. Import licences expire, technical certifications lapse, environmental clearances cease to operate, or project-specific statutory approvals become invalid. By the time the foundations are completed, the equipment can no longer be installed without fresh approvals, recertification, or substantial additional compliance.

At this stage, the erection contract may arguably enter the zone of frustration. Performance is no longer merely delayed. It may have become legally impossible, commercially impracticable, or fundamentally different from what the parties originally contemplated. The legal question then becomes significant. Can Contractor A, now acting through the joint venture, invoke Section 56 and claim that the erection contract has been frustrated due to external regulatory impossibility?

At first glance, the frustrating event appears external. The expiry of licences, regulatory approvals, or statutory permissions may seem to be supervening events beyond the parties‘ control. However, a deeper analysis reveals that these events became operative only because Contractor A first failed to perform its obligations under the civil works contract. In other words, the immediate event may appear external in form, but the chain of causation reveals that the impossibility was substantially created by the claimant’s own prior breach.

This is where existing Indian jurisprudence becomes inadequate. Traditional application of self-induced frustration focuses on a single contract. Modern construction disputes, however, require courts to recognise that self-induced frustration may arise across interconnected contracts forming part of one composite transaction.

A party should not be permitted to compartmentalise contractual obligations merely because separate agreements exist. Where the same economic actor participates across multiple contractual arrangements, and failure under one agreement directly creates the factual conditions that later frustrate another, the downstream impossibility cannot be treated as an independent supervening event. To hold otherwise would allow parties to manipulate contractual structures while avoiding commercial accountability. A contractor could create delay in one contractual segment, trigger regulatory or technical consequences in another, and then rely upon those downstream consequences as a basis for frustration or discharge. Such an approach would undermine both contractual risk allocation and commercial fairness. Indian Courts must, therefore, refine the doctrine of self-induced frustration to address composite construction transactions.

The doctrine should evolve from a narrow contract-specific inquiry into a broader doctrine of commercial causation. The relevant judicial inquiry should not be confined to the wording of one contract. Instead, courts should examine the integrated commercial architecture of the project. The courts should determine whether multiple contracts form part of one composite commercial transaction directed toward a common project objective. They should examine whether performance under one contractual segment is technically or commercially dependent upon prior performance under another. They should also consider whether the same economic actor substantially participates across those arrangements, even if different legal structures such as joint ventures or consortiums are used.

Most importantly, courts must trace the actual chain of causation and determine whether the alleged frustrating event became operative only because of the claimant’s own prior breach, omission, election, or delay under another connected contract. If the claimant knew, or reasonably ought to have known, that failure under one contractual segment would expose downstream performance to regulatory or technical impossibility, the resulting event cannot be characterised as truly external. Where these elements are established, Indian Courts should hold that the downstream frustration is self-induced. Such doctrinal refinement would not require courts to disregard contractual autonomy or rewrite commercial bargains. On the contrary, it would preserve the true allocation of risk by ensuring that parties cannot use contractual fragmentation to externalise liability while internalising benefit. More importantly, this approach would align Section 56 with the realities of modern infrastructure contracting. Construction disputes today involve phased obligations, technical dependencies, regulatory sequencing, and integrated project structures. A doctrine developed in the context of simple bilateral contracts must evolve if it is to remain commercially relevant.

Such an evolution would ensure that liability follows causation, that contractual risk allocation remains meaningful, and that the law does not permit parties to transform self-created obstacles into grounds for discharge. Ultimately, self-induced frustration is not merely a technical exception to Section 56. It is an expression of a deeper judicial principle, one that ensures that contractual relief remains available only where impossibility is genuinely external, and never where it is substantially of the claimant’s own making.