1. Contingent Contracts — Promises That Depend on an Uncertain Future Event

Every insurance policy is a contingent contract — you pay premiums, but the insurer only pays out if a specific uncertain event happens. This unit's opening topic is the rulebook the Act provides for exactly this kind of "pay only if" promise.

The Problem This Topic Solves

Most contracts create an immediate, unconditional obligation: deliver the goods, pay the price. But real transactions are often not that simple — a promise to pay only if a ship sinks, only if a person doesn't marry someone, only if a house burns down. Sections 31 to 36 of the Indian Contract Act, 1872 answer three questions about these "conditional" promises: when can they be enforced, when do they become void, and how are they different from a bet.

What Is a Contingent Contract? — Section 31

Section 31 defines it precisely: "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."

Three things make a promise "contingent" in this technical sense:

• Performance depends on the happening (or non-happening) of a future event
• That event must be uncertain — if it is bound to happen, the contract is not contingent, it is merely deferred
• The event must be collateral — incidental to the contract, not the very act the promisor undertakes to perform. A promise to paint a house "if you pay me first" is not contingent; the payment is part of the exchange itself, not a collateral condition

Contingent Contract vs. Wagering Agreement

Both look similar on the surface — both depend on an uncertain future event. But Section 30 makes wagering agreements void, while contingent contracts are perfectly enforceable. The difference is why the parties are betting on the event.

Contingent on the Happening of an Event — Section 32

Where a contract depends on an uncertain future event happening, it cannot be enforced until that event actually happens. If the event becomes impossible, the contract itself becomes void.

Contingent on the Non-Happening of an Event — Section 33

The mirror-image rule: where the contract depends on an uncertain future event not happening, it can be enforced only once it becomes impossible for that event to happen — not before.

When the Event Is a Living Person's Future Conduct — Section 34

A special problem arises when the contingency is how a living person will behave at some unspecified point — this can never be proven with certainty in advance. Section 34 solves it: such an event is treated as impossible the moment the person does something that makes it impossible for them to act in that way within any definite time, unless the contract is subject to further contingencies.

Contracts Tied to a Fixed Time — Section 35

Section 35 adds a time limit to Sections 32 and 33:

• A contract contingent on a specified event happening within a fixed time becomes void if the event does not happen (or becomes impossible) before the time expires
• A contract contingent on a specified event not happening within a fixed time can be enforced once the time expires without the event happening, or as soon as it becomes certain the event will not happen — whichever is earlier

Agreements on Impossible Events Are Void — Section 36

If the event itself is impossible, the agreement is void from the start — regardless of whether the parties knew about the impossibility when they made the agreement.

• Section 31 — a contingent contract depends on an uncertain event collateral to the contract
• Section 32 — contingent on an event happening: enforceable only once it happens; void if it becomes impossible
• Section 33 — contingent on an event not happening: enforceable only once it becomes impossible for the event to happen
• Section 34 — a living person's future conduct is deemed impossible the moment their own act rules it out
• Section 36 — an agreement on an impossible event is void, known or unknown to the parties

• Section 35 adds a fixed-time cutoff on top of Sections 32 and 33
• Wagering agreements (Section 30) look contingent but are void — the test is whether the parties have a genuine interest beyond the bet itself
• Frost v. Knight is the standard illustration for Section 34 — a party's own conduct can make a "future conduct" contingency impossible

A Practical Example

Anand takes a fire insurance policy on his shop, promising to pay a premium every year; the insurer promises to pay ₹5,00,000 only if the shop burns down. This is a contingent contract under Section 31 — the insurer's obligation depends on an uncertain, collateral event (fire). If the shop is demolished for road-widening before any fire could occur, the contingency (fire) becomes impossible, and under Section 32 the insurer's obligation to pay on that policy becomes void.

Quick Revision Points

• Contingent contract = depends on an uncertain event collateral to the contract (Section 31)
• Happening-of-event contracts: enforceable only after the event happens (Section 32)
• Non-happening-of-event contracts: enforceable only once the event becomes impossible (Section 33)
• A living person's future conduct becomes "impossible" the moment their own act rules it out (Section 34)
• Fixed-time contingencies follow Section 35's cutoff rules
• Impossible-event agreements are void from the start (Section 36)
• Contingent contracts are genuine transactions; wagers (Section 30) are void bets dressed up the same way