Jump to section
Every lawyer who has ever missed a deadline remembers the exact moment they found out. It arrives as a phone call, an email, a colleague's face going still. And the first thing almost everyone thinks is some version of: how could I let this happen? That instinct, to treat a blown limitation period or a missed filing as a personal failure of care, is the single biggest reason firms keep missing them.
Missed deadlines are not a discipline problem. They are a systems problem. A good lawyer working inside a bad system will eventually miss something, and no amount of conscientiousness closes that gap. If you want a docket that holds, you stop asking people to try harder and you start building something that catches errors before they reach a client's file.
Deadlines Are Not a Memory Problem
The lawyers who miss dates are not lazy or careless. Usually they are the busiest people in the office, carrying too many open matters and too many moving parts to hold in one head. That is the point. Human memory is a terrible place to store a limitation period. It is lossy, it is easily overwritten by the next urgent thing, and it fails silently. You do not get an alert when you forget.
So the question is not "how do I remember better." It is "how do I build a system that does not depend on anyone remembering at all." Once you reframe it that way, the whole conversation changes. You stop looking for more diligent people and start looking for better plumbing.
Note. A defence grade docket is one you could hand to a stranger. If a new hire could open your calendar and correctly tell you every critical date on every file without asking a soul, your system works. If they would have to interview three people first, it does not.
A Single Source of Truth for Every Date
The most common failure mode I see is scatter. The trial date lives in one lawyer's Outlook. The service deadline is on a sticky note. The limitation period is in the intake memo nobody reopened. The examination is in the assistant's head. When a date exists in four places, it effectively exists in zero, because no one place is authoritative and everyone assumes someone else is watching.
Pick one system and make it the truth. Every deadline, court date, limitation period, and internal milestone goes there and only there. Not "mostly there." Everywhere. The moment you allow a second unofficial list to grow, you have reintroduced the scatter you were trying to kill. This is why a shared, matter linked calendar beats a personal one: it is not tied to whoever happened to open the file first, and it survives that person going on vacation, changing firms, or forgetting.
This is also where practice management tooling earns its keep. When deadlines live inside the same matter record as the parties, the documents, and the billing, they stop being loose objects that can drift. A1 CMS keeps the docket attached to the file so a date cannot quietly detach from the matter it belongs to. Whatever you use, the principle holds: one place, no exceptions.
Two Sets of Eyes on Every Entry
Here is the uncomfortable part. The person who calculates a deadline is the worst person to check it. They already believe they got it right, so they read their own math and see what they expected to see. Anchoring is not a character flaw, it is how brains work.
The fix is structural, not motivational. Every critical date gets entered by one person and confirmed by a second before it is treated as final. It does not have to be slow. A calculated limitation period, for example, can be entered with the trigger date and the rule attached, and a second person confirms the trigger and the count. The reviewer is not asking "did you try hard." They are asking "show me the date you started from and the rule you applied."
The strongest firms treat a deadline entry the way a good newsroom treats a fact: it is not real until a second person has independently confirmed the source.
This same discipline is why a careful file opening process matters so much. The first hours of a matter are when the most important dates get set, and it is exactly when everyone is moving fast. Build the second look in at the front, and you catch the errors that would otherwise compound for years.
Building in Redundancy That Actually Fires
A reminder that only fires once is not a safety net, it is a coin flip. Real redundancy means a date announces itself more than once, through more than one channel, to more than one person, on a schedule that gives you room to actually act.
My rule of thumb for anything consequential:
- A far reminder weeks out, when you can still gather documents, retain an expert, or brief a client without panic.
- A near reminder days out, aimed at whoever is doing the work.
- A backstop reminder that goes to a supervising lawyer or a docketing coordinator, not the file handler, so the alert reaches someone other than the person responsible for the deadline.
The backstop is the piece firms skip, and it is the piece that saves you. If every alert routes back to the one overloaded person who is already behind, you have redundancy on paper and a single point of failure in reality. Redundancy only counts when the copies land on different desks. The way you handle limitation reminders across the docket is the clearest test of whether your system is genuinely layered or just noisy.
Warn. Beware the reminder that everyone has learned to dismiss. If your alerts fire so often, or so vaguely, that people clear them on reflex, your redundancy has quietly turned into background noise. Fewer, sharper, better routed alerts beat a wall of ignorable ones.
When to Trust the System Over Your Gut
Here is the part that takes real humility. Once you have built a system worth trusting, you have to actually trust it, especially when your instinct disagrees. If the docket says a limitation runs Thursday and your gut says you have another month, the docket wins until you have gone back to the source and proven otherwise. Gut feelings about dates are exactly the input that got firms in trouble in the first place.
This does not mean the system is never wrong. It means the correct response to a hunch is to verify against the rule, not to overrule the calendar from memory. A good docket makes that verification easy: the trigger date, the applicable rule, and who confirmed it should all be one click away. During a monthly file review, you are not re-guessing every date, you are checking that the system's dates still match reality after amendments, adjournments, and new claims.
None of this is glamorous, and that is the point. A solid docketing system is reliable by design. It survives busy weeks, sick days, staff turnover, and the ordinary human fact that even excellent lawyers forget things. If you are curious how the rest of the practice management picture fits together, from intake to review, the practice management writing here and my own other posts keep returning to the same idea: the firms that never miss a deadline are not staffed by superhumans. They stopped relying on humans to remember, and built something that remembers for them.
