Condition Subsequent

A condition subsequent is a future event that, if it happens, ends or suspends an already-formed contract duty. In Contracts, it works after the agreement is in place, not before.

What is Condition Subsequent?

A condition subsequent in Contracts is a contract term that can cut off an existing duty after the contract has already been made. If the stated event happens, the party’s obligation can end, change, or be discharged depending on the contract language.

That timing matters. With a condition subsequent, the contract starts out valid and enforceable, and the parties are already bound. The later event is what changes the legal landscape. That is different from a condition precedent, where nothing has to be performed until the triggering event happens first.

You usually see a condition subsequent when the parties want a built-in exit if something later makes performance impossible, illegal, or commercially unusable. Common examples include loss of a required license, insolvency, or a change in law that makes performance unlawful. In a business contract, for instance, a clause might say that the obligation to continue a service ends if the provider loses regulatory approval.

The wording has to be clear. Courts do not treat every upset or setback as a condition subsequent, and they do not like vague language that looks like an escape hatch for ordinary inconvenience. If a clause is written as a true condition subsequent, the party relying on it usually has to show that the triggering event actually occurred and fits the clause’s terms.

A good way to spot it is to ask: “Was the duty already alive, and did a later event cut it off?” If yes, you are probably looking at a condition subsequent. If the event has to happen first before the duty ever begins, that is condition precedent instead.

Contract law also cares about how this clause interacts with performance and breach. If one side tries to keep performing after the triggering event, the dispute may turn on whether the condition was waived, whether the event really happened, or whether the clause was drafted too loosely to enforce.

Why Condition Subsequent matters in CONTRACTS

Condition subsequent shows up whenever a Contracts class asks how and when obligations end. It is one of the cleanest ways to test whether you can track the life cycle of a contract, from formation to performance to termination.

It also helps you separate termination by condition from termination by breach. A breach means someone failed to do what they promised. A condition subsequent means the contract itself includes a future event that can wipe out or limit the duty even if no one did anything wrong. That distinction matters a lot in case analysis, because the legal result changes depending on whether the issue is breach, excuse, or contract language.

This term also connects to drafting. Lawyers use conditions subsequent to build flexibility into long-term agreements, but loose wording can create fights over whether the condition truly happened or whether the party waived it. In class, professors often use these clauses to see if you can read contract language carefully instead of assuming every bad outcome is a breach case.

If you can spot a condition subsequent, you can explain why a duty ended, who bears the risk, and whether the ending was automatic or disputed.

How Condition Subsequent connects across the course

Condition Precedent

This is the main comparison term. A condition precedent must happen before a duty arises, while a condition subsequent ends a duty that already exists. If you mix them up, you may misread whether the parties were bound at the start or whether a later event discharged performance. Many Contracts questions turn on that timing.

Breach of Contract

A breach happens when a party fails to perform a duty that is already due. A condition subsequent can cut off that duty before failure turns into breach, which changes the analysis. When you read a case, ask whether the dispute is about broken performance or about a clause that ended the obligation altogether.

Force Majeure

Force majeure clauses often overlap with condition language because they excuse performance after an unexpected event. A force majeure clause is usually broader and more event-focused, while a condition subsequent is about a specific contractual trigger that ends or alters an existing duty. The exact wording controls the result.

Waiver

A party can sometimes give up the right to rely on a condition subsequent by waiver. That means even if the triggering event happened, the party may still be treated as having chosen to keep the contract alive. This is a common issue when one side keeps accepting performance after the supposed triggering event.

Is Condition Subsequent on the CONTRACTS exam?

A Contracts quiz or case brief often asks you to label a clause and explain what happens when the triggering event occurs. The move is to identify whether the duty already existed, then check whether the later event fits the clause and ends performance. If the facts mention a lost license, insolvency, or a legal change, ask whether the contract was discharged by a condition subsequent or whether the party’s failure still counts as breach.

In a short-answer or issue-spotting question, use the sequence: contract formed, duty active, trigger happens, duty ends or is disputed. That order shows you understand the timing. If the facts hint that one side kept performing anyway, bring in waiver or the exact wording of the clause.

Condition Subsequent vs Condition Precedent

These are easy to mix up because both are conditions in contracts, but they work at different times. A condition precedent must happen before the contract duty starts, while a condition subsequent happens later and can cut off an already-existing duty. Timing is the whole difference.

Key things to remember about Condition Subsequent

• A condition subsequent is a later event that can end an existing contract duty.

• It applies after the contract is already in force, not before performance begins.

• Common triggers include loss of a license, insolvency, or a legal change that makes performance impossible or unlawful.

• The exact wording matters because courts read these clauses closely and do not assume every problem creates a condition subsequent.

• On a Contracts question, the first step is to ask whether the issue is termination by condition, breach, or waiver.

Frequently asked questions about Condition Subsequent

What is Condition Subsequent in Contracts?

A condition subsequent is a future event that ends or changes a duty that already exists under a contract. The agreement is valid first, and then the triggering event cuts off the obligation. In Contracts, that timing is what separates it from a condition precedent.

How is a condition subsequent different from a condition precedent?

A condition precedent must happen before a duty begins. A condition subsequent happens after the duty already exists and can terminate it. If you remember only one thing, remember that precedent comes first and subsequent comes later.

Can a condition subsequent end a contract automatically?

Yes, if the contract language says the duty ends upon the triggering event. But courts look closely at the wording, the facts, and whether the party waived the condition. Not every setback or inconvenience counts as the triggering event.

What is an example of a condition subsequent?

A contract might say that a business can continue providing services only until it loses a required license. If the license is revoked, the duty to perform may end. Other common examples include insolvency or a change in law that makes performance unlawful.