Deadline management: what should software decide?

Software should decide only what follows mechanically from confirmed inputs: the computed date, who gets reminded, when to escalate and what gets logged. Everything that needs an interpretation of facts or rules belongs to a person.

The split is easiest to see as a table. On the left are tasks where a computer is more reliable than a busy person. On the right are tasks where a computer only looks reliable.

Calendaring stores a date a person has already worked out; rules-based docketing computes a chain of dates from a trigger event using a maintained set of court rules. The first automates memory, the second automates arithmetic.

Rules-based docketing removes counting errors, but it moves the risk to the inputs: the jurisdiction, the trigger, the service type. Some practice management systems expose it. The Clio Manage API reference, for example, lists court rules endpoints for jurisdictions, triggers, service types and matter dockets, including an operation to preview calendar dates for a docket. The reference does not describe how the dates are computed or which plan is required, so check that with the vendor.

Whatever computes the date, a person still confirms the trigger. A docket built on the wrong service type is exact and wrong.

Rule 6(a)(1) of the Federal Rules of Civil Procedure excludes the day of the triggering event, counts every day including weekends and legal holidays, and includes the last day unless it is a Saturday, Sunday or legal holiday. In that case the period runs to the next day that is none of those.

Example, for illustration only: a 14-day period is triggered on Thursday 12 November 2026. Counting from the next day, day 14 is Thursday 26 November, which is Thanksgiving, a legal holiday under Rule 6(a)(6). The deadline therefore moves to Friday 27 November. If the state where the district court sits has declared that Friday a holiday, Rule 6(a)(6) can move it again, to Monday 30 November.

Three inputs change the result and are easy to get wrong in software. Rule 6(d) adds 3 days after the period would otherwise expire when service is made by certain methods such as mail, so the service method matters. Rule 6(a)(3) extends the deadline when the clerk's office is inaccessible on the last day. Local rules and court orders can set their own periods. None of this is legal advice; verify every computed date against the rules that govern the case.

Under CPR 2.8, a period expressed in days is counted in clear days, which excludes the day the period begins and, where the end is defined by an event, the day of that event. Where the period is 5 days or less, Saturdays, Sundays, bank holidays, Christmas Day and Good Friday do not count.

Two further rules matter for software. CPR 2.8(5) makes an act at the court office in time if done on the next open day when the office is closed on the last day. CPR 2.9 asks that the last date for compliance be expressed, wherever practicable, as a calendar date with a time of day.

Deemed service is where most automated calculations fail. Under CPR 6.14 a claim form served in the UK is deemed served on the second business day after the relevant step. Under the table in CPR 6.26, an email sent on a business day before 4.30pm is deemed served that day, and otherwise on the next business day. If the system does not know the exact send time or method, it should flag the deadline, not guess.

Deadline failures are a recurring share of malpractice claims. The ABA's Profile of Legal Malpractice Claims 2020 to 2023, published in September 2024, analyzes US and Canadian claims reported by participating insurers; the figures are in the paid report. Writing for the insurer ALPS in July 2026, risk manager Mark Bassingthwaighte reports that it puts administrative errors, such as failing to calendar properly and failing to react to the calendar, at nearly 25% of all claims.

The older ABA profile for 1996 to 1999, as cited by the Texas Lawyers' Insurance Exchange, listed failure to calendar a known deadline as the primary cause of 7.03% of claims and failure to react to a calendared date as 1.27%. The same article recommends separate calendar entries by attorney and assistant as a check, and reminders at several intervals before limitation dates.

Both figures describe administrative failures: a deadline that was not entered, or was entered and not acted on. Entry checks, reminders and escalation are the parts of the problem software handles well.

Safe deadline automation proposes, reminds and escalates, and never closes a deadline without a named person confirming it. In Elevate Consulting's builds, deadlines with an unclear service date are flagged instead of calculated.

Deadline automation is the wrong answer when the firm has no agreed manual process yet, because software then encodes the confusion. Decide first who enters, who checks and who closes a deadline.

It is also not yet worth it for a practice with very few court deadlines, where a disciplined shared calendar and a second person checking may be enough. Keep your existing calendar running in parallel during the first weeks of any new system, and compare both before you switch.