Facultative Cover Expiry Tracking: Stop Uncovered Risks
On this page
- Key Takeaways
- What Is Facultative Cover Expiry Tracking?
- Which Data Mistakes Leave Facultative Cover Expiring Unseen?
- Which Process Mistakes Let Expiries Slip Through?
- Which Record-Keeping Mistakes Hide Expiry Risk?
- What Routine Makes Facultative Cover Expiry Tracking Reliable?
- What Should Heads of Facultative Fix This Month?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
A construction policy is extended by three months, and nobody tells the facultative team.
The risk now runs far above treaty capacity, and the gap only shows up when a claim arrives.
Facultative cover expiry tracking compares every certificate's end date with the live policy period, so renewals happen before cover lapses.
Most failures come from eight avoidable mistakes in data, process and record-keeping, each with a simple fix.
Key Takeaways
- Track the certificate, not the policy. The two periods often differ.
- Every policy extension is a facultative event. Endorsements must reach the facultative team.
- Facultative never renews by itself. Each placement is negotiated separately.
- A lapse is a retention breach. Report it to risk, not just to operations.
What Is Facultative Cover Expiry Tracking?
Facultative cover expiry tracking is the routine that keeps every facultative certificate aligned with the period of the policy it protects.
It matters most for large risks above treaty capacity.
Munich Re's reinsurance glossary describes facultative reinsurance as negotiated separately for each cession.
Nothing renews automatically, so expiry must be managed risk by risk. Our treaty vs facultative guide explains the difference.
Facultative cover expiry tracking also protects the net retention the board approved. A lapsed certificate quietly turns a ceded risk into a retained one.
Reinsurers writing facultative business face the mirror image. Their facultative teams need expiry dates to know when exposure ends.
They also need to price any extension a cedent requests, rather than discovering it after a loss.
Which Data Mistakes Leave Facultative Cover Expiring Unseen?
Data mistakes leave facultative cover expiring unseen when the dates being tracked are not the dates that matter. These three cause the largest losses.
Why is tracking the policy expiry instead of the certificate expiry a mistake?
Tracking the policy expiry is a mistake because the facultative period can be shorter, longer or offset.
Fix: record the certificate's own start and end dates, and compare them with the policy every month.
Why is missing policy extensions a mistake?
Missing policy extensions is a mistake because the policy keeps running while the facultative cover stops.
Take a hypothetical USD 120m construction risk. Treaty capacity covers USD 70m, and facultative covers USD 50m for calendar year 2026.
The policy is extended to 31 March 2027, but the facultative is not. A USD 90m loss occurs on 15 February 2027, and the treaty is assumed to respond.
| Share of the USD 90m loss | Facultative extended (USD m) | Facultative not extended (USD m) |
|---|---|---|
| Treaty-protected share (70/120) | 52.5 | 52.5 |
| Facultative share (50/120) | 37.5 recovered | 37.5 paid net |
| Extra net loss to the cedent | 0 | 37.5 |
Fix: route every endorsement that changes a period, value or location to the facultative team.
Why is ignoring the time basis of the period a mistake?
Ignoring the time basis is a mistake because a certificate may start and end at a set local time, or follow the policy "as original".
Fix: record the time, time zone and basis, and confirm whether "as original" covers later extensions.
Which Process Mistakes Let Expiries Slip Through?
Process mistakes let facultative expiries slip through when no one is clearly responsible for acting in time.
Why is relying on the broker's reminder a mistake?
Relying on the broker's reminder is a mistake because the broker may not know about your policy changes.
Fix: keep your own expiry diary and treat broker reminders as a second check.
Why is assuming facultative cover renews with the policy a mistake?
Assuming facultative cover renews with the policy is a mistake because each placement is separate.
A renewed policy with no new certificate is uncovered above treaty capacity.
Fix: make "facultative bound" a condition of issuing renewal documents on risks that need it.
Late starts make this worse. Our analysis of facultative buying that starts too late covers the placement side.
Why is an expiry report with no owner a mistake?
An expiry report with no owner is a mistake because everyone sees it and no one acts.
Fix: name a renewal owner on every certificate and escalate unbound risks at seven days.
Which Record-Keeping Mistakes Hide Expiry Risk?
Record-keeping mistakes hide expiry risk by making the true position impossible to see in one place.
Why is leaving partly placed facultative off the tracker a mistake?
Leaving partly placed facultative off the tracker is a mistake because a placement at 80% still leaves 20% uncovered.
Fix: track the signed percentage, and treat anything under 100% as an open item.
Why is keeping certificate dates only in emails and PDFs a mistake?
Keeping certificate dates only in emails and PDFs is a mistake because versions multiply and nobody knows which is final.
The LMA's LMA5656 endorsement addresses which terms prevail when a later Fac Cert conflicts with the MRC.
The LMA notes that the agreement number and UMR fields must be completed for contract certainty.
Our guides to reinsurance contract certainty and version control for slips and wordings cover the wider issue.
Fix: hold dates in a structured register linked to the final signed document.
What Routine Makes Facultative Cover Expiry Tracking Reliable?
A reliable routine for facultative cover expiry tracking turns every expiry into a dated sequence of actions.
| When | Action | Owner |
|---|---|---|
| 90 days before expiry | Run expiry list and confirm whether the policy renews or extends | Facultative operations |
| 60 days | Decide to renew, change the line or let lapse with approval | Underwriter, head of facultative |
| 30 days | Instruct the broker and track quotes | Facultative placement |
| 7 days | Escalate anything unbound to the CUO | Head of facultative |
| Expiry day | Confirm bound with signed evidence | Facultative operations |
| Day after | Log unbound risks as net exposure | Risk function |
Which fields should the expiry tracker hold?
The expiry tracker should hold the fields that let anyone see a gap without opening a document.
| Field | Why it matters |
|---|---|
| Policy reference and current period | Shows the period that needs cover |
| Certificate reference and UMR | Links to the final signed document |
| Certificate start, end, time and basis | Shows the period actually covered |
| Gap in days | Highlights mismatches automatically |
| Reinsurers and signed percentage | Shows partly placed risks |
| Renewal owner and status | Makes one person accountable |
How do you know the routine is working?
The routine is working when three simple measures stay at or near zero each month.
- Risks with a period gap: policies running longer than their facultative cover.
- Unbound renewals inside 30 days: expiries with no firm placement yet.
- Lapses found after the event: gaps discovered only when a claim or audit arrives.
Any rise in the third measure means facultative cover expiry tracking is failing upstream, usually at the endorsement step.
Where does Insurnest fit in fac expiry tracking?
Insurnest fits as the treaty side of this picture. It does not track facultative certificates or send expiry reminders.
Reinsurance Treaty Management keeps one versioned record per treaty, with retention, limits and participations.
Those terms define treaty capacity, which decides when a risk needs facultative cover and what falls net if it lapses.
What Should Heads of Facultative Fix This Month?
Heads of facultative should fix the gaps that create the largest net exposure first.
- List every risk where the policy period is longer than its facultative cover.
- Add certificate dates, time basis and signed percentage to one register.
- Connect policy endorsements to a facultative review step.
- Name a renewal owner for every certificate expiring in the next 90 days.
- Report any lapse to the risk function as a retention breach.
Step 1 comes first because it finds exposure that may already be running uncovered today. Check long-tail project and construction policies with care.
Run it again after every renewal season, when endorsements and new certificates arrive in the same few weeks.
Key Terms
- Facultative certificate: The document that formalises a facultative cession.
- Treaty capacity: The most a cedent can place through its treaties on one risk.
- Period as original: A facultative period that follows the underlying policy.
- Signed percentage: The share of the facultative placement actually bound.
- UMR: Unique Market Reference, the identifier for a London market contract.
- Lapse: Facultative cover ending while the underlying policy continues.
Sources
- Munich Re Canada Non-Life: Reinsurance Glossary
- Lloyd's Market Association: Facultative Reinsurance Agreement Incorporation Endorsement Published (24 February 2025)
- Insurnest: Reinsurance Treaty Management
Frequently Asked Questions
What is facultative cover expiry tracking?
Facultative cover expiry tracking is the routine of monitoring when each facultative certificate ends and comparing that date with the underlying policy period. It ensures a renewal, extension or deliberate decision is made before cover lapses, so large risks never run above treaty capacity without protection.
Why does facultative cover expire unnoticed?
Facultative cover expires unnoticed because each certificate is negotiated separately and does not renew with the policy. Policy extensions, endorsements and renewals are often handled by underwriting while facultative dates sit in broker emails, so the two periods drift apart without anyone comparing them.
How far ahead should facultative renewals start?
Facultative renewals should start around 90 days before expiry for large or complex risks. That allows time to confirm whether the underlying policy renews, decide the line needed, instruct the broker and escalate before inception if capacity proves hard to find.
Who should own facultative cover expiry tracking?
Facultative cover expiry tracking should be owned by the head of facultative or reinsurance operations, with a named renewal owner on every certificate. Underwriters own the decision to renew, and the risk function should receive any risk left uncovered after expiry.
What does it cost when facultative cover lapses?
The cost of a lapsed facultative cover is the share of any loss that the facultative should have carried, now paid net. On a large risk this can far exceed the cedent's normal retention, which is why lapses should be reported as retention breaches.
Can facultative expiry tracking be automated?
Facultative expiry tracking can be automated with a register that compares certificate dates with policy dates and flags gaps on a fixed schedule. Automation still needs clean data and a named owner, because the renewal decision and placement remain human tasks.
What is the difference between a fixed period and a period as original?
A fixed facultative period has its own start and end dates, while a period as original follows the underlying policy. Teams should confirm whether as original covers later policy extensions or only the period known at placement, because wordings differ.
Should a cedent let facultative cover lapse deliberately?
A cedent can let facultative cover lapse deliberately when the risk now fits within treaty capacity or appetite. That decision should be recorded, approved at the right authority level and reflected in net retention reporting, rather than happening by default.

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 →