Standard: UM/UIM matched to liability

Here is a pattern that appears in an enormous number of personal auto files: liability limits chosen deliberately, and UM/UIM limits sitting at whatever the system defaulted to.

The client made one decision. The software made the other. And the one the software made is the one that protects the client’s own family.

The standard closes that gap: uninsured and underinsured motorist coverage is offered at limits matching liability. Any reduction or rejection requires a documented declination.

The asymmetry the standard corrects

Liability coverage responds when your client injures somebody else. It is the coverage the state requires, the coverage the conversation focuses on, and the coverage most producers explain well.

UM/UIM responds when somebody else injures your client and cannot pay for it.

Both are about the same event — a serious injury in a collision — and both are limited by a number chosen in advance. But only one of them is routinely chosen.

The consequence is a household that carefully bought substantial liability protection for strangers and left its own members at whatever the default was. Described that way, no client would choose it. Very few clients have ever been asked.

Why matched, specifically

Matching is not arbitrary. It follows from what the client already decided.

When a client selects a liability limit, they are answering a question: how much injury am I prepared to be responsible for? Whatever number they arrive at reflects their judgement about what a serious injury costs and what their household can absorb.

That judgement does not change based on who was driving the other car. An injury that costs a certain amount when your client causes it costs the same amount when someone else causes it. The only thing that changes is who is expected to pay — and if the person expected to pay carries minimum limits or nothing at all, the shortfall lands on your client.

So matching is simply applying the client’s own reasoning consistently in both directions. It requires no new judgement from them, which is why it works as a default.

Why the mismatch is so common

Three reasons, none of them a decision.

Defaults. Quoting systems frequently populate UM/UIM at a minimum or at a fixed value that does not follow liability. Whatever loads first is what most clients buy.

It is easy to decline for a small saving. UM/UIM is usually inexpensive relative to liability, which cuts both ways: raising it costs little, and dropping it saves little. Clients shaving a premium reach for it because it is unfamiliar and the saving looks free.

It is genuinely hard to explain quickly. “Uninsured and underinsured motorist bodily injury” is four words of jargon before the sentence starts. Producers under time pressure skip it, and clients do not ask about a coverage they cannot name.

That last one is the real barrier, and it has a fix.

The explanation that works

Short, concrete, and about the client rather than about the coverage.

“If somebody with no insurance puts you in hospital, this is the coverage that pays. It is the only part of your policy that protects your own family from other people’s choices — so we set it to match what you chose for liability.”

That is one sentence of mechanism and one sentence of rationale. It is enough for a client to make a real decision, and it converts an unfamiliar acronym into an identifiable situation.

Add the stacking or rejection specifics your state requires, and that is the whole conversation.

The declination side

The standard permits reduction or rejection — it just requires a record.

This is not incidental. In many states, rejecting or reducing UM/UIM is a formal act with a statutory form, and those forms exist precisely because the gap between what a client thought they had and what they had is so consequential here.

Where a state form is required, using it is compliance rather than documentation. The standard asks for something broader: a record, in the client file, that the matched limit was offered and what the client chose instead — including at renewals where a previously rejected coverage was re-offered.

That last part matters. A rejection signed at inception, never revisited, is a decision made once by a household that has since changed.

Implementing it

Configure UM/UIM to follow liability in the quoting workflow. The most effective version of this standard is a system setting, not a talking point. If the two fields move together by default, most of the standard is satisfied before anyone speaks.

Put the one-sentence explanation in the proposal. Written, every time, in the same words.

Route every reduction through the declination process. Same mechanism as the other standards — the document is a by-product of the sale.

Re-offer at the annual review. Particularly for households whose composition changed: a new driver, a new commute, an adult child back at home. The review standard and this one reinforce each other.

Know your state’s requirements precisely. UM/UIM rules vary more than almost any other personal auto coverage — whether UM and UIM are separate, whether stacking is permitted, what a valid rejection requires. Matching liability is the standard; the mechanics of offering and rejecting are local.

What to check in your own agency

Pull twenty auto files and compare two numbers on each: the liability limit and the UM/UIM limit.

Then, for every file where they do not match, look for a document showing the client chose the mismatch.

Most agencies find plenty of mismatches and very few documents. Both halves of that are the standard, and the first half is usually one configuration change away from fixed.