Contingent Contracts under Indian Contract Act

Contingent Contracts under the Indian Contract Act, 1872

Chapter III of the Indian Contract Act, 1872, spanning Sections 31 to 36, is devoted entirely to contingent contracts. These six sections, though compact, contain within them a self-sufficient and elegant legal framework that governs a wide class of everyday commercial arrangements — from insurance policies to option agreements, and from land sale contracts to litigation-linked obligations.

What is a Contingent Contract?

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 the Act provides is illuminating in its simplicity: A contracts to pay B Rs. 10,000 if B's house is burnt. The contract already exists between them. But its performance — the actual payment — is held in suspension until the uncertain event (the house being burnt) either occurs or does not.

The word "contingent" used in the Indian Contract Act carries the same meaning as "conditional" in common law — contracts which have been duly formed but provide that the performance of obligations under them is conditional on the happening or not happening of an event. Three elements are therefore essential to every contingent contract: first, there must be a valid, subsisting contract; second, the performance must depend on the occurrence or non-occurrence of an event; and third, that event must be collateral to the contract — meaning it is neither a performance directly promised as part of the contract, nor the whole of the consideration for the promise.

This collateral nature of the contingency is critical. A promise to pay money for finding a lost dog is not a contingent contract — the promise does not even arise as a contract until the dog is found. On the other hand, a contract to pay on the loss of a ship is contingent: the contract is already formed; only performance waits upon the ship's fate.

It is equally important to distinguish a contingent contract from a contract dependent on an absolutely certain event. A contract to pay on the death of a person is not truly contingent — death is inevitable; only the timing is unknown. True contingency requires that the event may or may not happen. All contracts of insurance (other than life insurance) are, for this reason, classic examples of contingent contracts.

Rules Governing Enforcement

Contracts Contingent on an Event Happening (Section 32)

Section 32 lays down that a contingent contract to do or not to do anything, if an uncertain future event happens, cannot be enforced unless and until that event has happened. If the event becomes impossible, the contract becomes void.

The illustrations in the section are instructive: A contracts to buy B's horse if A survives C — no enforcement until C actually dies in A's lifetime. In Firm N. Peddanna Ogeti Balayya v. Katta V. Srinivasayya Setti Sons (AIR 1954 SC 26), the Supreme Court enforced an agreement that entitled an agent to recover costs of litigation from the litigant, holding that such commission payable on the success of litigation was a classic contingent contract and enforceable upon the happening of the contingency (success in the suit).

Contracts Contingent on an Event Not Happening (Section 33)

Section 33 is the mirror image of Section 32. Where a contract is contingent on an uncertain future event not happening, it can be enforced only when the happening of that event becomes impossible. The Act's illustration is elegant: A agrees to pay B a sum if a certain ship does not return. The ship sinks. The sinking — making it impossible for the ship to return — is the trigger for enforceability. The impossibility of the event's occurrence is the condition of enforcement.

Contingency Dependent on Future Conduct (Section 34)

Section 34 deals with a special problem: what happens when the contingency depends not on an objective external event, but on how a living person will conduct themselves at some unspecified future time? The Act provides that such an 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 classic English case of Frost v. Knight (1872) LR 7 Ex 111 beautifully illustrates this principle. The defendant had promised to marry the plaintiff upon the death of his father. While the father still lived, the defendant married another woman entirely. The court held that by marrying another woman, he had rendered it impossible that he would ever marry the plaintiff, and she was entitled to sue immediately for breach. The principle applies because the section does not require that the impossibility be absolute and forever — it suffices that the person has done something making it impossible to fulfil the contingency within any definite time.

Time-Bound Contingencies (Section 35)

Section 35 introduces the dimension of time into contingent contracts, and it lays down two distinct rules corresponding to whether the contract is contingent on something happening or not happening within a fixed time.

Where performance is contingent on an event happening within a fixed time, the contract becomes void if, at the expiration of that time, the event has not happened — or if, before the time expires, the event becomes impossible. Where performance is contingent on an event not happening within a fixed time, it may be enforced either when the time expires without the event having occurred, or before the time expires, if it has become certain that the event will not happen. The illustration of a ship that is burnt within the year captures both rules with precision: if A promised to pay B if a ship returned within a year, and the ship is burnt — the contract is void; if A promised to pay B if the ship did not return within a year, and the ship is burnt — the contract becomes enforceable at once.

In P. Purushotham Reddy v. Pratap Steels Ltd. (AIR 2003 AP 141), the Andhra Pradesh High Court applied Section 35 to hold that where a contingent contract became time-bound, performance could not be demanded after the expiry of the stipulated period without the specified event having occurred.

Contracts Contingent on Impossible Events (Section 36)

Section 36 strikes at the very root of contingency: if the event on which the contract is contingent is itself impossible, the agreement is void — and this is so whether or not the parties knew of the impossibility at the time they contracted. The Act furnishes two vivid illustrations: a promise to pay Rs. 1,000 if two straight lines should enclose a space (geometrically impossible), and a promise to pay Rs. 1,000 if B will marry A's daughter C, when C was already dead at the time of the agreement. Both are void from inception.

This provision ensures that the law does not permit parties to dress up a merely illusory promise as a contract by anchoring it to an event that can never happen.

The Condition Must Be Collateral

Across all these provisions, the courts have consistently emphasised that the collateral nature of the condition is the hallmark that distinguishes a contingent contract from other arrangements. In Secy. of State for India v. A.J. Arathoon (1879 5 Mad 173), the Madras High Court dealt with a contract for supply of timber to a Government Department, where approval by a Superintendent was a condition precedent to the supplier's right to demand payment. The court held that since approval was collateral to the performance, the supplier could not demand payment until such approval was given.

It has also been established that a condition may be express or implied, and may even depend on the discretionary act of a third party or of one of the contracting parties themselves. The courts look at the substance of the arrangement rather than its form.

Contingent Contracts and Frustration

An important connection exists between contingent contracts and the doctrine of frustration. Where a contract itself contains, expressly or impliedly, a term by which it would stand discharged on the happening of a certain event, the dissolution of the contract takes place under Section 32 of the Contract Act — not under Section 56 (which deals with supervening impossibility or frustration). The Supreme Court made this distinction clear in Satyabrata Ghose v. Mugneeram Bangur & Co. (AIR 1954 SC 44), holding that questions of frustration in India must be decided on the provisions of the Act itself, and where the contract has provided for the contingency — even impliedly — Section 32 governs the outcome.

Contingent Contracts and Anticipatory Breach

A question naturally arises: if a contingent contract's performance is not yet due because the event has not occurred, can there be an anticipatory breach? The answer, drawn from Frost v. Knight and reaffirmed in Indian law, is yes. The principle of anticipatory breach applies even to contingent contracts. If the defendant has, by his own act, made it impossible that the contingency will ever be fulfilled, the aggrieved party is not required to wait. He may sue immediately. The option, however, remains with the aggrieved party — he may choose to await the stipulated time for performance, bearing the risk that circumstances may change in the meantime.

Practical Significance

The practical reach of contingent contracts in commercial life is vast. Contracts of insurance (other than life insurance), indemnity, and guarantee all bear the character of contingency. Property transactions made subject to government permission, contracts for sale of shares contingent on the conversion of a bank into a financial corporation, agreements to sell property when a mortgage is redeemed, ante-nuptial agreements contingent on a marriage taking place — all have been held by courts across India to constitute contingent contracts. In each case, the parties have formed a valid and binding contract, but the obligation of performance waits upon the occurrence or non-occurrence of the specified event. Neither party can unilaterally withdraw before the event occurs, and if a term can be implied that one party must use reasonable efforts to bring about the condition, the courts will give effect to it.