How to find out why a legal matter has stalled
To find out why a legal matter has stalled, check the last supported event and the next action someone was expected to take. A matter waiting for a scheduled outside event needs a different response from an unassigned task or a status that nobody updated.
Consider a weekly review with three matters that all appear quiet. The following situations and dates are fictional. The follow-up dates are internal review dates, not legal deadlines.
Three quiet matters, three different next steps
| Matter and recorded status | Supporting record and remaining uncertainty | Next action and owner | Internal follow-up |
|---|---|---|---|
| A: waiting for an outside report | The provider's October 16 email confirms delivery on October 23. There is no later report in the records reviewed. Delivery is still pending. | Matter coordinator: retain the expected-wait status and check for the report on the agreed date | October 23, 2026 |
| B: review packet not prepared | An October 15 task says "prepare packet for attorney review," but its owner is blank. The records do not establish whether anyone started it. | Supervising attorney: confirm who has the work and assign the next action | October 20, 2026 |
| C: waiting for a signed authorization | The October 18 upload log shows a file labeled "signed authorization." Its contents and suitability still need checking; the matter status has not changed. | Assigned paralegal: review the file and update the status only if it satisfies the request | October 20, 2026 |
Start with the records you already keep
Check your practice software's task and matter views before adding another tool. Clio's task-report documentation describes reports covering task status, including upcoming, overdue and completed work. Availability depends on the firm's subscription.
Use those records as a starting point. Then compare them with the relevant correspondence and documents. A task report can show the recorded status; determining the reason for a delay may require checking what happened around that task.
For each matter under review, establish:
- The last event supported by a record.
- The next action the firm expected, and who was responsible.
- Any stated dependency, such as a client response or an outside report.
- Whether a newer record changes what the status currently says.
If the information needed to answer a question is unavailable, say what is missing. A useful finding can be "we cannot yet establish who has this task."
Separate what happened from what needs checking
In the fictional review, the provider's email supports an expected delivery date. It does not establish that the report arrived. The blank owner on the packet task calls for an assignment check; it does not establish that someone neglected the work.
The authorization file's name and upload date establish that a file arrived. A person still needs to check that it is the right document for that matter.
Keep these differences visible in the review. Use descriptions such as "waiting for the agreed delivery date," "owner needs confirmation," "document needs review" or "cause not yet established." Let the evidence determine which description fits.
The firm's lawyers confirm legal deadlines and decide strategy. Client updates should follow the firm's agreed review and approval process.
Give each finding a next action
A progress report becomes more useful when it identifies a person and a next check. "Follow up" leaves both open.
For Matter B, a usable entry is: "Supervising attorney to confirm who has the review packet, assign its preparation and record the next internal check." Link it to the task with the missing owner.
You can use the following worksheet for one matter:
| Field | What to record |
|---|---|
| Matter and review time | Which matter was checked, and when |
| Observed status | What the system currently says |
| Evidence | Links to the relevant task, message or document |
| Uncertainty | What the records do not yet establish |
| Next action and owner | The specific check or action and the person responsible |
| Follow-up and completion | The next internal check; later, the record showing what was completed |
Keep a finding open until the agreed next action has a recorded outcome. An assigned task is not yet a completed one.
Where automation could help
SubAI can explore a recurring review that brings together the relevant tasks, correspondence and records, flags inconsistencies, and prepares a supported next step for the right person. The available information and your firm's review rules determine what can be automated.
That might mean a review list showing which matters need an owner confirmed, which have new documents awaiting inspection and which are still within an expected wait. We would first check what your existing software already provides and what additional connections it can support.
Check whether the review helps
Start with a small set of matters your team already reviews. Record the time spent investigating each one, which findings the firm accepts as useful, what needed correcting and which questions remain open.
At the next review, check whether the agreed actions were completed. Include the time needed to verify findings when comparing staff effort.
See how SubAI approaches law-firm automation. If document collection is the recurring obstacle, the document-intake checklist walks through that process. For help deciding who should maintain the work, compare software, a consultant and a managed service.