Condition Precedent and Subsequent

Contracts are not merely lists of promises; they are dynamic frameworks for managing risk and performance. The inclusion of conditions—events or facts that trigger, modify, or terminate duties—is what makes this management possible. For any lawyer or bar exam candidate, understanding the distinction between a condition precedent and a condition subsequent, and the rules governing their operation, is essential for accurately analyzing when a party’s duty to perform arises and when it can be discharged. Misapplying these concepts can lead to incorrect conclusions about breach and remedy, a common trap in both practice and examination settings.

Foundational Concepts: Triggering and Terminating Duties

At the heart of contract performance analysis is determining what must happen before a party is obligated to act. This is governed by two primary types of conditions.

A condition precedent is an event that must occur before a party’s absolute duty to perform its promise arises. It is a trigger. If the condition fails to occur, the duty to perform never matures, and no breach occurs for non-performance. Think of it as a "if this, then that" clause. For example, in a contract for the sale of a house, the buyer's duty to pay the purchase price is typically conditioned precedent upon the seller delivering a clear title report. No clear title, no enforceable duty to pay.

In contrast, a condition subsequent is an event that, if it occurs, discharges an existing, absolute duty to perform. It acts as a termination clause. The duty to perform is already active, but a subsequent event cuts it off. A classic example is found in insurance contracts: the insurer's duty to pay a claim is an active obligation once a covered loss occurs. However, that duty may be discharged by a condition subsequent, such as the insured’s failure to submit a proof-of-loss form within 60 days of the loss. The duty existed, but the condition subsequent extinguished it.

For the bar exam, a key strategy is to carefully parse the contractual language and temporal sequence. Language like "provided that," "on condition that," or "if" often signals a condition precedent. Language like "unless," "until," or "but if" may signal a condition subsequent. Ask: Did the duty to perform ever become absolute? If not, look for an unfulfilled condition precedent. If it did become absolute but was then excused, look for a fulfilled condition subsequent.

The Standard of Compliance: Express vs. Constructive Conditions

Not all conditions are created equal, and the consequences of failing to meet them depend heavily on their nature. This distinction is critical for analyzing claims of breach.

An express condition is explicitly stated in the parties' agreement, using clear, conditional language. The law treats these conditions strictly. Strict compliance is generally required. If the express condition is not perfectly satisfied, the duty dependent on it does not arise or is discharged, unless an excuse applies. For instance, if a commercial lease states, "Lessor's duty to renew this lease is expressly conditioned upon Lessee providing written notice of intent to renew no later than 90 days before termination," a notice given on the 89th day likely fails the condition, relieving the Lessor of the duty to renew.

A constructive condition (or implied-in-law condition) is not explicitly stated but is imposed by the court to ensure fairness, typically in contracts involving an exchange of performances. The classic example is the exchange of promises in a bilateral contract. Each party's performance is a constructive condition of the other party's duty to perform. For these, the law requires only substantial performance. A party who substantially performs its promise can enforce the contract against the other party, though the other may claim damages for any minor deviations. In a construction contract, if a builder completes a house with only trivial defects (e.g., a slightly wrong paint shade), they have substantially performed. The owner’s duty to pay the contract price is triggered, minus damages for the cost to correct the defect.

On exams, a frequent trap is conflating the standard for breach with the standard for triggering a duty. A failure of strict compliance with an express condition means the dependent duty does not mature—it's not a breach by the conditioned party, but rather a failure of an agreed-upon trigger. A failure of substantial performance of a constructive condition, however, is a material breach by the performing party, which can discharge the other party's duties.

Excuse of Conditions: Waiver, Estoppel, and Prevention

Even when a condition has not been strictly or substantially met, a party may still be obligated to perform. The law recognizes that insisting on a condition can sometimes be unjust. Three key doctrines excuse the non-occurrence of a condition.

Waiver is the voluntary relinquishment of a known right, including the right to insist on a condition. It often occurs through words or conduct. Crucially, a waiver can be retracted unless the other party has relied on it or it is supported by consideration. For example, if a contract requires delivery in specific packaging but the buyer repeatedly accepts deliveries in different packaging without objection, a court may find the buyer waived the packaging condition for past and possibly future deliveries under the course of performance.

Estoppel (or equitable estoppel) arises when one party makes a representation that induces the other party to rely to their detriment, making it unfair to allow the first party to insist on the condition. Unlike waiver, estoppel is focused on detrimental reliance and is not easily retracted. If a landlord tells a tenant, "Don’t worry about the condition that rent be paid by the 1st; the 5th is fine this month," and the tenant, relying on that, incurs a large, non-refundable expense on the 2nd, the landlord may be estopped from enforcing the timely payment condition for that month.

Prevention (or hindrance) is the doctrine that a party cannot take advantage of the non-occurrence of a condition if they themselves wrongfully prevented it from occurring. This is a principle of basic fairness. If a sales contract makes the buyer’s duty to pay contingent on securing a bank loan, but the seller then disparages the buyer to the bank, causing the loan to be denied, the seller has prevented the condition. The buyer’s duty to pay may be treated as if the condition had been satisfied, making the seller’s failure to deliver a breach.

In bar exam scenarios, when you see an unfulfilled condition, always ask: "Is there an excuse?" Look for patterns of conduct (waiver), representations inducing reliance (estoppel), or obstructive behavior (prevention).

Common Pitfalls

1. Confusing a Promise with a Condition: This is the most fundamental error. A promise creates a duty; a condition allocates risk by governing that duty. Labeling something a "condition" does not automatically make it one if it is truly a promise to perform. The test is intent: does the language or context show the parties intended an event to be a prerequisite (condition) or an obligation itself (promise)? Mislabeling leads to incorrect remedies—damages for breach of a promise vs. no duty arising from failure of a condition.

1. Applying "Substantial Performance" to Express Conditions: Students often want to apply fairness and the substantial performance doctrine across the board. Remember, courts enforce the parties' bargain. If they explicitly made an event an express condition, the law demands strict compliance. Arguing for substantial performance in such a case ignores the fundamental principle of freedom of contract.

1. Misidentifying Condition Subsequent: It is easy to mischaracterize a condition subsequent as a condition precedent because both can use "if" language. The key is to identify the moment the duty became absolute. If the duty was already unconditionally owed and an event cuts it off, it's subsequent. For instance, "Insurer will pay the claim, if the proof of loss is filed within 60 days" is still a condition subsequent to the already-arisen duty to pay. A helpful exam tactic is to frame the sentence: "The duty to X terminates if Y happens."

1. Overlooking Excuse Doctrines: When a condition fails, the analysis does not automatically end. Failing to consider waiver, estoppel, or prevention can lead you to an incomplete and incorrect conclusion. Always perform a final check: did the party now claiming the benefit of the condition act in a way that should bar them from asserting it?

Summary

• Conditions precedent are triggers that must occur before a duty to perform matures. Conditions subsequent are terminating events that discharge an already-existing duty.
• Express conditions, created by clear contractual language, require strict compliance. Their failure means the dependent duty does not arise.
• Constructive conditions, implied by law to ensure fair exchange, require only substantial performance. Failure to substantially perform is a material breach.
• Even unfulfilled conditions may be excused by a party's waiver (voluntary relinquishment), estoppel (detrimental reliance on a representation), or prevention (wrongfully hindering the condition's occurrence).
• For exam success, methodically: (1) Identify whether a clause is a promise or a condition, (2) Classify the condition as precedent or subsequent based on when the duty attached, (3) Determine if it is express (strict compliance) or constructive (substantial performance), and (4) Check for possible excuses like waiver, estoppel, or prevention.