Why Demand Letters Stall (It's Usually the Documentation)

The demand went out six weeks ago. The response was due in thirty days. The adjuster isn't returning calls, or returns them with "it's still in review." Now the file sits in the worst place a PI case can sit — done enough that nobody's working it, unresolved enough that nobody's paid — and the office's working theory is the comfortable one: the carrier is slow-walking us.

Sometimes that's true; carriers have their own incentives and their own backlogs. But after years of assembling demand packages and watching which ones move, I can tell you the uncomfortable base rate:

A stalled demand is usually a stalled file, and the stall is usually in the documentation.The uncomfortable base rate

Before escalating, audit. Here are the five failures behind most of the silence, in rough order of frequency.

1. The package gave the adjuster homework

Recall the reader this series described in the demand anatomy post: caseload-buried, software-driven, authority-limited. When a package arrives with everything verifiable — records complete, math checkable, exhibits indexed — that adjuster can evaluate and move. When it arrives with holes, the file doesn't get rejected. It gets set down — pending a supplemental request that enters their queue, then yours, then theirs again. Each hole is a round trip measured in weeks.

The most common homework assignments, per the checklist post: records referencing providers that aren't in the package; bills that don't reconcile to the specials summary; wage loss asserted without employer verification; the MRI findings cited without the imaging report attached. None of these kill a claim. All of them stop the clock — and the silence you're hearing is the file sitting in "pending documentation" status, which the adjuster has little incentive to announce.

2. The math doesn't survive checking

Evaluation starts with the specials, and the adjuster's first real act is arithmetic: do the attached bills sum to the demanded number? When they don't — a duplicate bill counted twice, a bill present but illegible, a number transposed — two things happen. The small one: recalculation and delay. The large one, covered in the anatomy post: the credibility discount that follows the file from then on. A package whose checkable claims fail checking invites skepticism of every claim that can't be checked, which is exactly where your general damages live.

3. The lien picture is missing

From the carrier's chair, a settlement isn't done when the number is agreed — it's done when it can close. Health-insurer subrogation, med-pay, government-payor interests: if the package is silent on liens, the adjuster knows the real negotiation hasn't started, because the net-to-plaintiff math is fiction until the lien picture exists. Files with unstated lien exposure get valued cautiously and slowly. Stating the liens — identified, amounts known or process underway — signals a file that can actually conclude, which is a quiet but real accelerant.

4. The timeline has unaddressed problems

The treatment gap, the pre-existing history, the late-emerging complaint — the chronology material this series keeps returning to. Here's how it stalls a demand specifically: the adjuster's review found the gap (their software practically highlights it), and the package didn't address it. Now the adjuster's evaluation includes a discount you've never been told about, and the "negotiation" that follows is two sides pricing different cases. The fix is the one from the anatomy post: find your timeline's problems first and address them in the letter — context, explanation, distinguishing facts — so the adjuster's file note reads your version, not just their software's.

5. The demand asked for the wrong conversation

Occasionally the stall is structural: a number so far outside the documented range that the adjuster routes it to a supervisor's someday-pile, a deadline so short the carrier treats it as unserious, or terms so vague ("demand the policy limits" with no stated limits information) that responding requires clarification nobody requests. The letter's job — anatomy post again — is to make responding easy. A demand that's easy to evaluate and awkward to ignore gets responses; one that's awkward to evaluate gets silence.

The audit, and the honest conclusion

So before the escalation call, run the ten-minute audit:

• Does every record cited exist in the package?
• Does the math reconcile to the penny?
• Are the liens stated?
• Are the timeline's known problems addressed?
• Is the ask inside the range the documents support?

Five yeses — then yes, lean on the carrier with a clear conscience and a clean record for the bad-faith file if it comes to that. Any no, and the fastest path to payment isn't pressure. It's a supplemental package that closes the hole — this week, not after the next round of phone tag.

The deeper conclusion is the one this cluster has been building all along: demands are won at assembly time. A stalled demand is expensive to fix and embarrassing to audit. A complete one was a checklist and a few paralegal-hours — and that trade is available on every file, every time, before the silence starts.

Educational content for legal professionals — not legal advice. All case examples fictional.