Explaining a declined claim to a client without losing them
- 21 hours ago
- 3 min read
Introduction
A client has a loss — a flood, a theft, a business interruption — and the insurer declines. Perhaps an exclusion applies, perhaps a condition was breached, perhaps the sum insured was inadequate and averaging has reduced the settlement to a fraction of the loss.
The client bought the policy on the broker's advice. Whatever the technical position, they are looking at the person who arranged it and asking why they have been paying premiums for six years. This is the moment the entire value of a broker is either demonstrated or destroyed. Treat it that way.
1. Explaining a declined claim to a client starts with checking the decline is right
Do not pass it on before examining it. Read it properly first.
Read the decline reason against the wording
Insurers decline incorrectly more often than clients would believe. Check the exclusion actually applies to these facts, and whether the condition was truly breached. Compare it to the facts.
Look at what was disclosed and when
If the risk was properly presented and the insurer accepted it, a decline on those grounds may be arguable. Your own file is the evidence. Pull the presentation documents.
2. Challenge it properly where there are grounds
This is the job. It is what the commission is for.
Put a reasoned case to the insurer
Not a complaint — an argument, referencing the wording, the presentation of the risk and the facts. Brokers overturn declines regularly by doing exactly this. Put it in writing.
Escalate through the right channels
Underwriter, claims manager, the insurer's own complaints route, then an ombudsman or dispute service. Tell the client each step is being taken. Keep them updated weekly.
3. Be honest when the decline is correct
Prolonging false hope is worse than the news. Say it clearly and once.
Explain the reason in plain terms
Which clause, why it applies, and what the outcome is. Clients accept bad news they understand far better than they accept vagueness. Quote the clause.
Say plainly if the cover was never suitable
If the sum insured was too low, or a peril was excluded, or a condition was always going to be breached in practice, and that was not flagged, own it. That is a broker failure and it may be a professional indemnity matter.
4. Help with what can still be done
Practical assistance is remembered. It also rebuilds trust.
Look for cover elsewhere in their arrangements
Another policy, a supplier's liability, a third party's responsibility, a warranty. Sometimes the loss is recoverable from a different direction entirely. Check every policy they hold.
Assist with the aftermath regardless
Contractors, documentation, a partial settlement, a payment plan on the premium. Being useful when there is no commission in it is what makes a client stay. Offer what you can.
5. Prevent it at every renewal
Nearly all declines trace back to placement. Renewal is the prevention.
Review sums insured and conditions annually
Underinsurance is the single most common cause of a disappointing settlement. Check the figures rather than rolling them over. Ask for updated values.
Explain the conditions in writing every year
Alarms, locks, inspections, records. A client who has been reminded annually is far more likely to comply and far less likely to be surprised.
Conclusion
Check the decline before passing it on, because insurers decline incorrectly more often than clients would believe: read the exclusion against the actual facts and look at what was disclosed and accepted at placement. Where there are grounds, put a reasoned argument rather than a complaint, and escalate through the proper channels while keeping the client informed.
Where the decline is correct, explain which clause and why in plain terms, and own it plainly if the cover was never suitable or a condition was never flagged. Look for recovery elsewhere in their arrangements, help with the aftermath even without commission, and prevent recurrence by reviewing sums insured and restating conditions at every renewal.
.png)



Comments