Every deadline in a law office involves three separate jobs. Someone has to work out the date. Someone has to remember it. And someone has to do the thing the date is for. Software is very good at the middle job, adequate at supporting the first, and no use at all for the third. Most missed deadlines in small firms happen because those three jobs were never separated, so nobody noticed that the reminder went out and the work did not.
This post is a practical map of which deadline reminders a firm of two to ten people can automate today, which parts of the process still need a person, and how to set the two up so they support each other rather than generate noise. It is written for the paralegal or office manager who runs the docket in practice, whatever the title on the door says, and it assumes ordinary case management software, not an enterprise docketing department.
Why the reminder is the easy part
The American Bar Association’s most recent Profile of Legal Malpractice Claims, covering 2016 through 2019, found that over one-third of reported claims arose from administrative errors, such as failing to calendar a deadline properly, or from client-relations failures. The ABA’s own commentary on the diligence rule puts it more bluntly: “Perhaps no professional shortcoming is more widely resented than procrastination.”
Read those two together and the shape of the problem is clear. The failure is rarely that nobody knew the date. It is that the date was entered wrong, entered in one place and not another, or entered correctly and then nobody acted on the reminder. Automation fixes the second of those completely and the third partly. It does nothing for the first, and if the firm treats it as if it does, the software becomes a very reliable way of reminding everyone about the wrong date.
So “can we automate deadline reminders?” is the wrong question; the answer is yes for most of them. The better question is which step in each deadline’s life a machine should own and which step a named person should own. The rest of this post answers that for the deadlines a small firm sees every week.
What a small law firm can automate today
Everything in this section is standard in mainstream case management software, including ours. None of it requires a court-rules subscription, a docketing clerk, or custom development. If your current system cannot do one of these, that is worth knowing before you build a manual process around the gap.
Statute of limitations alerts at fixed intervals
The limitations date is the one deadline every personal injury, medical malpractice, and contract matter carries from the day it opens. It belongs in the matter record as a distinct field, not as a calendar entry that can be dragged, and the software should generate alerts from it automatically: typically at twelve months, six months, ninety days, thirty days, and then daily inside the final two weeks. Those intervals should be set once at the firm level, not per matter, so that a new file gets the same coverage as an old one without anyone remembering to add reminders.
Two details matter. First, the alert should go to more than one person, because the file’s paralegal is sometimes on vacation. Second, alerts should not stop when the matter’s status changes to “in suit” until someone confirms the complaint was actually filed and accepted. Status changes are exactly the moments when files get mishandled. Our earlier piece on tracking statutes of limitations in PI firms covers the intake side of this in more depth.
The daily agenda email
The single most effective automation in a small firm is also the least glamorous: an email, generated overnight, listing every deadline, event, and task due today and in the next seven days, per person and for the office as a whole. It is the thing that catches the deadline nobody opened the software to look at. It works because it arrives in the one tool everyone already reads first thing in the morning.
The agenda should be per-user by default, with an all-office version going to the supervising attorney and whoever runs the docket. If your software can only produce one office-wide list, it still works; it just gets skimmed rather than read, and skimming is where things slip.
Calendar entries created from case events
When a deposition is scheduled, a hearing is set, or a discovery response date is entered on the matter, the calendar entry should be created by the software, on the office calendar and on the calendars of the people assigned to that matter. Typing the same date into three calendars by hand is where transposed digits and “was that the 14th or the 24th?” come from. One entry, propagated automatically, is one fewer place to be wrong.
The converse also matters: a case event with no calendar entry should be impossible. If the software lets someone record a hearing date in a note field where no reminder will ever fire, that path needs to be closed by policy.
Scheduled letters and follow-ups tied to case events
Much of the work around a deadline is correspondence that follows a pattern. Thirty days before trial, the client gets a preparation letter. Thirty days after a records request goes out with no response, a follow-up goes. Ten days before a deposition, the witness gets a confirmation. Event automation handles all of this: the rule is defined once (event type, offset, template, recipient), and the letter is generated and sent, by email or fax, when the condition is met, or queued for a person to review before sending.
The queue-for-review option is the right default for anything a client or opposing counsel will read. Fully automatic sending is fine for internal reminders and for routine follow-ups with records custodians.
Task due dates and escalation
Deadlines decompose into tasks: draft the response, get it reviewed, file it, serve it, confirm service. Each task should carry its own due date, set back from the deadline, and the software should remind the assignee as the date approaches and notify the supervising attorney when it passes without completion. That escalation step is the part small firms most often leave out, and it is the part that turns a reminder system into a safety net. A reminder that only the person who missed it can see is a reminder that can be missed twice.
Client appointment and document reminders
Where the firm uses a client portal, reminders about upcoming appointments, documents the client owes, or a deposition date can be sent through it as messages with read receipts, so the file shows that the reminder went out and that the client opened it. Where there is no portal, the same reminders go out as scheduled letters or emails. Either way, the point is that “did anyone tell the client?” becomes a question the file can answer.
What still needs a person
The items below are not automation gaps. They are places where the decision is a legal judgment or a fact-finding step, and a reminder system that pretends otherwise is more dangerous than no system at all. In each case, the software’s job is to make sure the person is prompted and that what they decide is recorded.
Calculating the date under the rule that actually applies
Deadline arithmetic is not as simple as adding days. Under Federal Rule of Civil Procedure 6(a), the day of the triggering event is excluded and every following day counts, weekends and holidays included. If the last day lands on a Saturday, Sunday, or legal holiday, the period runs “until the end of the next day that is not a Saturday, Sunday, or legal holiday.” Rule 6(d) adds three days after certain kinds of service. State courts have their own versions, some counting business days rather than calendar days, and local rules and individual judges’ standing orders can shorten or lengthen what the general rule provides.
Software can store the date and remind everyone about it. Whether the date is right depends on someone having identified the governing rule and applied it, and that step should be visible in the file: who calculated it, under which rule, on what basis. Firms with the budget buy a court-rules calendaring service for this. Firms without one have the paralegal calculate, the attorney confirm, and both initial the entry. Either way, the confirmation is a human act, and the reminder system should not fire until it has happened.
Deciding what the trigger event was and when it happened
“Thirty days from service” is only useful if everyone agrees when service was complete, and that can turn on how it was made, whether it was accepted, and what the return says. “Two years from the date of injury” assumes the date of injury is known, which in a delayed-discovery case it may not be. The trigger is a factual and sometimes legal determination. Enter it as a specific date with a note explaining the basis, and treat any change to it as a change to every deadline that depends on it.
Updating the system when a court order moves the dates
A continuance, an amended scheduling order, or a stay changes several deadlines at once. The software cannot read the order. A person has to, and then has to update every dependent date and confirm that the reminders reset. In practice this is the single most common way a well-run docket goes wrong: the trial date moves, the trial date is updated, and the pretrial deadlines keyed to the old trial date are left where they were. Make “update all dependent dates” an explicit task on the matter whenever an order comes in, assigned to a named person, with the supervising attorney confirming.
Deciding whether to ask for more time
When a reminder shows a deadline is at risk, the question of whether to seek an extension, from opposing counsel or the court, is a strategic and professional-responsibility judgment for the attorney. The reminder’s job is to surface the risk early enough that the choice exists. A thirty-day alert gives options; a two-day alert gives a motion.
Telling the client
ABA Model Rule 1.4 requires lawyers to keep clients reasonably informed about the status of their matters. When a deadline moves, or is met, or is at risk, deciding what to tell the client and how is the attorney’s call. Software can draft the letter from a template and record that it was sent. It should not be the one deciding whether the client hears about it.
The weekly docket review
Model Rule 5.3 makes lawyers responsible for the work of the nonlawyers they supervise, and that includes the docket. The practical form this takes in small firms is a short weekly meeting, thirty minutes at most, where the supervising attorney and the person running the docket walk through everything due in the next thirty days and every matter with no activity in the last thirty. The agenda email makes this meeting fast. It does not replace it. A system that is never reviewed by the person responsible for it drifts, and the drift is invisible until something is missed.
A reminder schedule for a firm without a docketing clerk
The table below is a starting configuration for a two-to-ten-person firm. The intervals are conventions, not rules, and any firm should adjust them to practice area and jurisdiction. What should not change is the last column: every deadline type has a named person who confirms the date before the automated reminders begin.
Three things this schedule assumes. Reminders go to more than one person for anything court-facing. Internal task reminders escalate rather than repeat, so the attorney hears about a missed task once, from the system, rather than about a missed deadline later, from the court. And the daily agenda is the backstop under all of it, so a reminder that was dismissed without action shows up again the next morning.
Setting it up without creating noise
The failure mode of automated reminders is not too few; it is too many, of the wrong kind, until people stop reading them. Some things that keep the signal usable in small firms.
Keep one system of record. If deadlines live in the case management system and also in personal Outlook calendars and also in a shared spreadsheet, the three will disagree within a month. Pick the case management system, keep the office and personal calendars inside it, and forbid direct entry anywhere else.
Separate reminders from alerts. A reminder is a heads-up on a normal schedule; an alert means something is wrong (a task is overdue, a limitations date is inside thirty days with no complaint filed). They should look different, arrive differently, and go to different people. When everything is an alert, nothing is.
Name an owner for the agenda. Someone reads the office-wide agenda every morning and acts on anything that looks off. In most small firms this is the senior paralegal or the office manager. It takes ten minutes and it is the highest-value ten minutes in the day.
Review the configuration quarterly. Reminder intervals that made sense for the practice two years ago may not fit the caseload now. Look at which reminders get dismissed without action; those are the ones to change or remove.
For the broader practices around centralizing and reviewing deadlines, our guide to managing legal deadlines covers the process side; this post is about where the automation boundary sits.
Frequently asked questions
What deadline reminders can law firms automate?
Statute of limitations alerts at fixed intervals, a daily agenda email of everything due, calendar entries created automatically from case events, scheduled letters tied to case events (a trial-preparation letter thirty days out, a records follow-up after thirty days of silence), task due-date reminders with escalation to the supervising attorney, and client reminders sent through a portal or by letter. All of these are standard in mainstream case management software.
Can software calculate legal deadlines automatically?
Some systems and dedicated court-rules services compute dates from a trigger event under a rule set. Even where that exists, a person should confirm the governing rule, the trigger date, and any local rule or standing order that modifies the result, and that confirmation should be recorded in the file. Where the software only stores dates, the calculation is done by the paralegal and confirmed by the attorney before reminders begin.
How far in advance should statute of limitations reminders be set?
A common configuration is twelve months, six months, ninety days, thirty days, and then daily in the final two weeks, sent to at least two people. The intervals matter less than two rules: set them once at the firm level so every matter gets the same coverage, and do not let reminders stop on a status change until someone confirms the filing was made.
How do small firms track deadlines without a docketing clerk?
By making the case management system the single place deadlines live, letting it create calendar entries and reminders automatically, naming one person to read the office-wide daily agenda each morning, and holding a short weekly review between that person and the supervising attorney covering everything due in the next thirty days.
Who is responsible when a paralegal misses a deadline?
Under ABA Model Rule 5.3, a lawyer with supervisory authority over nonlawyer staff must make reasonable efforts to ensure their conduct is compatible with the lawyer’s professional obligations, so responsibility for the docket rests with the supervising attorney regardless of who entered the date. That is why the weekly docket review and the “who confirms” step exist. Whether and how the rule applies in a given situation is a question for the attorney and, where relevant, the state bar.
What is the difference between a reminder and an alert?
A reminder is routine notice on a planned schedule (a hearing is in seven days). An alert signals that something is outside the plan (a task is overdue, a limitations date is within thirty days and no complaint has been filed). They should be visually distinct, delivered differently, and routed to different people, so that alerts are never lost in the daily stream of reminders.
Deadline tracking that runs itself, reviewed by people who know the case
Everything in the “automate” column above is built into The Legal Assistant: limitations alerts, the nightly agenda email, automatic calendar entry from case events, scheduled letters by email or fax, and task reminders. The Personal Injury Assistant adds the limitations tracking and records-request follow-ups a PI docket needs. Free trial, no contract.
This article is general information about law office workflow and does not constitute legal advice. Rules for computing time, statutes of limitations, and professional obligations vary by jurisdiction and change over time; the references to the Federal Rules of Civil Procedure and the ABA Model Rules are illustrative. Deadline calculations and decisions about extensions, client communication, and supervision are made by the responsible attorney under the rules of the relevant jurisdiction.