Most demands in a PI practice are negotiations. A time-limited policy-limits demand is something else: a test, constructed by the attorney, that the carrier either passes by paying or fails in ways that can change what the case is worth. The strategy behind these demands — when to send one, what conditions to set, what failure sets up — is among the most consequential judgment work in plaintiff practice, and none of it is mine to advise. (Lane discipline, as always in this series: I build packages; attorneys build strategy.)
But there's a reason this topic belongs on a litigation-support blog anyway: a time-limited demand is the single most defect-intolerant document package a PI office produces. An ordinary demand with a hole gets a supplemental-request cycle — annoying, survivable, covered two posts ago. A time-limited demand with a hole can simply fail as the thing it was meant to be, because the entire mechanism depends on the carrier having had a fair, complete, verifiable opportunity to evaluate and pay within the window. Every defect becomes the carrier's exit. The strategy is the attorney's; the defect-elimination is exactly my kind of work. Here's what that discipline looks like.
Why these packages punish imperfection
Think about what the demand is built to establish if the carrier doesn't pay: that the carrier had everything it reasonably needed, clearly stated terms, and a real window — and still failed to protect its insured. Now run the standard failure modes from the stalled-demands post through that frame. A missing imaging report isn't a delay anymore; it's the carrier's argument that evaluation wasn't reasonably possible. An ambiguous deadline isn't sloppy; it's the dispute that swallows the test. Unstated lien information isn't friction; it's "we couldn't have closed anyway."
In an ordinary demand, defects cost time. Here, defects hand the other side the narrative — we would have paid, but we couldn't tell what they were asking — and jurisdictions' case law is full of demands that died on exactly such details. Which is why the assembly standard isn't "complete." It's audit-proof: assembled as if a judge will one day walk through the package asking whether the carrier's failure was fairly its own.
The assembly discipline, itemized
What changes from the standard checklist post? Mostly intensity — every item there applies — plus a layer specific to the form:
Terms verification, word by word. Amount, deadline (date and time and method of acceptance), to whom acceptance is communicated, what constitutes acceptance, any conditions (releases, lien handling, payment mechanics) — each stated once, unambiguously, and consistently everywhere it appears. The letter, the cover page, and any referenced enclosure must agree exactly. This is verified by cross-read, not by confidence.
The deadline math, computed and documented. When the window opens (receipt? mailing?), how the days count, when it closes — computed against the demand's own terms and your jurisdiction's counting rules, then calendared with the proof-of-delivery date attached. The package that can't prove when its own clock started can't prove the clock ran out.
Completeness at the audit-proof standard. Every provider from the records system's log, every bill reconciled to the penny, liens identified with handling stated, the timeline's known problems addressed in the letter (the carrier's file will find them; the package should have answered them first). The completeness certificate from the records-system post stops being good practice here and becomes the point.
Delivery as evidence. Sent by the means the demand specifies and the jurisdiction respects, with delivery proof retained and the entire as-sent package preserved — exhibits, pagination, and all. If the dispute ever becomes "what exactly did the carrier receive, and when," the answer should be a file, not a reconstruction.
The pre-send audit, by fresh eyes. Every item above, checked by someone who didn't assemble it, against a written list, with sign-offs. Solo offices skip this for the worst reason — there's no second set of eyes available — which is, candidly, one of the most concrete things contract support is for.
The quiet conclusion
When the clock is running, the office that has a discipline doesn't need a heroic week. It needs the list, the log, and a second set of eyes that already knows the file.The series in miniature
Strip away the stakes and this post is the whole series in miniature: the highest-leverage documents in a PI practice are won or lost in assembly, verification, and proof — work that is systematic, delegable, and unforgiving of the midnight version.
That last part is where I come in — early, ideally. A package this intolerant of defects shouldn't meet its paralegal the week it ships.
Educational content for legal professionals — not legal advice. Time-limited demand law varies significantly by jurisdiction; your rules and your judgment control.