Termination Clauses: What's Standard in 2026
What is a standard termination clause?
A market-standard termination clause layers three exit rights rather than one. Termination for convenience on 30 to 90 days written notice, usually after an initial committed term and sometimes with a fee or transition obligation. Termination for cause on material breach, typically with a 30-day cure period and immediate exit for non-curable breaches. And an insolvency trigger, drafted knowing its enforceability is heavily restricted once a formal process starts. There is no single legal "correct" structure, but this is the architecture most counterparties recognize as fair.
A termination clause does two separate jobs that are easy to conflate. It sets the triggers, meaning who can exit and on what grounds, and it sets the consequences, meaning what actually happens at the moment the contract ends. A strong right to walk away is worthless if you cannot get your data out, keep operating during migration, or recover prepaid money. The load-bearing advice for in-house counsel is to negotiate the consequences, not just the triggers.
This guide is part of our "what is standard?" clause series. It is written for in-house legal teams and the business users they enable: the sales, procurement, and partnerships colleagues who hit these clauses daily and need to know when a term is normal, when to push, and when to escalate.
What's actually in a termination clause
A well-drafted termination clause has several moving parts, and they should be read as separate levers rather than one block of text.
1. Termination for convenience. The right to exit for any business reason without alleging fault, typically on prior written notice. It is heavily buyer-favorable, so suppliers resist it or attach an early-termination fee. A common compromise is a convenience right that commences later in the term, once the vendor has recovered implementation cost.
2. Termination for cause. The right to exit because the other side failed to perform: material breach, non-payment, or persistent breach. For curable breaches it runs through a notice-and-cure mechanism. The fight here is over what counts as "material," how long the cure window is, and whether the remedy is real termination or just service credits.
3. The insolvency trigger. The right to exit if the counterparty becomes insolvent or enters a formal process. These clauses remain common in drafts, but their enforceability is curtailed by US section 365(e) and UK CIGA 2020 once a formal process begins.
4. Effect of termination. The post-exit mechanics: cessation of access or license, settlement of outstanding payments, data return or deletion, refunds of prepaid fees, and transition assistance. This is where the clause earns its keep.
5. Survival. Which obligations outlast the contract and for how long, such as confidentiality, IP ownership, indemnification, and the liability cap.
A termination clause is only as good as its effect-of-termination section. A SaaS customer is renting access, not buying perpetual rights, so the agreement should state plainly that the right to access and use the software ends on expiry or termination. The reciprocal protections matter just as much: agree the data-return format in writing in advance, set a hard deadline for any transition window so it cannot quietly convert into a new long-term license, and write the refund formula explicitly. Negotiate the consequences, not just the triggers.
The survival list deserves a second look in particular. The risk is asymmetric survival, where the vendor protections, such as the liability cap and disclaimers, survive while the customer protections, such as data-return duties and indemnities running to the customer, lapse. Confirm the list is balanced rather than drafted to outlast only one side's obligations.
Is it reasonable?
Use the table below to triage a clause quickly. The "Standard" column is the position most counterparties accept without much friction. "Aggressive" is where you should push back. "Red flag" is where you escalate or walk.
| Element | Standard | Aggressive (push back) | Red flag (walk away) |
|---|---|---|---|
| Termination for convenience | Mutual right on 30 to 90 days notice, often after an initial term, with a declining fee | Convenience right for the vendor only, not the customer | No customer convenience right at all, plus multi-year auto-renew lock with no opt-out |
| Cure period | 30 days for general breach, 10 to 15 for payment, immediate for non-curable breaches | Long 60 to 90 day cure window before any breach becomes actionable | Long cure for the vendor, short or no cure for you, with vague "material" definition |
| Material-breach definition | Tied to objective, measurable criteria such as SLA metrics or enumerated triggers | Undefined "material breach" the vendor can dispute case by case | Exclusive-remedy clause capping your recourse at service credits, so an SLA miss never ripens into a termination right |
| Effect of termination | Data return or deletion in an agreed format, prorated refund on for-cause exit, priced transition help | No pro-rata refund of prepaid fees on for-cause exit | Vague or missing data-return timelines and formats, no transition assistance |
| Insolvency trigger | Insolvency right drafted, but understood to be limited by US section 365(e) and UK CIGA 2020 | Relying on the trigger as if fully enforceable post-filing | A clause structured so the only meaningful exit is one a bankruptcy court will void |
| Survival list | Balanced: confidentiality, IP, indemnity, liability, dispute resolution all survive both ways | Survival drafted to favor the vendor's protections | Vendor protections survive while your data-return and indemnity rights lapse |
The point of the table is symmetry and substance. A clean exit right means little if the data-return format, refund formula, and transition deadline are left vague, because that is where a departing customer actually gets stuck.
Treat any of these as a trigger to push back hard or escalate: a termination-for-convenience right that runs to the vendor but not to you; the vendor able to terminate on minor rather than material breach, or a long vendor cure window paired with a short or absent one for you; an ambiguous "material breach" with no objective criteria; cure periods of 60 days or more with no SLA metrics behind them; an exclusive-remedy clause that limits you to service credits so a breach never becomes a termination ground; SLAs measured annually so a failure takes a year to qualify; auto-renewal with no clear opt-out; no pro-rata refund of prepaid fees on a for-cause exit, or early-termination penalties with no offsetting credits; vague or missing data-return and deletion timelines and formats; and missing or unpriced transition-assistance provisions. Most of these are individually fixable. Several together usually mean the exit right was drafted to be unusable in practice.
How to negotiate it
The cleanest way to negotiate termination is to decide your three positions before you open the document, then trade down a defined ladder rather than improvising. This is the playbook concept: a documented ask, fallback, and walk-away for the clause, so anyone on the team negotiates it the same way.
A typical ladder for a buyer on a service-heavy deal looks like this. Ask: a mutual termination-for-convenience right on 60 to 90 days notice, a 30-day cure (shorter for payment and critical failures), for-cause triggers anchored to measurable SLA metrics, a prorated refund of prepaid fees on for-cause exit, and a priced transition window with a hard deadline. Fallback: accept that convenience commences only after year one, in exchange for a declining early-termination fee, longer notice, or a windowed change-of-control out, plus mutual carve-outs for data return and confidentiality. Walk-away: no customer exit right, a credits-only remedy that never ripens into termination, and no agreed data-return format.
Three tactics consistently help. First, anchor for-cause triggers to objective, measurable metrics rather than subjective judgment, so the vendor cannot argue a failure was not "material." Second, when the vendor refuses convenience outright, reach for realistic compromises instead of dying on the principle: a right that commences later in the term, a declining fee, longer notice, 12-month auto-renew cycles instead of multi-year locks, or an event-based out tied to renewal or a change of control. Third, fix transition fees in advance and attach consequences such as service credits if the provider fails, so the migration window cannot become a place where rates are quietly raised at the worst possible moment.
What the other side will argue
Most termination negotiations recycle the same handful of counterparty arguments. Having a calm, standard response ready keeps the conversation on the substance.
| They say | You say |
|---|---|
| "We cannot offer termination for convenience; it makes our revenue unpredictable." | "Understood, so let's commence the convenience right after year one, once you have recovered acquisition cost, with a declining early-termination fee." |
| "Sixty to ninety days is our standard cure period." | "For complex performance breaches, agreed. For payment and critical failures we need 10 to 15 days, since those are easily verified and easily cured." |
| "Any breach has to be material before you can terminate." | "Then let's define material against objective, measurable SLA metrics, so neither of us is arguing about it after the fact." |
| "Service credits are your remedy for an SLA miss." | "Credits are fine as a first remedy, but a persistent or critical SLA failure has to be an independent termination ground, not absorbed by the credit." |
| "Transition assistance is billed time-and-materials at the time of exit." | "We need the transition fees fixed in advance with a hard deadline and the data-return format agreed in writing, so the rate cannot move when we leave." |
The framing that unlocks most of these is to separate the trigger from the consequence. The vendor will happily debate the headline notice period while the refund formula, data-return format, and transition pricing go unexamined, and those are where a departing customer actually gets stuck.
Sample clause language
The language below is general, illustrative guidance to show what standard and aggressive positions tend to look like. It is not legal advice, it is not a substitute for counsel reviewing your specific agreement and governing law, and Bind is not a law firm. Enforceability in particular varies by jurisdiction, and insolvency-trigger enforceability is restricted in both the US and the UK; align the clause with the law that governs your contract.
Standard, balanced position (illustrative):
Either party may terminate this Agreement for convenience on not less than ninety (90) days prior written notice, effective no earlier than the end of the Initial Term. Either party may terminate for cause if the other party commits a material breach and fails to cure it within thirty (30) days of written notice describing the breach (or within ten (10) days for non-payment), provided that breaches of confidentiality or data-security obligations are non-curable and permit immediate termination. On termination for the Vendor's uncured material breach, the Vendor will refund the prorated portion of any prepaid, unused fees from the effective date of termination. On any termination, the Vendor will, for up to ninety (90) days, provide transition assistance and return or delete Customer Data in the format specified in Exhibit [X], at the rates set out in that Exhibit.
This is balanced because the convenience right is mutual and timed to the Initial Term, the cure periods are differentiated (shorter for payment, none for data and confidentiality breaches), the refund mechanic is explicit, and the data-return format and transition rate are fixed in advance rather than left to be billed at exit.
Aggressive, vendor-favorable position (push back, illustrative):
Vendor may terminate this Agreement at any time for convenience. Customer may terminate only for Vendor's material breach that remains uncured for ninety (90) days after written notice. Customer's sole and exclusive remedy for any service failure is the service credits set out in the SLA. Fees paid are non-refundable. Transition assistance, if any, will be provided on a time-and-materials basis at Vendor's then-current rates.
The problems are stacked. The convenience right is one-sided, running only to the vendor. The cure window is a long 90 days with no carve-out for critical or non-curable breaches. The exclusive-remedy clause caps the customer at credits, so a service failure never ripens into a termination right. There is no refund of prepaid fees, and transition help is unpriced and discretionary, which is exactly where rates get raised at the moment of exit. Each of those is a separate point to negotiate back toward the balanced position above.
How Bind handles this
Bind checks every contract against your playbook and flags non-standard termination terms automatically, such as one-sided convenience rights, over-long cure periods, credits-only remedies, and missing data-return or refund mechanics, so business teams can self-serve within guardrails legal sets once. Because Bind is rule-based and jurisdiction-agnostic, you encode your own standard, fallback, and walk-away positions for the termination clause, and Bind applies them consistently on every deal rather than depending on whoever happens to be reviewing. It is general enforcement of your rules, not legal advice. You can see how it fits an in-house workflow at bindlegal.com.
Ready to simplify your contracts?
See how Bind helps teams manage contracts from draft to signature in one platform.
Frequently asked questions
- What is a standard termination clause?
- A market-standard termination clause usually combines three exit rights. Termination for convenience on 30 to 90 days written notice, often after an initial committed term. Termination for cause on material breach, typically with a 30-day cure period and immediate exit for non-curable breaches. And an insolvency trigger, drafted knowing its enforceability is heavily restricted once a formal bankruptcy or rescue process starts.
- What is the difference between termination for convenience and termination for cause?
- Termination for convenience lets a party exit for any business reason without alleging wrongdoing, typically on prior written notice and sometimes with an early-termination fee or transition obligation. Termination for cause is triggered by the other side failing to perform, such as material breach or non-payment, and for curable breaches it is usually preceded by a notice-and-cure mechanism. Most well-drafted commercial contracts include both, giving layered exit rights.
- What is a standard cure period for a contract breach?
- The market-default cure period is 30 days from written notice describing the breach. Differentiated windows are common best practice: payment or non-payment breaches often get a shorter 10 to 15 days because they are easily verified and cured, while complex performance or technical breaches may get 30 to 60 days. Contracts routinely carve out non-curable breaches, such as confidentiality or data exposure, that trigger an immediate right to terminate.
- Are insolvency or bankruptcy termination clauses enforceable?
- Often not, once a formal process starts. In the US, section 365(e) of the Bankruptcy Code generally invalidates ipso facto clauses that terminate a contract solely because a party becomes insolvent or files for bankruptcy, subject to safe harbors. In England and Wales, the Corporate Insolvency and Governance Act 2020 voids supplier termination clauses triggered merely by the customer entering an insolvency or rescue process. The triggers stay common in drafts, but their enforceability is curtailed.
- What is a typical notice period for termination for convenience?
- For general commercial contracts the broad market range is 30 to 90 days written notice. Common patterns illustrate the practice: technology and SaaS deals often sit around 60 days, IT outsourcing nearer 90 days, professional services 30 to 60 days, and managed services 90 to 120 days because the transition is complex. Convenience rights frequently commence only after an initial committed or minimum term, so the vendor can recover setup cost.
- Which contract clauses survive termination?
- Provisions that commonly survive include confidentiality, IP ownership, indemnification, limitation of liability, dispute resolution, governing law and venue, and accrued payment obligations. Confidentiality commonly survives 3 to 5 years (longer for technology deals), trade-secret protection indefinitely, and liability caps typically indefinitely. The risk to check is asymmetric survival, where the vendor protections outlast the contract while the customer protections, such as data-return duties, quietly lapse. See our clause library guide.