Declined Reinsurance Submissions Analysis: Keep the Insight
On this page
- Declined Reinsurance Submissions: Why Reinsurers Lose the Insight and How to Capture It
- Key Takeaways
- What Is Declined Reinsurance Submissions Analysis?
- Why Do Reinsurers Lose the Insight From Declined Submissions?
- Declined vs Not Taken Up: Why Does the Difference Matter?
- Which Decline Reasons Should You Code?
- What Should You Capture When You Decline?
- How Do You Capture Insight From Declined Submissions?
- How Can You Test Whether a Decline Was Right?
- Who Uses Declined Submission Insight?
- How Long Should You Keep Declined Submission Data?
- Where Does Automation Help?
- How Do You Measure the Value of Decline Analysis?
- What Should CUOs Do Before the Next Renewal?
- Key Terms
- Sources
- Frequently Asked Questions
Declined Reinsurance Submissions: Why Reinsurers Lose the Insight and How to Capture It
Last reviewed: November 2026
Your written portfolio shows only the risks you said yes to. The submissions you declined hold a clearer picture of the market, and most of it is deleted with the inbox.
Short answer: Declined reinsurance submissions analysis means logging every decline with a coded reason and key submission data. Linked to later submissions and market outcomes, those records show whether your appetite, capacity and pricing rules are working.
Key Takeaways
- Declines are data, not just emails. Each one shows a risk the market offered and why you passed.
- Code the reason at the moment of decline. A free-text "not for us" cannot be analysed later.
- Separate declined from not taken up. Turning a risk away and losing it on price are different signals.
- Close the loop at the next renewal. The cedent's next submission shows how the declined year really performed.
What Is Declined Reinsurance Submissions Analysis?
Declined reinsurance submissions analysis is the structured review of risks a reinsurer chose not to quote or write. It asks why each decline happened and what it reveals about the portfolio.
The written book shows what you accepted. The declined flow shows what you were offered, which is a better guide to where the market is moving.
Why Do Reinsurers Lose the Insight From Declined Submissions?
Reinsurers lose the insight because a decline is usually a two-line email and nothing more. No record is created, so there is nothing to analyse later.
Why are declines rarely logged?
Declines are rarely logged because systems are built around bound business. Policy and treaty records start at quote or bind, not at first sight of a submission.
The underwriter has also already moved on. Logging a risk they will never write feels like wasted effort in a busy renewal.
What is lost when the decline is not recorded?
Three things are lost when a decline is not recorded. These are the reason, the data in the pack, and the link to the cedent's future submissions.
Without the reason, patterns stay invisible. Without the link, nobody can test whether the decision was right.
Declined vs Not Taken Up: Why Does the Difference Matter?
Declined and not taken up are different outcomes, and mixing them hides the real signal. One is your choice, while the other is the market's choice.
| Outcome | Who decided | What it tells you |
|---|---|---|
| Declined | The reinsurer | Where appetite, capacity or data rules turn business away |
| Quoted, not taken up | The cedent or broker | Where price, terms or line size were not competitive |
| Quoted, line signed down | The broker, on signing | Where the programme was oversubscribed and your written line was reduced |
| Bound | Both parties | What you actually wrote |
A rising decline rate may mean your appetite is tighter than your plan assumed. A rising not-taken-up rate points to price or terms instead.
Which Decline Reasons Should You Code?
Code a short, fixed list of decline reasons that maps to who can act on each one. Six to eight codes are usually enough.
| Decline reason | What it may signal | Who acts on it |
|---|---|---|
| Outside appetite (class, territory, structure) | Deliberate strategy, or a plan that needs review | CUO, portfolio management |
| Accumulation or capacity limit reached | Capital constraint, not lack of interest | Portfolio management, capital team |
| Price inadequate at broker's indication | Market pricing below your technical view | Pricing actuaries, underwriting |
| Terms or wording unacceptable | Wording drift in the market | Underwriting, wordings team |
| Data insufficient to price | Submission quality problem | Underwriting operations, broker manager |
| Counterparty or security concern | Cedent financial or conduct issue | Risk, credit |
| Deadline too short to assess | Intake or resourcing problem | Underwriting operations |
Keep a free-text note as well. The code drives analysis, while the note keeps the context.
What Should You Capture When You Decline?
You should capture enough data to compare the declined risk with the risks you wrote. That means a few core fields, extracted while the pack is still open.
- Cedent, broker, class, structure, layer and territory
- Requested capacity or line size
- Subject premium, limits and retention as presented
- Loss history summary, with its valuation date
- Coded decline reason, underwriter and decline date
These fields make declines comparable with bound business. Our article on broker submissions that cannot be compared explains why consistent fields matter for risk selection.
How Do You Capture Insight From Declined Submissions?
You capture the insight by building a short decline routine into intake. It should take the underwriter less than a few minutes per decline.
- Log at first sight. Create a record for every submission when it arrives, not when it is quoted.
- Extract the core fields. Pull structure, premium, limits and losses from the email and attachments.
- Code the decline. Pick a reason from the fixed list and add a one-line note.
- Send a clear reply. Tell the broker the reason where appropriate, so they can resubmit better business.
- Link future submissions. Match next year's submission from the same cedent to the declined record.
- Review quarterly. Analyse decline reasons by class, broker and underwriter with portfolio leaders.
Step five is the one most teams miss. It turns a list of declines into a test of judgment.
How Can You Test Whether a Decline Was Right?
You can test a decline by comparing it with the same cedent's next submission. That new pack carries loss history for the year you declined.
Illustrative example: a reinsurer declines a property per risk excess of loss programme for price inadequacy. A year later, the cedent's renewal submission shows two large losses into the layer during the declined year.
Linked together, the two records support the original decision. Had the year been clean, the same link would prompt a review of the pricing view instead.
This is not a precise back-test. Some cedents never return, and loss data may be incomplete, but even partial evidence beats no feedback at all.
Who Uses Declined Submission Insight?
Declined submission insight is used by underwriting, portfolio and broker management leaders. Each group asks a different question of the same data.
- CUO: Is our stated appetite the appetite we actually apply?
- Head of portfolio management: Are capacity limits turning away business we want?
- Pricing actuaries: How far is the market's price from our technical price, and in which classes?
- Broker relationship managers: Which brokers send business we cannot use, and why?
Lloyd's Principles for doing business describe advanced practice as analysing pre-bind trends in new and renewed business. That analysis should be granular enough to show trends between particular underwriters and brokers.
How Long Should You Keep Declined Submission Data?
You should keep declined submission data for a defined period linked to a clear purpose. Keeping everything forever is neither useful nor compliant.
Most treaty packs hold aggregated portfolio data. Some, such as life and health facultative files, contain personal data.
The UK GDPR storage limitation principle says data should not be kept "just in case". A retention policy, and anonymised core fields for analysis, solve both problems.
Where Does Automation Help?
Automation helps by removing the effort of logging and extracting, which is why declines go unrecorded. The decision and the reason still come from the underwriter.
Reinsurance Email Intelligence for submission capture reads broker emails and attachments as they arrive. It extracts cedent, broker, structure, premium, limits, claims history and exposure into one submission view.
That record exists whether the risk is quoted or declined. Underwriters then add the decision and reason code, and validate the extracted data.
Older declines often sit in unindexed email archives. Our guide to indexing the reinsurance archive covers how to make historic records searchable.
How Do You Measure the Value of Decline Analysis?
You measure the value by tracking whether decline data is complete and whether it changes decisions. A few metrics are enough to start.
| Metric | What it tells you |
|---|---|
| Declines with a coded reason | Whether the data is usable |
| Decline rate by class and broker | Where appetite and submission flow disagree |
| Mix of decline reasons over time | Whether constraints are shifting from appetite to capacity |
| Time from receipt to decline | Whether brokers get fast answers |
| Declined cedents returning with a submission | How often the decision can be tested |
What Should CUOs Do Before the Next Renewal?
CUOs should make declines visible and analysable before renewal volume peaks. The steps are simple and mostly about discipline.
- Agree a fixed list of decline reason codes with underwriting heads.
- Require a submission record at first sight, not at quote.
- Separate declined, not taken up and bound in all reporting.
- Review decline patterns with portfolio management every quarter.
Key Terms
- Declined submission: A risk the reinsurer chose not to quote or write.
- Not taken up (NTU): A quoted risk that the cedent or broker placed elsewhere or on different terms.
- Decline reason code: A fixed category recording why a submission was declined.
- Submission flow: All business offered to a reinsurer, whether written or not.
- Accumulation limit: A cap on exposure to one peril, region or counterparty that can force a decline.
- Storage limitation: The data protection principle that personal data should be kept no longer than necessary.
Sources
- Lloyd's: Principles for doing business at Lloyd's (2021), Underwriting Profitability, Principle 3
- Information Commissioner's Office: Principle (e): Storage limitation
- Insurnest: Reinsurance Email Intelligence
Frequently Asked Questions
What is declined reinsurance submissions analysis?
Declined reinsurance submissions analysis is the review of risks a reinsurer chose not to quote or write. It records why each submission was declined and what data it contained, so underwriting leaders can test appetite, pricing and broker relationships against the business they turned away.
Why do reinsurers lose the insight from declined submissions?
Reinsurers lose the insight from declined submissions because declines are usually sent as a short email and never logged as structured data. The submission pack stays in an inbox, the reason is not coded, and nothing links the decline to the same cedent's next submission.
What should a reinsurer record when it declines a submission?
A reinsurer should record the cedent, broker, class, structure, layer, territory and requested capacity, plus a coded decline reason and a short underwriter note. Key figures from the submission, such as premium, limits and loss history, should be extracted while the pack is still at hand.
What is the difference between declined and not taken up in reinsurance?
A declined reinsurance submission is one the reinsurer chose not to quote or write. Not taken up means the reinsurer did quote, but the cedent or broker placed the business elsewhere or on other terms. The two outcomes tell leaders very different things.
How can declined submissions improve reinsurance underwriting?
Declined submissions improve reinsurance underwriting by showing where appetite, capacity or data rules turn away business. Coded reasons reveal whether declines come from deliberate strategy, accumulation limits, pricing gaps or poor submission quality, and each cause needs a different response.
Can a reinsurer check whether a decline was the right decision?
A reinsurer can often check a decline when the same cedent submits again the following year. The new loss history covers the period the reinsurer declined, so linking the two submissions shows whether the decline avoided losses or missed profitable business.
How long should reinsurers keep declined submission data?
Reinsurers should keep declined submission data only as long as they have a clear business purpose for it, set out in a retention policy. Where packs contain personal data, data protection rules such as the UK GDPR storage limitation principle apply.
Which metrics help analyse declined reinsurance submissions?
Useful metrics are the decline rate by class and broker, the share of declines with a coded reason, time taken to decline, the mix of decline reasons over time, and how many declined cedents return with a later submission.
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 →
