Contracts are not just documents.
They are promises with consequences.
A supplier agrees to deliver goods by Friday. A client agrees to pay within 30 days. A founder signs a service agreement with a vendor. A landlord agrees to repair something before handover. A distributor agrees not to sell competing products. A consultant agrees to keep information confidential.
When everything works, nobody reads the contract. The PDF sits in a folder with a name like "final_final_signed_v3.pdf".
Then something goes wrong.
That is when the contract becomes important.
A breach of contract happens when one party fails to do what they promised, does something they promised not to do, refuses to perform, or makes performance impossible in a way the law recognises as a breach.
But not every inconvenience is a breach. Not every delay ends the contract. Not every breach gives you the right to claim huge damages. And not every angry email should become a legal notice.
This guide explains what counts as a breach, what remedies may be available, and how to document and pursue a claim in a practical way.
The first question is not: "Is this unfair?"
The first question is: "What did the contract require?"
That may sound cold, but contract law is built around the bargain the parties made.
Under the Indian Contract Act, parties to a contract must either perform or offer to perform their promises, unless performance is excused or dispensed with under the Act or other law. If one party wholly refuses to perform or disables themselves from performing, the other party may be able to put an end to the contract, unless they have accepted or acquiesced in its continuation.
So before deciding your next step, read the contract carefully. Look for:
A breach of contract usually means that one party has failed to perform a contractual obligation. Common examples include:
But the breach must be connected to an obligation. If the contract does not require a party to do something, it may be difficult to call their failure a breach. Bad behaviour is not always breach. Poor communication is not always breach. Commercial disappointment is not always breach.
The contract is the starting point.
Not all breaches are equal.
A minor delay in sending a weekly report is different from non-payment of the entire contract price. A small formatting error in a deliverable is different from delivering unusable software. A one-day delay in a non-urgent supply contract is different from missing a launch-date delivery where time was clearly critical.
A minor breach may give a right to compensation or correction, but not always a right to terminate.
A material breach may go to the heart of the contract and justify stronger remedies, including termination, damages, or other action depending on the terms.
A good contract often defines "material breach" and gives a cure period. For example:
That kind of clause matters. It prevents every small dispute from becoming a contract-ending event.
Sometimes the breach happens before the performance date. For example:
This is often called anticipatory breach or repudiation. Section 39 of the Indian Contract Act deals with a party refusing to perform, or disabling themselves from performing, their promise in its entirety. In such a situation, the promisee may put an end to the contract unless they have signified by words or conduct that they accept the contract continuing.
The practical lesson is important. If the other party refuses to perform, do not casually behave as if the contract is still continuing unless you mean to keep it alive. Your response matters. You may need to decide whether to:
Many contracts involve reciprocal promises. One party delivers goods; the other pays. One party provides documents; the other begins work. One party gives access; the other performs services. One party completes milestone one; the other releases milestone payment.
Under the Indian Contract Act, where reciprocal promises are to be performed simultaneously, no party needs to perform unless the other is ready and willing to perform their reciprocal promise. The Act also provides rules on the order of performance where the contract or nature of the transaction requires one promise to be performed first.
This matters in real disputes. A client may say: "You did not complete the work." The vendor may reply: "You never gave us access to the dashboard." A breach claim is weak if you were supposed to do something first and did not do it.
Before accusing the other side of breach, ask:
Delay is one of the most common contract disputes. But delay has layers. Sometimes time is clearly essential. Sometimes it is not. Sometimes the contract says time is of the essence, but the parties behave loosely for months. Sometimes repeated extensions change the picture.
Section 55 of the Indian Contract Act says that where a party promises to do something at or before a specified time and fails to do it, the contract becomes voidable at the promisee's option if the parties intended time to be of the essence. Where time is not essential, the contract does not automatically become voidable, but the promisee may claim compensation for loss caused by delay. If late performance is accepted, compensation for delay may require notice at the time of acceptance.
So do not assume: "They were late, so the contract is over." Ask instead:
Sometimes a party does not perform because something unexpected happens. Flood. Fire. War. Government restriction. Pandemic disruption. Export ban. Sudden illegality. Destruction of subject matter.
A force majeure clause may excuse or suspend performance if the event falls within the clause and the affected party follows the required process. Separately, Section 56 of the Indian Contract Act deals with agreements to do impossible acts and contracts that become impossible or unlawful after they are made. Where performance becomes impossible or unlawful due to an event the promisor could not prevent, the contract becomes void when the act becomes impossible or unlawful.
But force majeure is not a magic phrase. A party cannot usually say: "Business became difficult, so we will not perform." Difficulty is not always impossibility. Higher cost is not always impossibility. Reduced profit is not always impossibility.
Many disputes are not about whether something happened. They are about what the contract meant.
One side says: "Delivery means dispatch from our warehouse." The other says: "Delivery means receipt at our site." One side says: "Approval was deemed after seven days." The other says: "We never gave written approval."
Indian courts generally try to read commercial contracts as commercial documents. The Supreme Court has discussed business efficacy, implied terms, and commercial interpretation, but also warned that where the express terms are clear, courts should not substitute their own presumed understanding for what the parties explicitly agreed. Different clauses should be read harmoniously, without doing violence to another part of the contract.
For ordinary business owners, the lesson is simple: the court may look at context and try to make commercial sense of the bargain. But the court will not casually rescue you from bad drafting.
A contract is not supposed to be a riddle solved after the dispute. It should be a working tool. Good contracts reduce uncertainty by clearly answering:
Many commercial contracts include limitation of liability clauses, exclusion clauses, or caps on damages. A party may say: "Their breach was so serious that they cannot rely on the limitation clause." Maybe. But maybe not.
You still need to read the clause. Ask:
Fairness matters. But fairness does not automatically erase agreed risk allocation. The contract may already have decided who bears which risk.
If there is a breach, the next question is: "What remedy do I want?" Common remedies include:
The right remedy depends on the contract, the breach, the loss, and the forum. Do not ask for everything mechanically. A confused claim looks weak. A good claim knows what it wants.
Section 73 of the Indian Contract Act is the main damages provision. It says that when a contract is broken, the party suffering from the breach is entitled to compensation for loss or damage caused by the breach, which naturally arose in the usual course of things, or which the parties knew at the time of contracting to be likely to result from the breach. Compensation is not given for remote and indirect loss.
This reflects the old Hadley v Baxendale idea: ordinary foreseeable losses may be recoverable; unusual losses usually need special knowledge communicated at the time of contracting.
Example: a courier delays delivery of ordinary office stationery. You may claim the cost difference or direct loss caused by delay. But if that stationery was secretly required for a high-value product launch and the courier did not know that, claiming large lost profits may be difficult.
Section 73 also points to mitigation: when estimating loss, the means of remedying the inconvenience caused by non-performance must be taken into account. In plain language: if the other side breaches, you should take reasonable steps to reduce the loss.
Many contracts say: "For every week of delay, the supplier shall pay ₹50,000." Or: "On breach of confidentiality, the party shall pay ₹10 lakh." Or: "If the buyer defaults, the deposit shall be forfeited."
Section 74 of the Indian Contract Act says that where a contract names a sum to be paid in case of breach, or contains a penalty stipulation, the complaining party is entitled to reasonable compensation not exceeding the amount named or penalty stipulated.
The Supreme Court's treatment has developed over time. In Fateh Chand v Balkishan Das, the Court explained that Section 74 requires reasonable compensation, subject to the contractual ceiling. In ONGC v Saw Pipes, the Court gave greater force to clear liquidated damages clauses where the loss is difficult to prove and the amount is a genuine pre-estimate. In Kailash Nath Associates v DDA, the Court stressed that where no loss or legal injury is shown, forfeiture may fail.
The practical lesson:
Sometimes money is not enough. You may want the other party to actually do what they promised. This is called specific performance, governed by the Specific Relief Act, 1963. After the 2018 amendment, Section 10 says specific performance of a contract shall be enforced by the court subject to specified statutory provisions.
Specific performance may be relevant where:
But it may be difficult where:
The Specific Relief Act also recognises substituted performance. Where a contract is broken due to non-performance, the party suffering breach may, subject to statutory requirements, get the contract performed through a third party or by their own agency and recover the actual expenses and costs from the party in breach. A written notice of at least 30 days is required before undertaking substituted performance.
Example: a contractor abandons repair work midway. Instead of waiting forever, you may serve the required notice, hire another contractor, finish the work, and claim the additional cost from the defaulting contractor, if the legal requirements are satisfied.
Sometimes the remedy is not payment or performance. It is stopping something. For example:
An injunction is a preventive remedy. It is like asking the court to close the tap before calculating the water damage. Injunctions are fact-sensitive and often urgent. Delay can hurt.
Many businesses make a serious mistake here. They terminate first and read the termination clause later. Before terminating, check:
Wrongful termination can itself become a breach.
Contract claims are won with documents. Preserve:
A breach timeline is one of the simplest and most useful documents you can prepare.
| Date | Event | Document / Evidence |
|---|---|---|
| 1 March | Contract signed | Agreement PDF |
| 5 March | Advance paid | Bank transfer |
| 15 March | First milestone due | Clause 4.1 |
| 16 March | Vendor missed milestone | Email reminder |
| 20 March | Vendor promised completion | WhatsApp screenshot |
| 25 March | Defective work delivered | Inspection report |
| 28 March | Cure notice sent | Email + courier |
| 10 April | No cure completed | Follow-up email |
Before escalating, send a clear written notice unless urgency requires something else. A good notice should mention:
Under Clause 5.2 of the agreement dated [date], delivery was due by [date]. The goods have not been delivered despite reminders dated [dates]. Please cure this breach by delivering the goods by [date], failing which we reserve all rights under the agreement and applicable law, including termination and claim for damages.
A breach claim should have numbers. Depending on the case, calculate:
Contract claims are time-sensitive. Under the Limitation Act, 1963, suits for compensation for breach of contract generally have a three-year limitation period from when the contract is broken, or in cases of successive or continuing breach, from the relevant breach or cessation of the continuing breach. Specific performance claims also generally have a three-year period.
Limitation can become technical. Part payments, acknowledgements, continuing breaches, fraud, arbitration clauses, and special statutes can affect strategy. But do not assume repeated reminders keep the claim alive forever.
Where you go depends on the contract and dispute. Check whether the contract has:
If there is an arbitration clause, you may need to invoke arbitration instead of filing an ordinary civil suit. If the dispute is commercial and above the specified value, commercial courts may apply. If the counterparty is insolvent or nearing insolvency, ordinary recovery strategy may need rethinking.
Avoid these:
If the other side has breached, start here:
A breach of contract is not just a broken promise. It is a broken promise that the law can recognise, prove, and remedy.
The strongest contract claim usually has four things:
A clear clause.
A clear breach.
A clear record.
A clear loss.
Indian contract law gives remedies for breach, but it also expects discipline. You must show what was promised, what went wrong, what loss followed, and what steps you took to reduce the damage.
Courts may read contracts commercially. They may consider business efficacy. They may look at context. But they do not exist to rewrite poor bargains after the fact.
The best time to protect yourself is before signing.
The second-best time is when the first warning sign appears.
The worst time is after everyone has deleted the emails and started remembering the contract differently.
Read the contract while the relationship is still friendly. That is when it is cheapest.
Vuqen is a legal knowledge platform. Nothing on vuqen.in constitutes legal advice. For specific legal matters, please consult a qualified advocate.