Ask a firm which of its cases are in trouble and you will usually get a good answer. Ask which cases nothing has happened on for six weeks and the answer takes longer, and is often wrong.
That gap is where files go to die.
Quiet is not a signal anyone receives
A case in difficulty announces itself. Opposing counsel is aggressive, the client is unhappy, a deadline is close — all of these arrive as something in somebody's inbox.
A case that has simply stopped announces nothing. No email, no call, no deadline yet. It sits in exactly the same list as ninety others, in the same status it was in a month ago, and the status is not wrong. It is "awaiting records", and it is genuinely awaiting records. It has been awaiting records since March.
The absence of an event is information, and it is the one kind of information no system delivers unless somebody built it to.
Why review meetings do not catch it
Most firms have a version of the weekly case review. It works, up to a point, and the point is roughly the size of the caseload.
A review that examines twenty cases catches the quiet one. A review that has ninety cases and forty minutes examines the ones somebody raises — and the quiet case is by definition the one nobody raises, because nothing has happened to make anyone think of it.
The mechanism fails precisely as it scales, and it fails silently, so the firm's confidence in the mechanism grows at the same time its coverage shrinks.
A task list is not a case state
This is the distinction I would most like people to take away, because it is where the tooling usually goes wrong.
A task list describes work somebody intends to do. It empties when the work is done, and an empty list feels like success.
A case state describes where the file actually is. It does not empty. A case awaiting records is in that state whether or not anyone has a task about it, and it stays there for as long as the records have not arrived — which might be a week, and might be until somebody notices in November.
When a firm runs on task lists alone, "no outstanding tasks" and "nothing is happening" become indistinguishable. They are opposite conditions and they look identical.
What to measure instead
Not activity. Activity is easy to generate and easy to mistake for progress — a file with eleven notes this month may have moved less than one with a single well-timed call.
Measure time in state. How long has this case been where it is, and is that normal for that state?
That question is answerable, it needs no judgement to compute, and it surfaces exactly the cases nobody has thought about. A file awaiting records for eleven days is ordinary. The same file at seventy days is not, and nothing about it looks different in a list sorted by name.
The threshold matters less than having one. A rule that is roughly right and applied to every file beats a sharp rule applied to whichever files somebody remembered.
The part that is uncomfortable to automate
There is a reasonable objection here: cases are not uniform, and a system that flags every file at an arbitrary age will produce noise that people learn to dismiss. That is a real risk and it is how most alerting dies.
The answer is not to make the rule cleverer. It is to make the response cheap. A flagged case should cost somebody thirty seconds — look, decide, either act or say "this is fine, ask me again in three weeks". A flag that demands a meeting gets ignored; a flag that demands a glance gets used.
The firms that do this well are not the ones with the most sophisticated rules. They are the ones where noticing costs nothing, so noticing happens.