What Does “Frustration of Contract” Mean?
Sometimes, after a contract is signed, something happens that makes it genuinely impossible – or pointless – to perform. Not just harder or more expensive, but impossible or radically different from what was agreed.
That’s “frustration of contract” in plain words: an unexpected event, beyond either party’s control, destroys the very foundation of the agreement, so the contract is automatically discharged (it ends) and neither party is at fault.
For example, if a hall is booked for a wedding reception and the hall burns down before the event, the contract to use the hall is frustrated, nobody breached it, but it simply cannot be performed anymore.
Where Does This Term Come From?
The doctrine traces back to English common law, but in India it is codified in Section 56 of the Indian Contract Act, 1872, which deals with “agreement to do impossible act”:
“A contract to do an act which, after the contract is made, becomes impossible, or, by reason of some event which the promisor could not prevent, unlawful, becomes void when the act becomes impossible or unlawful.”
Indian courts apply this through the “doctrine of frustration,” most famously explained by the Supreme Court in Satyabrata Ghose v. Mugneeram Bangur & Co. (AIR 1954 SC 44), where the Court held that Section 56 itself (not English common law) governs the frustration of contracts in India, and that a contract is frustrated when a supervening event strikes at the very root of the agreement — not merely when performance becomes difficult, costly, or burdensome.
Why This Matters in a Contract
Frustration matters because it changes the entire consequence of non-performance. Normally, failing to perform a contract is a breach, and the other side can claim damages. But if a contract is genuinely frustrated:
- The contract is automatically void from the moment of the frustrating event, neither party needs to “terminate” it.
- Neither party is liable for damages, because nobody breached anything.
- Money already paid may have to be refunded, and parties are restored, as far as possible, to their original position.
This is a high bar, though. Courts apply it narrowly, a contract becoming more expensive, less profitable, or simply inconvenient does not amount to frustration. It must be a truly destructive, unforeseen event (like a law banning the activity, destruction of the subject matter, or death/incapacity in a personal-service contract).
How to Use This in a Contract
Because Section 56 only kicks in for genuinely unforeseen, contract-destroying events, most commercial contracts don’t rely on it alone, they add a force majeure clause that spells out, in advance, what counts as a frustrating event and what happens next. Here’s a typical example:
“Force Majeure. Neither Party shall be liable for any failure or delay in performance under this Agreement to the extent such failure or delay is caused by an event beyond its reasonable control, including but not limited to natural disasters, war, epidemic, government action, or change in law (a “Force Majeure Event”). The affected Party shall promptly notify the other Party and use reasonable efforts to mitigate the impact. If the Force Majeure Event continues for more than sixty (60) days, either Party may terminate this Agreement by written notice, without liability to the other.”
When drafting or reviewing such a clause:
- List specific triggering events rather than relying on vague language, courts read force majeure clauses narrowly.
- Add a notice requirement, so the affected party must promptly inform the other side.
- Set a time limit, after which either party can walk away if the disruption continues.
- State the financial consequence, whether advance payments are refunded, and whether partial performance is still paid for.
A clear force majeure clause reduces the need to argue about Section 56 later, since the parties have already agreed on what “impossible” looks like for their specific deal.
Watch the Full Breakdown
Reading about frustration of contract is one thing, seeing it explained through a real example makes the doctrine click much faster. Check out the video on this topic for a quick, visual walkthrough of the concept covered above.
