How to Review a Notice-and-Cure Period Before Termination for Cause

Nash, Ops at a 20-person UK SaaS, is about to treat “we have a cure period — that’s fair” as protection. Finance said standard for-cause. Knowing how to review a notice-and-cure period before termination for cause is a 25-minute hunt: write whether the notice names clause, facts, and cure; split undisputed-money days from performance days; replace Vendor discretion with a named incurable list; then lengthen, split, or walk.

September 2026. English law; exclusive courts of England and Wales. The packet — the exact file set that will be signed — is the vendor MSA (master services agreement — the frame contract vendors hang order forms on). Clause 14.2: for-cause after five (5) calendar days of written notice that “Customer is in material breach.”

Same 5-day clock for unpaid invoices and a multi-week implementation miss. Clause 14.3: Vendor may treat any material breach as incurable at Vendor’s reasonable determination and terminate immediately. No diligent-cure extension. AE Slack: “You have a cure period.” Hidden risk: the 5-day blob. Signature is Friday.

English common law does not give you a cure period. ContractKen (21 September 2026): no general duty to give notice and a chance to cure before a repudiatory termination; a party entitled to terminate at common law may do so immediately. Contractual cure still binds. A five-day empty notice can still make you the breacher.

Disclaimer: Checkory provides AI support, not legal advice. Consult a qualified lawyer for binding decisions.

What does the written notice have to name before the clock starts?

Circle clause 14.2. A notice that only says “Customer is in material breach” may never start the clock. Log the section number, the facts — which invoice, which SLA miss, which date — and what a sufficient cure looks like, or write “empty notice — fail.”

Do: demand clause, facts, and the cure required, with a calendar date. Don’t: assume an empty “you are in breach” letter started the clock. Typical mistake: treating “written notice” as enough when the words never name what to fix. Rob Melton: that line may fail to trigger the period. Nath (16 July 2026): skip a precise notice and you become the breacher. Womble Bond Dickinson: cite the clause; start the clock; state the cure. Method / deemed receipt: notices / deemed receipt. FAR 49.607 is US colour — specify the failure; 10 days after receipt, not an England-and-Wales minimum.

Why does one 5-day clock fail?

Circle the same five calendar days for everything. Drafting convention — not a survey — is about 10–15 days for payment and 30 days general. Nash’s paper inverts that into five days for invoices and implementation alike. Log two numbers, or “one 5-day blob — redline.”

Do: split a short clock for an undisputed invoice from a longer clock for performance. Don’t: let a payment window run on a bona fide disputed line. Bindlegal (16 June 2026): 30 general, 10–15 payment, immediate confidentiality or data — convention, not a survey. Pactolane: 30 days except 10 for an undisputed amount. In practice, five calendar days on an implementation miss is a payment window wearing a performance hat.

What belongs on an incurable list — not “any material breach”?

Circle clause 14.3: Vendor may treat any material breach as incurable at Vendor’s reasonable determination. That is a delete-key, not a list. Fraud, wilful IP theft, and a real data incident can be named as immediate. A late invoice is not.

Do: require named sections — confidentiality, data security, fraud / wilful misconduct. Don’t: leave “any material breach” to Vendor’s reasonable determination. Law Insider shows named confidentiality as immediate and sole-discretion “not curable” — hunt the second. Over-wide “any material breach” is a unilateral walk, not a list.

Is a five-day window a diligent-cure, or theatre you cannot actually fix?

Nash has no extra time if a genuine fix has started. A five-day cure for a complex deliverable may be too short to be meaningful. Log “theatre window — fail,” or demand commence-within-the-period plus a hard cap.

Do: demand 10 days undisputed money / 30 days performance / commence-within-30 + cap (60). Don’t: rely on an oral “take another week.” For example, a 30-day implementation miss cannot be diagnosed, patched, and re-tested in five calendar days. Pactolane: if non-monetary cannot finish in 30, extend while they began in the period and pursue with diligence, up to 60. Theatre is not fairness.

Is this convenience versus cause, or the claims-bar years?

This hunt is days to fix a named breach. If the fight is whether they can walk for convenience versus for cause, that is a different hunt. If the fight is how many years you have to bring a claim, that is a different hunt. Stay on the cure clock.

Do: one sentence then return. Don’t: spend Friday on a walk-right table or a twelve-month invoice bar. Convenience versus cause as a pair: termination for convenience vs cause. Years to sue: contractual limitation period / late claims bar. UKSC Providence [2026] UKSC 1 (15 January 2026) is JCT sequence, not this MSA. Steal the follow-the-steps warning — not a SaaS holding.

When to lengthen, split, or walk?

Lengthen performance to 30 days and require named notice content. Split 10 days undisputed money from 30 days performance, plus a diligent-cure cap. Walk — do not sign Friday — if empty “you are in material breach” plus a 5-day blob plus Vendor incurable discretion remain as a package.

Success bar: a one-page log plus one Friday pause sentence. “We have a cure period” is not that sentence if the notice is empty, the clock is 5 days for everything, and incurable is Vendor’s call. Workflow: named notice → split clocks → named incurable list → diligent-cure vs theatre → not B31 / not B71 → lengthen / split / walk.

Optional: upload the same PDF to document analysis for a first-pass — first machine pass extracting clauses before a human reads every page. A human still opens clause 14. Verify every High flag — high severity. Escalate to counsel — a qualified lawyer, not the chatbot.