Frustration in contract law is a common law doctrine that discharges a contract automatically when an unforeseen event, arising after formation and through no fault of either party, makes performance impossible, illegal, or radically different from what the parties agreed.
English courts apply the doctrine narrowly, and it remains one of the most tightly confined rules in English contract law. The legal test, the qualifying events, the financial consequences, and the distinction from force majeure and breach all shape how narrowly the doctrine is applied in practice.
The Legal Test for Frustration of Contract
The legal test for frustration requires a supervening event, outside the control of either party, that renders performance radically different from what was promised when the contract was made. Mere hardship or extra cost does not meet it.
This standard comes from Lord Radcliffe’s judgment in Davis Contractors Ltd v Fareham UDC [1956], the controlling authority. Frustration occurs, he held, only when circumstances make the obligation a thing radically different from the one the contract created.
Four conditions must hold before a court will find a contract frustrated:
The event occurs after the contract is formed.
Neither party caused it.
The contract did not foresee or provide for it.
It makes performance impossible or radically different, not merely harder or costlier.
Each condition ties the event to the core of the bargain. A frustrating event must strike at the root of what the parties agreed, defeating one of the essential elements of a contract rather than making performance inconvenient.
Because the threshold sits so high, frustration succeeds rarely. Courts protect the certainty of agreements and treat the doctrine as a remedy of last resort, not a way out of a bargain that has turned unprofitable.
Events That Can Frustrate a Contract
The events that can frustrate a contract include destruction of the subject matter, supervening illegality, the death or incapacity of a person essential to performance, and the non-occurrence of an event fundamental to the contract’s purpose.
Courts recognise a handful of categories:
Destruction of the subject matter. The thing the contract depends on is destroyed, as when premises burn down before they can be used.
Supervening illegality. A change in the law, the outbreak of war, or an embargo makes performance unlawful.
Death or incapacity. In a personal-service contract, the person engaged to perform dies or becomes unable to.
Non-occurrence of a fundamental event. Something the contract was built around fails to happen.
Government intervention. State action, such as requisition or a trading ban, prevents performance.
Which category applies depends on the nature of the agreement, since certain types of contracts, such as those for personal services, are far more exposed to incapacity than a routine supply arrangement.
Frustration Case Law Examples
An example of frustration of a contract is Taylor v Caldwell (1863), where a music hall hired for a run of concerts burned down before the performances. The court excused both parties and established that destruction of the subject matter discharges a contract.
Krell v Henry (1903) extended the principle to frustration of purpose. A flat was hired to watch the coronation procession of Edward VII, and when the coronation was postponed, the court held the contract frustrated even though the procession was never written into it.
Fibrosa Spolka v Fairbairn (1943) turned on supervening illegality. When wartime law made trading with German-occupied Poland unlawful, performance became illegal, the contract was frustrated, and the buyer recovered its advance payment.
When a Contract Is Not Frustrated
A contract cannot be frustrated by increased costs alone. Performance becoming more expensive, slower, or less profitable does not make it radically different, so a party who priced in that risk stays bound to perform.
Davis Contractors shows the limit in practice. A building firm faced scarce labour and materials, so the work ran long and over budget, but the House of Lords held that hardship of that degree does not frustrate a contract.
Self-induced frustration is an event brought about by a party’s own act or choice, and it defeats a frustration claim. In Maritime National Fish v Ocean Trawlers [1935], a company that chose which vessels to license could not treat the resulting shortfall as frustration.
A contract also stands where it foresaw the event or allocated its risk. When the contract’s terms already provide for what happens, including through a force majeure clause, there is nothing for the doctrine to fill and frustration is excluded.
Canary Wharf v EMA [2019] shows how narrow the doctrine remains. The High Court held that Brexit did not frustrate the European Medicines Agency’s 25-year lease, because neither impossibility nor a failure of common purpose was made out.
What Happens When a Contract Is Frustrated
When a contract is frustrated, it is discharged automatically. The contract ends at the moment of the frustrating event, both parties are released from all future obligations, and neither can sue for a breach that would otherwise follow.
Rights that accrued before the event still stand, and some secondary obligations, such as confidentiality or dispute resolution, can survive. Frustration differs from contract termination in one respect: it operates by law, not by a party’s choice.
The Law Reform (Frustrated Contracts) Act 1943
The Law Reform (Frustrated Contracts) Act 1943 is the statute that settles the financial consequences of frustration in English law. It governs money already paid, expenses incurred, and benefits received before discharge, so that neither party is left unjustly enriched.
The Act works through three rules:
Money paid before the frustrating event is recoverable, and money that was due stops being payable.
A party that incurred expenses may retain or recover a just sum out of any prepayments, up to the amount spent.
A party that received a valuable benefit before discharge may have to pay a just sum for it.
The Act applies unless the contract excludes it, and it does not reach every agreement. Contracts for the carriage of goods by sea, most charterparties, and contracts of insurance fall outside it and are governed by their own rules.
Frustration vs Force Majeure vs Breach of Contract
The difference between frustration and force majeure is one of source and control. Frustration is a common law doctrine a court applies when no provision covers the event, while a force majeure clause is a contractual term the parties write and control themselves.
Frustration | Force majeure | Breach of contract | |
Source | Common law doctrine | Contractual clause | Failure to perform an obligation |
Trigger | Unforeseen supervening event | Events defined in the clause | Non-performance by a party |
Who decides | The court | The clause as drafted | The court, on a claim |
Effect | Automatic discharge | Suspension or termination per the clause | Contract continues; damages available |
Remedies | Adjustments under the 1943 Act | As set out in the clause | Damages, sometimes specific performance |
A breach of contract belongs to a different category again. It is a failure to perform an obligation, which leaves the contract alive and the injured party able to claim damages, whereas frustration ends the contract without fault on either side.
The practical lesson is that control comes from drafting. A precise force majeure clause and clear termination clauses let the parties decide in advance what a disruptive event does to their agreement, and once a clause governs the event, the frustration doctrine has no role.
Managing Frustration Risk Across Your Contract Portfolio
Businesses manage frustration risk by drafting for it rather than litigating it, since courts will not rescue a party from an event the contract should have addressed. Force majeure and risk-allocation clauses, written into every significant agreement, decide the outcome in advance.
The harder problem is knowing what those agreements actually say. When a law changes or a supplier fails, a legal team cannot judge its exposure without seeing which contracts carry which clauses, and that review is slow when contracts sit in email and shared drives.
Contract lifecycle management platforms hold every agreement in a searchable contract repository with clauses and obligations tracked as structured data. Miramis is a contract lifecycle management platform that stores every contract in one place and keeps the clauses and obligations inside them visible, so a portfolio-wide review takes hours instead of weeks.
Pre-approved contract templates keep force majeure and risk-allocation language consistent across new agreements, so protection does not vary contract by contract. Obligation tracking then surfaces which live contracts are affected the moment circumstances change.
Keep Every Clause and Obligation in View
Understanding when a contract is frustrated matters most when you can see which of your own agreements are exposed. Legal and business teams use Miramis (formerly Pocketlaw) to keep every clause, obligation, and renewal in view across the full portfolio, and you can book a demo to see how it works.
Disclaimer:
Please note: Miramis is not a substitute for an attorney or law firm. So, should you have any legal questions on the content of this page, please get in touch with a qualified legal professional.
Related articles

What Is a Contractual Obligation? Definition and Examples
A contractual obligation is a binding duty each party owes under a contract. Learn the types, examples, and how obligations are enforced and tracked.

What Is Supplier Agreement Management? Process & Guide 2026
upplier agreement management (SAM) systematically manages vendor contracts from creation to renewal. Learn the 7-stage process, implementation steps, and CLM software requirements.

What Is a Wet Signature? Uses & Legal Requirements
A wet signature is a handwritten signature made with ink on paper. Learn when wet signatures are required, how they compare to e-signatures, and how to manage wet-signed contracts.

