Contracts run on trust. Both sides plan their finances, sourcing, and next steps around the assumption that the other party will deliver on the agreed date. But what happens when one party announces, weeks before that date, that it simply won’t perform? Does the other side have to sit and wait for the actual due date before doing anything about it? Indian contract law says no. This is where the doctrine of anticipatory breach steps in, giving the aggrieved party the right to act the moment the other side signals it won’t honour the deal.
Table of Contents
- What is anticipatory breach of contract?
- The legal basis: Section 39 of the Indian Contract Act
- An illustration worth remembering
- Where the doctrine began: Hochster v De La Tour
- Frost v Knight and conditional promises
- What can the aggrieved party do?
- Option 1: Treat the contract as discharged and sue immediately
- Option 2: Wait until the performance date
- Anticipatory breach versus actual breach
- Remedies available under Indian law
- Why this doctrine matters in practice
- Express versus implied repudiation: a quick recap
What is anticipatory breach of contract?
An anticipatory breach occurs when a party to a contract communicates, before the performance is actually due, that it will not fulfil its obligations. The refusal doesn’t have to wait for the deadline to pass. The moment one party makes it clear through words or conduct that it won’t perform, the other party’s right to sue is triggered, even though the actual date of performance is still in the future.
This can happen in two ways. A party may explicitly state that it will not perform, which is called express repudiation. Or a party may do something that makes performance impossible without directly saying so, known as implied repudiation. For example, if a supplier agrees to deliver machinery by a certain date but sells that exact machinery to someone else beforehand, the act itself signals an inability to perform, even without a formal announcement.
The legal basis: Section 39 of the Indian Contract Act
The doctrine is rooted in Section 39 of the Indian Contract Act, 1872, which addresses situations where a party refuses to perform, or disables itself from performing, its promise in its entirety. In such cases, the promisee has the option to end the contract, unless they have already indicated, through words or conduct, that they accept the contract’s continuation.
Legal commentary points out that Section 39 doesn’t use the phrase “anticipatory breach” explicitly, but its language and effect closely track the common law doctrine of the same name, which is why Indian courts have consistently read the two together while deciding disputes involving pre-performance repudiation, as discussed in this analysis of Section 39 and anticipatory breach.
An illustration worth remembering
A classic example used in Indian law texts involves a singer engaged to perform at a theatre twice a week for two months. If the singer informs the theatre manager midway through the arrangement that she will not perform for the remainder of the contract, the manager doesn’t have to wait for the contract term to end. He can treat the contract as terminated immediately and pursue damages for the loss caused by her refusal.
Where the doctrine began: Hochster v De La Tour
The doctrine has its roots in English common law, and Indian courts have often referred back to its origins. In the landmark case Hochster v De La Tour (1853), a courier was hired to accompany a nobleman on a European tour starting in June. In May, before the tour was due to begin, the nobleman informed the courier that his services were no longer required. The court held that the courier didn’t have to wait until June to sue. Since the contract existed from the date it was made, its breach could be actionable as soon as one party clearly refused to honour it, rather than only from the date performance was due.
Frost v Knight and conditional promises
A related question is what happens when a promise depends on some future event or contingency. In Frost v Knight (1872), the court extended the same logic to conditional contracts. Even where performance depends on a contingency that hasn’t yet occurred, if a party disables itself from performing before that contingency arises, the other party can sue for damages immediately rather than waiting to see whether the contingency ever materialises.
What can the aggrieved party do?
Once anticipatory breach occurs, the law doesn’t force the aggrieved party into a single course of action. They get to choose, and the choice matters because it changes how damages are calculated later.
Option 1: Treat the contract as discharged and sue immediately
The promisee can rescind the contract the moment the repudiation happens and claim damages right away, without waiting for the performance date to arrive. This lets them start mitigating losses early, for instance by sourcing goods from another supplier or entering into a substitute arrangement, as explained in this overview of anticipatory breach remedies in India.
Option 2: Wait until the performance date
Alternatively, the promisee can choose to keep the contract alive and wait to see if the other party changes its mind and performs after all. This comes with a risk. If the promisee’s conduct signals acceptance of the continuation of the contract, such as by continuing to deal with the breaching party as though nothing happened, they may lose the right to treat the earlier repudiation as a ground for termination, though they can still claim compensation for any loss already suffered because of the initial refusal.
Anticipatory breach versus actual breach
| Aspect | Anticipatory breach | Actual breach |
|---|---|---|
| When it occurs | Before the date fixed for performance | On or after the date fixed for performance |
| Right to sue | Arises immediately on repudiation | Arises once the due date passes without performance |
| Promisee’s choice | Can rescind now or wait for the due date | No choice to wait; the breach has already happened |
| Governing provision | Section 39, Indian Contract Act, 1872 | Sections 37, 73 and related provisions |
Remedies available under Indian law
Once the promisee decides to treat the contract as broken, several remedies become available:
- Compensatory damages: Monetary compensation for the direct financial loss caused by non-performance, generally assessed under Section 73 of the Indian Contract Act, which deals with compensation for loss caused by breach, as detailed in this note on breach of contract remedies.
- Rescission and restitution: The contract can be treated as cancelled, and any benefit already transferred under it can be recovered, restoring both parties as far as possible to their pre-contract position.
- Specific performance: Where monetary compensation wouldn’t be an adequate remedy, such as contracts involving unique goods or property, courts may direct the defaulting party to actually perform its obligations under the Specific Relief Act, 1963.
Courts also expect the aggrieved party to take reasonable steps to reduce their own losses rather than let them pile up. This principle of mitigation runs through Indian contract jurisprudence and directly affects how much compensation a court is willing to award.
Why this doctrine matters in practice
Business relationships rarely wait around for a court’s timeline. If a manufacturer knows three months in advance that a key supplier won’t deliver raw materials, waiting until the delivery date to act could mean lost production time, penalty clauses with the manufacturer’s own customers, or a scramble to find a substitute at short notice. The doctrine of anticipatory breach exists precisely to prevent this kind of forced passivity. It lets businesses respond to a broken promise the moment it’s made clear, arrange alternatives sooner, and reduce the overall damage, a rationale echoed in commentary describing the doctrine as a matter of business convenience and loss mitigation within Indian contract law.
For commerce students, this concept ties directly into how real deals are structured. Supply agreements, service contracts, and even simple purchase orders often include clauses anticipating exactly this scenario, because the law itself recognises that certainty about non-performance is sometimes just as actionable as non-performance itself.
Express versus implied repudiation: a quick recap
It helps to keep the two categories distinct when analysing case studies or exam problems:
- Express repudiation: The party clearly states, in words or in writing, that it will not perform its obligations.
- Implied repudiation: The party’s conduct makes performance impossible or highly unlikely, even without an explicit statement, such as disposing of the very goods promised to another buyer.
Both forms carry the same legal consequence under Section 39. What matters is not the form of the refusal but whether it clearly signals an unwillingness or inability to perform the contract as a whole.
What do you think? If you were running a business and a key supplier hinted, informally, that they might not deliver on time, would you treat that as a clear enough signal to invoke anticipatory breach, or would you wait for something more definite? How would that decision change if the goods involved were easily available elsewhere versus highly specialised?
References
- https://wbconsumers.gov.in/writereaddata/ACT%20&%20RULES/Relevant%20Act%20&%20Rules/the-indian-contract-act-1872.pdf
- https://ijosper.uk/index.php/i/article/view/298
- https://www.writinglaw.com/anticipatory-breach-of-contract/
- https://corridalegal.com/understanding-anticipatory-breach-in-india/
- https://lexibal.com/breach-of-contract-and-remedies-2/
- https://www.lawweb.in/2025/06/anticipatory-breach-of-contract.html
Leave a Reply