One claim or many? How aggregation decides what your PI limit really covers

Reviewed by Apex Insurance Brokers · Published 2026-08-24

Most conversations about professional indemnity insurance stop at the headline limit. A firm decides it wants £5m or £10m of cover, buys it, and files the schedule away. But the limit on the schedule is only half the story. The other half is a quieter clause, usually a few lines long, that tells you how many times that limit has to stretch if things go wrong more than once. That clause is the aggregation provision, and for firms carrying real exposure it is one of the most consequential sentences in the whole policy.

What aggregation actually does

Professional indemnity limits are usually written in one of two ways. An “each and every claim” limit provides the full sum insured for every separate claim, however many there are in the policy year. An “in the aggregate” limit provides that sum once, as a ceiling for everything combined across the year. Many firms actually hold a hybrid: a full each-and-every limit for most work, but an aggregate cap on certain heads of exposure — asbestos, pollution, or the excess layers of a programme, which are very commonly written in the aggregate even where the primary layer is each-and-every.

Aggregation is the mechanism that decides how individual claims are grouped before those limits are applied. If three claims are treated as three claims, an each-and-every limit answers each of them in full. If the wording pulls those same three claims together into one, they share a single limit — and they also attract a single excess or deductible rather than three. Aggregation therefore cuts both ways. Group claims together and you might exhaust one limit faster; keep them apart and you might pay your excess several times over. Which outcome helps you depends entirely on the numbers, and that is exactly why the wording matters.

The wording: what “related” has to mean

The clearest published example of an aggregation clause in the UK is the one in the Solicitors Regulation Authority’s Minimum Terms and Conditions, which every solicitors’ policy must contain. It groups together all claims arising from: one act or omission; one series of related acts or omissions; the same act or omission in a series of related matters or transactions; and similar acts or omissions in a series of related matters or transactions. Those four limbs are worth reading slowly, because the whole argument in a disputed claim tends to turn on which of them applies and on the meaning of two small words — “related” and “similar”.

If your firm is not a solicitors’ practice, you are not bound by those Minimum Terms — but you almost certainly have an aggregation clause of your own, and it may be drafted quite differently. Surveyors, architects, engineers, accountants and consultants sit under a patchwork of regulator requirements and open-market wordings, and the aggregating language varies from “one originating cause” or “one event” at one end to the solicitors’ “series of related matters” formula at the other. A single “originating cause” wording aggregates broadly, which can be a blessing when your worry is paying multiple excesses and a curse when your worry is exhausting a single limit. You cannot know which risk you are carrying until you have read your own clause.

What the courts have said

Two decisions frame how these clauses are read in practice. In AIG Europe Ltd v Woodman [2017] UKSC 18, the Supreme Court considered the solicitors’ “series of related matters or transactions” limb in the context of failed overseas property developments. The court declined to read in any rigid test — it rejected the idea that the transactions had to be dependent on one another — and held instead that whether matters are “related” is a fact-sensitive question, judged objectively, that asks whether the transactions in some way fit together. On the facts, claims by investors in the same development were related and aggregated; claims spanning two entirely separate developments were not. The lesson is that there is no bright line: the same clause can group claims in one scenario and separate them in another.

The counterpoint came in Baines v Dixon Coles & Gill [2021] EWCA Civ 1211. A partner in a solicitors’ firm had dishonestly misappropriated client money over a long period, and the insurer argued that the whole run of thefts was one series of related acts, so that the many victims should share a single limit. The Court of Appeal disagreed. An extended course of dishonest conduct by the same person was not enough, on its own, to make the separate thefts a single aggregated claim; each defrauded client kept a separate claim and a separate limit. For the firm and its clients that meant more cover in total, not less — a reminder that aggregation is not simply an insurer’s tool for capping payouts. It is a neutral mechanism whose effect depends on where the money falls.

Why it bites harder on a layered programme

For a sole practitioner with a single each-and-every limit, aggregation is often academic. For a larger firm carrying a primary layer and one or more excess layers stacked above it — a programme — it is anything but. Excess layers usually follow the form of the primary policy but are frequently written in the aggregate, and they only respond once the layer beneath is exhausted. Whether a cluster of related claims aggregates therefore decides which layer is on risk. Treated as many separate claims, they might each be absorbed within the primary layer, and the excess insurers never engage. Treated as one large aggregated claim, they can burn through the primary layer and reach into the excess tower, drawing in insurers who priced their layer on the assumption that they would rarely be touched.

The same logic runs through any self-insured retention or sizeable deductible the firm has agreed. A single aggregated claim means the firm carries its deductible once; a dozen unrelated claims mean it carries that cost a dozen times. Where a firm does work that naturally produces repeated, similar exposures — the same advice given to many clients, the same drafting used across a suite of transactions, the same survey methodology applied to a portfolio — the aggregation wording is doing quiet but heavy lifting on the firm’s true net exposure. Longer liability tails make this more pressing still: where claims can surface many years after the work, and several can flow from a single project, the question of whether they aggregate is one a firm may be living with for a long time.

What to check before you renew

Start by reading the aggregation clause in your current wording and identifying which formula it uses — “one originating cause”, “one event”, “a series of related acts or omissions”, or something else — because that phrase, not the headline limit, describes how your cover behaves in a bad year. Check whether your limit is each-and-every or in the aggregate, and confirm the basis of each excess layer, since a primary layer and its excess layers do not have to match. Make sure the aggregation language is consistent up the tower; a mismatch between how the primary and excess layers group claims can leave a gap exactly when you are relying on the higher layers. And test the wording against your own worst realistic scenario — the systemic error repeated across many files, the single project that spawns several claimants — rather than against a comfortable one-off. If you cannot say with confidence how your programme would respond to that scenario, that is the conversation to have with your broker now, while the wording can still be negotiated, rather than after a notification when it cannot.

Frequently asked questions

Does aggregation always favour the insurer?

No. It is a neutral mechanism. Grouping claims together can exhaust a single limit faster, which tends to help the insurer; but keeping them separate means the firm pays its excess or deductible several times over, which tends to help the insurer too. Whether a given outcome helps you or your insurer depends on the size and number of the claims and on how your limit and excess are structured. In Baines v Dixon Coles & Gill, the refusal to aggregate produced more cover for the firm’s clients, not less.

We are not solicitors — do these cases apply to us?

The cases interpret specific solicitors’ wording, so they are not automatically binding on a differently drafted policy. But they show how courts approach aggregation generally — as a fact-sensitive question about whether events fit together — and that reasoning informs how other wordings are read. The practical point is the same for every profession: read your own aggregation clause, because its language, not the solicitors’ version, governs your cover.

Can we change the aggregation wording?

Where a policy is written on open-market terms rather than a mandatory regulator wording, the aggregation clause is a term like any other and can be discussed at placement. Even where the core wording is fixed, the way it interacts with your limit structure, excess layers and deductible is something a broker can help you shape. The time to do it is before binding, when there is still room to negotiate.

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