Treaty Exhaustion Alerts: Warn Before Cover Runs Out
On this page
- What Are Treaty Exhaustion Alerts?
- How Does Cover Erode Across the Treaty Year?
- What Should Happen at Each Stage of the Timeline?
- How Fast Can a Layer Run Out?
- Who Should Receive Treaty Exhaustion Alerts?
- Where Does Treaty Management Fit in Exhaustion Alerting?
- What Should Teams Configure Before the Next Inception Date?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
A second storm in one season hits the same catastrophe layer.
Claims, reinsurance and underwriting each hold a different view of how much limit is left.
Treaty exhaustion alerts warn teams when losses have used an agreed share of a treaty's limit, so action is taken before cover runs out.
They work only if limits, reinstatements and thresholds are captured before inception and every loss is booked against them.
What Are Treaty Exhaustion Alerts?
Treaty exhaustion alerts are warnings triggered when cumulative losses reach set percentages of a treaty's available limit or aggregate.
They turn a year-end surprise into a decision taken mid-year.
Which covers can actually run out?
The covers that can run out are those with a finite total limit over the treaty period.
- Excess of loss layers with limited reinstatements. Once reinstatements are used, the layer is gone.
- Aggregate excess of loss or stop loss covers. Munich Re's reinsurance glossary describes these as responding to net losses over a period.
- Aggregate deductibles. These erode before cover attaches, which also needs tracking.
How Does Cover Erode Across the Treaty Year?
Cover erodes across the treaty year in a predictable sequence, even when losses are not predictable. The timeline below shows each stage.
| Stage | Timing | What happens | Who acts | What breaks |
|---|---|---|---|---|
| Set-up | 60 days before inception | Limits, reinstatements, deductibles and thresholds recorded | Reinsurance operations, broker | Aggregate terms left in the wording PDF |
| Baseline | Inception | Available limit and deductible remaining calculated | Reinsurance operations | Reinstatements missed or counted twice |
| Loss booking | Each notification, at least monthly | Incurred losses posted against each layer | Claims, reinsurance accounting | Paid-only view gives late warning |
| Major event | Event day to day 30 | Event estimates posted as provisional erosion | Claims, catastrophe team | Waiting for paid figures |
| Threshold crossed | At 50%, 75% and 90% | Alert raised and decision taken | Head of reinsurance, CUO | No named decision owner |
| Exhaustion | Limit fully used | Further losses treated as net | CUO, CRO, claims | Writing continues as if covered |
| Quarter-end | Every quarter | Erosion agreed with broker and reinsurers | Reinsurance accounting | Each party holds different figures |
| Expiry and run-off | Expiry onwards | Late-reported losses still erode the old year | Claims, accounting | Record closed too early |
The thresholds shown are illustrative. Set your own by class and season.
What Should Happen at Each Stage of the Timeline?
Each stage of the timeline has one job, and treaty exhaustion alerts fail when any one is skipped.
What must be set up before inception?
The set-up before inception is capturing every term that defines how much cover exists.
That includes layer limits, reinstatement count and basis, aggregate limits and deductibles.
Thresholds and alert recipients should be agreed at the same time. Our reinsurance treaty calendar guide shows where this fits.
What should happen when each loss is booked?
Each booked loss should be posted against the correct treaty year, layer and event.
Incurred figures, including case reserves, give earlier warning than paid figures.
A shared reinsurance claims ledger keeps claims and reinsurance working from the same loss figures.
Notice duties still apply as erosion builds. A claims cooperation clause may require early reporting of large losses.
What changes after a major event?
A major event changes the speed of erosion, so provisional estimates should be posted within days.
Waiting for individual claims can leave the erosion view weeks behind reality.
Event definitions matter as much as speed. An hours clause decides whether several days of storm damage count as one event or two.
That choice changes how much each event erodes, how many reinstatements are used and how much reinstatement premium falls due.
What decisions follow a threshold alert?
The decisions that follow a threshold alert are about protection and appetite.
Options include buying back a reinstatement, placing replacement or facultative cover, or restricting writing.
The economics of reinstatements should be modelled before the alert, not during it.
What happens at quarter-end and expiry?
Quarter-end is when erosion is agreed with the broker and reinsurers, so disputes surface early.
At expiry, the record must stay open, because late-reported losses on a losses-occurring basis still erode the old year.
How Fast Can a Layer Run Out?
A layer can run out within one season.
This hypothetical example uses a USD 25m xs USD 25m catastrophe layer with one reinstatement, so USD 50m is available in total.
| Event | Loss to layer (USD m) | Cumulative (USD m) | Erosion of USD 50m | Status |
|---|---|---|---|---|
| Event 1 | 18 | 18 | 36% | Below first threshold |
| Event 2 | 15 | 33 | 66% | 50% alert raised |
| Event 3 | 12 | 45 | 90% | 90% alert raised |
| Remaining | 5 | One more event exhausts it |
After Event 3, only USD 5m remains. A fourth USD 12m event would leave USD 7m, more than half the loss, net.
Real erosion is reported in the market. Artemis reported in March 2025 that LA wildfire losses eroded a good portion of Lancashire's annual aggregate deductible.
Lancashire's CUO also said plenty of limit remained, as Artemis reported. That answer depends on knowing the figure.
Who Should Receive Treaty Exhaustion Alerts?
Treaty exhaustion alerts should reach every person who must make a decision when cover runs short.
| Recipient | Decision they own |
|---|---|
| Head of reinsurance | Buy back, replace or top up cover |
| Chief underwriting officer | Restrict or reprice new business |
| Chief claims officer | Adjust reserving and recovery notices |
| CRO | Report net exposure against appetite |
| CFO | Plan for reinstatement premium and net losses |
What should an exhaustion alert contain?
An exhaustion alert should contain everything a recipient needs to decide without opening another file.
- Treaty, layer and treaty year affected.
- Erosion percentage and remaining limit, with reinstatements left.
- Loss basis used (incurred or paid) and the as-at date.
- The largest open losses driving the figure.
- The decision required, its owner and the deadline.
An alert that says only "layer 2 at 75%" invites a meeting rather than a decision.
Should reinsurers get the same alert as the cedent?
Reinsurers should get erosion figures from the cedent or broker, but their own decisions differ.
A reinsurer tracks how close each layer is to its full share of limit across all cedents. That view drives its own capacity and retrocession decisions.
Where Does Treaty Management Fit in Exhaustion Alerting?
Treaty Management fits as the treaty record that exhaustion alerting depends on. Reinsurance Treaty Management keeps one record per treaty.
That record holds structure, retention, limits and thresholds, participations and settlement conditions.
Terms are versioned as amendments occur, so an alert can read the limit in force on the loss date.
Versioning matters because available limit can change mid-year.
Buying back a reinstatement or adding a top-up layer changes the denominator behind every erosion percentage.
If that change is not recorded with its effective date, alerts fire too late or too early.
What does Treaty Management not do?
Treaty Management does not send alerts and does not manage reinsurance claims. The alerting logic and loss data sit in your claims or reporting tools.
Accuracy depends on the configured terms and source data, so teams validate both.
What Should Teams Configure Before the Next Inception Date?
Teams should configure treaty exhaustion alerts before the next inception date, while terms are fresh and losses are zero.
- List every treaty with a finite total limit or aggregate deductible.
- Record limits, reinstatement count and basis, and aggregates in one controlled place.
- Agree thresholds by class, tighter for peak-season layers.
- Name a decision owner for each threshold.
- Decide the loss basis, incurred or paid, and keep it consistent.
- Schedule quarterly erosion agreement with the broker.
- Test the alerts once with a hypothetical event before the peak season starts, and check every recipient acts.
Key Terms
- Erosion: The share of a treaty's available limit already used by losses.
- Exhaustion: The point where no limit remains for further losses.
- Reinstatement: Restoring a layer's limit after a loss, usually for extra premium.
- Aggregate limit: The maximum a treaty pays across all losses in a period.
- Aggregate deductible: Losses the cedent retains in total before an aggregate cover pays.
- Incurred loss: Paid losses plus case reserves on a given date.
Sources
- Munich Re Canada Non-Life: Reinsurance Glossary
- Artemis: Lancashire has "plenty" of aggregate reinsurance limit left despite erosion from LA wildfires: CUO (6 March 2025)
- Insurnest: Reinsurance Treaty Management
Frequently Asked Questions
What are treaty exhaustion alerts?
Treaty exhaustion alerts are warnings raised when losses have used up an agreed share of a treaty's available limit or aggregate. They give the reinsurance, claims and underwriting teams time to buy more cover, restrict writing or prepare for net losses before the cover runs out.
Why do treaty exhaustion alerts matter to a Chief Claims Officer?
Treaty exhaustion alerts matter to a Chief Claims Officer because claims beyond an exhausted limit are paid net. Reserving, recovery notices and settlement strategy all change once a layer is used up, so the claims team needs to know before the last recovery is booked.
How do you calculate treaty erosion?
Treaty erosion is calculated by adding the losses booked to a layer or aggregate and dividing by the total available limit. For a layer with one reinstatement, the total is twice the layer limit, and each event is still capped at the layer limit.
Who should receive a treaty exhaustion alert?
A treaty exhaustion alert should go to the head of reinsurance, the claims lead for the class, the chief underwriting officer and the risk function. Each has a different decision to make, from buying cover to restricting new business or reporting net exposure.
What erosion thresholds should trigger an alert?
The erosion thresholds that trigger an alert are a business choice, often set at points such as 50%, 75% and 90% of available limit. Thresholds should be tighter for layers exposed to a peak season, where one event can move erosion quickly.
Can treaty exhaustion alerts be automated?
Treaty exhaustion alerts can be automated by a claims or reporting system that compares booked losses with treaty limits. The alerting logic is only as good as the limits, reinstatements and thresholds it reads, so those terms need a controlled, versioned treaty record.
Should erosion be tracked on paid or incurred losses?
Erosion should usually be tracked on incurred losses, including case reserves and event estimates, for early warning. Paid losses lag by months, so a paid-only view can show plenty of limit left when the incurred position is already close to exhaustion.
What should a cedent do when a treaty is close to exhaustion?
A cedent close to treaty exhaustion should confirm the erosion figure with the broker and reinsurers, then decide whether to buy reinstatement or replacement cover, place facultative cover, restrict writing or accept higher net exposure. The decision owner should be named in advance.

Hitul Mistry
CEO, Insurnest
An InsurTech leader with more than a decade of experience across insurance and technology, focused on solving business problems with the help of technology. Has worked with brokers, insurance carriers, and reinsurance firms across the India, UAE, and US markets.
View LinkedIn profile →