FirmFooting / Briefs / Systems & SOPs
Systems & SOPs · Published Jun 27, 2026
Your Paralegal's Memory Is Not a Docketing System
Let me be precise about the argument, because the title invites the wrong reading. Your paralegal is probably the most reliable component in your firm. That is exactly the problem. A firm that runs on one person's excellence has no docketing system, it has a dependency, and the person carrying it never gets to put it down.
Jareer Ali·
Field notes·
13 min read
A law firm docketing system is a documented process and shared record: dates captured the day a notice arrives, one named owner per deadline, escalation to a second person as the date nears, and closure with evidence. A person who remembers all of that is not a system, however good they are, because there is no independent way to notice what they missed. The goal is not to replace them. It is to stop making them the only backup.
Key takeaways
- A docketing system is a process, not a product and not a person. Software holds dates; the system decides how they get in, who acts, and what happens when nobody does.
- "She has never missed one" is survivorship reasoning. It measures how many near-misses got caught quietly, not how much margin the firm has.
- Administrative errors fell from 30.13% to 23.15% of claims between the ABA's 2011 and 2016 studies as software spread, yet procrastination and failure to react to a calendar rose (ABA via TLIE).
- TLIE's summary is the whole lesson: a good system only avoids claims if it is used properly. Tools do not follow up. People do, and people need structure.
- Administrative and client-relations errors together are over a third of claims, and the ABA calls them uniquely within a firm's control (2016-2019 Profile, via WSBA).
- Documenting the docket is a retention benefit, not an insult. It is what lets your best employee take a real vacation.
I have had this conversation in a dozen firms and it always runs the same way. I ask how deadlines get tracked. The owner glances toward the door and says, essentially, "Denise handles it." Denise has been there eleven years. She knows which judge's clerk actually answers the phone, which clients need three reminders, and which filing takes longer than anyone budgets. She has never dropped a date. And when I ask what happens when Denise is on vacation, the room gets quiet, because everybody already knows the answer and nobody has wanted to say it.
So to be clear about who the villain is here: it is not Denise. Denise is the reason the firm has survived this long without a system. The problem is a firm that mistook her competence for infrastructure, and in doing so quietly assigned one employee the job of being the last line of defense against a malpractice claim. That is too much to ask of anyone, and it is a business risk sitting in plain sight.
What a docketing system is, and what a person is
Definitions first, because the phrase "docketing system" gets used to mean three different things and the confusion is load-bearing.
It is not software. Clio, Docketwise, MyCase, and Smokeball all have calendaring features, and a firm can own any of them and still have no docketing system. It is not a calendar either, because a calendar is a display of dates somebody already entered correctly. A law firm docketing system is the documented process plus the shared record: the rule that says a notice becomes an entry the day it arrives, the reference back to the source document, the one named owner, the escalation that fires when the owner goes quiet, the independent review, and the closure with evidence. Those rules exist outside any individual's head, or they do not exist.
Now put a person where the system should be. A skilled paralegal genuinely performs every one of those functions. The difference is not capability. It is observability. When a system misses something, the miss is visible: an item sits unowned, an escalation fires, a review surfaces a gap. When a person misses something, the miss is invisible until its consequence arrives, because the only record of what should have happened was in the same head that forgot.
The fix makes the invisible visible. The same docket, on a shared board, gives every deadline a named owner and a second observer, so a miss is something the firm can see, not something only one person could have caught.
| Matter # | Deadline | Owner | 2nd observer | Alarm | Status |
|---|---|---|---|---|---|
| M-2214 | SOL, PI claim | AR | JC | 7d | Observed |
| M-2955 | USCIS RFE response | AR | none | 1d | No second observer |
| M-1876 | Answer to complaint | DP | AR | 3d | Observed |
| M-3081 | Master hearing | AR | JC | 14d | Observed |
| M-4402 | Appeal window | AR | none | 2d | Single point of failure |
The three jobs memory is doing invisibly
If you want to replace a dependency with a system, you have to know what the dependency was actually doing. Institutional memory in a docket performs three distinct jobs, and firms usually only think about the first.
- Recognition. Knowing that this document, among the day's mail, contains a date that matters, and which date it is. This is the highest-skill part and it is partly legal judgment, which is why the attorney confirms it. A system supports recognition with a capture checklist by notice type; it does not automate the judgment.
- Prioritization. Knowing that a response window with a client who never sends documents on time needs to start three weeks earlier than one with a responsive client. This is pure experience, and it is the part most firms assume cannot be written down. It can. It becomes a lead-time rule and an internal target date that sits ahead of the true deadline.
- Follow-through. Remembering, on the right day, without being asked, to chase the thing that has not arrived. This is the part that is genuinely unreasonable to ask of a human under load, and it is the part a system does better than any person, because escalation does not get busy.
Written out like that, the path forward is obvious. Keep the human doing recognition, with attorney confirmation. Convert prioritization into explicit lead-time rules. Hand follow-through to the machine entirely. Nobody loses status in that arrangement; the person keeps the judgment work and sheds the anxiety work.
Why "she has never missed one" is the risk, not the reassurance
This is the argument I most often have to make twice, so let me make it carefully.
A firm with no misses in eleven years has two possible explanations, and they look identical from the outside. Either the process has real margin, or one person has been absorbing every near-miss quietly and the firm has been lucky about which weeks were busy. Nothing in the outcome distinguishes them. What distinguishes them is whether anyone can tell you how close the last near-miss got, and in a memory-based docket nobody can, because near-misses in that model are not events. They are a Tuesday.
The claims data points at exactly this seam. As calendaring and case management software spread through the profession, administrative errors fell from 30.13% of claims in the ABA's 2011 study to 23.15% in 2016. Genuine progress. But inside the scheduling categories, two moved the wrong way: procrastination in performing services and failure to react to a calendar entry both rose. The dates were stored. Somebody saw the reminder. The work still did not happen.
That is the mechanical reason a person cannot be the system. The failure mode is not "forgot the date." It is "saw the date, was underwater, intended to come back, and no second signal ever arrived." A human with too much on cannot escalate to themselves.
The part nobody says out loud
Everything above is a risk argument, aimed at owners. Here is the argument I think matters more, and it is about the person in the chair.
When one employee is the docket, that employee never fully clocks out. They check email on vacation, because they know nobody else is watching the response windows. They come in sick during a filing crunch. They feel a low background dread every time they take a day, and if something does slip while they are away, they will privately believe it was their fault for leaving. I have watched people carry that for years and describe it as normal.
None of that is generosity the firm earned. It is an unpaid liability the firm is running on, and it has predictable consequences: burnout, resignation at the worst possible moment, and the institutional amnesia that follows when eleven years of undocumented process walks out the door. If you want to keep your best administrator, one of the most valuable things you can do is build the system that makes them replaceable for two weeks in August. That is not a threat to their job. It is the difference between being valued and being trapped.
Say that out loud when you introduce the project, because the alternative reading is available and it stings. "We are documenting this so you can take a real holiday" lands very differently from "we are systematizing your role."
The free Footing Assessment scores your deadline, intake, and communication systems in about three minutes, and surfaces where a single person is the only observer. Matter numbers and metadata only, no privileged content.
Take the Footing Assessment →How to externalize it in a week
The work is smaller than it sounds, and the sequence matters mostly for political reasons: the person who holds the knowledge has to be the author, not the subject.
| Day | What happens | Why it works |
|---|---|---|
| 1 | The person who runs the docket lists every recurring deadline type they handle, by notice type. | Starts from their expertise, not an outside template. It also reveals categories nobody else knew existed. |
| 2 | For each type, write the lead time they actually use and why. | This converts invisible prioritization into a rule. "Start three weeks early on slow-document clients" becomes a field. |
| 3 | Move every open deadline into one shared record with a named owner. | Single-point capture. Now a second person can see the whole board for the first time. |
| 4 | Configure tiered escalation, and test it on a fake deadline. | Hands follow-through to the machine. Untested escalation is a belief, not a control. |
| 5 | They write the two-page procedure, with their name on it as author. | Authorship makes it accurate and makes it theirs. A document written about someone gets quietly ignored. |
One test tells you whether it worked, and you can run it deliberately rather than waiting for illness to run it for you. Pick a week, have that person genuinely step back from the docket, and see what the system surfaces without them. Anything that only they would have caught is a gap you now know about while the stakes are a controlled experiment instead of a real deadline. The full architecture behind this sits in our pillar on law firm deadline management, and the punchy build is in the deadline system a missed date can't survive.
What you are buying with a week of work is not efficiency. It is the ability to answer a question that currently has no answer: if the person who holds your docket were unavailable tomorrow, how would the firm find out what was due Friday?
Where to go next
- The Law Firm Deadline System: The Complete Guide live
The five components a docketing system needs, and how to build each one.
- How to Build a Deadline System a Missed Date Can't Survive live
The owner-and-escalation build, in the tools your firm already runs.
- How Often Should a Lawyer Update Their Client? live
The cadence that stops a stalled document chase from becoming a deadline risk.
- Legal Malpractice Statistics: What the Data Actually Says live
The sourced numbers behind the administrative third.
- The Paralegal Career Case for Systems: Become the Firm's Administrator, Not Its Memory live
Being the person who remembers everything feels like job security. It is actually a career.
Find out what only one person knows
Turn a dependency into a system.
Take the free Footing Assessment and it finds your single points of failure: which deadline types have no second observer, and what would go unnoticed next week. Or book the thirty-minute Risk Audit for a read on your exposure. A diagnosis, not a pitch.
Frequently asked questions
What is a law firm docketing system?
A law firm docketing system is the documented process and shared record that captures every deadline from an official notice or docket, assigns a named owner, escalates as the date approaches, and closes with evidence. It is a process, not a product and not a person. A calendaring tool holds the dates; the docketing system is the set of rules that determine how dates get in, who acts on them, and what happens when nobody does.
Why is relying on one person for docketing risky?
Because a single person is a single point of failure regardless of how good they are. Illness, vacation, a family emergency, a competing filing crunch, or resignation all remove the firm's only copy of the process at once. The risk is not the person's competence; it is that the firm has no independent way to notice when something has been dropped.
Is docketing the paralegal's job or the attorney's responsibility?
Both, at different levels. A paralegal or administrator commonly performs the operational work of capturing and tracking dates. The professional responsibility for the docket remains with the attorney, who identifies and confirms every deadline from the official notice or rule. A good system makes that division explicit rather than leaving it to habit.
What should a docketing system include?
At minimum: a capture rule stating that dates are entered the day a notice arrives, a reference to the source document, one named owner per deadline, tiered reminders that escalate to a second person, an independent review of upcoming deadlines by someone other than the owner, closure with evidence, and a written procedure a new hire could follow.
How do you document a docketing process without offending the person who runs it?
Frame it as capturing expertise rather than replacing it, and have the person who runs the docket author the documentation. They are the subject-matter expert, the document should carry their name, and the outcome they get is the ability to take a vacation without carrying the firm's risk on their phone.
- Scheduling Errors and Legal Malpractice, Texas Lawyers' Insurance Exchange, presenting ABA claims data (failure to react to a calendar 1.27% and procrastination 4.95% for 1996-1999; administrative errors 30.13% in 2011 to 23.15% in 2016). tlie.org
- ABA Standing Committee on Lawyers' Professional Liability, Profile of Legal Malpractice Claims (2011, 2016, 2016-2019). americanbar.org
- Risk Management by the Numbers, Washington State Bar Association. nwsidebar.wsba.org