The wrong termination date that still worked

The signal

A notice can fail even when everyone knows what the sender was trying to do. Occasionally, an obvious error is cured by context—but relying on rescue-by-interpretation turns a controlled exit into litigation.

Notice clauses combine several failure points: the triggering right, deadline, required wording, recipient, address, delivery method and evidence of receipt. A team that checks only the date can still miss the mechanism.

What happened

Court-record facts. A tenant held two ten-year commercial leases. Each lease gave the tenant one right to end the lease by serving at least six months’ written notice that expired on the third anniversary of the term commencement date.

The third anniversary was 13 January 1995. The tenant served notices more than six months in advance and expressly invoked the relevant break clause, but said that the leases would end on 12 January 1995—one day early.

The landlord argued that the wrong date made the notices ineffective. The Court of Appeal agreed. The House of Lords had to decide whether the notices, interpreted in their contractual setting, nevertheless communicated an effective exercise of the break right.

What the court decided

Holding. By a three-to-two majority, the House of Lords allowed the tenant’s appeal. A reasonable recipient who knew the leases and the only available break date would have understood that the tenant intended to end the leases on the third anniversary and had misdescribed that date by one day. The notices were therefore effective.

The majority’s test was objective: did the notice, read against the relevant context, leave a reasonable recipient in no reasonable doubt about how and when it was intended to operate? It was not enough that the sender privately intended to comply.

The decision did not abolish strict compliance. The speeches distinguished requirements about what a notice must communicate from other specified conditions. Lord Hoffmann’s example was direct: if the clause required blue paper, pink paper would not comply however clear the termination intention. The dissenting judges would have held the notices ineffective, underlining how contestable the boundary was.

Key takeaways

Paraveilux interpretation — not a court finding.

• A notice is an operational event with contractual dependencies, not just a letter.
• Context may clarify an obvious misdescription, but it cannot be assumed to repair the wrong recipient, method, lead time or other formal condition.
• A court’s ability to understand a mistake does not make the dispute inexpensive or predictable.
• Notice controls should verify both the message conveyed and every procedural condition attached to the right.

The hidden variable

Paraveilux interpretation — not a court finding. The hidden variable was whether the error created real ambiguity or merely used the wrong label for the only possible contractual event.

That distinction is difficult to operationalise after a notice has gone out. The sender tends to see an obvious slip; the recipient may see an attempted exercise of a valuable right on a date the contract does not permit. Once positions diverge, renewal exposure, premises planning, replacement suppliers or customer commitments may all depend on an interpretation fight.

The safer risk lens is therefore not “will a court forgive this?” It is “can the business prove, before release, that the notice matches the operative contract version and delivery rules?”

Questions for an owner

Practical questions, not prescriptions.

• Is there one verified record of each notice window, trigger and last safe service date?
• Who checks the contract version, amendments and date definitions before a notice leaves?
• Are named recipients, addresses and permitted delivery methods still current?
• Does the notice identify both the contractual right and the correct effective date?
• What independent evidence proves dispatch, delivery and receipt?
• Which operations, finance and customer commitments depend on the notice being effective?

Related reading

Hidden contract dependencies provides a way to map notice mechanics before they become urgent. Business dispute warning signals covers the evidence and escalation signals that appear when the parties read the same record differently.

Evidence boundary

Source transparency. The business roles above are anonymised. The source decision is Mannai Investment Co Ltd v Eagle Star Life Assurance Co Ltd [1997] UKHL 19; [1997] AC 749, decided 21 May 1997. The official judgment spans linked Parliament pages. The factual account and holding above reflect the majority result; the dissent is identified because it marks a material boundary. The Paraveilux interpretation and practical questions are not court findings.

Limitations

This case concerned particular break clauses in English commercial leases. It does not establish that an incorrect termination date, a defective notice or substantial non-compliance will generally be cured. Different clauses, statutory notices, jurisdictions and facts may demand different treatment. This brief does not assess later authorities or statutory changes and should not be used as a currentness opinion as at 13 August 2026.

This brief is general risk education, not legal advice or an outcome prediction.