Legal Rules Governing Contingent Contracts

Picture a simple promise: “I will pay you a lakh of rupees if your house burns down.” That is not a normal contract where both sides perform right away. It is a promise trapped in a waiting room, and the only thing that unlocks it is an uncertain event outside anyone’s control. Business Law calls this a contingent contract, and Indian law spends five full sections telling courts exactly when such a promise can be enforced and when it simply dies on paper. If you are studying commercial contracts, or you run a business that depends on insurance, tenders, or supply agreements, these rules are not academic trivia. They decide who gets paid and who walks away empty-handed.

What makes a contract “contingent” in the first place 🔗

A contingent contract is an agreement to do or not do something if a specific, uncertain, future event happens or does not happen. The event has to be collateral to the contract, meaning it sits outside the main promise itself, not a condition the promising party controls at will. Insurance is the textbook business example: an insurer promises to pay only if a fire, theft, or accident actually occurs. Until that trigger event happens, there is no obligation to pay anything.

The Indian Contract Act, 1872 defines this idea and then lays out its enforcement mechanics across Sections 32 to 36. These sections don’t just repeat the definition. They answer a much more practical question: at what exact point does a contingent promise become legally binding, and at what point does it become void?

The starting rule: enforcement depends on the event happening 🔗

Section 32 covers contracts that are contingent on an uncertain future event actually happening. The rule is direct: such a contract cannot be enforced by law unless and until that event occurs. If the event becomes impossible, the contract turns void.

Take the classic shipping example used across commerce textbooks. If A promises to pay B a sum of money when a specific ship returns, the promise stays dormant until the ship actually comes back. Nobody can demand payment while the ship is still at sea. But if the ship sinks, meaning the event can now never happen, the entire contract becomes void, and A owes nothing.

A well-known illustration from the Act itself makes this even sharper: if A agrees to pay B a sum when B marries C, and C dies before the wedding, the contract becomes void immediately, because the marriage between B and C is now impossible. This is explicitly captured in the text of Section 32, along with similar illustrations involving a horse sale conditioned on a third party’s refusal to buy.

Why this matters for business agreements 🔗

This rule protects both sides from being trapped in limbo forever. A supplier who promises a discount “if government approval comes through” cannot be forced to honour that discount the moment approval becomes permanently blocked. The contract simply lapses. This is also why insurance policies are drafted with precise trigger events. Vague triggers create disputes about whether the “event” that occurred actually matches what was promised in the policy.

The mirror rule: enforcement depends on the event not happening 🔗

Section 33 flips the logic. Where a contract is contingent on an event not happening, it can be enforced only when the happening of that event becomes impossible, not before.

Go back to the ship example, but reverse the terms. If A promises to pay B a sum of money if a certain ship does not return, B cannot claim payment simply because the ship is late or has not yet arrived. B has to wait until it becomes impossible for the ship to return at all, for instance if credible evidence confirms the ship was lost at sea. Only then does the contingency mature into an enforceable right, as several commentaries on the Act’s structure around Sections 31 to 36 point out.

Notice the pattern connecting Sections 32 and 33. One demands proof that something did happen. The other demands proof that something can never happen. Both share the same underlying idea: courts will not force performance based on guesswork about the future. They wait for certainty, one way or the other.

When the event depends on how a person behaves 🔗

Business promises are often tied not to natural events like storms or fires, but to how a specific person will act. Section 34 deals with this. If the future event is the way a particular living person will behave at some unspecified time, the event is treated as impossible the moment that person does something which makes it impossible for them to act in that way within any definite time, or without further conditions attaching to it.

The Act’s own illustration is a good one to remember: A agrees to pay B a sum if B marries C. Then C marries D instead. B marrying C is now impossible, because C is no longer available for that marriage under normal circumstances. It does not matter that D could theoretically die someday and C could technically marry B afterward. The contract is treated as void the moment C marries D, because that is the point at which the original contingency stopped being realistically achievable within a definite time frame, as explained in the official text and illustration of Section 34.

In commercial terms, this section shows up in agreements tied to a person’s future decisions, such as a distributor’s promise to pay a bonus “if the regional manager signs with us before the client switches vendors.” If that manager formally joins a competitor, the contingency becomes impossible immediately, not just delayed.

Contracts with a built-in deadline 🔗

Some contingent contracts don’t leave the timeline open-ended. They specify a fixed time within which the event must happen or not happen. Section 35 governs both scenarios.

Event must happen within fixed time 🔗

If a contract is contingent on a specified event happening within a fixed time, it becomes void if the time expires without the event happening, or if the event becomes impossible before the time is up, whichever comes first. There is no waiting beyond the deadline. Once the clock runs out, the promise is dead, regardless of whether the event might still happen a little later.

Event must not happen within fixed time 🔗

The reverse situation can be enforced when the fixed time expires without the event having happened, or earlier, if it becomes certain that the event cannot possibly happen before the time is up. This gives the promisee a defined exit point rather than an indefinite wait.

This is where fixed-term commercial contracts, tenders, and insurance-linked clauses lean heavily on Section 35, because businesses need certainty about when an obligation ends, not just whether it begins.

Agreements built on impossible events are void from day one 🔗

Section 36 closes the loop by dealing with agreements contingent on an event that is impossible in itself. Such agreements are void, whether or not the parties were aware of the impossibility when they made the agreement. If A promises to pay B a sum should the sun rise in the west, that agreement is void from the very beginning, since the event contradicts a known impossibility, as noted in analyses of the provisions governing impossible contingent events.

This section matters more than it looks. It stops parties from dressing up a fraudulent or nonsensical promise as a legitimate contract simply because it is phrased as “contingent.” Courts do not need to wait for anything to happen. The impossibility is baked in at the moment of agreement, so the contract is void immediately, no waiting period involved.

A quick side-by-side of the five rules 🔗

Why this framework matters beyond the exam 🔗

These five sections exist because business life is full of promises that hinge on something outside anyone’s direct control: weather, third-party decisions, regulatory approvals, market movements. Without a clear enforcement framework, every contingent promise would end up in a dispute about timing. Was the event supposed to happen by now? Has it truly become impossible, or is it just delayed? Sections 32 to 36 give courts, and businesses drafting contracts, a consistent way to answer those questions instead of relitigating them from scratch every time. Institutional teaching material on commercial law, including material used by professional bodies like the Institute of Chartered Accountants of India, treats this sequence as one of the more testable and practically relevant parts of the Contract Act for exactly this reason.

When you draft or review any agreement with an “if” clause tied to a future uncertain event, whether it is a supply contract, an insurance policy, or a bonus arrangement, these five sections are the checklist worth running through. Is the event supposed to happen or not happen? Is it tied to a person’s conduct? Is there a fixed deadline? Is the event even possible to begin with? Getting these answers right at the drafting stage avoids a lot of arguments later.

What do you think? If you were drafting a supply contract that depends on a government clearance coming through, would you rather build in a fixed deadline under a rule like Section 35, or leave the timeline open under Section 32? And can you think of a real business scenario where a contingent contract might quietly turn void without either party immediately realising it?

References

1. https://www.indiacode.nic.in/show-data?actid=AC_CEN_3_20_00035_187209_1523268996428&sectionId=38636&sectionno=32&orderno=33
2. https://indiankanoon.org/doc/124768/
3. https://thelegalschool.in/blog/contingent-indian-contract-act
4. https://ibclaw.in/section-34-of-indian-contract-act-1872-when-event-on-which-contract-is-contingent-to-be-deemed-impossible-if-it-is-the-future-conduct-of-a-living-person/
5. https://lawbhoomi.com/contingent-contracts-under-indian-contract-act/
6. https://resource.cdn.icai.org/74585bos60476-fnd-p2-nset-cp2-u6.pdf