How to Review a No-Waiver Clause Against Waiver by Conduct

Arden, Ops at a 20-person UK B2B SaaS, is about to treat “No failure or delay… shall constitute a waiver” as enough while Finance has accepted late invoices three months running. Knowing how to review a no-waiver clause against waiver by conduct is a 20-minute hunt: separate it from no-oral-modification → require writing, signature, and a specific waiver covering delay and partial performance → lock one breach ≠ future breaches plus cumulative remedies → treat conduct and election as still live with a reservation habit → add self-referential protection → keep / tighten / train ops.

September 2026. English law; courts of England and Wales. The packet — the exact file set that will govern the vendor — is an MSA — a master services agreement, the umbrella commercial contract. Clause 17 only names failure or delay. No writing or signature formality. No specific identified waiver. No one-breach≠future line. No cumulative remedies. No self-referential protection. AE Slack: “boilerplate — we’re protected.” Ops has never sent a dated reservation-of-rights note while Finance kept taking late cash and charging late fees.

A delay-only no-waiver line does not reliably stop waiver by positive conduct — and a ritual “all rights reserved” sentence may not cure accepting late payment as if punctual. Pinsent Masons on Tele2 (commentary, live 2026-09-26): continued performance without protest can affirm despite delay-focused wording. Mayer Brown on Lombard v Skyjets (commentary, live 2026-09-26): accepting late payment, offering more time, and charging late fees can waive that default; a failure-or-delay clause did not cover positive acts.

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

How do you separate no-waiver from no-oral-modification?

No. No-waiver fights accidental loss of an existing right through delay or conduct. No-oral-modification (NOM) fights informal changes to the bargain. Do: open the no-waiver heading when Finance is soft on late payment. Don’t: fight Slack “yes” price changes under this clause — that is a different hunt.

In practice, Rock Advertising Ltd v MWB (UK Supreme Court case page, live 2026-09-26) is the official NOM contrast: oral variations that miss required writing and signatures are generally invalid. If the fight is how variations must be signed, see how to review a no-oral-modification clause. Stay on waiver by conduct. This is not a moral-rights waiver in a commissioning agreement.

What does writing, signature, and late-payment coverage require?

Often not. Do: require any waiver to be in writing, signed, and specific to the identified right or breach, and state that delay, partial performance, and positive conduct do not waive. Don’t: treat Arden’s delay-only sentence as enough after Finance accepted late invoices and charged late fees.

For example, AO Shearman (live 2026-09-26) stresses writing-and-execution formality and an estoppel bar that needs more than the informal waiver itself. CMS on no-waiver effectiveness (live 2026-09-26): positive late-payment conduct sat outside a failure-or-delay shield. Circle “failure or delay.” Log “delay-only — fail.” Lender-case colour is not a second statute — put the fences in Arden’s MSA.

Review one-breach-not-future and cumulative remedies lines

It should not — if the paper says so. Do: add that a waiver of one breach is not a waiver of any other or subsequent breach, and that rights and remedies are cumulative. Don’t: let three soft months rewrite payment terms by vibes.

Typical mistake: Finance “helps once,” AE treats the term as permanently soft, and the next late invoice arrives with no paper trail that prior forbearance was limited. Gateley (live 2026-09-26) frames no-waiver as a holding pattern, not an indefinite stay — act promptly and keep later breaches alive on the page. Circle silence on future breaches.

Why does waiver by conduct still bite — and when to reserve rights?

Yes. Do: send a prompt, specific reservation-of-rights note naming the contract, the facts, and the rights preserved, then keep later conduct consistent. Don’t: rely on Clause 17 alone or on a ritual “all rights reserved” footer while taking late cash.

Travers Smith’s Don’t waive goodbye to your rights PDF (live 2026-09-26): do not lean on no-waiver without watching post-breach conduct; reserve promptly. Latham on URE Energy (January 2026): election needs actual awareness of the facts and of the right; estoppel can still arise from unequivocal conduct plus detrimental reliance. Lexology on reservation of rights (live 2026-09-26) (live 2026-09-26): identify specific rights, reserve quickly, and remember a reservation only holds the ring briefly. For Arden: open the payment emails, draft one dated note, and stop treating late fees as proof the right survived.

Checklist: self-referential protection against silence

That is the argument you want to close on the page. Do: add self-referential protection — no waiver of this clause is effective unless in writing and signed. Don’t: assume silence cannot be spun as waiving the formalities.

AO Shearman’s formality discussion (linked above) treats writing requirements seriously, with estoppel as a narrow exception that needs more than the informal act itself. Stephenson Harwood (live 2026-09-26) still warns that conduct signalling the contract is continuing can create estoppel risk. Circle a Clause 17 that never protects itself. Log “self-ref missing — fail.

When to keep, tighten, or train ops?

Keep only if formality, conduct coverage, future-breach language, cumulative remedies, and self-referential protection already pass — and ops has a reservation habit. Tighten delay-only wording into writing / signed / specific coverage of positive conduct, add future-breach and cumulative lines, and protect the clause itself. Train ops — and escalate to counsel — a qualified lawyer — if a late-payment pattern already sits on the file — before relying on Clause 17 alone.

Before FAQ, the success bar is a one-page keep / tighten / train-ops checklist you can fill today (no-waiver ≠ NOM? covers delay and positive conduct? writing + signed + specific? one breach ≠ future + cumulative? reservation habit? self-ref present?). Verify one sentence that would pause relying on Clause 17 alone after late-payment acceptance. Escalate to counsel — a qualified lawyer — if Finance still takes late cash while AE says “boilerplate”; keep the packet unsigned until the log passes.

Optional first-pass: upload the same MSA to document analysis and get the file back with flags on no-waiver / failure or delay language — then a human still opens Clause 17 and the payment thread. Checkory is not a law firm and does not replace counsel — a qualified lawyer.