How Can a Personal Injury Firm Control UM/UIM Notice, Consent, and Release Handoffs?

Scope: This is a legal-operations framework, not legal advice. UM/UIM requirements vary by jurisdiction and policy. A qualified lawyer must determine the controlling requirements for each matter.

Why the handoff becomes risky

A liability offer may arrive before the team has resolved every possible coverage path. The policy declarations may sit in intake. Correspondence may live in email. A carrier response may be stored under a different claim number. A release may enter an e-signature queue before the responsible lawyer has reviewed its effect.

The operational problem is not that support staff need to answer a coverage question. They should not. The problem is that the lawyer cannot make a timely, informed decision when the underlying sources and states are incomplete or invisible.

Public community discussions use phrases such as “notified ... before the settlement,” “consent to settle,” and concern that signing a release could affect another claim. Those phrases identify a sequencing problem. They do not establish a nationwide rule.

The distinction matters. The NAIC explains that underinsured-motorist coverage can vary by state or policy. Firms therefore need a workflow that makes variance visible instead of encoding one legal conclusion as a universal checklist.

Build one coverage-path record

Create one record for every matter where UM or UIM coverage is possible, unknown, or disputed. Do not reduce it to a single yes/no field.

Record the source, not merely the conclusion

For each possible policy, capture:

• named insured and potentially covered person, as shown in the source;
• carrier, policy number, and claim number;
• declarations, endorsements, and relevant correspondence received;
• source location and received date;
• policy period and loss date as source facts;
• notice method, recipient, date, and delivery evidence;
• consent or waiver request, response, and response source;
• liability offer and proposed release version;
• attorney decision, decision date, and linked instructions;
• client authority and the lawyer’s communication record;
• open exception, owner, due date, and escalation level.

Use controlled states such as UNKNOWN, REQUESTED, RECEIVED, NOT APPLICABLE, and ATTORNEY DECISION. Only a lawyer should select a state that embodies a legal conclusion.

Separate three kinds of status

“Coverage confirmed” is too broad. Keep these tracks separate:

1. Document state: What source material has the firm received?
2. Communication state: What was sent, to whom, and with what delivery evidence?
3. Decision state: What did the supervising lawyer determine, and what did the client authorize?

This separation prevents an email receipt from being mistaken for legal sufficiency. It also prevents a staff-created task from being mistaken for client settlement authority.

Run the workflow

1. Open the coverage-path record

At intake or when new coverage information appears, support staff create the record. They index the source documents without interpreting them. Missing fields remain UNKNOWN; they are not guessed from a police report, prior note, or carrier label.

2. Route a coverage-review packet

The packet should contain the underlying policies and endorsements, declarations, loss facts, other known coverage, claim correspondence, offer documents, and current release. A lawyer decides what is relevant and whether more investigation is required.

3. Record the lawyer’s requirements

The lawyer identifies the applicable jurisdiction, policy language, required notice, any consent or waiver process, timing considerations, and client communication plan. The instruction should state who may perform each administrative step.

4. Execute approved communications

Support staff may prepare or send an approved notice, request, or follow-up when the lawyer has supplied the content and recipient rules. Preserve the approved version, attachments, delivery evidence, and any response.

5. Hold consequential documents

Place a visible hold on a liability release or related settlement action until all lawyer-defined prerequisites show acceptable states. A hold is a workflow control, not a legal conclusion. Only the authorized lawyer may clear it.

6. Confirm client authority

ABA Model Rule 1.2(a) states, as model guidance, that the client decides whether to settle. The lawyer communicates the advice and obtains the required authority. Support staff may schedule that communication and record that a signed or otherwise approved authority artifact exists. They should not recommend acceptance or characterize the offer’s legal value.

7. Lock the approved package

After approval, lock the exact release version, related correspondence, client-authority artifact, and attorney approval. If any document changes, return the package to review instead of silently replacing a file.

8. Close or continue the path

Record what was completed, what remains open, and which later event will trigger review. Do not mark the UM/UIM path closed merely because the liability payment arrived.

Workflow at a glance

1. Open source-linked coverage-path record
2. Collect policies, endorsements, offers, and release versions
3. Route packet for attorney interpretation
4. Execute only lawyer-approved notice or consent steps
5. Hold consequential documents until prerequisites are cleared
6. Record client authority and lawyer approval
7. Lock the approved package and delivery evidence
8. Reopen on changed facts, documents, or responses

Assign responsibility

ABA Model Rule 5.3 commentary addresses measures, directions, and supervision for nonlawyer assistance. It is model guidance; firms must check their own jurisdiction’s rules.

Control technology and access

A case-management field is useful only when its meaning is controlled. Define who can edit decision states, who can clear holds, and which events create an audit entry.

Use role-based permissions for policy documents, medical information, settlement materials, and client communications. Avoid copying sensitive files into separate task tools merely to create reminders. A task should point to the governed source when possible.

Automations may flag missing documents, aging requests, or a release without a cleared gate. They must not infer coverage, decide whether consent is required, or clear a legal hold.

Version controls should preserve:

• the document reviewed by counsel;
• the document shown to or authorized by the client;
• the document transmitted;
• the delivery or signature evidence;
• later changes and their new approval cycle.

Define useful KPIs

These are definitions, not benchmarks. Each firm should choose targets after measuring its own process.

Measures to define

• Coverage-source completeness: Percentage of open coverage paths with every lawyer-required source received or explicitly excepted
• Release-gate compliance: Percentage of consequential releases that show every required approval before transmission
• Exception age: Elapsed time since a missing source, unanswered request, or conflicting document entered the exception queue
• Rework rate: Percentage of packets returned because a source, approval, or version was missing

Measure the evidence, not the hoped-for outcome. “Faster settlements” would require a validated baseline and careful attribution. A safer initial dashboard shows whether the firm followed its own control design.

Review queue indicators

• unknown coverage sources
• notice and consent state
• release holds
• client authority
• attorney approval
• exception age

The accessible dashboard should use text labels in addition to color, provide keyboard-readable filters, and link each count to the underlying matter record. It should never expose client data in an unrestricted view.

Handle exceptions

The policy or endorsement is missing

Keep the requirement UNKNOWN. Route the gap to the lawyer and follow the lawyer’s approved retrieval process. Do not assume the declarations page resolves every term.

State law and policy language appear to conflict

Escalate with both sources attached. Staff should not select which authority controls.

A release arrives before review is complete

Apply the administrative hold, preserve the exact version, and alert the designated lawyer. Do not communicate that the document is safe or unsafe to sign.

The carrier does not respond

Age the exception and follow the lawyer-defined escalation ladder. Never treat silence as consent unless counsel has made and documented that determination.

The client wants an immediate answer

Route the client to the lawyer. Support staff can explain the communication process, but they cannot advise whether signing affects coverage or whether an offer should be accepted.

New coverage appears after an approval

Reopen the coverage-path record. Remove the prior ready state, preserve the earlier decision, and route the new source for review.

Implement the workflow

For a mid-size or large firm, start with a controlled pilot:

• designate a lawyer owner and operational owner;
• identify trigger events that open or reopen the record;
• define source, communication, and decision states;
• specify which roles may change each state;
• create the coverage-review packet template;
• add a visible release hold and clearance rule;
• define exception owners and escalation intervals;
• test changed-document and absent-response scenarios;
• audit a sample for approval and version evidence;
• revise the process before broader rollout.

Training should include “do not decide” examples. A staff member should know that recording a policy limit, requesting a document, and tracking a response are different from determining available coverage or the legal effect of a release.

Fit and not-fit

This workflow fits firms with repeatable motor-vehicle matters, multiple handoffs, distributed staff, or inconsistent coverage records. It can also help when an internal team uses supervised virtual legal assistant services for document collection, indexing, approved follow-up, and exception reporting.

It does not fit a model that expects nonlawyers to interpret policies, choose legal requirements, advise clients, negotiate, approve settlement, or release claims. It also cannot replace jurisdiction-specific forms, attorney review, or a firm’s confidentiality and security assessment.

For related educational material, see our personal injury legal operations resources. Firms evaluating administrative capacity can review personal injury law firm support.

Frequently asked questions

How can a personal injury law firm control UM/UIM notice, consent-to-settle, and release handoffs without delegating judgment?

Use one source-linked record with separate document, communication, and decision states. Staff maintain evidence and execute approved tasks. Lawyers interpret the policy and jurisdiction, advise the client, and approve consequential actions.

What should the firm record before a liability release moves forward?

Record the current policy sources, other known coverage, notice and consent instructions, carrier responses, exact release version, client authority, attorney approval, and every unresolved exception.

Does every UIM matter require consent before settlement?

This article does not assert that. Requirements may vary by state and policy. A lawyer must determine and document the rule for the specific matter.

Can a virtual legal assistant send a notice or consent request?

Potentially, as an administrative task under firm-approved procedures and lawyer supervision. The assistant should not decide whether a notice is legally required, interpret a response, or select the next legal step.

Who decides whether to accept a settlement?

The client does, after legal advice from the lawyer. ABA Model Rule 1.2(a) expresses that allocation as model guidance; applicable jurisdictional rules control.

Sources and disclosure

• American Bar Association, Comment on Model Rule 5.3. Research retrieval: September 13, 2026.
• National Association of Insurance Commissioners, Shopping Tool for Auto Insurance. Research retrieval: September 13, 2026.
• American Bar Association, Model Rule 1.2. Research retrieval: September 13, 2026.

Last updated: 2026-09-13.