Insurance and legal commentary, not advice on your specific position. Aggregation outcomes are highly fact-sensitive — consult your broker and legal advisors. Apex Insurance Brokers Limited is authorised and regulated by the Financial Conduct Authority, FRN 724952.

Originating cause vs matter — the wording battles in PI aggregation

The aggregation trigger your insurer drops into your policy decides more about your aggregation exposure than any other clause. The same losses, on the same facts, can produce wildly different aggregation outcomes depending on whether the trigger is "originating cause", "matter or transaction", "series of related matters or transactions", or one of the hybrid formulations the London market has produced in the post-Spire era. This spoke explains the wording battles, the case law on each trigger, and how to read what you have actually bought.

This article is Spoke 8 of the Apex hub on aggregation and series clauses in PI insurance.

Plain English explanation

Aggregation clauses do not all do the same thing. There are roughly four families:

Causal triggers — aggregate by reference to the cause of the claims. Includes "originating cause", "one source or original cause", "common cause", "underlying cause". The case law on these is led by Lloyds TSB v Lloyds Bank Group Insurance [2003] UKHL 48 (fragmentation) and Spire Healthcare v RSA [2022] EWCA Civ 17 (aggregation by pattern).

Transactional triggers — aggregate by reference to the work that gave rise to the claims. Includes "matter or transaction", "series of related matters or transactions", "any one Project". The case law is led by AIG v Woodman [2017] UKSC 18.

Event triggers — aggregate by reference to the event that gave rise to the claims. Includes "any one occurrence", "any one event", "any one accident". Common in liability policies but used less often in pure PI.

Hybrid triggers — aggregate if any of two or more rungs is satisfied. The SRA Minimum Terms use a four-rung hybrid covering act/omission, series of acts/omissions, same act/omission in related matters, similar acts/omissions in related matters. Many commercial PI policies use a two-rung hybrid covering originating cause and series of related matters.

Each family aggregates a different shape of cluster. The wording battle at the heart of every aggregation dispute is which trigger applies and whether the trigger is satisfied.

The four wording families compared

Trigger family	Typical wording	Leading case	Aggregates when	Best for
Causal — originating cause	"All claims arising from one originating cause"	Lloyds TSB (2003) / Spire (2022)	A single root cause unites the claims	Insurer (often)
Causal — common cause	"All claims arising from a common cause"	Caudle v Sharp [1995] CLC 1148	A common cause is operative across claims	Insurer (often)
Transactional — matter	"All claims arising from one matter"	(Construction analogue)	One unit of work gave rise to multiple claims	Both, depending on shape
Transactional — series of related matters	"Series of related matters or transactions"	AIG v Woodman (2017)	Matters or transactions are related in a real way	Insurer (in cluster cases)
Event — occurrence	"Any one occurrence / event"	Axa v Field [1996]	A single event causes the claims	Insurer (in mass-event cases)
Hybrid	Multiple triggers, any satisfies	SRA MTC clause 2.5	Any of the listed triggers is satisfied	Insurer always

A few things stand out from the table.

Causal triggers reach further back than transactional triggers. "Originating cause" goes back to the root of the loss. "Matter or transaction" stays at the unit of work. So the same systemic flaw can satisfy "originating cause" without satisfying "matter or transaction".

Transactional triggers can defeat causal triggers. If the matters are not related (different clients, different schemes, different products), "matter or transaction" wording fragments even where the underlying cause is unitary. This is the Lloyds TSB logic.

Hybrid wordings give insurers options. With two or more rungs, the insurer needs to succeed on only one. The policyholder needs to defeat all.

How the four wordings handle the same fact pattern

Take the BSPS-style fact pattern: an IFA advised 60 steelworkers to transfer out of BSPS over an 18-month period using a methodology that systematically failed to consider scheme features. 40 complaints upheld. £80,000 average award. £3.2 million total.

Originating cause wording (Spire-style): the methodological flaw is a single originating cause. Aggregation succeeds. One excess, one limit.

Originating cause wording (Lloyds TSB-style): each advice event is its own originating cause; the methodology is context, not cause. Aggregation fails. Many excesses, many limits.

Matter or transaction wording: each advice event is one matter. The matters are individual.

Series of related matters wording (Woodman): the matters are related through the common scheme (BSPS). Aggregation succeeds.

Event wording (rare in IFA): no single event. Aggregation fails.

Hybrid wording (Spire + Woodman): aggregation succeeds on either rung.

The same cluster aggregates under three wordings and fragments under two. Brokers' job is to know which wording you have and what the consequences are.

Why insurers like causal triggers

A causal trigger reaches further back than any other. It can capture systemic exposures that the policyholder has not even noticed. From the insurer's perspective this is the most efficient way to control mass-claim exposure: one cause, one limit, regardless of how many advice events, transactions or matters the cause manifested in.

Insurers also like causal triggers because they shift the diagnostic question. Under a transactional trigger, the parties argue about whether the matters are related (a fact-rich, sometimes ambiguous inquiry). Under a causal trigger, the parties argue about whether the cause is unitary (often clearer cut, particularly where the firm has a documented methodological flaw).

The trade-off is policyholder pushback. Lloyds TSB-style fragmentation arguments succeed against causal triggers if the policyholder can show that individual professional judgment was at the heart of each claim. Spire-style aggregation succeeds if the policyholder cannot show that.

Why policyholders like (or dislike) transactional triggers

Transactional triggers are bilateral in their effect. They aggregate where matters are related; they fragment where matters are not related. The policyholder's preferred outcome flips with the cluster shape.

Policyholder prefers aggregation: when claims are many but small. One excess across many small claims is much better than many excesses. (Conveyancing for a single developer; will-writing in bulk.)

Policyholder prefers fragmentation: when claims are few but large. Many limits across few large claims is much better than one limit across many large claims. (Scheme failures; cladding; mass investment mis-selling.)

The clause is the same in both cases. The cluster shape decides the policyholder's preference. This is also why bargaining over the trigger at renewal is difficult — the policyholder cannot consistently say "I want aggregation" or "I want fragmentation". The policyholder wants whichever the cluster ends up looking like, which is unknown at renewal.

Common drafting moves and their consequences

Some drafting choices we see frequently:

Lloyds-style four-rung hybrid (SRA Minimum Terms). Wide insurer options. Covered in Spoke 4.

Originating cause plus series rung (typical commercial PI). Wide insurer options. Combines Spire and Woodman reach.

Originating cause only (older market wordings). Narrower than the hybrid. Insurer must satisfy Spire-style test; policyholder can argue Lloyds TSB fragmentation.

Series rung only (less common, occasionally seen in bespoke risks). Narrower than the hybrid. Insurer must satisfy Woodman; cannot fall back to originating cause.

Project rung (architects, D&B contractors). Aggregates within projects. Outside projects, falls back to other rungs. Covered in Spoke 6.

Event rung (liability and cyber). Aggregates by event. Most common in cyber policies where a "cyber event" is the operative concept. Covered in Spoke 11.

"Same act or omission" rung only (narrowest). Almost never seen as a stand-alone trigger because too narrow to be commercially viable for insurers. Covered in Spoke 9.

Worked example with numbers — comparing wordings on identical losses

Take a solicitor with £2 million primary limit and £25,000 excess. Cluster: 30 conveyances for a single developer on a single estate, all affected by a common title defect. £60,000 loss per buyer. £1.8 million total cluster loss.

Under "any one occurrence" (event) trigger: there is no single occurrence — the conveyances span 18 months. Aggregation fails. 30 individual claims. 30 × £25,000 excess = £750,000 excesses paid. Insurer pays balance within £2 million per-claim limit.

Under "originating cause" trigger (Spire-style): the title defect is the originating cause. Aggregation succeeds. One £25,000 excess. Insurer pays £1.775 million within limit. Solicitor pays £25,000.

Under "matter or transaction" trigger (standalone): each conveyance is its own matter. No "series" rung. Aggregation fails. 30 excesses. Same as event analysis.

Under "series of related matters or transactions" trigger (Woodman): the 30 conveyances are connected through common developer, common estate, common title defect = related series. Aggregation succeeds. One excess. Insurer pays balance within £2 million limit.

Under SRA MTC four-rung hybrid: rung D (similar acts or omissions in series of related matters or transactions) succeeds. Aggregation. One excess. Same as Woodman analysis.

So on this fact pattern, the policyholder pays £750,000 under event/matter-only wordings and £25,000 under originating-cause/series-rung wordings. The difference is the wording, not the facts.

Sector implications

Solicitors. SRA MTC fixes the wording (clause 2.5(a) four-rung hybrid). Limited room for variation.

Surveyors. Variation between insurers. Hybrid wordings dominate. Originating-cause rung very common.

Architects. Project rung dominant; series and act/omission rungs as backstops. Originating cause less common.

IFAs. Most variable. Hybrid wordings dominate but rungs differ.

Accountants/audit. Hybrid wordings dominate; originating-cause and series rungs common.

Engineers. Project-style wordings common, especially in civil/structural engineering. See the consulting engineer PI proposal completion guide.

Tech consultants / IT. Project rung plus event rung. Cyber-style aggregation overlap. See Spoke 11 and the IT/tech consultant PI proposal completion guide.

What this means for your firm

Identify the rungs in your wording. Have your broker annotate the aggregation clause, identifying each rung, the case law that governs each rung, and the kind of cluster each rung captures.

Stress-test your worst-case cluster against each rung. For each rung, ask: "If this rung is satisfied, what does my net exposure look like?" Compare results across rungs.

Decide which rungs you want to negotiate. Some rungs are negotiable at the margins (a sub-limit for cyber, a sub-limit for conveyancing fraud, an aggregating excess). The trigger language itself is usually not negotiable, but the consequences of the trigger can be.

Disclose cluster features at proposal under all relevant rungs. Fair presentation under IA2015 s.3 covers cluster features that could trigger aggregation under any rung. Disclose for both causal and transactional rungs.

How wordings have moved since 2017

Three drafting trends since AIG v Woodman:

Two-rung hybrids have become the market norm. Originating cause plus series-of-related-matters covers both the causal and transactional aggregation patterns. Insurers prefer the breadth.

Project rungs are tightening in architect and D&B wordings. Project definitions are more carefully drafted and tend to be wider (capturing multi-phase and framework work).

Cyber language is bespoke. Cyber aggregation language has diverged from general PI language and uses concepts like "cyber event", "cyber incident" and "single source" that have their own emerging case law. See Spoke 11.

FAQs

Q1. Which trigger is the most insurer-favourable? A hybrid that combines an originating-cause rung with a series rung. The insurer can succeed on either.

Q2. Which trigger is the most policyholder-favourable for limit protection? An event trigger where no single event exists across the cluster. Forces fragmentation.

Q3. Which trigger is the most policyholder-favourable for excess control? A wide aggregating trigger (originating cause or series rung). Unifies the excess.

Q4. Why are causal triggers controversial? Because they can reach systemic features the policyholder may not have known were material. Policyholders argue that proper construction limits the reach; insurers argue that proper construction lets the wording do its job.

Q5. Can I argue that my wording's trigger is ambiguous? Sometimes. Where the wording is genuinely ambiguous, the contra proferentem rule construes against the insurer (in standard-form contracts). Most aggregation triggers, however, have been judicially construed and are now considered clear in meaning even where their application is ambiguous.

Q6. Does the trigger choice affect run-off? Yes. Aggregation in run-off uses the same wording as the live policy. A wide trigger in the live policy is a wide trigger in run-off.

Q7. Can I have different triggers for limit and excess? Yes, although unusual. Some wordings aggregate the limit broadly (insurer protection) but the excess only narrowly (policyholder protection on excess multiplication). Look for this.

Q8. Is the trigger choice driven by the underwriter or the policyholder? Almost entirely by the underwriter. Standard wordings reflect insurer preferences. Bespoke negotiation can shift sub-limits but rarely the trigger itself.

Q9. Does Brexit affect any of this? No. The case law is English law and was unaffected by the UK leaving the EU. Brussels Recast and Rome I changes have not bitten on aggregation analysis.

Q10. What is the single most useful action in 2026? Get your broker to produce a wording map: each rung, the case law, the cluster pattern it captures. Use it as your reference document for proposal, notification and renewal.

Originating cause vs matter - aggregation wording compared