How to Review Failure-to-Notify Prejudice on a Third-Party Claim

Friday 9 October 2026 is the signature date. Gwenda reviews a 15-person UK brand of linen oven gloves from a Fishguard workshop. English law. Courts of England and Wales.

The packet — the papers you will actually sign — is a fulfilment MSA — a master services agreement — with Preseli Pack Ltd in Haverfordwest.

Two notice sentences sit on one page.

For example, a Bath retailer wrote on Tuesday 22 September 2026 about stained gloves. They say about £3,260. That figure is not a court finding, and it is not prejudice.

On Friday 2 October 2026 at 18:14 UK time a coordinator emailed the Haverfordwest address: there is a retailer complaint, and details will follow. No claimant. No facts. No estimate.

Slack on 6 October 2026 is the pressure. It says a week late is already killing the indemnity, Friday counts as Friday, the amount is unnecessary, and this page is defence control and the whole indemnity.

In practice the Friday send is not the receipt day. The typical mistake is reading the saver as if the unless-sentence had already won.

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

What does a prompt written notice have to include?

Clause 12.3 asks for the claim, the facts then known, and a good-faith estimate, so far as then known. A heads-up with none of the three is not that notice. Do not treat the Friday email as done.

Towergate's SPA notice clause, in the 2020 judgment, required the details and circumstances and an estimate in good faith. Share-sale colour only.

Males LJ's point, as FromCounsel records it, is that extra technicality merely introduces a trap. Guildhall's 23 May 2024 note says the same.

Check the log: Friday email is a heads-up, missing claim, facts, and estimate. £3,260 is not the notice and not prejudice. Dodika does not let you skip three named contents.

How do you review a late notice that claims prejudice?

Clause 12.3 says a failure to give prompt notice does not relieve the Supplier except to the extent of actual prejudice.

A December 2023 note from Torys says a failure to notify should not reduce the indemnity unless the delay causes material prejudice, and then only to that extent. Canadian drafting, not this email.

The saver is printed. Nobody has written what Preseli Pack lost because the email was late.

Do not treat £3,260 as that loss. Prejudice is not presumed. An insurer's notice-prejudice rule is a different contract.

The result: “12.3 cuts cover only to the extent of actual prejudice. Prejudice is not shown.”

When to treat “shall not be liable unless” as a wipe?

Clause 12.4 says the Supplier shall not be liable unless written notice is given as soon as possible and in any event within seven Business Days of becoming aware. That is the red flag. It can wipe cover where no prejudice is shown.

Heritage is the contrast, not the calendar. In the Court of Appeal judgment, “shall not apply unless” was the condition-precedent shape. A bare notice duty beside it was not. One Essex Court points at that analysis.

Towergate is the other edge. Addleshaw Goddard reports a dual condition: “as soon as possible and in any event” before a long-stop. Notice before the anniversary still failed. Appleby calls “as soon as possible” an imperative even beside a long-stop. Do not slide that diary onto Fishguard.

Count this packet. Aware Tuesday 22 September 2026. Seven Business Days land on Thursday 1 October 2026. A log, not a ruling. Neither case has decided Preseli Pack.

Which day does the notices block treat as receipt?

Clause 19.2 is the clock. Before 17:00 UK time on a Business Day, that day. At or after 17:00, or not a Business Day, 09:00 UK time the next Business Day. Slack's Friday is not that sentence.

The email left at 18:14 on Friday 2 October 2026. Under 19.2 it is deemed received at 09:00 on Monday 5 October 2026. The seventh Business Day was Thursday 1 October. Neither date is a ruling.

In Ener-G, the notices clause deemed a delivery outside 09:00 to 17:00 received at 09:00 the next Business Day. Colour only, not clause 19.2.

If the fight is whether email is allowed, or the address is stale, stop and use the notices and deemed-receipt guide. This review only asks whether 12.4 and 19.2 name the same day. They do not name Slack's Friday.

Workflow: letter received → copy 12.3 and 12.4 → apply 19.2 → mark prejudice shown or not → keep the saver, strike the condition, or walk. Verify the 17:00 cutoff in the signed copy.

Is this defence control, or the whole indemnity?

No. This page is the notice procedure. Who runs the defence, and who may settle, is a different hunt. If Slack calls 12.3 defence control, one sentence to the defence-control and settlement guide, then stop.

What the indemnity covers is the indemnity checklist.

An insurer's condition precedent is not this sentence. If Slack says wilful default, stop.

Should you keep the saver, strike the condition, or walk?

The sentence that pauses Friday is “shall not be liable unless,” beside a saver, while the only email is a Friday heads-up deemed received on Monday.

If a harmless delay should cut cover only for actual prejudice, keep 12.3 and strike 12.4. The unless-words are already there.

If Friday's yes needs that forfeiture, walk. Do not sign on a week that Slack already calls fatal.

A later note can still carry the claim, the facts, and a good-faith estimate to the Haverfordwest address. It does not repair 12.4.

Optional pass: upload the same file. Flags come back on that file. It is not a chat. It is not LegalZoom. It is not a Word add-on. It is not a CLM. counsel — a qualified lawyer — still decides if the two sentences collide. The checklist below is the pass before that call.