Conditions Precedent in Minnesota Contracts

What is a condition precedent in a Minnesota contract?

A condition precedent is an event that must occur before one party’s contractual duty arises. Minnesota courts describe it as any fact, other than mere passage of time, that must exist or happen before a duty of immediate performance by the promisor can arise. Carl Bolander & Sons, Inc. v. United Stockyards Corp. applied that formulation in a 1974 Minnesota Supreme Court decision; the Court of Appeals echoed it in Aslakson v. Home Savings Association, describing a condition precedent as one to be performed before the agreement becomes operative.

The Restatement (Second) of Contracts § 224 captures the same idea: a condition is an event, not certain to occur, which must occur before performance under a contract becomes due. The doctrinal point is narrow but consequential. Until the condition is satisfied (or excused), the conditioned duty has not yet matured. There is no breach to sue on, because there is no duty to breach.

How does Minnesota distinguish a condition from a covenant?

Minnesota draws a sharp line between a condition and a covenant, and the line runs through the contract’s language. A covenant is a promise to do (or not do) something. A condition is an event whose occurrence triggers (or whose nonoccurrence excludes) a duty. The same fact pattern can be drafted either way, and the court reads the document to figure out which the parties chose.

The decisive Minnesota Court of Appeals decision is Mrozik Construction, Inc. v. Lovering Associates, Inc., 461 N.W.2d 49 (Minn. Ct. App. 1990). A subcontract said the general contractor would pay the subcontractor “to the extent” the general contractor had been paid by the owner. The general contractor argued that owner-payment was a condition precedent to its own duty to pay the sub. The court of appeals rejected that reading.

Minnesota will not find a condition precedent absent unequivocal contract language. The disputed clause, the court held, was a timing provision, not a condition. The general contractor still owed the subcontractor.

Mrozik states the default rule that runs through Minnesota condition cases: when the language is ambiguous, the court reads it as a promise rather than a condition. Forfeiture-style outcomes are not assumed.

What contract language signals a true condition?

Certain words push the court toward reading a clause as a condition rather than a covenant. None of them is magic, and none is sufficient on its own, but the pattern matters.

• “If and only if”
• “Subject to”
• “Provided that”
• “On the condition that”
• “Conditioned upon”
• “Unless and until”

These phrases tell the reader (and the court) that the clause defines a gate, not a duty. By contrast, language framed as a promise (“the buyer will obtain financing”; “the seller shall deliver inspection reports”) reads as a covenant. The buyer who fails to obtain financing has breached a promise; the failure does not in itself dissolve the agreement.

In my practice, the cleanest way to draft a condition is to use the conditional phrase, identify the event in operative terms, and then say what does not happen if the event does not occur. The pattern looks like this:

If and only if [event] occurs by [date], then [obligor] shall [perform]. If [event] does not occur by [date], this agreement shall be void and neither party shall have any further obligation.

That is unambiguous in Mrozik’s sense. It tells the court exactly what the parties wanted and removes the temptation to read the clause as a covenant when one side wants a damages remedy after the fact.

For related drafting issues that often interact with conditions, see legal triggers for withholding payment in B2B contracts and integration clauses that override side letter terms.

Why does the distinction between a condition and a covenant change the remedy?

The remedy turns on what the broken term was. If the term was a covenant, the breaching party’s failure is a breach: the non-breaching party may sue for damages, but its own performance generally remains due (subject to material-breach doctrines). If the term was a condition, the failure of the conditioning event means the conditioned duty never came due in the first place. There is nothing to perform, and nothing to recover, because no duty was triggered.

That asymmetry is what makes the distinction so consequential in deal drafting. A covenant is symmetric: both sides keep performing, the injured party gets damages. A condition is binary: the gate either opens or it doesn’t, and if it doesn’t, the contract simply does not run.

This is also why Minnesota’s reluctance to find unequivocal conditional language matters. Under Mrozik, when the parties have written something the court can read either as a promise or as a condition, the default is the promise. The damages remedy preserves the bargain; the condition reading would forfeit it. Courts prefer to keep contracts alive.

How does the substantial-performance doctrine treat conditions?

Substantial performance is the doctrine that lets a party recover under a contract even when its performance fell slightly short of perfection. Minnesota applies the doctrine to constructive conditions, meaning conditions the law implies from the parties’ promises (most often in construction and services contracts).

But substantial performance does not soften an express condition. When the parties have drafted a true condition into the contract, the condition must be satisfied in fact. The “almost but not quite” reading that rescues a contractor who installed slightly out-of-spec materials does not rescue a buyer whose financing came in two days after the deadline. Minnesota courts generally enforce express conditions as drafted, subject to the narrow excuse doctrines covered below; substantial performance is not one of them.

This is the doctrinal core of why drafting matters so much. Substantial performance is the safety net for performance disputes; it does not exist for conditions the parties chose to make express. If a deadline matters enough to be a true condition, it has to be met. If it doesn’t matter that much, it should be drafted as a covenant.

When will a Minnesota court excuse a missed condition?

Minnesota courts will excuse the failure of a condition precedent in a narrow set of circumstances. The four main excuse doctrines are waiver, estoppel, prevention, and disproportionate forfeiture. Each is an equitable check on the strict-compliance default, and each requires specific factual elements rather than a general appeal to fairness.

The doctrines do not operate as a sliding scale. A court applying excuse doctrine looks for the precise facts the doctrine requires. Waiver requires intentional relinquishment of a known right. Estoppel requires reliance on the other party’s words or conduct. Prevention requires that the obligee made occurrence of the condition impossible. Disproportionate forfeiture, under Capistrant, requires both non-materiality of the condition and a forfeiture grossly out of scale with the harm. None of these is a general “fairness” doctrine the court applies on its own; each must be pleaded and proved by the party asking to be excused.

How does waiver eliminate a condition?

Waiver is the voluntary, intentional relinquishment of a known contractual right. A party that has the benefit of a condition precedent can waive it expressly, in writing, or by conduct that is inconsistent with insistence on the condition. Once waived, the condition is gone for the occurrence the waiver covered.

In my practice, roughly half of the condition disputes I see start as waiver-by-acceptance fights: the party with the benefit of the condition let the first missed deadline pass without objection, then tried to enforce strict compliance the second time around. The most common pattern in commercial practice involves waiver by acceptance. A buyer with a financing condition closes anyway despite shaky financing; a lender with a covenant-compliance condition continues to fund the loan despite a known covenant breach; a franchisor with a quarterly-reporting condition keeps cashing royalty checks while reports come in late. In each case, the waiver covers the past instance.

The party who waived once may insist on strict compliance going forward, but only if it gives clear notice and a reasonable opportunity to cure before the next obligation matures. Waiver by silence after the next deadline becomes the next waiver. The rights stay enforceable only with deliberate, documented enforcement.

How does estoppel keep a condition alive after a missed deadline?

Estoppel is the equitable cousin of waiver. Where waiver focuses on the conduct of the party with the right, estoppel focuses on whether the other side reasonably relied on that conduct to its detriment. The result is similar: the party with the right is barred from enforcing the condition strictly.

In condition-precedent disputes, estoppel typically appears when one side leads the other to believe the condition has been satisfied or will be excused, and the other side then performs (or forbears) in reliance. A general contractor that tells a subcontractor “go ahead and start work, we’ll handle the permit later” cannot then refuse payment on the grounds that the permit was a condition precedent and the sub started work before it issued. The reliance is what fixes the conduct.

For business owners, the practical lesson is that informal assurances given in the field can override carefully drafted contract language. The cleanest way to preserve a condition is to never say anything that could be reasonably read as a green light to perform without it.

How does prevention by the obligee excuse a condition?

A party cannot benefit from the failure of a condition that the party itself prevented. The prevention doctrine bars a party from relying on the failure of a condition that the party itself caused.

The classic Minnesota fact pattern is the buyer who needs the seller’s cooperation to satisfy a closing condition (an audit, an estoppel certificate, a regulatory consent), and the seller stalls or refuses. The seller cannot then walk away on grounds that the condition was not satisfied. The seller’s own conduct prevented occurrence; the law does not let the seller capitalize on the resulting failure.

In employment commission disputes (the Capistrant fact pattern), prevention can show up when an employer terminates a salesperson on the eve of a close to avoid paying the commission contingent on closing. The departing employee may invoke prevention to argue that the condition (closing within X days of an employee-driven sale) should be excused. The doctrine is fact-intensive but conceptually narrow: the obligee’s own act has to be the reason the condition failed.

What makes a condition-precedent clause survive a Capistrant challenge?

Capistrant v. Lifetouch National School Studios, Inc., 916 N.W.2d 23 (Minn. 2018), is the Minnesota Supreme Court’s most recent major statement on when a court will refuse to enforce a condition precedent on disproportionate-forfeiture grounds. A long-tenured sales executive forfeited substantial residual commissions because he had not promptly returned company property when his employment ended (the employer treated the return-of-property clause as a condition precedent to the commission payments). The Minnesota Supreme Court held that the disproportionate-forfeiture analysis under Restatement (Second) of Contracts § 229 applies in two sequential steps:

1. Materiality. Is the condition a material part of the agreed exchange? If yes, the court enforces the forfeiture. The proportionality analysis does not apply.
2. Proportionality. If the condition is not material, the court asks whether the resulting forfeiture is disproportionate to the harm from non-occurrence. If disproportionate, the court excuses the condition.

The practical consequence for drafters is that not every condition the parties write down will survive a Capistrant challenge. A condition tied to something genuinely central to the bargain (closing the sale, completing the regulatory filing, delivering the inventory) is material and will hold. A condition that operates as a tripwire to forfeit a major economic right for a tangential failure (a delayed return of company property in exchange for substantial residual commissions) is the Capistrant problem itself. Courts will not enforce it.

For employment-style contracts where conditions interact with restrictive covenants, see our overview of Minnesota noncompete agreements, where similar materiality and proportionality analyses surface.

The bottom line for Minnesota businesses

The condition-versus-covenant distinction is one of the highest-stakes drafting choices in any Minnesota contract. The same operative event, drafted as a condition, can dissolve a multi-million-dollar deal. Drafted as a covenant, it preserves the deal and gives the injured party damages.

Minnesota courts default to the covenant reading when language is ambiguous, refuse to enforce conditions that produce disproportionate forfeitures on non-material breaches, and apply familiar excuse doctrines (waiver, estoppel, prevention) to keep contracts alive. None of that is automatic; each rule has elements that have to be pleaded and proved.

If you are drafting a contract where a particular event has to be a hard gate, the language has to say so unequivocally; if you are reading one where the other side is treating an ambiguous clause as a forfeiture trigger, the case law in Minnesota gives you several routes to push back. For a candid read on how a specific clause is likely to play out in your situation, email [email protected] with the contract language and a brief description of what is at stake; for the broader picture on related issues, see our Minnesota contracts practice area.