Contingent Contracts under Sections 31 to 36 of the Indian Contract Act, 1872: The Collateral Event, Enforcement on Happening and Non-Happening, Future Conduct of a Living Person, Fixed Time and Impossible Events

Chapter III of the Act runs to six sections and deals with contracts whose performance depends on something that may or may not happen. The definition in Section 31 turns on one word, collateral, and the five sections that follow work out when such a contract may be enforced and when it becomes void. The category is far larger in practice than its short treatment suggests: insurance, indemnity, guarantee, agreements conditional on a licence or an approval, and most construction and acquisition documents are contingent contracts, and the rules in Sections 32 to 36 decide when the obligation crystallises.

1. The Definition

Section 31, Indian Contract Act, 1872

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.

Illustration. A contracts to pay B rupees ten thousand if B's house is burnt. This is a contingent contract.

1.1 The essential elements

There must be a valid contract. Section 31 defines a contingent contract, so every requirement of Section 10 must be satisfied. A wagering agreement is not a contingent contract, because it is not a contract at all.
Performance must depend on an event. The obligation is not immediate; it arises or is defeated on the event.
The event must be collateral to the contract. It must stand outside the contract, and must not be a performance promised by either party. A condition requiring one party to do something is a term of the contract, not a contingency.
The event must be uncertain. If the event is bound to happen, the contract is absolute with performance postponed, not contingent. Death is certain, but the date of death is uncertain, so a contract conditional on a person dying before a stated date is contingent.
The event must not be within the promisor's mere will. An obligation the promisor may perform or not as he pleases is illusory, and there is no consideration for it.

1.2 Collateral event and promised performance

The distinction that decides most disputes is between an event collateral to the contract and a performance promised under it. If A agrees to deliver goods and B agrees to pay on delivery, the delivery is not a contingency; it is A's promise, and the sections on reciprocal promises apply. If A agrees to sell land provided the authority grants permission, the grant is collateral, because neither party has promised to bring it about, and Chapter III applies.

📖 Chandnee Widya Vati Madden v. Dr. C. L. Katial, AIR 1964 SC 978

Facts: An agreement for the sale of immovable property in Delhi provided that the vendor should obtain the permission of the Chief Commissioner for the transaction within two months of the agreement, and that if the permission was not forthcoming within that time it was open to the purchaser either to extend the date or to treat the agreement as cancelled. The permission was not obtained within the period and the vendor sought to treat the agreement as at an end.

Held: The Supreme Court held that time was not of the essence of the agreement and decreed specific performance. The express terms gave the option of extension to the purchaser, which showed that the parties did not intend the lapse of the period to determine the agreement automatically. The purchasers had throughout been willing to extend the time and to perform, and it was the vendor who had refused. The Court directed the vendor to apply for the permission so as to complete performance of her part of the contract.

Ratio: Where a contract is conditional on a permission being obtained, the party who undertook to obtain it must make the application, and the expiry of a stipulated period does not by itself discharge the contract where the terms show that the parties did not so intend.

2. Section 32: Enforcement on the Happening of an Event

Sections 32 and 33, Indian Contract Act, 1872

32. Contingent contracts 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, such contracts become void.

Illustrations. (a) A makes a contract with B to buy B's horse if A survives C. This contract cannot be enforced by law unless and until C dies in A's lifetime. (b) A makes a contract with B to sell a horse to B at a specified price, if C, to whom the horse has been offered, refuses to buy him. The contract cannot be enforced by law unless and until C refuses to buy the horse. (c) A contracts to pay B a sum of money when B marries C. C dies without being married to B. The contract becomes void.

33. Contingent contracts to do or not to do anything if an uncertain future event does not happen, may be enforced when the happening of that event becomes impossible, and not before.

Two consequences follow. A suit brought before the event has happened is premature and must fail, not because the contract is bad but because the cause of action has not yet arisen. And where the event becomes impossible, the contract becomes void under Section 2(j), so Section 65 applies and any advantage received under it must be restored.

Five situations, five rules for when the obligation can be enforced

3. Section 33: Enforcement on Non-Happening

Section 33 is the mirror of Section 32 and is often overlooked. Where the obligation depends on an event not happening, the contract can be enforced only when the happening of the event has become impossible, and not merely when it seems unlikely or when a reasonable time has passed. The illustration to the section is of an agreement to pay a sum if a ship does not return; the contract may be enforced when the ship sinks.

4. Section 34: Future Conduct of a Living Person

Section 34, Indian Contract Act, 1872

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.

Illustration. A agrees to pay B a sum of money if B marries C. C marries D. The marriage of B to C must now be considered impossible, although it is possible that D may die and that C may afterwards marry B.

The section supplies a rule of practical certainty. Strictly, a person who has married another may one day be free to marry the promisee, and on a literal view the event would never become impossible. Section 34 treats it as impossible once the person has done something that makes the contemplated conduct achievable only through further contingencies. The contract therefore becomes void at that point under Section 32, and the parties are not left waiting indefinitely.

5. Section 35: Event Within a Fixed Time

Section 35, Indian Contract Act, 1872

Contingent contracts to do or not to do anything if a specified uncertain event happens within a fixed time become void if, at the expiration of the time fixed, such event has not happened, or if, before the time fixed, such event becomes impossible.

Contingent contracts to do or not to do anything if a specified uncertain event does not happen within a fixed time may be enforced by law when the time fixed has expired and such event has not happened, or before the time fixed has expired, if it becomes certain that such event will not happen.

Section 35 combines the two directions of Sections 32 and 33 with a time limit. The practical effect is to convert an open-ended contingency into one that resolves on a date, which is why time-limited conditions are so common in commercial documents: they give both parties a point at which they know where they stand.

6. Section 36: Impossible Events

Section 36, Indian Contract Act, 1872

Contingent agreements to do or not to do anything if an impossible event happens are void, whether the impossibility of the event is known or not to the parties at the time when it is made.

Illustrations. (a) A agrees to pay B one thousand rupees if two straight lines should enclose a space. The agreement is void. (b) A agrees to pay B one thousand rupees if B will marry A's daughter C. C was dead at the time of the agreement. The agreement is void.

Section 36 parallels the first paragraph of Section 56, which makes an agreement to do an impossible act void, and it produces the same result whether or not the parties knew. Note the drafting: Section 36 speaks of a contingent agreement, not a contingent contract, because such an arrangement never becomes a contract at all.

7. The Six Sections in Summary

Section	Situation	Rule
31	Definition	A contract to do or not to do something if an event collateral to the contract does or does not happen
32	Contingent on an event happening	Not enforceable unless and until the event happens; becomes void if the event becomes impossible
33	Contingent on an event not happening	Enforceable when the happening of the event becomes impossible, and not before
34	Contingent on how a living person will act at an unspecified time	The event is deemed impossible when that person does something making the conduct achievable only under further contingencies
35	Event to happen, or not to happen, within a fixed time	Void if the time expires without the event, or if the event becomes impossible before the time; enforceable in the converse case when the time expires or the event becomes certain not to happen
36	Contingent on an impossible event	Void, whether or not the parties knew of the impossibility

8. Contingent Contracts in Practice

Insurance. The insurer's obligation arises on the collateral event of the loss. The assured has an insurable interest, which is what keeps the contract outside Section 30.
Indemnity. Section 124 makes the promisor liable on the collateral event of the promisee suffering loss.
Guarantee. The surety's liability under Sections 126 to 147 arises on the collateral event of the principal debtor's default.
Agreements conditional on approval, licence or clearance, such as a sale of land subject to regulatory permission, are governed by Sections 32 and 35.
Anticipatory breach of a contingent contract is possible. In Frost v. Knight, (1872) LR 7 Ex 111, a promise to marry on the death of the promisor's father was repudiated during the father's lifetime, and the court held that the promisee need not wait for the contingency and could sue at once, the repudiation being an immediate breach.

📖 Frost v. Knight, (1872) LR 7 Ex 111

Facts: The defendant promised to marry the plaintiff on the death of his father. While the father was still living the defendant broke off the engagement and announced that he would not perform his promise. The plaintiff sued at once, without waiting for the father's death.

Held: The action succeeded. Where a party to a contract renounces his obligation before the time for performance has arrived, the other party may treat the renunciation as an immediate breach and sue at once, or may keep the contract alive and wait for the time of performance. The fact that the obligation was contingent on a future event did not prevent the repudiation from operating as a present breach.

Ratio: A contingent contract may be broken by anticipatory repudiation before the contingency occurs. The promisee may sue immediately or may await the event, at his election.

⚠ Contingency and condition of performance are not the same

A term requiring one party to do something before the other must perform is a condition of performance governed by the sections on reciprocal promises in Sections 51 to 54, not a contingency under Chapter III. The difference matters for the remedy. If the condition is a party's own promise and he fails to fulfil it, that is a breach and the other party may sue for damages. If the event is genuinely collateral and does not occur, there is no breach at all; the contract simply becomes void under Section 32 and the remedy is restitution under Section 65.

9. The Position Stated Shortly

Section 31 requires a valid contract whose performance depends on an uncertain event collateral to it.
An event promised by a party is not collateral; it is a term, and the reciprocal promises sections apply.
Section 32 makes the contract unenforceable until the event happens and void if it becomes impossible.
Section 33 allows enforcement where the event does not happen, only when its happening becomes impossible.
Section 34 deems an event impossible where a living person has acted so as to make the contemplated conduct achievable only under further contingencies.
Section 35 applies the same rules with a fixed time, so the contingency resolves on a date.
Section 36 voids an agreement contingent on an impossible event, whether or not the parties knew.
Chandnee Widya Vati Madden: where a permission is to be obtained, the party who undertook it must apply, and the expiry of a period does not automatically discharge the contract.
Frost v. Knight: a contingent contract may be repudiated anticipatorily, and the promisee may sue at once or wait.
Where the collateral event fails there is no breach; the contract becomes void and Section 65 governs restitution.

10. Related Topics and Provisions

Topic or provision	Connection
Contingent Contract vs Wagering Agreement	The classification question, in full
Contingent Contract vs Absolute Contract	Where the obligation is immediate and unqualified
Contingent Contract vs Conditional Promise	Conditions precedent, subsequent and concurrent
Wagering Agreements under Section 30	Why a wager is not a contingent contract
Sections 31 to 36, Indian Contract Act	The six provisions of Chapter III
Section 56, Indian Contract Act	Impossible acts and supervening impossibility
Section 65, Indian Contract Act	Restoration where a contract becomes void
Sections 124 and 126, Indian Contract Act	Indemnity and guarantee
Sections 51 to 54, Indian Contract Act	Reciprocal promises and conditions of performance