Contingent Contracts (Sections 31–36)

Sections 31 to 36 of the Indian Contract Act, 1872 govern a class of contracts whose enforceability is suspended on the happening or non-happening of a future uncertain event collateral to the contract. Section 31 defines the contingent contract. Sections 32 and 33 govern enforcement on the happening or non-happening of the event. Section 34 deals with the contingency of a person's future conduct. Section 35 governs contingencies tied to a fixed time. Section 36 voids agreements contingent on impossible events. The architecture is a single idea developed across six sections: the bargain exists, but the rights it creates are dormant until the collateral event resolves itself. The same architectural sense is reflected in the chapter on the essentials of a valid contract, where the place of the contingent contract within the larger taxonomy of valid, void and voidable contracts is set out.

For the candidate, the key analytical task is to identify when a contract is contingent and when it is not. Many fact-patterns superficially resemble contingent contracts but turn out, on careful reading, to be conditional sales, contracts with reciprocal promises, or contracts with a mode of performance dependent on an external event. The Supreme Court has been firm on the point: a contract is not contingent merely because performance depends on something outside the parties' control. The event must be both collateral to the contract and uncertain. Without these two limbs, Section 31 does not apply.

Section 31 — definition and essentials

Section 31 defines a contingent contract as a contract to do or not to do something, if some event collateral to such contract does or does not happen. The illustration in the section is direct: A contracts to pay B Rs 10,000 if B's house is burnt. The contract exists on signing. The right to receive the money does not become enforceable unless and until the burning takes place. Insurance contracts are the textbook example — the insurer has a present obligation, but the obligation to pay crystallises only on the happening of the insured-against event. The Supreme Court in Commissioner of Excess Profits Tax v. Ruby General Insurance Co., AIR 1957 SC 669, treated insurance as a paradigm of the contingent contract.

Two essentials emerge from the section. The first is the uncertainty and futurity of the event. An event that has already happened, or that is bound to happen as a matter of certainty, cannot be the subject of a contingency under Section 31. The second is that the event must be collateral to the contract — it must not form part of the consideration, and it must not be the very obligation of one of the parties. Where the parties promise to do something for each other, the promises are reciprocal, not contingent. The Supreme Court in Northern India Iron and Steel Co. Ltd. v. State of Haryana, AIR 1976 P&H 59, held that an agreement to pay minimum demand charges is not a contingent contract — there is no collateral event; the consumer is liable to pay the charges regardless.

The Allahabad High Court in Bhairon Prasad Chaurasiya v. Smt. Tara Devi, AIR 1980 All 36, illustrated the same boundary. An agreement to sell a house was argued to be a contingent contract on the basis that either party might refuse to perform. The Court rejected the argument: such a contingency would not be collateral to the contract; it would be the very performance of the contract. An agreement to purchase property is neither a contingent contract nor a mere possible right or interest. The case is the standard exam authority on what is not a contingent contract.

Reciprocal promises versus contingent contracts

Section 31 must be read with the rules on reciprocal promises in Section 51. Reciprocal promises that form the consideration for each other are not contingent contracts — they are not collateral to each other. Where A promises to pay Z Rs 300 if Z sells his land to A, the contract is not contingent on the sale, since the sale is the consideration moving from Z. But where A promises to sell his land to Z if A succeeds in his pending litigation concerning the land, the contract is contingent — the success of the litigation is collateral to the substantive bargain of sale. The illustration is from Ismail v. Dandbhai, 2 Bom LR 118, and the principle is settled.

The same distinction was applied in Kirpal Das v. Manager, Encumbered Estates, AIR 1936 Sind 26. A contract by a person to sell his share in joint property when the joint owners agreed to partition was held to be a contingent contract enforceable on the partition. The partition was collateral to the substantive obligation to sell the share, and the partition itself was uncertain when the contract was made. The case is doctrinally important — it shows that the collateral event need not be wholly external; it can be the act of a third party (the joint owners) so long as it is uncertain and collateral. The relationship with the chapter on acceptance arises only at the formation stage — once the contract is formed, its enforceability is suspended on the contingency.

Section 32 — enforcement on the happening of the event

Section 32 governs contingent contracts to do or not to do anything if an uncertain future event happens. Such contracts cannot be enforced by law unless and until that event has happened. If the event becomes impossible, the contract becomes void. The provision is structural: it identifies when the rights and duties under the contract crystallise into enforceable obligations. The illustrations are clear. A contracts with B to buy B's horse if A survives C. The contract is unenforceable until C dies in A's lifetime. A contracts to pay B a sum of money when B marries C; C dies without marrying B; the contract becomes void.

The Supreme Court in Bashir Ahmad v. Government of Andhra Pradesh, AIR 1970 SC 1089, applied Section 32 to a contract for the sale of a manuscript. The contract was alleged to be contingent on the formation of a company that the Government had proposed to float. The Court held that the contract was not contingent on the formation of the company — even if the company was not formed, the seller did not lose his right to enforce the contract for the part already performed. The case is a useful illustration of how courts identify the true contingency: not every external uncertainty is the collateral event under Section 31.

Where the event has become impossible, the contract is void. In Gian Chand v. Gopala, (1995) 2 SCC 528, the Supreme Court applied this rule to a contract for the sale of land where the State had subsequently issued a notification under Section 6 of the Land Acquisition Act. The acquisition rendered the contract impossible of performance. The contract being a contingent contract based on the uncertain future event of the property remaining in the seller's hands, the contract became void on the issuance of the notification, and the buyer was entitled under Section 33 to the refund of the earnest money. The case is the standard authority on the operation of Section 32's second limb.

Section 33 — enforcement on the non-happening of the event

Section 33 is the converse of Section 32. 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 illustration: A agrees to pay B a sum of money if a certain ship does not return; the ship is sunk; the contract can be enforced when the ship sinks. The non-return is established by the impossibility of return; the right under the contract becomes enforceable.

The boundary between Section 32 and Section 33 is conceptual. Section 32 is about performance triggered by an event happening. Section 33 is about performance triggered by an event not happening. The distinction matters for limitation — the cause of action accrues when the right becomes enforceable, and that is the date when the collateral event happens (Section 32) or becomes impossible (Section 33). The Supreme Court in Ramzan v. Hussini, (1990) 1 SCC 104, applied the same principle to an agreement contingent on the redemption of a mortgage by the plaintiff: limitation began running on the date of redemption, since that was the date on which the contract became enforceable. The interplay with the chapter on performance of contract is important — the time and manner of performance under a contingent contract are governed by the rules on performance, but the date from which performance is due is fixed by Sections 32 and 33.

Section 34 — contingencies tied to a person's future conduct

Section 34 deals with the contingency of how a person will act at an unspecified time. The event is deemed to become impossible when that 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 the standard one: 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 remains theoretically possible that D may die and that C may afterwards marry B.

The provision answers a problem of practical certainty. Without Section 34, every contract contingent on a person's future conduct would remain perpetually unenforceable — the conduct may always be performed at some future time. The section fixes the contingency as impossible when the person does something inconsistent with the future conduct, or that requires further contingencies before the conduct can occur. The earlier authority on the section, In re Jaunpur Sugar Factory, 89 IC 438, applied it to a subscription for shares conditional on the company appointing the subscriber as its sole agent. The company went into liquidation before making the appointment. The contingency was held to have become impossible, and the subscriber was not liable on the shares.

Section 35 — contingencies within a fixed time

Section 35 governs contingent contracts where the event must happen within a fixed time. The first limb addresses contracts contingent on an event happening within the time: such a contract becomes void if, at the expiration of the time, the event has not happened, or if before the time the event becomes impossible. The second limb addresses contracts contingent on an event not happening within the time: such a contract may be enforced when the time has expired and the event has not happened, or before the time has expired if it becomes certain that the event will not happen.

The illustrations are paired. A promises to pay B a sum of money if a certain ship returns within a year. The contract may be enforced if the ship returns within the year and becomes void if the ship is burnt within the year. The same facts recast for Section 35's second limb: A promises to pay B a sum of money if a certain ship does not return within a year. The contract may be enforced if the ship does not return within the year, or if it is burnt within the year. The two limbs cover the universe of fixed-time contingencies.

The Andhra Pradesh High Court in Panem Venkanarayana Sastry v. Rajupalli Chinna Yella Reddy, AIR 1959 AP 256, applied Section 35 to an agreement for sale subject to the title being approved by the buyer's family lawyer within a reasonable time. The Court held that the absence of a fixed time in the agreement meant a reasonable time was implied, and the ten days that elapsed before the lawyer's approval was not unreasonable. The agreement was therefore enforceable. The case is the standard authority for the principle that where a contingency is tied to time but no specific time is named, the law fills the gap with reasonableness. A parallel rule operates in the chapter on consideration, where the requirement that consideration be real but not necessarily adequate sets the same baseline of reasonableness.

Section 36 — agreements contingent on impossible events

Section 36 declares contingent agreements to do or not to do anything if an impossible event happens to be void, whether the impossibility of the event is known or not to the parties at the time when the agreement was made. The section closes the chapter with a categorical rule. The two illustrations are textbook: A agrees to pay B Rs 1,000 if two straight lines should enclose a space — void; A agrees to pay B Rs 1,000 if B will marry A's daughter C, who was dead at the time of the agreement — void.

The provision is conceptually distinct from Section 32. Under Section 32, the contract begins as a valid contingent contract and becomes void only if the event subsequently becomes impossible. Under Section 36, the impossibility exists at the moment of contracting, and the agreement is void from inception. The difference matters for restitution: a contract that is void from inception falls under Section 65 of the Act, treated more fully in the chapter on quasi-contracts under Sections 68 to 72; a contract that becomes void on supervening impossibility may also engage Section 56 and the doctrine of frustration.

Distinguishing Section 32 from Section 56

The most-tested distinction in this chapter is between Section 32 and Section 56. Section 32 dissolves the contract by its own force — the parties have provided expressly or impliedly that the contract will operate only if the contingency materialises, and the contract terminates when the contingency fails. Section 56 dissolves the contract by an external force — supervening impossibility renders performance unlawful, physically impossible, or so radically different from what was contemplated that the contract is no longer the same. The Calcutta High Court in Durga Devi Bhagat v. J.B. Advani & Co. Ltd., 76 CWN 528, drew the line precisely: Section 32 comes into play when the contract is dissolved by its own force, while Section 56 occupies its field when the contract crumbles down due to an impact of a violent nature with an outside force.

The line has practical consequences. Where the parties have provided in the contract for the consequence of a particular event, the contract operates by its own terms and Section 32 disposes of it. Where the parties have not provided for the supervening event, Section 56 may apply to relieve them from performance. The fuller treatment of frustration is in the chapter on the doctrine of frustration under Section 56; the candidate should hold the conceptual distinction firm and apply the right section to the facts.

Distinguishing wager from contingent contract

The second key distinction is between a contingent contract and a wagering agreement. Both depend on an uncertain future event. Both involve parties whose rights crystallise on the determination of the event. The decisive difference is that the contingent contract has an independent obligation — sale, lease, payment of a debt, performance of a service — that the contingency makes enforceable. The wager has no underlying transaction other than the bet itself; the parties have no real interest in the event apart from winning or losing the stake. An insurance contract is not a wager because the insured has a real interest in the event. A bet on the outcome of a horse race is a wager because the bettor has no interest in the race other than the bet. The wager is void under Section 30, treated in the chapter on void agreements; the contingent contract is governed by Sections 31 to 36 and is enforceable on the happening of the collateral event.

Burden of proof and pleading

A plea that a contract is contingent is a defensive plea — it says the right is not yet enforceable, or has become void by the failure of the event. The burden is on the party asserting the plea. The Rajasthan High Court in Nemi Chand v. Harak Chand, AIR 1965 Raj 132, held that a plea that a contract is contingent must be alleged and proved by the party who sets it up, and that there is no duty on the trial court to go into the matter suo motu. The provision is unlike Section 3 of the Limitation Act, which casts a duty on the court to dismiss a time-barred suit even if the plea is not raised. Section 32 simply provides that the contingent contract shall not be enforced unless the event happens; it does not require the court to dismiss without a plea.

For the practitioner, this has consequences. A defendant wishing to resist a suit on the basis that the contract was contingent and the contingency has not materialised must plead the fact, lead evidence to establish it, and demonstrate that the event was both collateral and uncertain. The Supreme Court has on several occasions rejected casual pleas of contingency where the parties had in fact entered into a substantive bargain with a specific mode of performance. The Bombay High Court in Rachhoddas v. Nathmal Hirachand & Co., AIR 1949 Bom 356, drew the boundary: where the parties provided that goods were to be taken delivery of when they arrived, they were dealing with the mode of performance and not with the question of the very obligation to perform.

Bank guarantees, sale-deeds and the modern fact-patterns

Section 31 is regularly applied to bank guarantees. The Supreme Court has held that a contract of guarantee is an independent contract between the bank and the beneficiary, and where the bank's obligation is to pay on the happening of an uncertain future event, the guarantee is a contingent contract under Section 31, enforceable only on the happening of that event. The principle is also applied to agreements for sale of immovable property contingent on the seller obtaining permission, eviction of a tenant, or conversion of agricultural land — each of these is a collateral event and the contract is contingent within Section 31.

The Supreme Court in Rojasara Ramjibhai Dahyabhai v. Jani Narottamdas Lallubhai, AIR 1986 SC 1912, applied the section to a contract for sale of agricultural land subject to obtaining permission for non-agricultural use. Once the seller acquired full title and obtained the permission, the contingency was satisfied and the contract became enforceable. The case in Nandkishore Lalbhai Mehta v. New Era Fabrics (P) Ltd., AIR 2015 SC 3796, applied the same reasoning to an agreement for sale subject to clearances under the Urban Land Ceiling Act and consent of the labour union — once the union refused consent, the agreement could not be performed, and the buyer was entitled to refund of the deposit with interest. The fuller treatment of remedies in such cases is in the chapter on remedies for breach.

Exam angle and pitfalls

The pitfalls in this chapter are characteristic. First, do not confuse a contingent contract with a wager — the contingent contract has an independent obligation, the wager has only the bet. Second, do not confuse Section 32 with Section 56 — Section 32 operates by the contract's own force, Section 56 by external supervening impossibility. Third, do not assume that every external uncertainty is a collateral event — the event must be both uncertain and outside the consideration. Fourth, do not assume that an agreement to perform a future obligation is contingent — performance is the substance of the bargain, not a collateral event. Fifth, remember that under Section 36 an agreement contingent on an impossible event is void from inception, regardless of the parties' knowledge.

Candidates should also remember the conceptual link to the rules on free consent and on lawful object and consideration. A contingent contract may be void under Section 23 if the collateral event itself is unlawful — for example, a contract to pay a sum if a third party commits a crime. The contingency is irrelevant if the agreement is independently void on Section 23 grounds. Conversely, a contract that is otherwise valid does not become contingent merely because performance depends on something — the Supreme Court has rejected this argument repeatedly. Section 31 requires both collaterality and uncertainty; it cannot be invoked simply because the parties' performance is conditional in the loose sense.

Frequently asked questions

What is the difference between a contingent contract and a wagering agreement?

Both depend on an uncertain future event, but the structural difference is decisive. A contingent contract under Section 31 has an independent substantive obligation — a sale, a lease, a debt — that the contingent event makes enforceable. The parties have a real interest in the event apart from the contingency itself. A wagering agreement has no underlying transaction; the only stake is the bet on the outcome. The Carbolic Smoke Ball formulation captures the test: in a wager, neither party has any interest in the contract other than the sum or stake he will win or lose. An insurance contract is contingent, not a wager, because the insured has a real interest in the event.

What is the difference between Section 32 and Section 56 of the Indian Contract Act?

Section 32 dissolves a contract by the contract's own force — the parties have agreed expressly or impliedly that the contract will operate only if the contingency materialises, and the contract terminates when the contingency fails or becomes impossible. Section 56 dissolves a contract by an external supervening impossibility — performance becomes unlawful, physically impossible, or so radically different from what was contemplated that the contract is no longer the same. The Calcutta High Court in Durga Devi Bhagat v. J.B. Advani & Co. Ltd. drew the line precisely: Section 32 operates when the contract dissolves by its own force, while Section 56 operates when the contract is overtaken by an outside force the parties did not provide for.

Is an agreement to sell a house a contingent contract because either party may refuse?

No. The Allahabad High Court in Bhairon Prasad Chaurasiya v. Smt. Tara Devi, AIR 1980 All 36, held that an agreement to sell a house is not a contingent contract on the ground that either party may refuse to perform. The reason is structural: such a contingency is not collateral to the contract — it is the very performance of the contract. Section 31 requires that the event be collateral, meaning outside the consideration and the substantive obligations of the parties. A refusal to perform is itself a breach, not a contingency, and the remedy is a suit for breach, not the doctrine of contingent contracts.

Can a bank guarantee be a contingent contract under Section 31?

Yes. A contract of guarantee, particularly a bank guarantee, is an independent contract between the bank and the beneficiary. Where the bank's obligation to pay arises only on the happening of an uncertain future event — such as default by the principal debtor or breach of a stipulated condition — the guarantee is a contingent contract within Section 31. The Bombay High Court in Western Coalfields Ltd. v. Rajesh, 2012 (1) Mh LJ 394, confirmed that such a guarantee cannot be enforced under Section 32 unless and until the contingent event has occurred. Once the event happens, the bank's obligation crystallises and the beneficiary may invoke the guarantee.

Is an agreement contingent on an impossible event void from inception?

Yes. Section 36 declares that 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 the agreement was made. The two illustrations capture the rule: an agreement to pay if two straight lines should enclose a space, and an agreement to pay if B will marry A's daughter C, who was dead at the time. Both are void from inception. Section 36 is conceptually distinct from Section 32 — Section 32 voids the contract on supervening impossibility, while Section 36 voids the agreement on antecedent impossibility.