Category: Insurance definitions · Reviewed by Jake Leat, Associate Director · Last reviewed May 2026
Aggregation of claims in PI insurance is the contractual mechanism that decides whether multiple related claims are treated as a single claim or as separate claims for the purpose of applying limits and excesses. Aggregation can dramatically change the financial outcome of a loss: a single £500,000 limit applied to one aggregated claim is very different from the same limit applied separately to each of five related claims.
A claims-made PI policy responds on either a “each and every claim” basis, an “aggregate” basis, or some combination of the two. The limit of indemnity sets the most the insurer will pay; the excess sets the most the insured must pay first. What aggregation does is define the unit to which both apply — what counts as “one claim”.
In the simplest case, one client, one piece of work, one error, one claim. The limit and the excess each apply once. Aggregation becomes important when something has gone wrong in a way that affects multiple clients or multiple pieces of work. The classic scenarios: a defective house-style template used across many client files; a systemic error in a tax-planning approach replicated for many clients; a software defect built into many client deliverables; a misinterpreted regulatory requirement applied across a portfolio.
In those scenarios, the question is whether the insurer treats the resulting claims as one aggregated claim (one limit, one excess, the insured pays one excess and the insurer can be capped at the single limit even if total losses are higher) or as separate claims (each carries its own limit and its own excess; the insurer’s total exposure is much larger but the insured pays multiple excesses).
The answer depends on the aggregation language in the wording. Aggregation can help or hurt either side depending on the facts. A small excess multiplied across fifty separate claims hurts the insured; a single limit applied to fifty aggregated claims hurts the insured. The wording determines which way the lever falls.
UK PI wordings use several standard aggregation tests. The most common are:
“Originating cause” or “single originating cause” — claims are aggregated if they arise from one originating cause. This is the broadest formulation. A single root cause, however far back, can pull together many downstream claims. Used widely in solicitors’ PI under the SRA Minimum Terms and Conditions and increasingly in other professions.
“Same act, error or omission” — claims are aggregated only if they arise from the same single act. This is narrower; near-identical errors made on different files for different clients on different dates are typically not aggregated under this formulation because each is a separate act.
“Series of related acts, errors or omissions” — claims are aggregated where they arise from a series of related acts. This sits between the other two: it captures patterns of related conduct (such as a partner systematically applying the wrong approach across many client files) without going as broad as “originating cause”.
“Related claims” — claims are aggregated where they are related by reference to clients, transactions, or events. Wording-specific; the breadth depends on the definition of “related”.
In practice the operative test is read by the courts contextually. The leading UK authority on aggregation in solicitors’ PI is the Supreme Court decision in AIG Europe Ltd v Woodman (2017), which interpreted the “similar acts or omissions” and “matter or transaction” wording in the SRA MTC and gave courts a framework for assessing what amounts to one aggregated claim. Subsequent decisions have built on this framework in the solicitors’, accountants’ and surveyors’ contexts.
Aggregation usually cuts the same way for both limit and excess, but some wordings split them: aggregate the limit (one cap across the series) and apply separate excesses to each claim, or the reverse. The schedule and definitions section together define the unit, and any departures from the default need to be read carefully.
A mid-sized firm of solicitors with twenty fee-earners holds PI cover at £3m each and every claim, with a £25,000 excess each and every claim. The firm has a property department doing residential conveyancing across a developer’s housing scheme — fifty plots sold over two years to fifty separate purchasers.
A defect in the firm’s standard transfer template — applied identically to each plot — fails to reserve a critical right of way over a strip of land. The defect is discovered when two purchasers try to use the route to a shared garage block and find access disputed.
Letters of claim arrive from twenty-two of the fifty purchasers, each claiming losses of between £8,000 and £35,000 for diminished property value, costs of obtaining the right of way retrospectively, and consequential losses.
Total claimed quantum is around £420,000.
Under an “originating cause” aggregation wording, the insurer treats all twenty-two claims as one aggregated claim arising from the single originating cause (the defective template). The firm pays one excess of £25,000 and the insurer pays the balance up to the £3m limit. Net result: firm out of pocket £25,000; insurer’s exposure capped at £3m (not reached); aggregate cover for the year reduced.
Under a narrower “same act, error or omission” wording, the insurer might treat each transaction as a separate act (each transfer was a separate piece of work for a separate client) and apply the excess separately to each. Result: twenty-two excesses of £25,000 each = £550,000 in excesses, which exceeds the total claim quantum. The insurer pays nothing because every individual claim falls within the excess. The firm carries the entire £420,000.
The difference between these two outcomes turns entirely on the aggregation wording — a single contractual phrase. Solicitors’ firms relying on SRA MTC cover are protected by the prescribed wording; firms in other professions need to check what aggregation language applies and whether it works for or against them in the scenarios their work creates.
Aggregation is most important for firms whose work is volume-based and template-driven. Conveyancing, residential mortgage advice, employment-tribunal claims, pension transfers and tax compliance services all involve large numbers of files using broadly similar approaches and shared templates. A single root cause can produce many claims.
It also matters for firms doing serial work for one client — a long-running consultancy engagement, an audit relationship spanning several years, a series of fund launches advised under one retainer. The question is whether claims arising from the engagement are one claim or many.
And it matters at limit-buying decisions. A firm with a £2m limit covering work that could plausibly aggregate to one claim of £5m is materially under-insured under an aggregation-favourable wording. A firm with a £1m limit and a £10,000 excess covering one hundred similar small files is materially over-paying its excess exposure under an aggregation-unfavourable wording.
For solicitors, the SRA Minimum Terms and Conditions prescribe a specific aggregation test using the “matter or transaction” and “similar acts or omissions” formulations. Insurers cannot reduce this aggregation breadth for solicitors below the MTC standard. The position for following-form excess layers depends on the underlying primary wording — see following form PI excess layers.
For architects under ARB, surveyors under RICS and accountants under ICAEW, ACCA, AAT and other bodies, the aggregation wording is set by the insurer rather than the regulator. Standard wordings used by the leading professional indemnity insurers vary; some apply “originating cause” by default, others use “same act” or “series of related acts”.
The “deeming clause” in many wordings is closely related. Where multiple circumstances are notified, the wording may deem them to be one notification arising from a common cause. This can interact with aggregation to produce surprising outcomes in claims handling.
Circumstance notification is the process by which related matters get into the policy in the first place — aggregation then decides how many claims they amount to. The SRA Minimum Terms and Conditions prescribe the aggregation test for solicitors. Following form excess layers typically aggregate in step with the primary policy, but exceptions exist and the wording should be checked.
What does aggregation of claims mean in PI insurance?
Aggregation is the contractual mechanism for deciding whether two or more related claims are treated as one claim or as separate claims for the purpose of applying limits and excesses. The wording defines the test (originating cause, same act, related claims, and similar formulations) and the test is applied to the facts of the loss.
Does aggregation help or hurt the insured?
It depends on the facts. If many claims of relatively small individual value arise from one root cause, aggregation usually helps the insured by triggering only one excess. If a few large claims arise from related but distinct acts, aggregation may hurt the insured by collapsing several limits into one.
What is the difference between “originating cause” and “same act” aggregation?
“Originating cause” is broad: claims aggregate if they trace back to a single root cause, however many separate acts may have followed. “Same act” is narrower: claims aggregate only where they arise from the same individual act, error or omission, so similar but separate acts on different files for different clients typically do not aggregate.
How does the SRA Minimum Terms and Conditions handle aggregation?
The SRA MTC prescribes a specific aggregation test using the language of “matter or transaction” and “similar acts or omissions”. The Supreme Court in AIG Europe Ltd v Woodman (2017) provided the leading interpretation. Insurers writing SRA-compliant cover cannot reduce aggregation breadth below the MTC standard.
What happens if my policy aggregates a claim above my limit?
If aggregated losses exceed the policy limit, the insurer pays up to the limit and the insured carries the excess loss. This is one of the principal reasons firms doing volume or template work should review their limit against the worst-case aggregation scenario rather than the worst-case single-file scenario.
Do excess-layer policies aggregate the same way as the primary policy?
Following-form excess-layer policies generally aggregate in step with the underlying primary policy, on the basis that the excess layer follows the primary wording. Exceptions exist where the excess layer has its own aggregation language. The wording should be checked, especially where the layer is written by a different insurer to the primary.
Can the insurer choose how to aggregate after a loss?
The wording controls. The insurer cannot retrospectively re-characterise claims to suit its position; the test is the test in the policy. In practice there is often genuine room for argument about whether the test is satisfied on the facts, and aggregation disputes between insured and insurer (and between layers) are a regular feature of complex PI claims.
How should I check my aggregation wording at renewal?
Read the definitions section of the policy alongside the limit and excess clauses. Note the precise test used. Think through whether your work creates scenarios where the same root cause could affect many files or many clients, and ask the broker whether the wording aggregates favourably for that scenario. Consider asking for “originating cause” aggregation if your work is template-driven.
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Aggregation of claims in PI insurance — how the wording decides one claim or many",
"description": "Aggregation in PI insurance decides whether multiple claims count as one or many for limit and excess. Here is how UK wordings handle it in 2026.",
"author": {
"@type": "Organization",
"name": "Apex Insurance Brokers Ltd",
"url": "https://www.apexinsurancebrokers.co.uk/"
},
"publisher": {
"@type": "Organization",
"name": "Apex Insurance Brokers Ltd"
},
"datePublished": "2026-05-29",
"dateModified": "2026-05-29",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://www.apexinsurancebrokers.co.uk/definitions/aggregation-of-claims-pi-explained/"
}
}
{
"@context": "https://schema.org",
"@type": "DefinedTerm",
"name": "Aggregation of claims (PI insurance)",
"description": "The contractual mechanism by which multiple related claims under a professional indemnity policy are treated as one claim or as several claims for the purpose of applying policy limits and excesses. The test is defined in the policy wording.",
"inDefinedTermSet": {
"@type": "DefinedTermSet",
"name": "Apex Insurance Brokers Glossary",
"url": "https://www.apexinsurancebrokers.co.uk/glossary/"
}
}
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What does aggregation of claims mean in PI insurance?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Aggregation is the contractual mechanism for deciding whether two or more related claims are treated as one claim or as separate claims for the purpose of applying limits and excesses. The wording defines the test and the test is applied to the facts of the loss."
}
},
{
"@type": "Question",
"name": "Does aggregation help or hurt the insured?",
"acceptedAnswer": {
"@type": "Answer",
"text": "It depends on the facts. If many claims of relatively small individual value arise from one root cause, aggregation usually helps the insured by triggering only one excess. If a few large claims arise from related but distinct acts, aggregation may hurt the insured by collapsing several limits into one."
}
},
{
"@type": "Question",
"name": "What is the difference between originating cause and same act aggregation?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Originating cause is broad: claims aggregate if they trace back to a single root cause, however many separate acts may have followed. Same act is narrower: claims aggregate only where they arise from the same individual act, error or omission, so similar but separate acts on different files for different clients typically do not aggregate."
}
},
{
"@type": "Question",
"name": "How does the SRA Minimum Terms and Conditions handle aggregation?",
"acceptedAnswer": {
"@type": "Answer",
"text": "The SRA MTC prescribes a specific aggregation test using the language of matter or transaction and similar acts or omissions. The Supreme Court in AIG Europe Ltd v Woodman (2017) provided the leading interpretation. Insurers writing SRA-compliant cover cannot reduce aggregation breadth below the MTC standard."
}
},
{
"@type": "Question",
"name": "What happens if my policy aggregates a claim above my limit?",
"acceptedAnswer": {
"@type": "Answer",
"text": "If aggregated losses exceed the policy limit, the insurer pays up to the limit and the insured carries the excess loss. This is one of the principal reasons firms doing volume or template work should review their limit against the worst-case aggregation scenario rather than the worst-case single-file scenario."
}
},
{
"@type": "Question",
"name": "Do excess-layer policies aggregate the same way as the primary policy?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Following-form excess-layer policies generally aggregate in step with the underlying primary policy. Exceptions exist where the excess layer has its own aggregation language. The wording should be checked, especially where the layer is written by a different insurer to the primary."
}
},
{
"@type": "Question",
"name": "Can the insurer choose how to aggregate after a loss?",
"acceptedAnswer": {
"@type": "Answer",
"text": "The wording controls. The insurer cannot retrospectively re-characterise claims to suit its position. In practice there is often genuine room for argument about whether the test is satisfied on the facts, and aggregation disputes between insured and insurer are a regular feature of complex PI claims."
}
},
{
"@type": "Question",
"name": "How should I check my aggregation wording at renewal?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Read the definitions section of the policy alongside the limit and excess clauses. Note the precise test used. Think through whether your work creates scenarios where the same root cause could affect many files or many clients, and ask the broker whether the wording aggregates favourably for that scenario."
}
}
]
}
Apex Insurance Brokers Ltd is a Bristol-based independent insurance broker authorised and regulated by the Financial Conduct Authority (firm reference number 724952), registered at Companies House under number 07014570. The firm advises UK professional service practices on Professional Indemnity and related covers. Contact: info@apexinsurancebrokers.co.uk or 0117 325 0027.
Last reviewed: May 2026 by Apex Insurance Brokers Ltd.
Important: this article is general information, not advice on your specific circumstances. For advice on PI insurance for your firm, contact us on 0117 325 0027 or info@apexinsurancebrokers.co.uk.
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