A contingent contract is a type of agreement where the fulfillment or enforcement of the contract is dependent on the occurrence or non-occurrence of
Contingent Contract Under the Indian Contract Act, 1872: A Complete Deep Dive
Life is unpredictable. We plan our days, our businesses, and our futures around events that may or may not happen. When two people shake hands on a deal, they usually expect things to go a certain way. But what happens when the very validity of that handshake depends on something uncertain happening in the future? That is exactly where the concept of a contingent contract steps in — one of the most practical, widely used, and yet often misunderstood areas of Indian contract law.
If you are a law student, a business owner, or simply someone curious about how contracts work when the future is foggy, this guide is for you. We are going to unpack everything about contingent contracts under the Indian Contract Act, 1872 — from the basic definition to the fine legal distinctions, real-world examples, landmark judgments, and how they differ from wagering agreements. No tables, no robotic language — just a clear, human, and detailed walkthrough.
What Is a Contingent Contract, Really?
Let us start with the basics. A contingent contract is not your everyday contract. In most contracts, if A agrees to sell a car to B for five lakh rupees, A must deliver the car and B must pay the money. Simple. The obligation is immediate and unconditional. But in a contingent contract, the obligation to perform only arises if a specific future event happens — or does not happen.
Section 31 of the Indian Contract Act, 1872 defines it in these words:
"A contingent contract is a contract to do or not to do something, if some event collateral to such contract does or does not happen."
Let us break that down in plain English:
- There must first be a valid contract between two parties.
- The performance of that contract is not immediate.
- It is conditional upon a future event.
- That future event must be uncertain — nobody knows for sure whether it will happen.
- The event must be collateral to the contract, meaning it is not the main subject but something that triggers the main obligation.
Think of it like this: you promise to pay your friend ten thousand rupees if his house burns down. The burning of the house is not the main contract — the main contract is your promise to pay. But that promise only wakes up if the house actually catches fire. That is the soul of a contingent contract.
The Legal School explains this beautifully with the illustration: A contracts to pay B ₹10,000 if B's house is burnt. This is a contingent contract because the payment depends on a future uncertain event that is collateral to the agreement itself.
The Building Blocks: What Makes a Contract "Contingent"?
Not every contract with a condition is a contingent contract. To truly qualify under Section 31, certain essential elements must be present. Let us look at them one by one.
- There must be a valid contract in place. Without a contract, there is nothing to be contingent upon. The agreement must satisfy all the basic requirements of a valid contract — offer, acceptance, consideration, capacity, and lawful object.
- The contract must involve doing or not doing something. This is straightforward. The promise must be about an action or an omission.
- The performance must be conditional. This is the heart of the matter. The promisor is not bound to perform unless and until a specific condition is fulfilled.
- The condition must be a future uncertain event. If the event has already happened or is certain to happen, it is not a contingent contract. The uncertainty is what gives it character.
- The event must be collateral to the contract. This is crucial. The event should not be the consideration itself. For example, if A announces a reward of ₹100 to anyone who finds his lost dog, and B finds it, B's act of finding is both acceptance and performance. This is not a contingent contract because the event is not collateral — it is the very performance.
- The event should generally not be within the control of the parties. While there are exceptions, the typical contingent contract depends on external factors — natural events, third-party actions, or market conditions — rather than the will of the parties themselves.
Section 32: When the Contract Depends on an Event Happening
Now we move into the enforcement mechanics. Section 32 deals with contracts that are contingent upon a future event happening. The rule is simple but powerful:
A contingent contract to do or not to do anything if an uncertain future event happens cannot be enforced by law unless and until that event has happened. If the event becomes impossible, the contract becomes void.
Let us understand this with the illustrations provided in the Act itself:
- A makes a contract with B to buy B's horse if A survives C. This contract cannot be enforced until C actually dies during A's lifetime. If C outlives A, the contract simply melts away.
- A makes a contract with B to sell a horse to B if C, to whom the horse has been offered, refuses to buy him. The contract is in deep sleep until C actually refuses. Until that refusal happens, B cannot force A to sell.
- A contracts to pay B a sum of money when B marries C. If C dies without ever marrying B, the event becomes impossible, and the contract becomes void.
The Rajasthan High Court in Nemi Chand and Ors. vs. Harak Chand and Ors. (1965) emphasized that a contingent contract to do or not do something depends on the occurrence of an undetermined future event, and until that event happens, the contract remains unenforceable. The court also clarified that it is the responsibility of the parties to prove the occurrence or impossibility of the event — not the court's job to investigate suo moto.
Another important case is V.P. Desa v. Union of India (AIR 1958 MP 297), where a car was insured against loss in transit. The car was damaged, but it was never actually put in the course of transit. The insurer was held not liable because the contingent event — loss during transit — never occurred. This shows how strictly courts interpret the "happening of the event" requirement.
Section 33: When the Contract Depends on an Event NOT Happening
Sometimes, the contract is structured the other way around. The obligation arises not when something happens, but when something does not happen. Section 33 governs this scenario.
Contingent contracts to do or not to do anything if an uncertain future event does not happen can be enforced when the happening of that event becomes impossible, and not before.
The classic illustration is: A agrees to pay B a sum of money if a certain ship does not return. If the ship sinks, its return becomes impossible, and only then can A be forced to pay. Until the ship sinks or it becomes definitively clear that it will never return, the contract remains dormant.
This section teaches us an important lesson: non-occurrence is not enough; impossibility of occurrence is what triggers enforcement. The contract waits patiently until the "not happening" becomes a certainty, not just a probability.
Section 34: When the Event Depends on a Living Person's Conduct
This is where things get interesting. What if the future event is not a natural disaster or a ship's voyage, but the behavior of a living person? Section 34 addresses this specific situation.
If the future event on which a contract is contingent is the way in which a person will act at an unspecified time, the event shall be considered to become impossible when such person does anything which renders it impossible that he should so act within any definite time, or otherwise than under further contingencies.
The illustration is poignant: A agrees to pay B a sum of money if B marries C. If C marries D instead, the marriage of B to C becomes impossible. Even though D might die someday and C might then marry B, the law treats the event as impossible because it is now dependent on further contingencies — D's death — which are indefinite and uncertain.
The landmark English case Frost v. Knight (1872) is often cited here. The defendant promised to marry the plaintiff after his father's death. While the father was still alive, the defendant married another woman. The court held that performance had become impossible, and the plaintiff could sue for breach. This established the principle of anticipatory breach in contingent contracts.
Another case, Pym v. Campbell (1856), involved a written agreement to buy the benefits of the plaintiff's invention if it was approved by an engineer. The engineer did not approve it. The court held there was no concluded contract because the contingent condition was not met. This reinforces that in contingent contracts, the condition is everything.
Section 35: The Time Factor — What Happens When Time Is Fixed?
Time is money, and in contingent contracts, time can also be the dealbreaker. Section 35 deals with two distinct scenarios where a fixed time is attached to the contingency.
First scenario — Event must happen within fixed time:
If a specified uncertain event must happen within a fixed time, the contract becomes void if:
Example: A promises to pay B if a certain ship returns within a year. If the ship does not return within that year, or if it sinks during the year, the contract becomes void. The promise evaporates.
Second scenario — Event must NOT happen within fixed time:
If a specified uncertain event must not happen within a fixed time, the contract may be enforced when:
Example: A promises to pay B if a certain ship does not return within a year. If the ship sinks during the year, or if the year passes without its return, the contract can be enforced. The promise wakes up.
This section is particularly important in insurance contracts, shipping agreements, and construction contracts where deadlines are critical and parties need certainty about when their obligations begin or end.
Section 36: The Impossibility Rule — When the Foundation Is Cracked
Finally, we come to Section 36, which is the safety net of contingent contract law.
Agreements contingent on impossible events are void, whether the impossibility was known or not to the parties at the time of making the agreement.
This is a hard rule with no exceptions. If the very event on which the contract is built is impossible from day one, the contract is dead on arrival.
The Act gives two striking illustrations:
- A agrees to pay B ₹1,000 if two straight lines should enclose a space. This is void because it is geometrically impossible — two straight lines can never enclose a space.
- A agrees to pay B ₹1,000 if B will marry A's daughter C, but C was already dead at the time of the agreement. The contract is void because the event was impossible from the very beginning, even if A did not know about C's death.
This section protects parties from entering into meaningless agreements and prevents courts from being burdened with enforcing the impossible. It also aligns with the broader principle that law does not compel the impossible.
Real-World Applications: Where Do We See Contingent Contracts?
Contingent contracts are not just textbook concepts. They are everywhere in our daily lives and business dealings. Let us look at some common examples:
- Insurance contracts are perhaps the most prominent example. A life insurance company promises to pay the nominee only if the insured person dies during the policy term. A fire insurance company pays only if the insured property actually burns down. The event is uncertain, collateral, and future — textbook contingent contract.
- Real estate transactions often use contingent contracts. A buyer might agree to purchase a property only if the bank approves the loan, or only if the seller obtains clear title documents, or only if zoning permissions are granted.
- Employment contracts sometimes include contingent clauses. A company might promise a bonus to an employee if the company achieves certain revenue targets, or if the employee completes a certification.
- Construction and infrastructure projects frequently use contingent contracts. A contractor might be paid additional amounts if the project is completed ahead of schedule, or if certain quality benchmarks are exceeded.
- Supply chain agreements often have contingent elements. A manufacturer might agree to buy raw materials from a supplier if the supplier's factory passes a quality audit, or if import duties do not exceed a certain threshold.
In the case of Nandkishore Lalbhai vs. New Era Fabrics Pvt. Ltd. & Ors. (2015), the Supreme Court of India dealt with a contract for the sale of land that was contingent upon two conditions: approval by labour unions and change of land use by competent authority. Neither condition was satisfied. The Supreme Court held that the contract was not enforceable against the seller because the contingent events did not occur. This case is a powerful reminder that in contingent contracts, the conditions are king.
Contingent Contract vs. Wagering Agreement: The Critical Difference
This is where many students and even professionals get confused. Both contingent contracts and wagering agreements involve future uncertain events. So what makes one valid and the other void? The distinction is crucial and has been the subject of numerous judicial pronouncements.
Section 30 of the Indian Contract Act declares that wagering agreements are void. They are not illegal, but they are unenforceable. A contingent contract, on the other hand, is perfectly valid and enforceable under Section 31.
Here are the key differences explained in simple terms:
- Nature of the event: In a contingent contract, the event is collateral to the main agreement. In a wagering agreement, the event is the sole determining factor — the entire agreement revolves around the bet.
- Reciprocal promises: A wagering agreement necessarily involves reciprocal promises — both parties promise to pay depending on the outcome. A contingent contract may or may not involve reciprocal promises.
- Interest in the subject matter: In a contingent contract, the parties usually have a genuine interest in the subject matter beyond the money involved. In a wagering agreement, the parties have no interest in the event except for winning or losing the stake.
- Control over the event: In a contingent contract, the event may sometimes be within the control of a party, though typically it is not. In a wagering agreement, neither party should have control over the event — it must be purely a matter of chance.
- Enforceability: This is the big one. A contingent contract is enforceable when the event happens. A wagering agreement is void from the outset — no court will help you collect your winnings.
- Legal status: A contingent contract is valid. A wagering agreement is void (though not necessarily illegal, except in some states like Maharashtra and Gujarat where gambling is prohibited).
The Supreme Court in Gherulal Parakh v. Mahadeodas clarified that while a wagering contract is void and its performance cannot be sued upon, it is not forbidden by law. Therefore, transactions that are accessory to a wagering agreement — such as loans taken to place bets — are not automatically void. This nuanced position helps distinguish between the voidness of the wager itself and the legality of surrounding transactions.
Another important case is Carlill v. Carbolic Smoke Ball Co., where the court explained that a wagering contract is essentially an agreement between two persons holding different opinions about a future uncertain event, where one will win and the other will lose, and neither has any interest in the event other than the stake.
Landmark Judgments That Shaped Contingent Contract Law
Indian courts have interpreted and refined the law of contingent contracts through several important judgments. Let us look at some that every law student and practitioner should know.
- Frost v. Knight (1872): This English case established the principle of anticipatory breach in contingent contracts. The defendant promised to marry the plaintiff after his father's death but married someone else while the father was still alive. The court held that the plaintiff could sue immediately because the defendant's action made the contingent event impossible. This principle has been widely accepted in Indian jurisprudence.
- Nemi Chand and Ors. vs. Harak Chand and Ors. (1965): The Rajasthan High Court held that a contingent contract depends on the occurrence of an undetermined future event, and it is the parties' responsibility to prove this in court. The court will not take suo moto cognizance. This case is frequently cited for the proposition that contingent contracts require active proof of the triggering event.
- Nandkishore Lalbhai vs. New Era Fabrics Pvt. Ltd. & Ors. (2015): The Supreme Court held that a contract for sale of land contingent upon labour union approval and change of land use was not enforceable when those conditions were not met. This case is a modern reaffirmation of the sanctity of conditions in contingent contracts.
- V.P. Desa v. Union of India (AIR 1958 MP 297): The Madhya Pradesh High Court held that an insurer was not liable when the insured car was damaged without being put in transit, because the contingent event — loss during transit — never occurred. This case is essential for understanding insurance as a contingent contract.
The Dark Side: Disadvantages and Risks of Contingent Contracts
While contingent contracts are incredibly useful, they are not without their pitfalls. Anyone drafting or entering into such a contract should be aware of these risks:
- Uncertainty in performance: The fundamental nature of a contingent contract means that performance is uncertain until the condition is met. This creates anxiety, delays business planning, and can lead to situations where one party is left in limbo for extended periods.
- Ambiguity and complexity: Contingent contracts must be drafted with extreme precision. If the condition is vague or poorly worded, disputes are inevitable. What exactly constitutes "approval"? What counts as "impossible"? These questions can lead to expensive litigation.
- High chance of disputes: Because the triggering event is uncertain, parties often disagree about whether it has occurred, whether it has become impossible, or whether the time frame has been satisfied. This makes contingent contracts more litigation-prone than absolute contracts.
- Time-consuming: The very nature of waiting for a future event means that contingent contracts can delay projects, transactions, and business decisions. In fast-moving industries, this can be a significant disadvantage.
- Risk of frustration: If the event becomes impossible due to unforeseen circumstances — such as a natural disaster, war, or legislative change — the contract may become void, leaving parties without the expected benefit of their bargain.
Drafting Tips: How to Write a Bulletproof Contingent Contract
If you are a lawyer, business owner, or contract manager, here are some practical tips for drafting contingent contracts that stand up in court:
- Define the contingent event with crystal clarity. Do not use vague language like "if circumstances permit" or "if things work out." Be specific: "if the municipal corporation grants building permission by March 31, 2026."
- Specify the time frame explicitly. If the contract is time-bound, state the exact date or period. Ambiguity about time is a common source of disputes.
- Address impossibility explicitly. Consider including clauses that define what happens if the event becomes impossible, and whether partial performance or alternative obligations are acceptable.
- Avoid making the event the consideration. Remember, the event must be collateral, not the consideration itself. Structure the contract so that the main obligation is clear, and the condition merely triggers it.
- Include dispute resolution mechanisms. Given the higher litigation risk, include arbitration or mediation clauses to resolve disagreements about whether the condition has been met.
- Document everything. Since the burden of proof is on the party seeking enforcement, maintain thorough records of all communications, approvals, and events related to the condition.
The Bottom Line: Why Contingent Contracts Matter
In a world of uncertainty, contingent contracts are the legal tools that allow businesses and individuals to plan for the future without taking blind risks. They are the backbone of the insurance industry, the real estate market, international trade, and countless other sectors. They allow parties to say: "Yes, I will do this, but only if that happens."
The Indian Contract Act, 1872, through Sections 31 to 36, provides a robust and logical framework for these contracts. The law recognizes that not all promises can be absolute, and that sometimes, the future must be allowed to unfold before obligations crystallize. At the same time, the law protects parties from being bound to the impossible, the uncertain, and the unfair.
Understanding contingent contracts is not just an academic exercise. It is a practical necessity for anyone who deals with agreements in the real world. Whether you are buying a house, insuring your car, hiring an employee, or investing in a project, the principles of contingent contracts will touch your life.
The key takeaway is this: a contingent contract is a promise that sleeps until a future event wakes it up. But if that event is impossible from the start, or if it never happens within the agreed time, the promise dies in its sleep. The law ensures that this sleeping promise is neither abused nor ignored — it is simply governed by the rational, fair, and time-tested rules laid down in Chapter III of the Indian Contract Act.
Source Links
- The Legal School — Contingent Contracts: Sections 31 to 36 of the Indian Contract Act (2026)
https://thelegalschool.in/blog/contingent-indian-contract-act - IILS India — Contingent Contract Under the Indian Contract Act with Important Case Laws
https://www.iilsindia.com/study-material/324977_1608480395.docx - Scribd — Contingent Contracts in Indian Law (PDF)
https://www.scribd.com/document/793762370/Contingent-contracts-31-to-36 - ALEC — Understanding Essentials of Contingent Contract under the Indian Contract Act 1872
https://www.alec.co.in/show-blog-page/understanding-essentials-of-contingent-contract-under-the-indian-contract-act-1872 - Manupatra — Law of Contract and Specific Relief, Chapter VIIIB
http://student.manupatra.com/Academic/Abk/Law-of-Contract-and-Specific-Relief/Chapter8B.htm - Pahuja Law Academy — Chapter 7: Wagering Agreements and Contingent Contracts
https://www.pahujalawacademy.com/chapter-7-wagering-agreements-and-contingent-contracts - The Legal School — Difference Between Contingent Contract and Wagering Agreement (2026)
https://thelegalschool.in/blog/difference-between-contingent-contract-and-wagering-agreement - Egyankosh — Unit 6: Void Agreements and Contingent Contracts (PDF)
https://egyankosh.ac.in/bitstream/123456789/56345/1/B-2U-6.pdf - Scribd — Wagering vs. Contingent Contracts Explained (PDF)
https://www.scribd.com/document/888840386/Week-9-Wagering-Contracts-Contingent-Contracts-Time-of-Essence-Frustration
COMMENTS