Termination for Cause vs Termination for Convenience in Indian Contracts

Termination for cause means one party can end the contract because the other side did something wrong: a material breach, insolvency, fraud, or a change of control the contract treats as a trigger. Termination for convenience means either party can walk away on notice, for no reason at all. Indian contracts treat these very differently, and most disputes happen because a contract blurs the two. The one thing people get wrong most often: they let "for cause" mean "for any breach, however small," and forget to write in a cure period. This guide (published by Adira, which makes CLM and contract review software, so we have a commercial stake in you understanding contracts well, but it is written to stand on its own) walks through the Indian statutory position, a real Supreme Court case that turned entirely on a cure-period clause, and what to check before you sign a termination clause.

Plain meaning

A termination-for-cause clause lets a party end the contract early because the other side has done something the contract defines as serious enough: a material breach not fixed in time, insolvency, fraud, or sometimes a change of control that hands the business to a competitor. It usually comes with machinery: a notice describing the breach, a cure period (commonly 15 to 30 days), and a right to terminate only if the breach is not cured within that window.

A termination-for-convenience clause is the opposite in spirit. Either party, or sometimes only one, can end the contract on notice (30, 60, or 90 days is common) without giving any reason and without proving anything went wrong. No breach, no cure period, no fault-finding, just notice and an exit, sometimes with a wind-down fee attached.

Contracts that mix the two badly cause the most fights. A clause that says "either party may terminate for material breach or for convenience on 30 days' notice" sounds tidy, but if it does not define what counts as material, and gives no cure period before a for-cause termination bites, every default becomes an instant termination right, with no chance to fix the problem first.

Who it protects and what triggers it

Termination for cause protects the non-breaching party from being stuck with someone who is not performing, without forcing them to prove damages in court first, they only have to show the breach happened, notice was given, and it was not cured. It also protects the breaching party: a real cure period gives them a chance to fix a genuine mistake before the relationship ends.

The trigger should be a defined, specific event: non-payment beyond a stated period, a missed milestone, a data breach, loss of a required licence, or insolvency. A trigger like "any breach of this Agreement" is a red flag by itself, because it makes a single missed email deadline in an SLA legally the same as walking away from the whole deal.

Termination for convenience protects whoever holds the right to invoke it, almost always the party with more bargaining power, a customer over a vendor, a landlord over a tenant. It needs nothing except a decision and a notice. The real question for the weaker party is whether the clause is mutual, what notice period applies, and whether a wind-down obligation softens an abrupt exit.

What to look for

Five mechanics decide whether a termination clause is fair, and none show up if you only read the heading:

1. Is breach defined, or is it "any breach"? A material-breach standard tied to specific obligations (payment, deliverables, confidentiality, IP, compliance) is normal. "Any breach, however minor" as a trigger is a red flag.
2. Is there a cure period, and how long? 15 to 30 days for a curable breach is standard. No cure period, or one too short to meet, defeats the point of calling it "for cause."
3. Automatic or elective termination? Some clauses end the contract the moment the cure period lapses; others require a further notice. Automatic termination removes the flexibility to keep a struggling vendor in place while you find a replacement.
4. Is convenience termination mutual, and is the notice period workable? A one-sided right shifts nearly all commercial risk onto the other side. Check the notice period is long enough to find a replacement.
5. What survives termination? Confidentiality, IP ownership, payment for completed work, and data return should explicitly survive under either route, or a for-convenience exit can strand a customer mid-cutover.

The Indian position: Sections 39 and 55 of the Contract Act

Indian law does not use the phrase "termination for cause" as a statutory term, but two provisions of the Indian Contract Act, 1872 supply the default rules most negotiated clauses sit on top of.

Section 39 gives the non-breaching party the right to end the contract when the other side refuses to perform in its entirety:

"When a party to a contract has refused to perform, or disabled himself from performing, his promise in its entirety, the promisee may put an end to the contract, unless he has signified, by words or conduct, his acquiescence in its continuance." Source: Section 39, Indian Contract Act, 1872

This is the statutory ancestor of "termination for cause": if the other party has refused, or made itself unable, to perform the promise wholly, you can put an end to the contract, without needing a specific clause. Two things matter in the wording. First, it requires refusal or disablement "in its entirety," a partial shortfall does not automatically qualify unless your own termination clause says it does. Second, if you keep accepting performance after the refusal, you lose the right to terminate on that ground, though you keep the right to claim damages.

Section 55 is the source of "time is of the essence" language in almost every cure-period clause:

"When a party to a contract promises to do a certain thing at or before a specified time... and fails to do any such thing at or before the specified time, the contract... becomes voidable at the option of the promisee, if the intention of the parties was that time should be of the essence of the contract." Source: Section 55, Indian Contract Act, 1872

If time was not intended to be of the essence, late performance does not automatically make the contract voidable, the promisee only gets compensation for the loss caused by delay. This is why cure periods matter in drafting: a cure period converts a disputed "was time essential" question into a clean, contractual trigger. If the breach is not cured in the stated window, you can terminate, without litigating what the parties "intended."

A named case: Delhi Airport Metro Express v Delhi Metro Rail Corporation

The clearest recent illustration of how much a cure-period clause can decide is Delhi Airport Metro Express Pvt. Ltd. v Delhi Metro Rail Corporation Ltd. (Supreme Court of India, 9 September 2021). DAMEPL, the concessionaire operating the Delhi Airport Metro Line, issued a cure notice to DMRC on 9 July 2012 over structural defects in civil works, giving 90 days to cure under Article 29.5.1 of the Concession Agreement. When DMRC had not cured the defects in that window, DAMEPL issued a termination notice on 8 October 2012 and ended the concession.

The dispute that reached the Supreme Court was really about how to read the 90-day cure clause: did the clock run once from the first notice, or could DMRC claim a fresh 90 days after the termination notice too. The arbitral tribunal read the clause to mean defects had to be cured within 90 days of the cure notice, failing which DAMEPL could terminate, and the Supreme Court in 2021 held this was "a possible interpretation" and declined to interfere.

Why this matters for your contract: a multi-year dispute, arbitration, a High Court appeal, and a Supreme Court judgment, turned entirely on the wording of one cure-period clause and when its clock started. (This 2021 judgment was itself set aside by the Supreme Court in 2024 through a rare curative petition, on grounds unrelated to the cure-period reading, a reminder that precise drafting matters more than hoping a court reads an ambiguous clause your way.)

Termination for convenience: Indian Oil v Amritsar Gas Service

The other half of this page has its own settled authority: Indian Oil Corporation Ltd v Amritsar Gas Service and Others (Supreme Court of India, (1991) 1 SCC 533, decided 19 November 1990). The distributorship agreement had two termination clauses side by side: Clause 27 allowed termination for specified cause, Clause 28 allowed either party to terminate on 30 days' notice, no reason required, a classic convenience right.

When the Corporation terminated citing Clause 27, the arbitrator initially ordered restoration of the distributorship plus compensation. The Supreme Court held that restoring the distributorship was not something a court, or an arbitrator, could order, because the agreement was a "determinable" contract under the Specific Relief Act, one either party could lawfully end on notice under Clause 28 regardless of the Clause 27 dispute. Section 14 of the Specific Relief Act, 1963 lists contracts that cannot be specifically enforced, and a contract "in its nature determinable" is one of them. The Court held the only relief available was compensation for the 30-day notice period, not reinstatement.

Why this matters practically: if your contract has a termination-for-convenience clause anywhere in it, Indian courts treat the whole relationship as "determinable," and specific performance, being forced to keep supplying, buying, or employing, is generally off the table even if you separately win an argument about wrongful for-cause termination. Your remedy shrinks to damages for the notice period. Think carefully before including a broad, one-sided convenience right, it can undercut the protection your for-cause clause was meant to give the other side.

Red flags

Normal	Red flag	Why it matters
"Material breach" is defined, tied to specific obligations (payment, deliverables, IP, compliance, confidentiality)	Trigger is "any breach of this Agreement," however minor	Turns a missed formality into the same ground as walking away from the whole deal
Cure period of 15-30 days for a curable breach, running from written notice	No cure period, or termination is immediate on notice of breach	Removes any real chance to fix a genuine mistake before losing the contract
Termination requires a further notice once the cure period lapses	Contract terminates automatically the moment the cure window ends	Removes flexibility to keep a struggling counterparty in place while you transition away
Convenience right is mutual, both sides can exit on notice	Only one party (usually the stronger one) can terminate for convenience	Shifts nearly all commercial and continuity risk onto the weaker party
Convenience notice period is workable (30-90 days depending on the relationship)	Notice period is a few days, or unspecified	Leaves the exiting counterparty no real time to find a replacement or wind down
Confidentiality, IP, payment for completed work, and data return survive termination under either route	Survival clause lists only a few obligations, or is silent on data return	Can leave a party without paid-for deliverables or a legal basis to demand data back
Insolvency and change of control are separate, cause-based triggers	Insolvency or change of control is missing from the termination grounds entirely	Leaves you stuck with a bankrupt or hostile-owned counterparty until the term ends

Bad clause → better clause

Bad: "Either party may terminate this Agreement immediately upon written notice if the other party breaches this Agreement."

What is wrong: no distinction between a minor and a material breach, no cure period, no defined list of triggering events, and termination is immediate, which effectively converts the whole contract into terminable-at-will dressed up as "for cause."

Better: "Either party (the 'Non-Breaching Party') may terminate this Agreement for cause by written notice if the other party (a) commits a material breach of this Agreement (including non-payment of undisputed amounts for more than 30 days, or failure to deliver a Milestone under Schedule 2) and fails to cure such breach within 21 days of written notice describing the breach in reasonable detail, or (b) becomes insolvent, has a winding-up petition admitted against it, or undergoes a Change of Control to a direct competitor without prior written consent. Termination shall take effect on the date stated in a further written termination notice issued after expiry of the cure period, and shall not be automatic. Sections [Confidentiality], [IP Assignment], [Payment for Services Rendered] and [Data Return] shall survive termination under this Clause."

What changed and why: material breach is defined against specific, checkable obligations, there is a real cure period with a notice requirement, insolvency and change of control are separate cause-based triggers, termination requires an affirmative second notice instead of happening automatically, and survival is spelled out rather than left implied.

How it interacts with related clauses

Termination for cause rarely stands alone. Three related clauses decide how much it actually protects you:

• Termination for convenience. A convenience right anywhere in the contract can make the whole relationship "determinable," limiting your remedy to notice-period damages even if a for-cause termination was wrongful. Read the two clauses together, not as independent fallbacks.
• Force majeure. A force majeure event (a pandemic, a disaster, a government order) is not a breach. A well-drafted contract should say a party excused by force majeure cannot simultaneously be terminated "for cause" over the same non-performance.
• Limitation of liability and indemnity. Termination does not usually wipe out accrued claims from the breach that triggered it. Check that your liability cap and indemnity obligations explicitly survive termination.

You can map how a termination clause connects to force majeure, payment, and survival clauses for free in Weave, which lets you mark up and comment on a contract's clauses before you send it back for negotiation.

US and global contrast

US contracts use "termination for cause" and "termination for convenience" as standard, heavily negotiated categories, but most US commercial contracts, unlike Indian ones, are often genuinely terminable at will absent a fixed-term commitment, so a "for convenience" clause frequently confirms an already-available right rather than granting a new one. Cure periods follow broadly similar mechanics, notice, a defined window (commonly 10 to 30 days), and a right to terminate if uncured, and US courts assess "materiality" through doctrines like substantial performance, similar in effect to how Indian courts read Section 39's "refused to perform... in its entirety." The bigger difference is remedy: Indian courts, as Indian Oil v Amritsar Gas Service shows, are markedly reluctant to order specific performance or reinstatement, damages for the notice period is the default outcome, whereas some US jurisdictions, particularly franchise and distribution relationships with statutory protection, allow injunctive relief more readily.

FAQ

What is the difference between termination for cause and termination for convenience? Termination for cause requires a specific triggering event, usually a defined material breach, insolvency, or change of control, and typically comes with a notice-and-cure mechanism. Termination for convenience requires no reason at all, either party can end the contract simply by giving notice for the stated period.

Does Indian law require a cure period before terminating for breach? Not as a blanket rule, but Section 39 requires the refusal or disablement of performance to be "in its entirety" before the promisee can end the contract on that ground alone. In practice, almost every negotiated Indian contract writes in an explicit cure period, commonly 15 to 30 days, rather than relying on the bare statute to judge whether a partial breach was serious enough.

Can I still get an injunction to keep my contract alive if the other side terminates wrongfully? Usually not, if the contract also contains a termination-for-convenience clause anywhere in it. As Indian Oil v Amritsar Gas Service (Supreme Court, 1991) held, a contract either party can end on notice is "determinable" under Section 14 of the Specific Relief Act, and courts will not specifically enforce it. Your remedy is usually damages for the notice period, not reinstatement.

What happens if a cure-period clause is ambiguous about when the clock starts? Exactly this question, whether a 90-day cure period ran once from the first notice or restarted after a later notice, was the central dispute in Delhi Airport Metro Express v Delhi Metro Rail Corporation (Supreme Court, 2021), which took years of arbitration and litigation to resolve. Draft the trigger date explicitly, the date of the notice, not the date it is received or acknowledged, to avoid the same fight.

Should insolvency and change of control be treated as "for cause" grounds? Yes, and separately from ordinary breach. They are status changes in the counterparty, not breaches of a specific obligation, so they should be standalone triggers, usually without a cure period, since there is often nothing to "cure."

Is termination for convenience always unfair to the smaller party? Not inherently. It becomes a red flag when it is one-sided, paired with a short notice period, or has no wind-down obligation attached. A mutual convenience right with a workable notice period lets both sides avoid a long, contentious for-cause dispute when a relationship simply is not working.

This guide gets you to understanding what a termination-for-cause clause does under Indian law, how it differs from termination for convenience, and what to check before you sign. It does not tell you whether a specific clause in your contract is enforceable, well-drafted, or wise to invoke in your situation, that depends on the exact wording, the facts of the breach, and how the rest of your contract is drafted, and is not legal advice. Talk to a lawyer before you send a termination notice or rely on one you have received.