A demand letter sits half-drafted for two weeks, not because the associate handling it is behind, but because the medical records request sent six weeks ago never actually got a response, and nobody's been tracking that it's overdue.
That's where most personal injury case workflow actually breaks. Not at the dramatic moments, intake, settlement, trial, but in the waiting in between.
Where PI matters actually stall
A personal injury matter moves through a predictable sequence: intake, treatment, records collection, demand, negotiation, resolution. Most firms know this sequence well. What they don't track well is the waiting inside it, specifically the records requests that sit with a provider's office for weeks with no response, and nobody following up until someone notices the demand can't move forward.
Records collection is the quiet bottleneck in PI work because it depends on a third party who has no urgency to respond quickly. A firm's own team can be fast and organized, and a case still stalls for a month because a records custodian hasn't gotten to the request yet, and nobody at the firm has a system for catching that silence early.
A records request, week by week
Say a paralegal sends a records request to a hospital's medical records department on a Tuesday. Two weeks pass with no response, which is normal, most requests take longer than firms would like. By week four, still nothing, but the file looks the same as it did on day one: request sent, status unchanged, nothing flagging that this has gone quiet for a month.
By week six, the attorney finally asks why the demand isn't ready, and the paralegal realizes she hasn't checked that specific request since she sent it, because nothing prompted her to. She calls the provider, gets told the request needs to be resent with a corrected date range, and the clock effectively restarts. What should have been caught in week three, a request that had gone unusually quiet, instead cost the matter an extra month it didn't need to lose.
Why the records-request gap is invisible
Most case management tools track that a records request was sent. Few track whether it's actually been fulfilled, and fewer still surface it automatically when a request has gone unanswered past a reasonable window. So the gap sits invisible until someone, usually the paralegal managing the file, happens to check on it, which might be days or weeks after it should have been flagged. That's the same non-billable hours drain that shows up anywhere a firm relies on memory instead of a system.
Multiply this across a full PI caseload, dozens of matters, each with multiple outstanding records requests at different stages, and the firm is relying entirely on someone's memory or diligence to catch every stall. That's not a realistic system. It's a hope, and it scales badly the moment caseload grows past what one paralegal can hold in her head.
What a structured PI workflow looks like
A workflow built around how PI cases actually move treats each records request as a dependency with a follow-up date attached, not a task that's marked "sent" and forgotten. If a request hasn't been fulfilled by a set point, ten business days is a reasonable default for most providers, that gets flagged automatically, the same way law firm deadline tracking flags a filing deadline at risk because the work behind it hasn't moved.
This matters more in PI than almost any other practice area, because the demand can't go out until every records request behind it is resolved. One silent gap holds the entire matter hostage, and the firm often doesn't know it's hostage until someone asks why the demand still isn't ready. The fix isn't working faster. It's catching the silence sooner, before six weeks of nothing becomes the reason a case takes three extra months to resolve.
How to start
Map your firm's PI workflow the way it actually runs, intake through resolution, and mark every point where the matter depends on an outside party responding: records requests, provider bills, liens. For each one, set a follow-up window, ten business days is a reasonable starting point for most medical providers, and make sure something surfaces it if that window passes without a response. This is the same discipline behind paralegal deadline tracking applied specifically to the waiting periods that make PI cases uniquely dependent on people outside the firm, and it holds just as true for family law matters with their own outside dependencies.
Frequently asked questions
Where do personal injury cases stall most often?
Usually during records collection. The firm's own work can move quickly, but the case depends on medical providers responding to requests, and that wait time is rarely tracked closely enough to catch when it's gone too long.
Why don't case management tools catch this automatically?
Most track that a request was sent, not whether it was fulfilled or how long it's been outstanding. Without a follow-up trigger, a stalled records request stays invisible until someone happens to check the file.
How does this affect the demand letter timeline?
The demand usually can't go out until every records request behind it is resolved. A single unanswered request can hold up the whole matter for weeks, even if everything else on the file is moving on schedule.
What's a reasonable follow-up window for a records request?
Ten business days is a reasonable default for most medical providers before flagging a request as overdue and following up. Some providers respond faster, some slower, but without any window at all, requests just sit until someone happens to notice.
What's the fix for PI-specific workflow stalls?
Treat every outside dependency, records requests, bills, liens, as a tracked item with a follow-up date, not a task marked complete once it's sent. That turns silent waiting into something visible enough to act on before it costs the case months.
If records requests are quietly stalling your firm's PI demands, see how Legalboards tracks the waiting, not just the tasks → app.legalboards.io/register
