One of the most important and least understood distinctions in contract drafting is the difference between a condition and a covenant. Both concepts appear in virtually every significant commercial agreement, yet the practical consequences of mischaracterizing one as the other can be severe. Whether a contractual provision is a condition or a covenant determines what happens when it is not satisfied — and the answers are fundamentally different in each case.
Courts care about this distinction because it shapes remedies. A failed condition excuses the party from whom performance was expected; it does not give rise to a claim for damages. A breached covenant gives rise to a claim for damages but does not necessarily excuse the other party’s performance. Getting the characterization wrong in drafting can mean the difference between being able to walk away from a deal and being stuck in it while pursuing a damages claim of uncertain value.
What Is a Condition Precedent?
A condition precedent is an event or state of affairs that must occur or be true before a contractual obligation becomes due. The condition is not itself something that either party promises to bring about (though sometimes a party does promise to use efforts to satisfy it); it is simply a prerequisite to the obligation’s activation. If the condition does not occur, the obligation never arises — neither party has failed to perform anything, because nothing was yet owed.
Classic examples of conditions precedent in commercial contracts include financing contingencies in real estate purchase agreements (the buyer’s obligation to close is conditioned on obtaining a mortgage on specified terms), regulatory approval conditions in M&A agreements (the obligation to complete the acquisition is conditioned on receiving antitrust clearance), and material adverse change conditions (the obligation to close a financing is conditioned on no material adverse change having occurred in the target’s business).
When a condition precedent fails — the financing falls through, the regulatory approval is denied, the MAC clause is triggered — the party whose obligation was conditioned on it is excused from performance. They do not breach by failing to close; their obligation to close simply never arose because the condition never occurred. Depending on the contract, they may be entitled to a refund of any deposit paid or other protections, but there is no breach and therefore no damages claim based on the non-closing itself.
This excusal-without-breach consequence is precisely what makes conditions valuable in contracting. Buyers use conditions precedent to protect themselves against closing a deal that has become economically irrational — for example, because regulatory approval was denied or because the seller’s representations have become false. Conditions create an escape valve, a legitimate way out of a deal when specified adverse circumstances materialize, without requiring either party to accept fault for the failure.
What Is a Covenant?
A covenant is a promise — a binding commitment by one or both parties to do or refrain from doing something. Covenants are obligations. A party who fails to fulfill a covenant has breached the contract and is liable for resulting damages. The non-breaching party’s remedies depend on whether the breach is material (giving rise to a right to terminate as well as damages) or immaterial (giving rise to damages only), but in either case there is a breach with legal consequences.
In a commercial contract, covenants typically include obligations like: paying an invoice by a specified date, delivering goods conforming to specified specifications, maintaining required insurance, refraining from competing during a specified period, and providing specified reports or notices. Each of these is something the party has affirmatively promised to do or not do. Failure is a breach.
The critical difference between a covenant and a condition precedent is that a covenant imposes an obligation to perform, while a condition precedent merely specifies a prerequisite to an obligation. When a party breaches a covenant, the non-breaching party is entitled to damages. When a condition fails, there is no breach — the obligation simply did not arise. This is why careful drafters pay close attention to how provisions are characterized.
Conditions Subsequent and Concurrent Conditions
While conditions precedent arise before an obligation becomes due, conditions subsequent work differently: they specify an event the occurrence of which terminates an already-existing obligation or discharges a party from further performance. For example, a landlord’s repair obligation might be conditioned on the tenant giving timely notice of the defect — if the tenant fails to give notice within the specified time, the obligation to repair is extinguished. Conditions subsequent are less common than conditions precedent but appear frequently in notice requirements and similar provisions.
Concurrent conditions arise when the parties’ performances are conditioned on each other — each party’s obligation to perform is conditioned on the other’s willingness to perform simultaneously. The classic example is the closing of a real estate sale: the seller’s obligation to deliver title is conditioned on the buyer’s simultaneous payment of the purchase price, and vice versa. Neither party must tender performance first; both obligations arise simultaneously and are conditioned on mutual exchange.
Understanding these variations is practically useful because they arise in any contract involving a multi-step closing process, an exchange of performances at a defined time, or ongoing obligations with notice requirements. When you are drafting the mechanics of a transaction, characterizing the obligations correctly as conditions, covenants, or concurrent conditions determines what happens legally if one party fails to perform on schedule.
The Drafting Challenge: Signal Words and Their Consequences
Courts look at the language used to determine whether a provision is a condition or a covenant. Conditional language — ‘provided that,’ ‘subject to,’ ‘on the condition that,’ ‘if and only if,’ ‘unless and until’ — signals a condition. Promissory language — ‘shall,’ ‘will,’ ‘agrees to,’ ‘commits to,’ ‘is obligated to’ — signals a covenant. When drafters mix these signals inconsistently, courts face interpretive uncertainty.
A particularly common drafting problem is using the word ‘shall’ to describe what appears to be a condition. If a contract says ‘the buyer shall provide a letter of credit by May 1,’ is that a covenant (breach of which gives the seller a damages claim) or a condition precedent to the seller’s obligation to ship (the occurrence of which excuses the seller from shipping if the letter of credit is not provided)? The answer depends on the overall context and how courts in the applicable jurisdiction characterize ambiguous provisions.
Courts sometimes apply a preference against conditions when language is ambiguous. The reasoning is that conditions can result in forfeiture — a party loses their right to receive performance through no fault of their own, simply because a condition failed — and courts disfavor interpretations that lead to forfeiture. When the language is ambiguous as to whether a provision is a condition or a covenant, some courts will interpret it as a covenant (with damages consequences for breach) rather than as a condition (with excusal as the consequence of failure).
For business owners, this judicial tendency toward covenants means that if you want a provision to function as a true condition — with excusal of your performance obligations if it fails — you must use clear, unambiguous conditional language. Leaving the characterization to implication or using mixed language creates risk that a court will treat your intended condition as a covenant, leaving you with only a damages claim rather than the right to walk away.
Practical Implications for Commercial Transactions
In commercial deals involving multiple steps or contingencies — acquisitions, financings, joint ventures, development agreements — the precise characterization of each condition and covenant requires careful attention. Start by asking: for each provision, what is the consequence you want if it is not satisfied? If you want excusal from further performance, draft it as a condition. If you want damages for non-performance, draft it as a covenant. Both can sometimes apply: a party can simultaneously covenant to use efforts to satisfy a condition and have the benefit of the condition itself.
When you are on the receiving end of conditions — someone else’s obligation to you is conditioned on your satisfaction of some requirement — consider carefully what the condition actually requires. Time-limited conditions deserve particular scrutiny: if the condition must be satisfied by a specific date or it fails, what exactly must you do and when? Notice requirements tied to conditions are especially important to track. Missing a notice deadline can cause a condition to fail or a right to be forfeited even when the underlying merits are fully in your favor.
In long-term contracts like license agreements, supply agreements, and distribution agreements, covenants typically do most of the work. The ongoing obligations of both parties — to pay royalties, supply conforming goods, maintain quality standards, provide reports — are covenants, not conditions. But conditions often appear at formation (approval of territory, execution of a credit application) and in provisions addressing major changes in the relationship (change of control, regulatory approval for new products). Reviewing these carefully at the outset reduces the risk of surprises when circumstances change.