If you read only one section of your professional indemnity policy this year, make it the aggregation clause. It is short, often only two or three sentences. It determines whether a cluster of related claims — twenty conveyances, five hundred mis-sold pension transfers, a thousand affected investors in a single failed scheme — share one limit of indemnity and one excess, or whether each of them is treated as its own claim with its own excess.
The difference between those two outcomes is sometimes the difference between a solvent firm and an insolvent one. A £2 million policy with a £25,000 excess looks like a £2 million policy if twenty linked claims aggregate into one. The same policy looks like a £500,000 policy with £500,000 of self-insured excess if those twenty claims each stand alone. The wording that decides which it is — “originating cause”, “matter”, “transaction”, “series of related matters or transactions” — is the most disputed wording in UK PI insurance and has produced more reported judgments than any other clause type bar the duty of fair presentation.
This guide is the deepest single treatment of aggregation we are aware of on the UK web. It is written for compliance officers, claims technicians, COLPs, COFAs, managing partners, FDs and risk leads who need to understand what aggregation actually does in their policy, what the cases say, and what to do about it at proposal, notification, claim and renewal. Twelve linked spoke articles take individual cases, individual sector wordings, and individual scenarios in much greater depth. The article you are reading is the map.
Every PI policy carries a limit of indemnity. Most also carry an excess (sometimes called a deductible or retention). The limit says how much the insurer will pay; the excess says how much you pay before the insurer steps in. Both are stated “for each claim”, “for each occurrence” or “in the aggregate”. So far, so simple.
The complication is that “claim” is a defined term. The definition usually treats a number of related claims as one claim for the purposes of the policy. That mechanism — taking claims that the world treats as separate and bundling them into one for insurance purposes — is aggregation. The contractual hook is the aggregation clause (sometimes called the series clause because the most common test is whether the underlying matters form a “series”).
Aggregation cuts two ways.
When you have a single excess of £25,000 and ten claims aggregate, you pay one £25,000 excess across the cluster, not ten. That is helpful. When you have a £2 million limit and twenty claims aggregate, you have £2 million of cover for the entire cluster, not £40 million. That is harmful. Insurers and policyholders therefore have systematically opposed interests on aggregation, which is why aggregation litigation is plentiful and the wording is fought over at every renewal.
Aggregation is not the same as batch cover in product liability, not the same as a cause-based attachment in reinsurance treaties, and not the same as the discovery mechanism in claims-made policies. It is its own creature, governed in the UK by ordinary contract construction principles refined through forty years of insurance case law.
A second piece of vocabulary that matters: aggregation clauses do not all aggregate by reference to the same trigger. The market uses four standard triggers, and the trigger your insurer chose will decide most outcomes before any judge ever has to construe the wording. We turn to those four triggers next.
Most UK PI wordings use one of four formulations to decide when separate claims aggregate. Each represents a different bargain between insurer and insured. Each has been litigated repeatedly. The drafting reads, in market shorthand:
Trigger 1 — “Any one occurrence” or “same act or omission”. The narrowest. Claims aggregate only if they arise from precisely the same act or precisely the same omission by the insured. If a solicitor releases client money in breach of trust on twenty different files in twenty different transactions, they have committed twenty omissions — even if the omissions are identical in character — and aggregation under this trigger fails.
Trigger 2 — “Originating cause” or “common cause”. Wider. Claims aggregate where they share a single originating cause. The leading case is Caudle v Sharp [1995] CLC 1148 in the marine context, and Lloyds TSB v Lloyds Bank Group Insurance [2003] UKHL 48 in the PI context. “Originating cause” reaches back to the root of the problem — the systemic flaw, the misunderstanding of regulation, the bad procedure — rather than the individual file-level error.
Trigger 3 — “Matter” or “transaction”. Aggregates claims arising from a single matter or transaction. Looks at the unit of work, not the cause of the loss. Two claims arising from the same transaction aggregate; two claims arising from different transactions do not, even if they share a common cause.
Trigger 4 — “Series of related matters or transactions”. The standard SRA Minimum Terms formulation and the most common wording across UK PI generally. This is the test the Supreme Court construed in AIG v Woodman [2017] UKSC 18. It aggregates claims arising from a series of matters or transactions that are related in some real way. The breadth of the test is determined by what “related” means — and that is exactly what Woodman decided.
You will sometimes see hybrid drafting that lists more than one trigger, with aggregation deemed to occur if any of them applies. The SRA Minimum Terms, for example, aggregate under clause 2.5(a) by reference to (i) one act or omission, (ii) one series of related acts or omissions, (iii) the same act or omission in a series of related matters or transactions, and (iv) similar acts or omissions in a series of related matters or transactions. That is a four-rung ladder, and an insurer trying to bring claims under one limit only needs to win on one rung.
Our spoke article on “originating cause” versus “matter” explores the wording battles in much more depth. Our spoke on “same act or omission” explains why insurers virtually never accept that wording at renewal in 2026.
Aggregation is not, primarily, a fairness clause. It is a portfolio control. Insurers price PI to a probable maximum loss (“PML”) for the firm they are underwriting. The PML calculation depends on assumptions about whether systemic problems will exhaust the limit once or many times.
If aggregation is wide — “series of related matters or transactions” — then a systemic problem at a regulated firm hits the limit once. The insurer’s worst case is one limit per occurrence-cluster. The reinsurer behind the insurer can rely on the same. That makes the risk underwritable.
If aggregation is narrow — “same act or omission” only — then a systemic problem at a firm could hit the limit dozens or hundreds of times. The insurer’s worst case becomes the limit multiplied by the number of clients affected. That is uninsurable for most professional firms without a vastly different premium and very different reinsurance support.
This is why brokers asking for narrow aggregation triggers usually get nowhere. The market is structured around the wide trigger. What is achievable is clarity at the wording level (so you know what you have bought), wording add-ons for specific exposures (cyber sub-limits, conveyancing sub-limits, mortgage fraud sub-limits) and higher limits to compensate for the aggregating effect. We unpack what you can and cannot achieve at renewal in Spoke 12.
For a buyer, aggregation matters in three ways.
Limit exhaustion. A series of related claims aggregating into one consumes one limit. If the limit is too small for the cluster, the firm is personally liable for the balance. For solicitors, this is the SRA Minimum Terms problem: the standard £2 million limit (£3 million for incorporated firms) was set in 2000 and has not moved. A multi-investor scheme failure, conveyancing fraud sweep or trust account breach can easily run to £20 million in losses across a cluster. The partners are personally on the hook for £18 million.
Excess multiplication or unification. A wider aggregation clause means one excess across many claims. A narrower aggregation clause means one excess per claim. For a firm with a £25,000 excess, the difference between paying one £25,000 excess on a 50-claim cluster and paying fifty is £1.225 million. In a regulated firm with regulatory capital floors, excess multiplication can be solvency-threatening.
Personal liability of partners. For unincorporated partnerships, exhausted limits are partner liability. The decision in AIG v Woodman meant that 214 investors aggregated into two clusters of c. £5 million each, which the firm’s £3 million per claim limit could not satisfy. Partners stood behind that gap. Aggregation analysis is therefore not abstract — it is the route by which an insurance question becomes a personal-bankruptcy question.
Run-off cover and aggregation. Aggregation interacts viciously with run-off. Run-off cover, particularly the mandatory six-year cover under the SRA Minimum Terms, typically has a single aggregate limit that erodes over the run-off period. If a wide aggregation clause groups all post-cessation claims into a small number of large notifications, the run-off limit can be exhausted in years one or two of six. Our solicitors’ run-off cover deep dive explores this in detail.
We deal with Woodman fully in Spoke 1. What follows is the short version every PI buyer should be able to give from memory.
Facts. A firm of solicitors, ILP, acted on two property development schemes (Turkey and Morocco). Investor money was held in escrow and was supposed to be released only when adequate security had been taken over the development sites. The firm released money without adequate security. Both schemes failed. 214 investors lost about £10 million between them. ILP’s £3 million per-claim PI policy contained the SRA-style “series of related matters or transactions” aggregation language. AIG argued all 214 investors aggregated into one claim with one £3 million limit. The investors said claims were either separate or grouped only by scheme.
Decision. The Supreme Court adopted an open-textured test: matters or transactions are “related” if, looking at things realistically and in the round, an objective observer would describe them as connected in some real way. The Court rejected the Court of Appeal’s “intrinsic connection” test as too narrow and rejected any test that required the transactions to be conditional or dependent on each other. On the facts the Turkey and Morocco schemes were not related to each other (different sites, different investor pools, different trust deeds) but the investors within each scheme were related.
The three-step test from Woodman, distilled. Apply each in order. If the answer to any of them is no, aggregation under “series of related matters or transactions” fails.
Are there matters or transactions at all? Identify the unit of work that generated each claim. Aggregation needs more than one claim, and each claim has to be attributable to a matter or transaction.
Do those matters or transactions form a series? A “series” requires more than one and requires some connecting thread. The thread can be temporal, contractual, structural or transactional. It need not be intrinsic.
Is the series “related” in a real way? This is the open-textured question. The test is objective, realistic and in-the-round. Common scheme, common fund, common security failure, common investor pool, common counterparty, common documentation will usually satisfy it. Common adviser, common species of error, common professional discipline will usually not.
The three-step test now governs aggregation under SRA Minimum Terms wording and travels — by analogy — to virtually all UK PI wordings containing “series of related matters or transactions” language.
The diagram below applies the Woodman three-step test to a real-world fact pattern. Print it. Stick it above your claims technician’s desk. It will not give you a determinative answer in every case (the test is open-textured, and judges have remitted cases for fresh determination on aggregation), but it will get you to a defensible working view in two minutes.
The flowchart deliberately stops at “aggregation applies / does not apply” and pushes you back to your broker. The reason is that the consequence of aggregation in your specific policy depends on whether the aggregation trigger applies only to the limit, only to the excess, or to both — and on whether the policy has separate sub-limits for particular categories of claim (fidelity, conveyancing, fraud, cyber) that may sit outside the general aggregation regime.
We split the underlying detail across twelve in-depth articles. Each one is self-contained and includes worked numerical examples, FAQs, and links back to this hub.
| # | Spoke | What it covers |
|---|---|---|
| 01 | AIG v Woodman & Others [2017] UKSC 18 — the leading case | Facts, ratio, the three-step test, post-Woodman application. |
| 02 | Spire Healthcare v RSA [2022] — “series of related matters” most recent authority | The Paterson case, Court of Appeal reasoning, what changed. |
| 03 | Lloyds TSB v Lloyds Bank Group Insurance [2003] — the original three-step test | House of Lords pensions mis-selling case. |
| 04 | Aggregation in SRA Minimum Terms — clause 2.5 | Solicitors-specific position, four-rung ladder, worked examples. |
| 05 | Aggregation in RICS minimum wording | Surveyor-specific, valuation series claims. |
| 06 | Aggregation in ARB/RIBA wording | Architect-specific, project-level aggregation. |
| 07 | Aggregation in IFA / financial services wording | DB transfer aggregation case studies, FOS approach. |
| 08 | “Originating cause” vs “matter” — the wording battles | Why the trigger your insurer picks decides most outcomes. |
| 09 | “Same act or omission” — the narrowest aggregator | Why insurers do not accept this at renewal. |
| 10 | Conveyancing fraud aggregation | Multi-property scams, Friday afternoon fraud, vendor impersonation. |
| 11 | Cyber/data breach aggregation | MOVEit/Capita-style mass events, single occurrence vs systemic. |
| 12 | How to negotiate aggregation at renewal | Practical broker guide, market reality 2026. |
Aggregation is rarely a free-standing question. It sits inside a web of policy mechanics that all have to be considered together. Five interactions matter most.
Notification. Aggregation analysis usually starts at notification, not at claim. If you notify a single circumstance covering a cluster, you are inviting the insurer to treat all subsequent claims as one. If you notify each file separately, you are inviting fragmentation. Brokers should advise notification by cluster — see our solicitors’ proposal completion guide and IFA proposal guide for proposal-stage disclosure.
Fair presentation. The Insurance Act 2015 imposes a fair presentation duty (section 3). Material circumstances include circumstances that could give rise to a cluster of related claims, not just to a single claim. Failure to disclose cluster-level exposures can trigger proportionate remedies under Schedule 1. See our Insurance Act 2015 overview and the fair presentation deep dive.
Limit of indemnity. Aggregating clauses make the limit work harder. SRA Minimum Terms set a £2 million floor; firms doing scheme work, conveyancing in volume, or trust account work routinely buy £5 million to £25 million in excess layers. See our solicitors’ “how much PI cover” guide.
Excess. A single aggregated excess can either help or hurt. Reduced aggregating excesses are sometimes negotiable; we explore that in Spoke 12.
Run-off. Run-off limits sit on top of a fixed aggregate over the run-off period. Aggregation in run-off is the difference between exhausting the cover in year one and having cover for the full six. See the solicitors’ run-off cover deep dive.
1. What is an aggregation clause in PI insurance? A clause that defines when two or more apparently separate claims are treated as one claim for the purposes of the policy — typically by reference to a common originating cause, matter, transaction or “series of related matters or transactions”. It controls how many times the excess applies and whether the limit of indemnity is exhausted once or many times.
2. What are “series clauses”? Series clauses are the most common form of aggregation clause in UK PI insurance. They aggregate claims arising from a series of related matters or transactions. The leading case is AIG v Woodman [2017] UKSC 18.
3. Is aggregation good or bad for me as a policyholder? Both. Aggregation reduces excess multiplication (one excess instead of twenty) but accelerates limit exhaustion (one limit instead of twenty). Whether the net effect is favourable depends on the cluster size, the limit, the excess, and whether other layers sit above.
4. What is the AIG v Woodman three-step test? (1) Are there matters or transactions at all? (2) Do they form a series? (3) Is that series “related” in a real way, viewed objectively and in the round? All three must be yes for aggregation under “series of related matters or transactions” to apply.
5. Does aggregation apply to the limit, the excess, or both? Depends on the policy. The SRA Minimum Terms apply aggregation to the limit. Many commercial PI policies aggregate the excess as well. Some apply different aggregation triggers to limit and excess. Read your specific wording.
6. What is the “originating cause” test? A wider aggregation trigger than “matter” or “transaction”. Aggregates claims that flow from a single root cause — for example, a systemic misunderstanding of regulation across a portfolio of advice files. The leading case is Lloyds TSB v Lloyds Bank Group Insurance [2003] UKHL 48. See Spoke 3.
7. Can I negotiate aggregation at renewal? The trigger itself is usually fixed by the insurer’s standard wording or by minimum-terms rules. Negotiable items include: aggregated excess limits, fidelity sub-limits, conveyancing fraud sub-limits, cyber sub-limits, and the size of the limit overall. See Spoke 12.
8. How does aggregation interact with run-off cover? Run-off cover usually has a single aggregate limit over the run-off period. Aggregation can either rapidly exhaust that aggregate (bad) or unify multiple notifications into one cluster within the aggregate (neutral). For SRA-regulated firms the mandatory six-year run-off uses one aggregate limit for the whole period.
9. What aggregation wording applies to solicitors? The SRA Minimum Terms clause 2.5(a). Aggregation triggers: one act or omission; one series of related acts or omissions; the same act or omission in a series of related matters or transactions; similar acts or omissions in a series of related matters or transactions. See Spoke 4.
10. What aggregation wording applies to surveyors? RICS minimum wording uses an aggregating “any one claim” structure with bespoke aggregation language depending on the insurer. Most market wordings follow a “series of related matters or transactions” formulation similar to SRA. See Spoke 5.
11. What aggregation wording applies to architects? ARB Code requires “adequate and appropriate” insurance; the market norm follows project-level aggregation for design and supervision services. See Spoke 6.
12. How does aggregation work for IFA defined-benefit transfer claims? DB transfer claims often aggregate by reference to common advice methodology or common scheme. FOS aggregates by individual complainant for award purposes, but the insurance aggregation question turns on the policy wording. See Spoke 7.
13. Does cyber aggregate as one event or many? Depends on whether the breach is treated as a single occurrence (e.g. one ransomware deployment) or as multiple acts/omissions (e.g. failing to patch on twenty endpoints over three months). Cyber aggregation is the fastest-moving area of aggregation drafting. See Spoke 11.
14. How should I notify a cluster of related claims? Notify the cluster not the individual file. Identify the connecting feature (scheme, fund, transaction type, counterparty). State that you are notifying any matters or transactions related to that feature. This protects the limit and avoids fragmentation. Take broker and legal advice before sending.
15. What happens if the limit aggregates and is exhausted? The insurer pays the limit; you pay the excess; the balance is your liability. For partnerships, that is partner liability. For incorporated firms, that is corporate liability and can be solvency-threatening. Excess layers may pick up above the primary if you have purchased them.
If you are a managing partner or COFO/COFA, your priority should be to read Spoke 4 on SRA Minimum Terms clause 2.5 (if solicitor) or the corresponding sector spoke. Then read Spoke 12 on renewal negotiation. Then have a structured conversation with your broker about cluster mapping for fair presentation under the Insurance Act 2015.
If you are a claims technician handling a live cluster, work through the three-step test in Section 6 with your broker and external coverage counsel. Then read Spoke 1 on AIG v Woodman and the relevant case-law spoke for your sector.
If you are a compliance officer mapping aggregation risk for the board, start with the proposal-form completion guides and use the cluster-disclosure approach we set out for each profession.
For tailored advice on your specific aggregation wording, contact us at Apex Insurance Brokers. We are an FCA-authorised broker (FRN 724952) specialising in UK professional indemnity for regulated firms.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Article",
"headline": "Aggregation and series clauses in UK PI insurance: the complete 2026 guide",
"datePublished": "2026-06-04",
"dateModified": "2026-06-04",
"author": {
"@type": "Organization",
"name": "Apex Insurance Brokers Limited",
"url": "https://www.apexinsurancebrokers.co.uk/"
},
"publisher": {
"@type": "Organization",
"name": "Apex Insurance Brokers Limited"
},
"mainEntityOfPage": "https://www.apexinsurancebrokers.co.uk/aggregation-and-series-clauses-pi-insurance-uk/"
},
{
"@type": "FAQPage",
"mainEntity": [
{"@type": "Question", "name": "What is an aggregation clause in PI insurance?", "acceptedAnswer": {"@type": "Answer", "text": "A clause that defines when two or more apparently separate claims are treated as one claim for the purposes of the policy — typically by reference to a common originating cause, matter, transaction or series of related matters or transactions."}},
{"@type": "Question", "name": "What is the AIG v Woodman three-step test?", "acceptedAnswer": {"@type": "Answer", "text": "(1) Are there matters or transactions at all? (2) Do they form a series? (3) Is that series related in a real way, viewed objectively and in the round? All three must be yes for aggregation to apply."}},
{"@type": "Question", "name": "Does aggregation apply to the limit, the excess, or both?", "acceptedAnswer": {"@type": "Answer", "text": "Depends on the policy. SRA Minimum Terms apply aggregation to the limit; many commercial PI policies aggregate the excess as well. Read your specific wording."}},
{"@type": "Question", "name": "Can I negotiate aggregation at renewal?", "acceptedAnswer": {"@type": "Answer", "text": "The trigger is usually fixed by insurer wording or minimum-terms rules. Negotiable items include aggregated excess limits, sub-limits for fidelity, conveyancing fraud and cyber, and the overall limit of indemnity."}}
]
},
{
"@type": "BreadcrumbList",
"itemListElement": [
{"@type": "ListItem", "position": 1, "name": "Apex Insurance Brokers", "item": "https://www.apexinsurancebrokers.co.uk/"},
{"@type": "ListItem", "position": 2, "name": "Knowledge hub", "item": "https://www.apexinsurancebrokers.co.uk/knowledge/"},
{"@type": "ListItem", "position": 3, "name": "Aggregation and series clauses", "item": "https://www.apexinsurancebrokers.co.uk/aggregation-and-series-clauses-pi-insurance-uk/"}
]
}
]
}
Last reviewed 4 June 2026. Insurance and legal commentary, not advice on your specific position. Apex Insurance Brokers Limited is authorised and regulated by the Financial Conduct Authority, FRN 724952.
Apex Insurance Brokers serves UK professional services firms and commercial businesses. Call 0117 325 0027, email hello@apexinsurancebrokers.co.uk, or request a quotation.
Get a quote