Contract Terminology/Condition Subsequent
Contract Terms

Condition Subsequent

An event that, if it occurs after a contract is formed, extinguishes an existing obligation - the opposite of a condition precedent.

While straightforward in theory, many businesses fail to actively track obligations tied to this concept - often resulting in missed deadlines, unintended renewals, penalties, or loss of contractual rights.

US Law  ·  For business owners and founders

Legal disclaimer: This page is for informational purposes only. It does not constitute legal advice. Contract law varies by state and circumstance. Always consult a qualified US attorney before signing or drafting any contract.

What is a Condition Subsequent?

A condition subsequent is a contractual event that, upon its occurrence, extinguishes or discharges a party's already-existing obligation. Unlike a condition precedent - which must be satisfied before a duty arises - a condition subsequent operates after performance has begun, terminating the obligation if a specific future event happens.

Classic examples appear in insurance contracts: coverage may be in force (obligation exists) but terminates if the insured engages in a prohibited activity. In employment agreements, an employee's right to a bonus may be extinguished if they resign before a vesting date.

Courts construe ambiguous terms as conditions precedent rather than conditions subsequent, because a condition subsequent can operate as a forfeiture - depriving a party of an already-accrued right. Clear, express language is essential when drafting a condition subsequent.

In practice, many teams rely on a contract expiry tracking system to stay on top of dates and obligations tied to clauses like this.

Key Elements
Existing Duty Is Discharged, Not Prevented
The key feature of a condition subsequent is that the obligation already exists and is performing - the condition subsequent terminates it. This contrasts with a condition precedent, which prevents a duty from arising in the first place.
Triggering Event Must Be Specific
The condition subsequent must clearly identify what event discharges the obligation. Vague language creates ambiguity about whether the condition has been triggered, leading to disputes.
Forfeiture Risk
Because a condition subsequent can deprive a party of an existing right, courts strictly construe them and may apply equitable doctrines (like prevention or waiver) to avoid unfair forfeiture.
Burden of Proof
The party seeking to avoid an obligation under a condition subsequent generally bears the burden of proving the triggering event occurred.
Real-World Example
Scenario

A software company grants an employee a $50,000 retention bonus, payable after 12 months of continued service. The agreement includes a condition subsequent: the bonus obligation is extinguished if the employee is terminated for cause within the bonus period.

The bonus obligation exists from day one. If the company terminates the employee for cause before the 12-month mark, the condition subsequent is triggered and the company's obligation to pay is discharged. The company must prove the termination qualified as "for cause" under the agreement's definition.

This is why many businesses adopt automated deadline tracking to ensure no critical dates are missed before they pass.

Sample Clause Language
Condition Subsequent Clause
Company's obligation to pay the Retention Bonus shall be subject to the following condition subsequent: in the event Employee is terminated for Cause (as defined herein) prior to the Bonus Payment Date, Company's obligation to pay the Retention Bonus shall be immediately and automatically discharged and extinguished, and no portion of the Retention Bonus shall be due or payable.
Watch Out For
Courts disfavor conditions subsequent
Because they operate as forfeitures of existing rights, courts interpret ambiguous provisions as conditions precedent rather than conditions subsequent. If you intend a condition subsequent, use explicit language.
Prevention doctrine
If the party who benefits from the condition subsequent wrongfully causes the triggering event, courts will not allow them to escape their obligation. A company cannot manufacture a "for cause" termination to avoid paying a bonus.
Notice requirements
Many courts and contracts require the party relying on a condition subsequent to give notice that the condition has been triggered. Failing to provide timely notice may waive the right to invoke the condition.
Don't let condition subsequent deadlines catch you off guard

Key dates tied to condition subsequents - renewal windows, expiry cutoffs, notice periods - can easily slip through the cracks when tracked manually. Missing them triggers automatic extensions, penalties, or lost rights. ExpiryEdge tracks every critical deadline and sends automated reminders before they're due - so nothing slips.

Instead of relying on spreadsheets or manual follow-ups, a centralized renewal reminder system ensures every deadline is visible, tracked, and actioned automatically.

How to Use This in Your Favor
Define the triggering event with precision
Specify exactly what constitutes the condition subsequent - not just "for cause termination" but a defined list of qualifying events. Vague conditions lead to litigation over whether the trigger was met.
Include a notice and cure provision
Require the party relying on the condition subsequent to give written notice within a specified period. This creates a clear record and may allow the other party to dispute or cure the triggering event.
Related Terms
Frequently Asked Questions

A condition precedent must occur before a duty to perform arises. A condition subsequent, if it occurs, extinguishes a duty that already exists. Both affect whether performance is required, but at different stages of the contract.

Yes, if clearly drafted. Courts will enforce them but apply strict construction and equitable doctrines to prevent abuse - particularly where the condition is used as a forfeiture mechanism.

Quick Facts
EffectDischarges an existing obligation if the specified event occurs

Common InInsurance policies, licensing agreements, employment contracts

Contrast WithCondition precedent (must occur before duty arises)

Burden of ProofParty relying on condition subsequent typically must prove the triggering event occurred
Never miss a deadline again
ExpiryEdge tracks every renewal, permit, certificate, and contract date - and alerts you before anything expires.Start free - no credit cardSee how it works →