Termination for Cause
Definition
Termination for Cause
Termination for cause ends an outsourcing contract because the other party has breached it, normally after a written notice and a failed opportunity to fix the problem. Breach is the trigger, and the party terminating must be able to prove it.
The clause is the counterweight to convenience termination — it costs nothing to invoke, but it carries the risk that a court or tribunal later finds the breach was not serious enough.
Most contracts distinguish material breach from persistent minor breach. The first is a single failure grave enough to justify exit; the second is an accumulation that passes a stated threshold.
Evidence decides these cases — a buyer who never issued a formal notice, never logged the failures and never escalated has a weak position however bad the service felt.
Key takeaways
- Cause requires a breach, and the terminating party carries the burden of proving it.
- Most clauses demand written notice and a cure window, commonly 15 to 30 days.
- Persistent minor breach needs a counting rule, or it is unusable in practice.
- A wrongful cause termination can convert into a convenience termination, with the fee attached.
How it works
A workable clause defines what counts as breach, how notice is given, how long the defaulting party has to cure, and what happens to charges and data on the day service stops. Vague drafting fails all four.
Federal terms show the shape. Under the standard default clause, the right to terminate arises if the contractor “does not cure such failure within 10 days” of a written notice specifying the failure.
| Trigger type | Typical threshold | Cure period | Evidence needed |
|---|---|---|---|
| Material breach | Single grave failure | 15 to 30 days, or none | Incident record, impact |
| Persistent breach | Three misses in six months | 30 days | Signed performance reports |
| Insolvency | Filing or administration | None | Public record |
| Regulatory failure | Licence loss, sanction | None | Regulator notice |
| Security incident | Defined severity level | Varies | Forensic report |
The persistent-breach row is where most clauses collapse — without a counting rule tied to the service level agreement clause, nobody can say whether the threshold has been crossed.
Getting it wrong is expensive. The same federal terms provide that where a default termination turns out to be unjustified, the parties’ rights become “the same as if the termination had been issued for the convenience” of the buyer.
UK procurement guidance treats performance measurement as the foundation. All new projects, it says, should carry measures “relevant and proportionate to the size and complexity of the contract”, which is what makes a cause case provable.
Examples
Cause terminations are rare and consequential, and they usually turn on paperwork rather than on how bad the service was. The four cases below show what separates a clean exit from a costly one.
A utility terminates after a provider misses its answer-time target for five consecutive months. Every miss sits in a signed report and every service credit was claimed, so the threshold is arithmetic rather than argument.
An insurer terminates immediately after a data incident exceeds the contract’s defined severity level. No cure period applies, because the clause treats that category as incurable by design.
A logistics buyer serves a cure notice and the provider fixes the problem in 21 days. The termination right lapses, which is exactly what the cure mechanism exists to achieve.
A retailer terminates for cause, loses the argument and pays. The tribunal finds the failures were real but not material, and the exit is re-characterised as convenience.
Related terms
Cause sits inside a stack of clauses that measure, escalate and finally end a relationship. The entries below show which one applies at which point in that sequence.
- Escalation plan: the governance steps that must usually be exhausted before notice is served.
- Right to audit clause: the tool that produces the evidence a cause case depends on.
- Termination fees: normally not payable on a valid cause exit, which is the commercial point.
- Business continuity clause: keeps the service running while the termination takes effect.
- Underpinning contract: the provider’s own supplier agreement, where the root cause often actually sits.
FAQ
What counts as material breach?
A failure that deprives the other party of substantially the whole benefit of the contract. Contracts that list specific examples are far easier to enforce than those relying on the phrase alone.
Is a cure period always required?
No. Insolvency, licence loss and defined security incidents are commonly carved out as incurable, allowing immediate termination.
Does the buyer pay a fee when terminating for cause?
Normally not, and that is the commercial distinction. Exit payments attach to convenience termination, not to a valid cause exit.
What happens if the breach is disputed?
The service usually continues under the continuity clause while the dispute runs. A wrongful termination can be re-characterised as convenience, with the fee then due.
Can a provider terminate the buyer for cause?
Yes, most often for sustained non-payment or for a failure to supply agreed inputs such as system access or source data.
How many failures make a persistent breach?
Whatever the contract says. Three misses in six months is a common formulation, but the number is meaningless without a defined measurement window.
Read how outsourcing contracts are structured and governed across the Outsource Accelerator knowledge base.
Independent
