Conditions Precedent and Closing Deliverables
Conditions precedent decide when a closing obligation comes due. Courts read them narrowly because forfeiture is disfavored, and ambiguous language is usually treated as a promise instead.
In short
- A true condition suspends a duty until the event occurs; if it never occurs, nobody breached and no damages are owed.
- Courts construe conditions narrowly because forfeiture is disfavored, so ambiguous language is usually read as a promise rather than a condition.
- A party that prevents a condition from occurring, or closes knowing it failed, generally cannot later rely on that failure.
- Contract law is state law; bring-down standards, material adverse change tests, and satisfaction clauses are read differently from one state to another.
Sections
A condition precedent is an event that must happen before a party's duty to perform comes due. If the event never happens, the duty never arises, and the party who was excused has breached nothing. That is exactly what a closing deliverables list does. It converts each side's obligation to pay money, transfer title, or release a lien into an obligation that ripens only when every listed item is delivered or waived. Because a true condition can cause a forfeiture, courts read conditions narrowly and prefer to treat doubtful language as a promise. Contract law is state law, so every rule described here varies by jurisdiction.
Condition or promise
The most consequential question about any deal term is whether it is a condition, a promise, or both. The answer decides what happens when the term is not satisfied.
If a term is a true condition, non-occurrence means the other side's duty simply never becomes due. Nobody owes damages. The deal does not close and the parties walk away. If the same term is a promise — a covenant — non-performance is a breach. The injured party can sue for damages, but its own duty to perform is not automatically excused unless the breach is material.
Because a true condition can wipe out a party's right to be paid for work already done, courts apply a rule of construction: where language is genuinely ambiguous, it is read as a promise rather than as a condition. The doctrine is usually stated as a preference against forfeiture. It is a tie-breaker, not an override. Plain condition language still controls.
The distinction also drives remedies. A party denied the benefit of a broken promise may seek damages or, where the subject matter is unique, the equitable relief described in specific performance and injunctions in contract disputes and summarized in Cornell's specific performance overview. A party facing an unfulfilled condition usually has no claim at all, only the right to refuse to close.
The words that create a condition
Drafters signal a condition with a small, recognizable vocabulary. None of these phrases is magic, and courts read the whole instrument, but their presence or absence moves the analysis.
- "Subject to" and "conditioned upon" — the most common signals, although "subject to" is also used loosely to mean "as modified by."
- "It shall be a condition precedent to Buyer's obligation to close that ..." — the clearest formulation, and the one least likely to be reargued.
- "If and only if" and "unless and until" — conditional in form and rarely mistaken for anything else.
- "Provided that" — conditional in appearance, but so overused that it frequently introduces an exception rather than a condition.
- "Shall," "agrees to," and "covenants that" — promise language, pointing away from a condition.
Where the drafting is thin, courts fall back on interpretation principles: the ordinary meaning of the words, the structure of the agreement, and, if the language is ambiguous, admissible evidence of context. Those principles, including the limits described in Cornell's note on the parol evidence rule, are covered in contract interpretation, plain meaning, ambiguity, and parol evidence. Note also which party each condition protects. A condition to Buyer's obligation belongs to Buyer, to insist on or to give up.
Conditions to closing and conditions to effectiveness
Two different things are commonly called conditions, and confusing them causes real damage.
A condition to effectiveness asks whether the contract exists as a binding instrument at all. Until it is satisfied there may be no enforceable agreement, no covenants, no exclusivity, and no obligation to work toward closing. Board approval before signature and delivery of a fully executed counterpart are typical examples.
A condition to closing assumes a live, binding contract. The parties are already bound by interim covenants — to operate in the ordinary course, to seek consents, to keep information confidential — but neither is obliged to consummate the transaction until its own conditions are met. That is the ordinary shape of a signing-then-closing deal.
Where the two sides cannot practically perform at the same instant, an escrow bridges the gap. Signature pages, funds, stock powers, and lien releases go to an escrow agent under written instructions, and the agent releases them only when the stated conditions are certified as satisfied. The exchange is then simultaneous in law even though the pieces arrived over several days. Electronic signature pages held in escrow are effective under the same rules as any other electronic record, a subject treated in electronic signatures and record retention; the federal statute appears at 15 U.S.C. 7001.
Almost every deal with a gap between signing and closing also carries an outside date, sometimes called a drop-dead date. It is a termination right, not a condition. Once the date passes without a closing, either party may walk away, usually excluding a party whose own breach caused the delay. Outside dates are extended by written amendment far more often than they are enforced, but they set the negotiating clock.
Conditions that recur in almost every deal
Bring-down of representations
The representations were true when the contract was signed. A bring-down condition asks whether they are still true at closing. The standard chosen matters enormously. "True and correct in all respects" is a hair trigger, while "true and correct in all material respects," or a qualifier keyed to the absence of a material adverse effect, gives the representing party room to breathe. Many agreements exclude representations that speak only as of a specified earlier moment, and require an officer's certificate confirming the bring-down.
No material adverse change
A no-MAC condition lets a party refuse to close if the other side's business has deteriorated badly between signing and closing. In practice these conditions are hard to invoke. In Delaware, whose decisions carry weight because so many companies are organized there, courts have required a change that is durationally significant and substantial when measured against the target's long-term earning power, and the definition itself usually carves out industry-wide, economy-wide, and general market conditions. Other states approach the question through their own case law. There is no single national standard.
Third-party consents and regulatory clearance
Some things cannot be transferred without someone else's agreement: landlords, key customers, lenders, licensors, and government agencies. A consents condition is only as strong as its list. A condition requiring "all consents" hands a reluctant buyer an exit over any missing minor item, while a condition limited to scheduled material consents keeps the deal on track. Regulatory clearance conditions are usually mandatory in substance, because closing without a required clearance is not lawful in the first place.
Caution: A closing condition and a surviving covenant are not interchangeable. A condition is used up at closing: once a party closes, it has taken the deal as it found it, and the unmet condition supports no later claim. A covenant that expressly survives closing continues to bind and can be sued on afterward. Deciding which items are conditions, which are surviving covenants, and which are both is a drafting choice with lasting consequences.
Waiver, prevention, and satisfaction standards
Conditions exist for someone's benefit, and that person can give them up. Waiver can be express, which is what a well-drafted no-waiver clause requires in a signed writing, or it can happen through conduct. A party that closes with full knowledge that a condition was never satisfied generally cannot complain about it later. Accepting deliverables, funding, or continuing to demand performance despite a known failure all point toward waiver.
The mirror image is the prevention doctrine. A party may not cause the failure of a condition and then rely on that failure to escape its own duty. Courts describe this as the implied duty not to hinder or prevent satisfaction of a condition, and it is closely related to the implied covenant of good faith and fair dealing recognized in most states. If a buyer's own refusal to file a required application blocks regulatory clearance, that buyer will usually be treated as having lost the benefit of the condition.
Satisfaction clauses raise a third problem. When the condition is that something must be "satisfactory to Buyer," which standard applies? Courts generally sort the cases by subject matter. Where the subject is commercial quality, mechanical fitness, or operative fitness, most states apply an objective test: would a reasonable person be satisfied? Where the subject involves personal taste, judgment, or aesthetics, they apply a subjective test bounded by honest good faith. The line is not drawn identically everywhere, and some states default to the objective reading whenever the contract is silent.
Materiality is usually not the question for a condition — the event either occurred or it did not. But agreements soften conditions with materiality qualifiers constantly, and the resulting argument over the word "material" is one of the main reasons closing disputes reach a courtroom. Where the parties chose an unfamiliar forum or governing law, those choices can shape the outcome as much as the condition language, a point developed in choice of law and forum selection.
Questions this raises
Can one party waive a closing condition that also protects the other side?
No. A condition can be waived only by the party for whose benefit it exists. Mutual conditions, such as the absence of an injunction barring the closing or receipt of a required regulatory approval, normally cannot be waived by one side alone, and some cannot be waived at all because closing without them would be unlawful. Well-drafted agreements state expressly whose benefit each condition serves, which removes the argument entirely.
If a condition fails, can the disappointed party recover its deal costs?
Usually not, unless somebody also broke a promise. Pure non-occurrence of a true condition is nobody's fault, and each side bears its own advisory and financing expense. The picture changes if the failure was caused by a breached covenant, such as a seller that refused to pursue a consent it had promised to seek, or if the agreement contains an expense reimbursement provision triggered by that specific failure.
Does an officer's certificate confirming the conditions actually prove anything?
It proves less than people assume. A bring-down certificate is a statement by the signing party that its own representations remain true. It satisfies a delivery requirement and creates a written record, and a knowingly false certificate can support a fraud or breach claim. But it is not independent verification, and a party relying on it without diligence is relying on the other side's word restated on closing day.
What happens if the outside date passes while a consent is still pending?
Either party holding a termination right may generally exercise it, subject to any provision denying that right to a party whose own failure caused the delay. In practice the parties usually amend the date, because walking away destroys value for both sides. If one side genuinely wants out, the outside date becomes the cleanest exit available, and the negotiation shifts to who pays what on termination.
Is a financing condition the same as a financing covenant?
They are different, and the difference is the whole fight. A financing condition means the buyer need not close if funds are unavailable. A financing covenant means the buyer promised to obtain funds and is liable in damages if it fails. Many negotiated agreements drop the condition, keep the covenant, and add a defined remedy, so the seller is not left holding an unfunded deal with no claim at all.
Running the closing in order
- Build the deliverables list from the conditions. Every closing document should trace to a numbered condition. An item that traces to nothing is either unnecessary or a condition someone forgot to draft.
- Assign an owner and a lead time to each item. Third-party consents, payoff letters, and good standing certificates come from outside the deal and cannot be produced overnight.
- Track satisfaction in writing. Keep a running status column: satisfied, waived, pending, or at risk. A waiver should be recorded as a waiver rather than quietly dropped.
- Settle the escrow mechanics early. Written release instructions, an identified agent, and clear authority to release avoid a last-minute standoff over who moves first.
- Confirm the bring-down before the closing call, not during it. If a representation has become untrue, the parties need time to negotiate a disclosure update, a waiver, or a price adjustment.
- Calendar the outside date. Start extension discussions well before it arrives rather than on the day it expires.
- Close the file properly. Record which conditions were waived and which covenants survive, because that record is what any later claim will be built on.
General background on contract formation and enforcement is collected by Cornell's Legal Information Institute in its contract overview. The uniform acts that many of these transactions sit on top of are published by the Uniform Law Commission, and general information about how a dispute proceeds once it is filed is available from the federal judiciary. The closing itself is a paperwork exercise built on a legal question, and the legal question is always the same one: whose duty has come due, and what made it due.
Sources
General information, not legal advice. Apex Legal Digest is a publication, not a law firm, and reading it creates no attorney–client relationship. Law differs by state and changes; check the sources above or consult a licensed attorney in your jurisdiction before acting.
Apex Editorial Desk
Apex is an independent reference publication. Entries are researched against primary sources and revised when the law moves. How we source · Corrections