Anticipatory repudiation and adequate assurance

The Repudiation Line: When Future Nonperformance Becomes Breach

Anticipatory repudiation and adequate assurance turn on one narrow question: has a party objectively committed to nonperformance, or only created justified insecurity about future performance? Start by asking whether the threatened performance is still due. If the particular performance at issue is already due, failure to perform is an ordinary breach; anticipatory repudiation concerns performance not yet due.

Then identify the governing law. Common law governs contracts outside the sale of goods; Article 2 governs a sale of goods under UCC § 2-102. If common law applies, repudiation requires a clear, positive, and unequivocal manifestation of intent not to perform the party’s remaining contractual duty. The manifestation may be words or voluntary conduct that makes performance impossible or plainly demonstrates refusal.

A statement of uncertainty is not enough. “I may be late,” “I am worried about financing,” or “I do not know whether I can perform” ordinarily communicates insecurity, not refusal. A request to renegotiate is also not necessarily repudiation if the party remains willing to perform the existing contract. But “I will not deliver unless you agree to a higher price” is ordinarily repudiation because the party has coupled a demand for a new term with refusal to perform the existing duty.

Conduct can be as decisive as words. Selling unique goods to someone else, transferring the only asset needed to perform, or otherwise taking an act inconsistent with performance may be an unequivocal repudiation. Financial difficulty alone is not automatically repudiation; the question is what the party objectively communicated or did.

Under UCC § 2-610, repudiation requires a clear repudiation respecting performance not yet due that substantially impairs the value of the contract to the aggrieved party. The UCC therefore adds a materiality threshold stated in commercial terms. A vague concern or minor expected nonconformity does not satisfy § 2-610. A clear refusal to supply the essential goods, however, ordinarily substantially impairs the contract.

The practical sequence is therefore: future due date, objective manifestation, governing law, and-under Article 2-substantial impairment. Do not use the adequate-assurance doctrine to replace the repudiation test. A party that has clearly repudiated has already crossed the repudiation line; a party that has merely caused justified concern may instead be met with a demand for assurance. This chapter is closed-book: state the common-law test, the § 2-610 test, and the § 2-609 trigger without prompts.

The Retraction Window: When a Repudiation Can Be Taken Back

Retraction is not an automatic reset. Once a party has repudiated, ask three questions in order:

1. Has the repudiating party’s next performance become due?
2. Has the other party canceled, materially changed position in reliance, or otherwise acquired a protected position?
3. Did the purported retraction clearly communicate an intent to perform the original contract?

At common law, a repudiating party generally may retract before the next performance is due. The retraction must clearly indicate an intention to perform; a statement such as “I suppose I can still try” may be too equivocal. A purported retraction that adds a new refusal or insists on different terms is not a retraction of the original contract.

The right ends when the nonrepudiating party has canceled the contract, materially changed position in reliance on the repudiation, or indicated that the repudiation is final. The important fact is not merely that the recipient heard the repudiation. The important fact is that the recipient acted or communicated in a way that makes reliance or finality legally significant.

For example, if a buyer receives a seller’s unequivocal refusal and promptly cancels the contract, the seller cannot revive the contract merely by promising performance the next day. Likewise, if the buyer reasonably purchases replacement goods or otherwise materially changes position because of the repudiation, retraction is barred. A recipient who has done nothing consequential may not be able to block a timely, clear retraction simply by saying that the repudiation was inconvenient.

UCC § 2-611 supplies the Article 2 rule. Until the repudiating party’s next performance is due, the party may retract unless the aggrieved party has canceled the contract or materially changed position in reliance on the repudiation. The UCC expressly makes cancellation and material reliance the central bars. Do not automatically import every common-law formulation into the UCC rule.

Under § 2-611, retraction may occur by any method that clearly indicates an intent to perform, but it must include any assurance justifiably demanded under UCC § 2-609. Thus, a seller who repudiates, receives a justified written demand for assurance, and then says only “I still hope to ship” has not necessarily retracted effectively. The response must address the assurance reasonably demanded.

A valid retraction reinstates the repudiating party’s contractual rights, with due allowance to the aggrieved party for delay caused by the repudiation. Retraction does not erase the practical consequences of the delay or give the repudiating party an automatic extension of the original performance date. The distinction is sharp:

• Before retraction: ask whether the recipient has canceled or materially relied.
• At retraction: ask whether the promise to perform is clear and concerns the original contract.
• After valid retraction: the contract is restored, but delay caused by the repudiation receives appropriate allowance.

The Assurance Demand: Turning Insecurity into a Timed Response

Adequate assurance is a UCC mechanism for the middle ground between performance and repudiation. It applies when reasonable grounds for insecurity arise about the other party’s performance, but there is not yet a clear repudiation under UCC § 2-610. The demand is governed by UCC § 2-609.

The demanding party must make a written demand for adequate assurance. An oral request may communicate concern, but it does not trigger § 2-609’s statutory response period. The grounds must be objectively reasonable in context. Evidence that a buyer has lost financing, repeatedly failed to make payments, become insolvent, or repeatedly failed to perform may support insecurity. A generalized hunch, strategic desire for extra protection, or mere dissatisfaction with the transaction does not automatically suffice.

The requested assurance must be adequate, not perfect. Its form depends on the risk that created the insecurity. Financial statements, a letter of credit, a guarantee, a deposit, confirmation of inventory, or a credible performance schedule might be adequate in the appropriate setting. The demand cannot be used to obtain extraordinary security unrelated to the concern. Between merchants, UCC § 2-609 directs that the reasonableness of the grounds and the adequacy of the assurance be determined according to commercial standards.

After making a justified demand, the demanding party may, if commercially reasonable, suspend performance for which it has not already received the agreed return while awaiting assurance. This is a temporary protection, not an immediate cancellation right. The party should not treat the mere sending of the demand as proof that the other side has repudiated.

The responding party must provide adequate assurance within a reasonable time, but the period cannot exceed 30 days after receipt of the demand. The exact rule is not “30 days in every case”; it is a reasonable time subject to a 30-day maximum. If adequate assurance is timely supplied, the basis for the demand is addressed and the parties remain bound to perform. If adequate assurance is not supplied within the permitted period, the failure is treated as a repudiation under § 2-609.

The near-miss distinctions are decisive:

• Clear refusal: § 2-610 repudiation; no assurance demand is needed as a prerequisite.
• Uncertainty supported by reasonable facts: § 2-609 written assurance demand.
• Uncertainty without reasonable grounds: no statutory assurance right.
• Written demand followed by timely adequate assurance: no repudiation from the insecurity alone.
• Justified written demand followed by failure within a reasonable time not exceeding 30 days: repudiation under § 2-609.

Loading diagram…

Recurring errors usually arise from collapsing neighboring rules:

• Treating “I may not be able to ship” as repudiation even though the speaker expressly intends to try.
• Treating a telephone request for assurance as a written UCC § 2-609 demand.
• Counting every case as 30 days instead of asking whether the response was required within a reasonable time.
• Assuming a repudiation can always be retracted because the performance date has not arrived.
• Treating a demand for extraordinary security as adequate assurance merely because the demanding party wants greater certainty.

The Merchant’s Uncertain Promise: A Worked Item on Two Lines

On May 1, Restaurant and Distributor, both merchants, contracted for Distributor to deliver 1,000 cases of goods on July 1, with payment due on delivery.

On June 1, Distributor told Restaurant, “Our lender froze our line. I do not know whether we can ship, but I intend to try to deliver on July 1.”

Restaurant immediately telephoned a demand for adequate assurance. Distributor provided none by June 11.

The Three Final Traps: Repudiation, Retraction, and Assurance

High-Yield Points - ⚡ Biggest Takeaways

Treat future nonperformance as repudiation only when the refusal is clear and unequivocal. Retraction fails after cancellation or material reliance, even if performance is not yet due. Under UCC § 2-609, reasonable insecurity requires a written demand and failure within a reasonable time not exceeding 30 days.