Not every term in a contract is a promise that can be breached. Some terms are conditions -- events, not promises, that control whether and when a party's duty to perform arises or ends at all. Getting the classification right matters enormously in litigation, because failure of a condition and breach of a promise carry very different consequences: a party whose duty was conditional and whose condition never occurred owes nothing and has not breached anything, while a party who broke a promise owes damages even after having performed everything else.

The two classic categories are conditions precedent, which must occur before a duty to perform ever arises, and conditions subsequent, which cut off a duty that already existed once they occur. The label matters less than the underlying question it is meant to answer -- when, exactly, does the obligation exist and when does it stop -- but courts and drafters still use both terms, and knowing which one is in play changes who bears the burden of proving what happened.

A condition precedent is an event that must happen before a party's duty to perform becomes due at all. A buyer's duty to close on a house is typically conditioned on the buyer first obtaining financing; an insurer's duty to pay is typically conditioned on the insured first giving timely notice of the claim. Until the condition occurs, there is no duty to perform, and no breach for failing to perform, because the obligation simply has not yet ripened.

A condition subsequent, by contrast, cuts off a duty that has already arisen. The classic (and now less common) drafting pattern is an insurance clause providing coverage that terminates if the insured fails to file suit within a specified period after a loss -- the duty to pay exists from the moment of loss, but the condition subsequent extinguishes it if the triggering event later occurs. Modern drafting increasingly restates conditions subsequent as conditions precedent to the duty's continuation, because courts have found the older terminology confusing and the practical effect can usually be achieved either way.

Conditions are not promises, and the difference controls the remedy. Failure of a condition simply means the conditioned duty never arises (for a condition precedent) or is cut off (for a condition subsequent) -- there is no breach and no damages claim arising from the condition's non-occurrence itself, unless a party had also separately promised to bring the condition about. A promise, by contrast, creates liability for damages the moment it is broken, regardless of what happens to any other duty.

This doctrine is also distinct from anticipatory repudiation, even though both can excuse a party from performing. Anticipatory repudiation deals with one party clearly announcing, before performance is due, that it will not perform its promise -- it is about a party's own prospective refusal to honor an obligation it otherwise has. Condition precedent and subsequent analysis instead asks whether an independent triggering event -- financing approval, a third party's action, a deadline, a casualty -- has occurred to make an obligation arise or disappear in the first place, with no repudiation by either party required.

Courts read ambiguous contract language against finding a condition where possible, because conditions are a harsh doctrine -- if a condition fails, even by a small margin and even for reasons beyond a party's control, the conditioned duty simply never arises, with no room for a materiality or substantial-performance analysis the way an ordinary breach claim would allow. Courts look for explicit conditional language ('if,' 'provided that,' 'on condition that,' 'subject to') as the strongest signal the parties intended a true condition rather than an ordinary promise.

The party who benefits from the condition (typically the one seeking to avoid performing) argues for the harsher failure-of-condition reading; the party burdened by it argues the clause should be read as an ordinary promise instead, so that only substantial, material non-occurrence -- not literal, technical non-occurrence -- excuses performance, and so that the other side's own conduct (waiver, prevention of the condition, or estoppel) can be raised as a defense to the condition's failure.

In Juricratic, condition precedent and condition subsequent are modeled as gating nodes that sit logically prior to (or that terminate) the underlying breach claim path, rather than as claims in their own right -- a party's entire theory of the case can turn on whether a disputed clause is classified as a condition at all, since that classification decides whether the harsh all-or-nothing failure rule applies or whether an ordinary materiality-based breach analysis governs instead.

Because the condition-versus-promise classification is frequently the single most contested and highest-leverage issue in these disputes, a user can adjust dials for how clearly conditional the contract language reads, whether waiver or prevention doctrine plausibly excuses the condition's non-occurrence, and how a court is likely to construe ambiguous language, and observe how the modeled outcome distribution shifts between the two doctrinal paths. These remain simulation inputs, never a claimed prediction of how a specific court will classify the clause.