Home / Insights / One template, forty buildings: the aggregation clause in a fire consultancy’s PI
Insights for fire consultants
One template, forty buildings: the aggregation clause in a fire consultancy’s PI
Fire consultancies repeat things: one template, one assessor, one modelling assumption, used across a client’s whole portfolio. When the repeated thing is wrong, the aggregation clause decides whether you face one claim or forty, one limit or several, one excess or many.
Guidance only. Cover depends on your own policy wording; speak to us about your position.
Why repetition makes this the clause to read first
Your work is repeatable by design. A housing provider instructs assessments of every block it owns. One assessor uses one template. One smoke control assumption is carried from tower to tower. If the method has a flaw, the flaw is in every building.
Most policies contain an aggregation clause: words that treat a number of claims as one claim where they share a cause. Claims treated as one share a single limit and, usually, a single excess. Fire safety cover is also often given with its own lower limit, in the aggregate, with defence costs inside it. The two provisions have to be read together, and with the notification clause.
The words that do the work
Aggregation clauses look alike and are not. A few words set how wide the net is.
| Wording | How wide | How a court has read similar words |
|---|---|---|
| “One originating cause” or “one source or original cause” | The widest form. It looks for a single unifying factor behind the claims. | In Spire Healthcare v Royal & Sun Alliance [2022] EWCA Civ 17, the Court of Appeal treated claims by two groups of patients as one, because all arose from one consultant’s conduct. It also said the search must not reach back to remote or coincidental causes. |
| “A series of related acts or omissions” or “related matters or transactions” | Narrower. Similarity is not enough. The acts or matters must be connected. | In AIG Europe v Woodman [2017] UKSC 18, on solicitors’ minimum terms, the Supreme Court said related transactions need a real connection and must fit together in some way. It called the question highly sensitive to the facts. |
| No aggregation clause, or “any one claim” alone | Each claim stands by itself. | Not tested here. Each building or claimant may carry its own limit and excess, subject to any aggregate limit for the year. |
Those cases turned on the words and facts before the court. Neither concerned fire safety, and neither tells you how your own policy would respond. They show why the exact words matter.
Aggregation cuts both ways
It is tempting to see aggregation as the insurer’s clause. It is not always. In the same case the Supreme Court said these clauses should be read without leaning towards a wide or a narrow meaning, because they can favour either side (AIG Europe v Woodman). Which side depends on the size of the claims.
- Forty claims treated as one. One limit has to pay for every building, which may not be enough. But only one excess is usually payable.
- Forty separate claims. Under a limit for each claim, every building has its own limit. But the excess may be payable forty times, which can leave smaller claims largely uninsured.
- An aggregate limit for fire safety. The total payable in the year is capped whichever way the clause falls, and defence costs inside the limit reduce what is left. Aggregation then mainly decides how many excesses you pay.
Check how the excess is expressed too. It may apply to each claim, or to each claimant within a claim.
How aggregation and notification work together
PI is written on a claims made basis. If you notify a circumstance properly, later claims arising from it usually attach to the policy year in which you notified. For a repeated method, that puts the notification at the centre.
Suppose a later survey shows your template missed the same defect in one block, and the same template was used on thirty more for that client. Notifying the one building protects one building. Notifying the method, and naming the buildings where there is a specific reason to expect a claim, may bring the later claims into the same year. Vague blanket notifications are often challenged, so the detail matters.
The year matters most when terms change. If renewal brings a new fire safety restriction, claims that attach to the expiring year are dealt with on the expiring terms. Claims that do not are dealt with on the new ones.
Six things to check in your own wording
- The aggregation words in the printed wording, and in the fire safety endorsement. The endorsement may have its own.
- Whether the limit for fire safety claims is for each claim or in the aggregate, and whether defence costs sit inside it.
- Whether the limit can be reinstated once it has been used, and on what conditions.
- How the excess applies: to each claim or each claimant, and whether it applies to defence costs.
- Whether the basis of limit your appointments require is the basis your policy gives.
- How your largest client’s portfolio compares with the limit: the number of buildings, and what one repeated error could cost to put right.
What we tell insurers about repeated work
Insurers want to know how concentrated your work is, and what stops one error repeating. We set out your largest clients and the number of buildings for each, how many reports each assessor signs, who controls changes to templates and standard paragraphs, and how reports are checked.
Independent sign off speaks directly to this risk. Under BAFE SP205, for example, each assessment is signed off by a validator (BAFE). Where modelling is involved, we describe who reviews the assumptions before they are reused on the next project. Fair presentation explained
Is one limit enough for your largest client?
Send us your wording and endorsements, and we will explain how the aggregation words, limit and excess may apply to a portfolio claim.
Related: PI for fire consultants · The clause guide · Claims support