Frustration of contract is a doctrine that discharges both parties from their contractual obligations when an unforeseen event occurs after formation, making performance impossible, illegal, or radically different in nature from what was originally contemplated. Under Indian contract law, this principle finds expression in the Indian Contract Act, 1872, particularly in provisions dealing with impossibility of performance and supervening impossibility. The statutory foundation recognises that parties contract based on the state of facts existing at formation; when those facts change fundamentally and unexpectedly, the law steps in to relieve both parties from liability. This is not about mere hardship, inconvenience, or increased cost—it is about performance becoming something entirely different from the bargain struck. The doctrine operates through several interlocking elements that must all be present for frustration to discharge a contract. First, there must be a supervening event—something occurring after contract formation that was not anticipated by the parties. Second, this event must be beyond the control of either party; neither can have caused or contributed to it through their conduct or negligence. Third, the event must make performance impossible, illegal, or fundamentally transform the nature of the obligation such that performance would be radically different from what was undertaken. The burden lies on the party claiming frustration to prove these elements clearly. Courts do not easily infer frustration, as contracts are binding promises, and the law respects the allocation of risk made by the parties themselves. If a contract contemplated certain contingencies or allocated risks explicitly, frustration cannot apply—the parties have already addressed the concern. This interplay between unforeseeability, causation, and radical difference creates a high threshold that protects contractual sanctity while providing escape where genuinely warranted. When frustration is validly established, the consequences are significant but precisely defined. The contract is discharged—both parties are freed from further performance obligations. However, this discharge is prospective: obligations that accrued before frustration remains payable. Money paid before frustration is not automatically recoverable; courts examine whether the payee has received the benefit intended or whether retention would be inequitable. The Indian Contract Act provides that when a contract becomes impossible of performance after formation, the liability of the party undertaking to do that act ceases. There are no damages for breach, as neither party is at fault; frustration is not a breach but a legal discharge. However, modern jurisprudence recognises exceptions: if a party's own breach causes the frustrating event, they cannot rely on frustration. Similarly, if a party has assumed the risk of the supervening event through clear contractual language, frustration is excluded. Some contracts are so structured that frustration is impossible—for instance, if the contract explicitly provides for payments despite the occurrence of certain events, the parties have chosen not to be frustrated by those events. Frustration sits within a broader ecosystem of discharge doctrines in contract law. It differs fundamentally from breach—breach is failure without lawful excuse, while frustration is a lawful excuse precluding breach. It also differs from mistake at formation; frustration concerns events after formation, whereas mistake vitiates consent at the moment of contracting itself. In comparative perspective, frustration echoes the civilian concept of force majeure or the common law doctrine of impossibility, but Indian law has given it a distinctive shape through statutory interpretation. The doctrine intersects with the law of tort in cases where a party's negligence causes the frustrating event—such conduct may preclude the frustration defence and expose that party to liability. Additionally, frustration must be distinguished from merely onerous performance; if a contract becomes more expensive or difficult but remains possible, frustration does not apply. Courts also consider whether the frustrated party had an opportunity to complete performance before the supervening event; timing is critical to establishing that performance has become impossible, not merely delayed. CLAT examiners test frustration through several characteristic distortions that catch unprepared candidates. One common twist involves facts where a party claims frustration but has actually caused or materially contributed to the supervening event—the examiner presents the event as seemingly external while hiding the party's culpability in the narrative. Another trap reverses the temporal sequence: examiners describe an event that occurred before or at the moment of contract formation and ask whether it frustrates; candidates must recognise that supervening means after formation. A frequent confusion arises when candidates conflate frustration with commercial impracticability or mere hardship; CLAT questions deliberately present scenarios where costs have risen sharply or performance has become significantly more burdensome, testing whether candidates incorrectly treat difficulty as equivalent to impossibility. Examiners also create ambiguity around risk allocation by presenting contracts with conditional language or force majeure clauses, then asking whether frustration applies—the correct analysis requires recognising that explicit contractual allocation excludes the frustration doctrine. Finally, a scope-creep trap imports principles from sale law (goods perishing through no fault of seller) or tort law (negligence causing the supervening event) into a contract frustration question, testing whether candidates remain focused on the supervening impossibility framework rather than wandering into adjacent doctrines. The key to avoiding these traps is rigorous element-checking: supervening? Beyond control of both parties? Impossibility or radical difference? And critically: has the contract already allocated this risk?