The Conditions Subsequent Clause: What It Means and How to Negotiate It (2026)

What is a conditions subsequent clause? A condition subsequent is an event that, if it happens (or fails to happen) after a contract is already in force, brings an obligation or the whole contract to an end, or triggers a defined consequence. It is the mirror image of a condition precedent, which must be satisfied before an obligation or the contract comes into being. A short way to hold the two apart: a condition precedent is a gate the deal has to pass through before it starts; a condition subsequent is an exit the deal can take after it has started. Getting the label right matters, because it decides whether anything happened at all, or whether something that was live now has to be unwound. This article is general guidance, not legal advice. Have a qualified professional review a contract before you rely on it. ## Sample condition subsequent clause ```

CONDITION SUBSEQUENT This Agreement takes effect on the date of signature. If [specified event, for example board or regulatory approval] has not occurred by [long stop date], then [the Agreement shall automatically terminate / the following obligations shall cease / Party B may terminate on written notice], and in that case [consequences, for example any deposit paid shall be refunded within [N] days and neither party shall have any further liability except for accrued rights].

|---|---|---|
| Is the obligation live before the condition? | No, not until it is satisfied | Yes, it is already live |
| Effect of the condition | Brings the obligation into being | Ends or changes an existing obligation |
| Risk if it is not met | Nothing started, nothing to unwind | Live obligations must be unwound |
| Typical example | Deal conditional on approval before completion | Approval must be kept or confirmed after completion, or the deal reverses | ## A worked example A company agrees to buy a business, and the deal is signed and completed, but the parties agree that a key customer contract must be novated to the buyer within 60 days. If the deal is structured so that completion happens now and a failure to novate within 60 days lets the buyer unwind the sale or claim a price reduction, the novation is a condition subsequent: the contract is already live, and a later event changes it. If instead the parties had agreed that completion would not happen at all until the novation was done, the novation would be a condition precedent to completion. Same fact, two very different structures, decided entirely by the wording. This is why it is worth being deliberate about which structure you are using. ## How to negotiate a conditions subsequent clause - **Be explicit about which it is.** The label does not decide the point; courts look at the substance of the wording to see whether a contract already exists and only a later event affects it. Draft so there is no doubt.
- **Set a clear long stop date.** A condition that can be satisfied "at any time" leaves the deal hanging. Put a deadline on it.
- **Say whether termination is automatic or on notice.** This decides whether a party must act to end the contract or whether it ends by itself.
- **Spell out the unwind.** Because the contract was live, you need to say what happens to money paid, work done, and continuing obligations.
- **Allocate effort.** Say who must use reasonable efforts to satisfy or avoid the condition, and what counts as a breach of that duty. ## Common mistakes to avoid - Mixing precedent and subsequent language so it is unclear whether the deal ever started.
- No long stop date, so the condition can hang over the contract indefinitely.
- No unwind mechanics, leaving deposits, part performance and accrued rights uncertain when the condition bites.
- Assuming automatic termination when the clause actually required a notice, or the other way round. ## A note on jurisdiction The precedent and subsequent distinction comes from general contract principles and appears across common-law systems. In India the Indian Contract Act, 1872 does not use the term "condition subsequent." The closest statutory concept is the contingent contract in sections 31 and 32: a contract to do or not do something if a collateral uncertain event happens or does not happen, which cannot be enforced until the event occurs and becomes void if the event becomes impossible. Indian courts have held that the label alone is not decisive; they examine the actual wording to decide whether a valid contract already exists. Conditions attached to property can also engage the Transfer of Property Act, 1882. The position varies by jurisdiction. Last verified October 2026. ## Where a contract workspace helps A condition subsequent is really a timing device. Something has to be watched, and if it happens or fails to happen by a set date, the contract changes or ends. The hard part is rarely the drafting. It is remembering the trigger and the long stop date across a stack of live contracts, and keeping the unwind steps straight when the condition finally bites. The idea of an AI contract workspace is to hold all of that in one place: draft and read the clause as part of a connected contract, lift the condition and its deadline onto a live timeline, flag the risk per clause, and edit the wording in plain English. [Adira](https://adiralaw.com) is one tool built on this single-workspace approach. The explanation above stands on its own; a workspace just makes it harder to miss the date on which a condition subsequent turns on.