Skip to content

Breach of Contract

A legally cognizable failure to honor a binding contractual duty, including qualifying anticipatory repudiation.

Version
v1 · 2026-09-28 · History
Domain-specific #
8267
Domain group
Professional & Organizational Practice
Origin domain
Law & Governance
Subdomain
Contract Law → Law & Governance
Aliases
Contractual breach

Core Idea

Breach of contract is a legal event relative to an enforceable agreement and its specific obligations. A party may fail to perform when due, interfere with another's contractual performance, or, where the governing law recognizes it, clearly repudiate a future duty in advance. The analyst must state the parties, duty, timing, conduct, and legal frame. Being unhappy with a bargain is not breach; neither is a failure of a nonbinding plan. The English case Hochster v De La Tour shows why nonperformance is not only an after-the-deadline category: an unequivocal repudiation before a courier engagement began supported an immediate action.

The occurrence and gravity of breach are separate from remedy. English law distinguishes breaches of conditions, warranties, and innominate terms, with termination rights depending on the term or substantial consequences; not every failure ends the contract. Other regimes, including UCC sale-of-goods rules, use their own anticipatory-repudiation thresholds and options. Damages, cure, election, and termination require further analysis rather than following automatically from the word breach. This entry records the structural legal distinction, not advice about a present dispute or a universal remedy chart.

How would you explain it like I'm…

Breaking the Deal

When two people make a real promise that counts, like I give you my toy car and you give me your sticker, that is a contract. A breach of contract is when someone does not do their part, or clearly says ahead of time that they will not. Just wishing you had made a different deal is not a breach. And what happens next, like how to fix it, is a separate question.

Not Keeping Your Side of the Deal

A contract is an agreement that the law will actually back up, with specific jobs each side has promised to do. Breach of contract means one side fails to do its promised job when it is due, gets in the way of the other side doing their job, or, in some legal systems, clearly announces in advance that it will not do its job. Feeling unhappy with a deal is not a breach, and neither is breaking a plan that was never a binding promise. In one famous English case, someone was told before a job even started that they would not be needed, and the court let them sue right away. Whether there is a breach is one question; what the fix should be, like money or ending the deal, is another.

Failing a Binding Obligation

Breach of contract is a legal event: it only makes sense relative to an enforceable agreement and the specific duties it creates. A party breaches by failing to perform when performance is due, by interfering with the other party's performance, or, where the governing law recognizes it, by clearly repudiating a future duty in advance (called anticipatory repudiation). In the English case Hochster v De La Tour, an unequivocal repudiation before a courier job had even begun let the other side sue immediately, showing that breach isn't only something that happens after a deadline passes. To analyze a breach you need the parties, the duty, the timing, the conduct, and which legal system applies. Whether a breach happened and how serious it is are separate from what remedy follows; not every breach lets the other side end the contract.

 

Breach of contract is defined relative to an enforceable agreement and its particular obligations, so an analysis must specify the parties, the duty in question, its timing, the conduct, and the governing legal framework. Breach can take several forms: failure to perform when due, interference with the counterparty's performance, and, where recognized, anticipatory repudiation, an unequivocal advance refusal of a future duty. Hochster v De La Tour is the classic English illustration: a clear repudiation before a courier engagement was to start supported an immediate action. Dissatisfaction with a bargain, or the non-fulfilment of a non-binding plan, is not breach. Crucially, occurrence and gravity of breach are distinct from remedy. English law classifies terms as conditions, warranties, or innominate terms, and the right to terminate depends on the type of term or on how substantial the consequences are. Other regimes, such as UCC sale-of-goods rules, set their own anticipatory-repudiation thresholds and options. Damages, cure, election, and termination each require further analysis rather than following automatically from a finding of breach.

Structural Signature

Sig role-phrases:

  • binding contractual relation — Identifies parties and an enforceable contract under the relevant legal system. It is constitutive. Counterfactual: Disappointed hopes under an informal promise without a binding contract are not breach of contract.
  • specific duty and conditions — States what performance, restraint, or cooperation the contract actually requires and when. It is constitutive. Counterfactual: Conduct outside the contract's duties cannot breach it merely because the counterparty dislikes it.
  • nonperformance or qualifying repudiation — Locates the actual omission, interference, or sufficiently definite future renunciation against the duty. It is constitutive. Counterfactual: A tentative worry about future ability is not automatically a renunciatory breach.
  • governing law and classification — Determines how the deviation is recognized, including actual versus anticipatory form and seriousness of the term or consequence. It is boundary. Counterfactual: A label imported from another jurisdiction cannot settle termination rights in this case.
  • remedy and election distinction — Separates occurrence of breach from damages, termination, cure, and any required communication of election. It is boundary. Counterfactual: A minor warranty breach need not end the contract even when a remedy may exist.

What It Is Not

  • Not a broken informal promise. A binding contractual duty must first be established.
  • Not any performance worry. Anticipatory repudiation requires sufficiently clear conduct under governing law.
  • Not automatic termination. Breach and the right to end a contract are distinct legal questions.
  • Not identical to damages. Compensation requires separate remedy, causation, and measure analysis.
  • Closest near-miss. A supplier announces uncertainty about delivery but has not refused or definitively manifested inability to perform; that concern is the closest excluded neighbor to anticipatory repudiation unless the governing facts and law make the statement unequivocal.

Scope of Application

  • Contract interpretation. Locate the precise duty and time that the alleged conduct failed to honor.
  • Dispute classification. Distinguish actual nonperformance from a legally sufficient anticipatory renunciation.
  • Remedy analysis. Keep breach occurrence separate from damages, cure, and termination entitlement.
  • Comparative contract law. Explain why English common-law and UCC sale rules may use different thresholds and choices.

Clarity

Identify the contract, parties, duty, deadline, conduct, and governing law. Include unexcused missed performance and clearly qualifying advance repudiation; exclude mere uncertainty about future performance. The nearest miss is a supplier's tentative concern that does not amount to a definite refusal. A breach finding does not itself decide damages or termination. State which term was breached and whether the alleged response requires a further election or seriousness test.

Manages Complexity

The term compresses a relation among agreement, duty, timing, and deviation, letting very different failures be compared without treating them as the same remedy. Separating actual from anticipatory breach prevents parties from having to wait for an inevitable deadline while protecting ordinary uncertainty from premature litigation. Separating occurrence from termination avoids the equally serious error of turning every minor nonperformance into a right to abandon the bargain.

Abstract Reasoning

  1. Establish that an enforceable contract and relevant parties exist under the chosen law.
  2. Identify the exact obligation, its due time, and any lawful modification or excuse.
  3. Compare actual conduct or advance communication with that obligation.
  4. Classify any deviation as actual or qualifying anticipatory breach under the governing test.
  5. Only then analyze seriousness, election, available remedies, and proof of loss separately.

Knowledge Transfer

The broad pattern of commitment, applicable criterion, and non-satisfaction can inform reasoning about service agreements or institutional obligations, but 'breach of contract' requires legal enforceability and the governing doctrine of performance or repudiation. An engineering failure or disappointed expectation is not literally this legal cause of action. The English Hochster rule and UCC §2-610 should not be blended into one jurisdiction-free remedy statement.

Examples

Canonical

Suppose a valid contract requires delivery of specified goods by an agreed date, no excuse or modification applies, and the seller does not deliver. The missed duty is an actual breach. A court or parties must still ask whether the term, consequences, cure provisions, and jurisdiction permit damages, termination, or another response; the nonperformance alone does not prove every remedy. This is a defining construction, not a reported judgment.

Mapped back: binding contractual relation → valid sale agreement between buyer and seller; specific duty and conditions → specified goods due on an agreed date; nonperformance or qualifying repudiation → seller's unexcused missed delivery; governing law and classification → actual breach with term severity yet to be assessed; remedy and election distinction → damages or termination remains a separate legal question.

Applied / In Practice

In Hochster v De La Tour, the parties had contracted for Hochster to serve as a courier on a future tour, but De La Tour renounced the engagement before service was due. The Queen's Bench allowed the claimant to sue without waiting until the start date, establishing an English anticipatory-breach application. The case does not make every expression of doubt a breach or settle how a different jurisdiction would classify a different contract.

Mapped back: binding contractual relation → the agreed courier engagement; specific duty and conditions → future tour service beginning on the agreed date; nonperformance or qualifying repudiation → De La Tour's pre-start renunciation; governing law and classification → English Queen's Bench anticipatory breach; remedy and election distinction → immediate action permitted, not universal automatic termination.

Structural Tensions

T1 — Breach Occurrence versus Remedial Consequence. A duty can be violated without the innocent party being entitled to end the entire contract. Condition, innominate-term, and warranty analyses differ, and damages require their own causation and measure. Collapsing these stages can overstate rights as badly as denying the breach altogether. The legal classification must be made under the governing contract and jurisdiction.

Diagnostic: What precise remedy follows from this particular duty and consequence?

T2 — Future Performance Period versus Present Renunciation. An anticipatory refusal can be legally actionable before the scheduled performance date, as Hochster shows, yet ordinary doubts or negotiations do not always amount to refusal. Treating every concern as breach chills communication; treating a clear renunciation as harmless forces the other party to wait futilely. The threshold of definiteness and seriousness keeps the two apart.

Diagnostic: Has the party clearly repudiated an obligation whose future loss meets the governing test?

Structural–Framed Character

Breach of contract is framed-leaning: a portable obligation/deviation relation exists, but legal enforceability and remedy rules are institutional. Evaluative weight: breach is a legal classification, not by itself a moral verdict or proof of compensable harm. Human-practice-bound: the obligations arise from parties and a recognized agreement. Institutional origin: courts and legislatures define repudiation thresholds and remedies, though an individual missed duty can be factually observed. Vocabulary travels: performance and nonperformance travel, while breach of contract retains legal force. Import versus recognize: another enforceable agreement can be tested under its governing law; calling a failed friendship promise breach imports legal vocabulary without its conditions.

The verified portable skeleton is Failure: observed conduct does not satisfy a presently applicable contractual criterion, including a current obligation not to renounce a future duty unequivocally. Its character: a jurisdiction-sensitive legal subtype whose actual and anticipatory routes require their own tests and do not determine remedy automatically.

Structural Core vs. Domain Accent

The legal breach relates a duty to conduct, and legal consequences need an additional step.

What is skeletal. An applicable criterion sets required conduct, and observed nonperformance or an unequivocal present repudiation fails it. This is a strict instance of Failure: the criterion can govern honoring a future duty now, even before service is due. The contract itself remains a related agreement, not a parent of its breach event.

What is domain-bound. Contract law must first recognize an enforceable agreement, interpret the duty, and apply its jurisdiction's timing and repudiation tests. Condition, warranty, and innominate-term categories affect English termination analysis; UCC goods law has its own options.

Why this does not clear the prime bar. An organization can fail a service objective with no contract, and a binding contract can remain intact despite a nonbinding concern. Breach of contract cannot be identified merely from a missed goal: legal enforceability, timing, and repudiation thresholds supply the narrower differentia. Failure carries the portable non-satisfaction relation; the contract-law subtype does not travel without its legal frame.

This entry is a kind of Failure.

  • Strict parent — failure. Actual default and qualifying present renunciation each fail an applicable contractual criterion; the legal duty and governing law narrow the genus.

  • Related — contract. The enforceable agreement supplies the obligation, but its breach is an event relative to that agreement, not a kind of contract.

  • Related — commitment. A contractual duty is a legally governed commitment; not every unkept commitment is breach of contract.

Relationships to Other Abstractions

Local relationship map for Breach of ContractParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Breach of ContractDOMAINPrime abstraction: Failure — is a kind ofFailurePRIME

Current abstraction Breach of Contract Domain-specific

Parents (1) — more general patterns this builds on

  • Breach of Contract is a kind of Failure Prime

    A breach is observed non-satisfaction of an applicable contractual duty or present no-renunciation criterion under governing law.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

Breach of Contract sits in a moderately populated region (40th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Decisions Under Constraint & Commitment (9 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-08

Not to Be Confused With

  • Nonbinding promise. Tell: Was there an enforceable contractual duty?
  • Tentative performance concern. Tell: Was future duty clearly repudiated under the governing law?
  • Contract termination. Tell: Does this breach actually confer a right to end the agreement?
  • Damages. Tell: What separate loss, causation, and remedy rules apply?

References

  • Hochster v De La Tour [1853] EWHC QB J72, original anticipatory-breach judgment: https://www.bailii.org/ew/cases/EWHC/QB/1853/J72.html
  • Grand China Logistics Holding (Group) Co. Ltd v Spar Shipping AS [2016] EWCA Civ 982, paras. 21–22 on breach classification and termination: https://www.bailii.org/ew/cases/EWCA/Civ/2016/982.html
  • Uniform Commercial Code §2-610, anticipatory repudiation in sale of goods: https://www.law.cornell.edu/ucc/2/2-610
  • Frozen Wikipedia discovery revision: https://en.wikipedia.org/wiki/Breach_of_contract (revision 1367226781).