Fifty-seven percent of firms take a week or more to send a demand
The delay is almost never the argument. It is assembly — pulling figures out of bills, indexing exhibits, and finding out on day three that a wage verification never arrived.
Fifty-seven percent of plaintiff firms need a week or more to produce a demand letter. That figure comes from Supio’s plaintiff-specific report, and if you work at one of those firms it will not surprise you.
What is worth examining is where the week goes. Almost none of it is writing.
The week, honestly accounted for
Ask an attorney how long it takes to write a demand and the answer is usually two or three hours. That is true, and it is why the week is confusing until you break it down.
Waiting on records. Requests go out, come back incomplete, go out again. This can be most of the elapsed time and none of the effort.
Reading the file. Somebody has to know what is in a thousand pages before they can argue from it. On a treating case that is a day and a half; on a complex one, three or four days.
Tabulating specials. Every provider, every bill, billed and paid, reconciled against the ledgers. Tedious, error-prone, and it goes straight into the number you are asking for.
Indexing exhibits. Thirty or forty documents, numbered, cross-referenced against the narrative that cites them.
Discovering something is missing. Usually on day three. A wage verification, an imaging report, the records from the provider nobody listed. Now you are waiting again, with a half-built package on somebody’s desk.
Writing. Two or three hours.
Review. An hour, unless the review turns up a discrepancy between the narrative and the records, which sends it back.
Add it up and the week is real. It is also almost entirely assembly.
Why this is the wrong work for a person
None of the above requires judgment except the writing and the review. The rest is gathering, cross-checking and formatting, done by somebody who is good at law.
Two consequences follow.
The first is cost. You are paying skilled people to do unskilled work on a file that is not earning anything until it moves.
The second is worse and less visible. Assembly at this volume produces errors — a bill counted twice, a provider missed, a date that does not match the record it cites. Those errors go into a number you send to an adjuster, and correcting one afterward costs you credibility at exactly the moment you need it.
The demand is not slow because writing is hard. It is slow because nobody knows what is in the file yet.
What actually shortens it
Find the absence on day one. Most of a slow demand is waiting on something nobody knew was missing. That is checkable at the start: take an independent list of who treated this person — the billing index, the custodian cover sheets — and compare it against what actually arrived. Anything on the list without records is a request you can send in week one instead of week three.
Make the chronology the source. If the narrative, the specials table and the exhibit index all derive from one dated, cited chronology, they agree with each other by construction. When they are built separately from the same pile of paper, reconciling them is its own job.
Reconcile billed and paid once. Not per document, per case. The figures live across several ledgers and explanation-of-benefit forms, and adding them up twice produces two answers.
Draft from your own prior demands. Your firm has sent hundreds. The structure, the language, the arguments that work in your venue are all in them. A first draft assembled from your own past work is closer to sendable than a first draft from a template.
Where AI is useful here, and where it is not
The obvious move is to have software write the demand. Drafting was never the bottleneck, so that solves the two hours and leaves the week.
The useful application is upstream. Records read once and returned as a dated chronology with a page citation on every line. Specials tabulated from the bills and reconciled. Missing documents flagged against an independent list before anybody starts writing.
Do that and the demand stops being an assembly job. The attorney gets a file that is already known, and writes for two hours, which is what they thought the job was in the first place.
There is a caution attached. A demand drafted from a bad chronology is a fast way to send a wrong number, and a wrong number in a demand is worse than a slow one. Which is why the chronology has to be checkable — every line traceable to a page — rather than merely produced. The procedure for checking one takes about ten minutes.
The number this actually moves
Shorter demand turnaround is not really about the demand. It shortens the time between signing a case and being paid on it, and that cycle is what a plaintiff practice runs on.
It also reduces the number of files sitting in the state every firm has and nobody likes: signed, worked up, and waiting on somebody to have four clear days. Those files are where statutes creep up and where clients call to ask what is happening.
A firm that sends demands in two days instead of nine has not just saved seven days of work. It has changed how many cases it can carry at once, which is the constraint underneath most of the rest.
Questions we get asked
- How long does it take to send a demand letter?
- Supio's plaintiff report found 57% of firms need a week or more. The writing is rarely what takes the time. Assembly does — tabulating specials, indexing exhibits, checking the narrative against the records, and discovering partway through that something is missing.
- Why do demand letters take so long to prepare?
- Because the work is gathering rather than drafting. The figures live across several billing ledgers, the exhibits have to be indexed and cross-referenced, and the missing wage verification is usually found on day three rather than day one.
- What should go in a demand package?
- Liability, a treatment narrative, special damages tabulated, general damages argued, the demand itself with a response deadline, and the supporting records as indexed exhibits. The structure is standard; the time goes into the material behind it.
- Can AI write a demand letter?
- It can draft one, and drafting was never the bottleneck. The useful application is upstream: turning the records into a dated, cited chronology and a reconciled damages table, so the draft has something accurate to be built from. A demand drafted from a bad chronology is a fast way to send a wrong number.
- What is the fastest way to shorten demand turnaround?
- Find out what is missing on day one instead of day three. Most of the delay in a slow demand is a document nobody knew was absent until somebody went looking for it, and absence is checkable against an independent list at the start.
- Does sending demands faster actually matter?
- It shortens the time between signing a case and being paid on it, which is the cycle a plaintiff firm runs on. It also means fewer files sitting in the state where the statute is running and nothing is happening.
Not ready to book a call
Send us five pages of a record set. We will send back what we found in it.
Five pages is enough, redacted however you like. You get a short video back within two business days showing what a chronology would surface from it: the dates, the gaps, the things worth knowing before the other side finds them.
- Send five pages of a real file. Redact whatever you like first.
- We run them and record what comes out, including what it misses.
- You get the video within two business days. If there is nothing worth showing, we say so.