Standard: written declination letters

If an agency adopted exactly one of the practice standards, this is the one to adopt.

It is the connective tissue for several of the others. The liability floor standard requires a documented choice when a client goes lower. The UM/UIM standard requires a documented declination for any reduction. The exposures standard means disclosing flood and earthquake whether or not you can place them — which produces declinations by the dozen.

All of those requirements resolve into the same artefact: a written record that a recommendation was made and refused.

What the standard covers

The published standard names the categories explicitly rather than leaving “recommended coverage” to interpretation: umbrella, UM/UIM, higher liability, water backup, replacement cost, flood, earthquake, or any recommended endorsement.

The document must be signed or acknowledged and kept in the client file. Not noted. Not remembered. Not summarised in an activity log six weeks later.

The full standards text is the authoritative version.

Why the naming matters

Listing the categories does two things a general obligation would not.

It removes the judgement call about what counts. An agency deciding case by case which recommendations rise to the level of needing documentation will, under time pressure, decide that most of them do not.

It surfaces the coverages that get skipped. Water backup and UM/UIM are on that list for the same reason: they are inexpensive, they are frequently declined, and they are almost never documented, because a small declination does not feel like it needs a document.

Small declined coverages produce large uncovered losses. That is precisely why they are named.

Why it is rarely done

Not because agencies do not know about it. Because of three practical frictions, each of which has a fix.

It feels like distrust. Asking a client to sign something acknowledging they declined your advice reads, to some producers, as adversarial. It is the opposite: it is the record that the client was given a real choice. Framed as “this is how we document what we recommended, so you always know what you have and what you don’t”, it lands as thoroughness rather than defensiveness.

It is extra work at the worst moment. The declination is needed at exactly the point where the sale is closing and everyone wants to be finished. Any process that adds a separate step here will erode.

Nobody owns it. If it is everyone’s responsibility, it is nobody’s, and it disappears the first busy week.

Making it a by-product

The only version of this that survives contact with a real agency is one where the declination is generated by the same action that closes the business.

Generate it from the proposal. If the proposal already lists what was recommended and what was selected, the declination is a derived document, not a new one. Anything the client did not take goes on it automatically.

Send it with the policy documents. It arrives as part of a package the client is already expecting to receive and acknowledge, rather than as an unusual extra request.

Accept acknowledgement, not only signature. The standard says signed or acknowledged. An emailed confirmation, an e-signature, a documented and dated verbal acknowledgement with a follow-up email — all of these are records. Insisting on wet signatures is how the practice dies.

Make one person accountable for the exception report. Not for producing every letter — for reviewing, weekly, which closed files do not have one. That report is the whole enforcement mechanism.

What belongs on the document

Enough for someone reading it in three years to reconstruct the decision.

The coverage that was recommended, described in plain language rather than by form number. What it would have cost. What the client chose instead. The date. Some indication of the consequence — not a scare, just the mechanism: this coverage would have responded to X; without it, X is uninsured.

That last element is what makes it a client-protective document rather than a purely defensive one. A declination that only protects the agency is a liability waiver. A declination that tells the client what they are carrying is a service artefact that happens to also protect the agency.

The client-facing case

Worth stating, because it is the part that makes this sustainable.

Clients forget what they declined. Not through carelessness — because the decision was made once, quickly, during a conversation about something else, possibly years ago.

A declination letter means the client can find out what they turned down without relying on anyone’s memory. At the next review, it becomes the agenda: here is what you declined, here is what changed since, do you want to revisit it. That is a better renewal conversation than any prospecting call, and it exists only because somebody wrote it down.

What to check in your own agency

Take the last twenty policies you bound. For each, ask: what did we recommend that they did not take, and is there a document showing it?

Most agencies running this exercise for the first time find the number of documents is close to zero while the number of declined recommendations is close to twenty.

That gap is the standard. Closing it is mostly a workflow change, and it is the highest-value one available.