Condition precedent: what it means and how to draft it

What a condition precedent does

A condition precedent controls the timing and trigger of an obligation rather than the substance of what a party promises to do. It answers a single question: what has to happen first? Common examples include a buyer’s financing coming through before a purchase closes, a regulator granting approval before a merger completes, a certificate of insurance being delivered before work begins, or a third party signing off before a payment falls due.

The legal consequence is precise and easy to underestimate. If a genuine condition precedent fails, the dependent obligation simply never arises, and the party who would have performed is excused without being in breach. That is very different from a broken promise, where the obligation exists and its breach creates liability. Because the two outcomes diverge so sharply, courts look closely at whether a clause creates a condition (a trigger) or a covenant (a promise), and the drafter’s word choice is the primary evidence.

Conditions precedent do two useful jobs at once. They allocate risk by deciding which party bears the consequences if the triggering event does not happen, and they sequence performance so that obligations unlock in a deliberate order. In a share purchase agreement, for instance, the seller does not want to transfer the business until the buyer has paid, and the buyer does not want to pay until warranties are confirmed and approvals are secured. Layered conditions precedent turn that standoff into an orderly closing.

Drafting example

Closing of the Transaction is conditioned upon, and Buyer shall have no obligation to pay the Purchase Price unless and until, each of the following conditions precedent has been satisfied or waived in writing by Buyer: (a) Seller shall have delivered executed assignments for all Assets [defines exactly what triggers the duty]; (b) all consents listed in Schedule 3 shall have been obtained and remain in effect [names the source of each consent to remove ambiguity]; and (c) the representations in Section 5 shall be true and correct in all material respects as of the Closing Date [ties the condition to a fixed measurement date]. If these conditions are not satisfied or waived on or before [date], either party may terminate this Agreement by written notice, and neither party shall have further liability except as stated in Section 12 [supplies a clear deadline and a clean exit].

The annotations point to the elements that make a condition enforceable: an unmistakable trigger phrase (“conditioned upon”), a defined event, a named source, a measurement date, a waiver mechanism, and a longstop date with a clean termination path.

What the law says

Under US common law, a condition is generally defined as an event, not certain to occur, that must occur (unless its non-occurrence is excused) before performance under a contract becomes due. That framing follows the Restatement (Second) of Contracts, which courts across most states treat as persuasive authority.

Three principles recur. First, express conditions are usually enforced strictly, so substantial performance is not always enough to satisfy them. Second, because strict enforcement can cause forfeiture, courts disfavor forfeiture and will read an ambiguous provision as a promise rather than a condition when a condition would produce a harsh, disproportionate loss. Third, a party whose own conduct wrongfully prevents a condition from occurring generally cannot rely on that non-occurrence to escape its duty, an idea often called the prevention doctrine.

Procedure matters too. Under Federal Rule of Civil Procedure 9(c), a plaintiff may plead generally that all conditions precedent have occurred or been performed, but a defendant who denies performance must do so with particularity. Many state rules mirror this. Conditions may also be waived by the party they protect, and a course of conduct can amount to waiver even without a signed writing, which is one reason a strong clause states that waivers are effective only in writing.

Common mistakes to avoid

The most frequent error is ambiguity about whether a clause is a condition or a covenant. Language such as “the buyer will obtain financing” reads like a promise, while “conditioned upon the buyer obtaining financing” reads like a trigger, and the two produce opposite results when financing falls through. Choose trigger words deliberately: “subject to,” “conditioned upon,” “provided that,” and “on the condition that” all signal a condition.

A second mistake is leaving the condition open-ended. Without a deadline (often called a longstop or drop-dead date), the obligation can hang indefinitely, and neither party knows when they are free to walk away. Always pair a condition with a date and a termination right.

A third mistake is failing to say who must satisfy the condition and what evidence proves satisfaction. If a certificate, consent, or approval is required, name it, name its source, and state who bears the cost and effort of pursuing it, ideally with a “reasonable efforts” or “commercially reasonable efforts” standard tied to that party. A fourth mistake is silence on waiver, which invites arguments that informal conduct waived a right one side thought was preserved. A fifth is scattering conditions across several sections so no one can see the full closing checklist in one place.

When it matters most

Conditions precedent carry the most weight in high-value, multi-step transactions where performance cannot safely happen all at once. Mergers and acquisitions, real estate closings, financing and loan drawdowns, construction milestones, licensing deals that depend on regulatory clearance, and supply agreements that hinge on certification all rely on them. They also matter in any deal with a gap between signing and closing, because that gap is exactly the window the conditions are meant to govern.

They matter most, in practice, at two moments: when a deal is being papered and a small wording choice quietly reallocates risk, and much later when something goes wrong and a party asks whether it ever had to perform at all. The clause drafted in an afternoon becomes the pivot of a dispute months down the line.

That is why conditions precedent belong to disciplined contract management, not just careful drafting. Tracking each condition, its deadline, its owner, and its supporting evidence across a portfolio is where value is protected or lost. A CLM platform like Pactolane keeps every condition, consent, and longstop date in a central repository with renewal and deadline alerts, so a missed approval never quietly becomes a missed closing. Its AI copilot, PactAI, can extract conditions from an executed agreement, flag conflicting or ambiguous triggers, and produce a plain-language summary of what still has to happen before each obligation goes live. Careful drafting sets the trigger; steady management makes sure someone is watching for it.