Blanket notification

Category: Claims and policy principles · Reviewed by the Apex broking team · Last reviewed 2026-08-22 · ~4 min read

Definition

A blanket notification — sometimes called a generic or “hornet’s nest” notification — is a notification of circumstances that identifies a systemic problem rather than a specific dispute with a specific client. Typical triggers are a defective piece of advice repeated across many engagements, a software or process failure affecting a batch of files, a departing fee earner whose work is being reviewed, or a regulatory finding that calls a whole line of work into question. The purpose is to bring every claim that later emerges from that root cause back into the policy year in which the notification was accepted.

Why the mechanism exists

Claims-made policies respond to claims first made during the period. Almost all of them also contain a notification of circumstances provision, under which circumstances that may give rise to a claim can be notified during the period, and any claim later arising from those circumstances is then deemed to have been made in that period. Without that provision an insured who saw trouble coming would be caught between a policy that had expired and a renewal that excluded known circumstances. The deeming provision is what makes a blanket notification worth making.

What makes a notification effective

Effectiveness is a matter of the policy wording, and the wording varies more than most people expect. Some require circumstances “likely to” give rise to a claim; others accept circumstances that “may”; others require awareness of a specific act, error or omission. The leading English authority on what a notification has to do is HLB Kidsons (a firm) v Lloyd’s Underwriters [2008] EWCA Civ 1206, in which the Court of Appeal considered whether communications to underwriters amounted to an effective notification of circumstances under a claims-made professional indemnity policy. The practical lesson from the case is that the notification must actually convey the circumstances relied on, in a way that satisfies the policy’s own requirements as to content, recipient and timing.

How a blanket notification is usually framed

A workable blanket notification does four things. It describes the root cause with enough specificity that the class can be identified later. It states the population potentially affected, even approximately, and how it was scoped. It explains why claims may follow. And it is sent to the address and in the manner the policy specifies, within the period. A notification that says only “we are reviewing our files and may have made errors” risks failing on the first two points, which is where later arguments about whether a particular claim “arises from” the notified circumstances start.

The trade-off at renewal

A blanket notification is not free. Once made, the circumstances are known, and known circumstances are almost universally excluded from the following year’s cover and must be disclosed as part of a fair presentation of the risk. Renewal terms may harden, an aggregate deductible or a specific exclusion may be imposed, and the market available to the firm may narrow. The right comparison is not notify-versus-say-nothing; it is notify now into a policy that is on risk, or leave the class uncovered and face a disclosure obligation anyway.

Aggregation and the limit

Locking a class into one policy year cuts both ways. If the wording aggregates claims arising from one originating cause or one series of related acts, the whole class may be subject to a single limit of indemnity and a single excess. That can be a very good outcome for the excess and a very poor one for the limit. Whether the aggregation language and the notification language are consistent is one of the things worth checking before the notification is drafted rather than after.

Why it matters

Blanket notification is one of the few genuinely strategic decisions a policyholder makes about a claims-made policy, and it is usually made under time pressure at the end of a policy year. The parts that reward preparation are knowing what the notification clause actually requires, knowing how the aggregation clause will treat the class, and having a documented basis for the scope described. Notifications are best drafted with the broker and, where the exposure is significant, with coverage counsel.

Frequently asked questions

Is a blanket notification the same as making a claim?

No. It is a notification of circumstances that may give rise to claims. No claim has yet been made, and no indemnity is yet payable. Its effect is to fix the policy year that will respond if claims do follow, under the policy’s deeming provision.

Will a blanket notification affect our renewal?

It is likely to. Once circumstances are notified they are known, and known circumstances are normally excluded from the next policy and must be disclosed as part of a fair presentation of the risk. That is a reason to plan the notification carefully, not a reason to avoid making one.

How specific does a blanket notification need to be?

Specific enough to identify the root cause and the class of matters affected, and compliant with whatever the policy requires as to content, recipient and timing. HLB Kidsons v Lloyd’s Underwriters [2008] EWCA Civ 1206 is the usual starting point for what an effective notification has to convey.

Related entries

• Circumstance notification
• Definition of circumstance
• Known circumstances exclusion
• Notification deadline
• Claims-made-and-reported trigger

This entry is part of the Apex Insurance Wiki. Last reviewed 2026-08-22. Next review: 2027-02-22. It is insurance information, not legal advice, and it states the position as at August 2026.

Apex Insurance Brokers Limited is authorised and regulated by the Financial Conduct Authority (FRN 724952). This page is general information, not advice on a specific policy.