Short answer: MGAs should not view El Nino aggregation only as geography. They should also review physical aggregation: short-RUL roofs, weak drainage, prior water intrusion, exposed utilities, stale records, tenant consequence, and renewal timing across accounts.
The portfolio question is not just where the properties are. It is how fragile they are.
Why Aggregation Needs Physical Evidence
Two portfolios can have similar regional exposure and very different physical risk. One may have current roof records, clean drainage, documented repairs, and long RUL. Another may have unknown roof age, recurring leaks, no photos, and below-grade utilities.
Those are not the same underwriting problem.
The Aggregation Fields
| Field | Why it matters |
|---|---|
| Region | Identifies possible shared weather context |
| Roof RUL | Shows remaining margin |
| RUL confidence | Shows data quality |
| Prior water intrusion | Shows real building behavior |
| Drainage condition | Indicates heavy-rain vulnerability |
| Utility exposure | Converts water into function risk |
| Occupancy | Shows tenant and operations consequence |
| Renewal timing | Shows market pressure |
| Records quality | Shows underwriting confidence |
The aggregation view should combine hazard, condition, and data quality.
The El Nino Boundary
NOAA and WMO context can support earlier portfolio triage. It does not prove loss frequency or severity for an MGA book. The source boundary should remain explicit in underwriting notes.
Use El Nino as a reason to ask better questions sooner.
Account Triage Outputs
An MGA review should produce categories:
- Clean file.
- Records request.
- Roof inspection needed.
- Drainage or water-intrusion follow-up.
- Utility exposure review.
- Loss-control referral.
- Underwriting escalation.
- Watchlist for renewal timing.
The goal is to reduce uncertainty before renewal pressure.
Broker and Insured Communication
MGAs should ask for targeted evidence rather than broad climate questionnaires. A better request is:
“Please provide current roof RUL, dated roof and drainage photos, repair closeouts, leak history, utility exposure notes, and open issues for the listed priority locations.”
That request is easier to satisfy and easier to underwrite.
Aggregation Views That Matter
MGAs can build several views:
| View | What it shows |
|---|---|
| Geography | Where accounts may share weather context |
| Roof RUL | Where physical margin is thin |
| Data confidence | Where records are too weak for the decision |
| Water history | Where buildings have already shown vulnerability |
| Utility exposure | Where water could become downtime |
| Renewal calendar | Where action is time-sensitive |
| Occupancy consequence | Where interruption is more material |
The value is in the overlap. A cluster of short-RUL roofs with poor drainage records and the same renewal month is more useful than a map alone.
Governance Boundary
Aggregation dashboards should show reason codes. A score without reason codes is hard to defend to underwriting, brokerage, claims, capacity providers, or regulators. The dashboard should say whether the concern comes from hazard context, physical condition, missing data, or timing.
The Bottom Line
El Nino aggregation review should include physical vulnerability, not only location. MGAs and insurers should combine region, RUL, drainage, water history, utilities, occupancy, records, and renewal timing into an evidence-based triage queue.
Read next: MGA portfolio triage, insurers and MGAs physical intelligence, and physical intelligence risk scoring.
Sources and Scope
Source lanes include NOAA CPC ENSO Diagnostic Discussion, WMO El Nino/La Nina Update, NOAA NCEI Billion-Dollar Weather and Climate Disasters, IBHS Commercial Roof Best Practices, and FEMA P-348 Protecting Building Utility Systems from Flood Damage. This article is not actuarial, underwriting, insurance, legal, engineering, claim, credit, or investment advice.