If you own the calendar for a litigation team, your real job is not remembering dates. It is building a system where a deadline cannot quietly go unrecorded, get miscalculated, or sit on a calendar that nobody acts on. Good legal calendaring is boring, repeatable and checked twice, and that is exactly the point.
Most missed deadlines are not memory failures. They trace back to one of three gaps: the triggering document never reached the person who dockets, the computation used the wrong rule or ignored an order, or the reminder fired and nobody owned the work. This guide builds a workflow around those gaps, using the Federal Rules of Civil Procedure as the reference point. State rules and local practices differ, sometimes significantly, so treat every federal default below as something to verify against the rules that govern your matter.
Why do law firms miss court deadlines?
Deadlines get missed at entry, at calculation, or at follow-through. A dependable system puts a control at each stage instead of relying on one careful person.
- Entry failures. An order announced from the bench, an electronic filing notice routed to a former associate’s inbox, or discovery requests mailed to an old address. The trigger exists; the calendar never hears about it.
- Calculation failures. Counting from the wrong day, missing the extra days added for certain service methods, forgetting a court holiday, or applying a federal default that a scheduling order changed.
- Follow-through failures. The deadline is on the calendar, but the only reminder lands on the due date, belongs to someone on leave, or was deleted when the hearing moved.
ABA Model Rules 5.1 and 5.3 expect lawyers with managerial authority to have reasonable measures in place for the work of lawyers and staff. Your system is part of how the firm meets that expectation, but the responsible attorney always owns the final computation.
How do you calculate a court deadline correctly?
Every deadline is a calculation with four inputs: a trigger event, a period, a counting method, and any adjustment for how service was made. Record all four so anyone can recheck the math.
Under Federal Rule of Civil Procedure 6(a), a period stated in days is computed this way:
- Exclude the trigger day. Day one is the day after the event, whether that is service, entry of an order or a filing.
- Count every day. Intermediate Saturdays, Sundays and legal holidays all count.
- Include the last day. If it falls on a weekend or legal holiday, the period runs to the next day that is not one. If the clerk’s office is inaccessible on the last day, Rule 6(a)(3) extends the period as well.
- Add days for certain service methods. When the period runs from being served and service was by mail, by leaving the paper with the clerk, or by other consented means, Rule 6(d) adds three days after the period would otherwise expire. Electronic service no longer earns those three days in federal court.
- Confirm when the last day ends. For electronic filing, Rule 6(a)(4) ends the day at midnight in the court’s time zone unless a statute, local rule or order says otherwise.
When a deadline is measured backward from an event, such as a paper due a set number of days before a hearing, Rule 6(a)(5) says to keep counting backward if the last day lands on a weekend or holiday. That moves the deadline earlier, not later, and it is one of the most common computation errors on any docket.
Common federal triggers and defaults
| Trigger | Typical federal default | Rule |
|---|---|---|
| Service of summons and complaint | Answer or Rule 12 motion within 21 days | FRCP 12(a)(1)(A)(i) |
| Timely waiver of service | Answer within 60 days after the request was sent (90 if sent outside the U.S.) | FRCP 12(a)(1)(A)(ii) |
| Interrogatories, document requests or requests for admission served | Responses or objections within 30 days | FRCP 33, 34, 36 |
| Rule 26(f) conference held | Initial disclosures within 14 days | FRCP 26(a)(1)(C) |
| Trial date set | Pretrial disclosures at least 30 days before trial; objections within 14 days after | FRCP 26(a)(3)(B) |
| Entry of judgment | New trial or alter/amend motion within 28 days; notice of appeal generally within 30 days | FRCP 59; FRAP 4(a)(1)(A) |
What does a reliable calendaring workflow look like?
A reliable workflow moves every trigger through the same path on the same day, with a second set of eyes before the entry goes live.
- Centralize triggers. Route filing notices, mailed service, emailed discovery and hearing outcomes to one docketing inbox that two people monitor. Ask attorneys for a two-line note after every hearing: what was ordered, and by when.
- Docket the same business day. Anything received today is computed and entered today. A stack of “to docket” mail is itself a risk.
- Count from service, not receipt. For mailed papers, service is complete on mailing under Rule 5(b)(2)(C), so the clock starts before the envelope reaches your desk.
- Verify independently. A second person recomputes from the trigger document without looking at the first computation. Disagreements go to the responsible attorney.
- Set the owner and reminder chain. Assign a responsible attorney and a backup, with reminders sized to the work involved.
- Confirm to the attorney. Send the computed date with the rule basis so the attorney can catch errors from the substantive side.
- Close with proof. Mark a deadline complete only with a file-stamped copy, a service confirmation, or a note that the task was intentionally dropped.
Template: docket entry
Matter: [Client] v. [Opposing party], [case number], [court]
Deadline: Responses to Defendant’s First Requests for Production
Trigger: Requests served by mail on [mailing date]; received [date]
Rule basis: FRCP 34(b)(2)(A), 30 days, plus FRCP 6(d), 3 days for mail service
Computed due date: [date]. Computed by [initials]; verified by [initials]
Do-date: Draft responses to attorney by [date]
Reminders: 21, 10, 5 and 2 days before the due date
Owner / backup: [attorney] / [attorney]
Which deadlines do firms forget to calendar?
The deadlines that slip are often the internal, derivative and client-facing dates that never got their own entry.
- Limitations and notice-of-claim deadlines spotted at intake, before anything is filed
- Objections to pretrial disclosures, exhibit and witness list exchanges, and deposition designations
- Expert disclosures (in federal court, absent an order, at least 90 days before trial, with rebuttal disclosures within 30 days after the other side’s)
- The discovery cutoff, plus the last day to serve requests so responses come due before it (check how your scheduling order defines completion)
- Meet-and-confer steps that must happen before a discovery motion; the ESI meet-and-confer checklist covers the early conference
- Mediation statements and settlement conference submissions
- Proposed orders and transcript requests due after a hearing
- Client deliverables: records the client must send and documents the client must sign
Calendar backward from every hearing
Court deadlines say when something is due, not when your team should start. For each hearing, build a backward schedule of internal targets, adjusted to the court’s exchange deadlines:
| When | Internal target |
|---|---|
| 21 days out | Request missing records from the client; confirm witnesses; issue and serve subpoenas |
| 14 days out | Pull exhibits, draft the exhibit list, flag authentication gaps |
| 10 days out | Produce message logs and summaries; attorney review begins |
| 7 days out | Binder draft to the attorney; exchange copies if the order requires |
| 3 days out | Final copies for the court, the other side and witnesses; remote-hearing uploads |
| 1 day out | Logistics check: courtroom, technology, client arrival time |
The hearing exhibit binder checklist covers what the binder itself needs, and the paralegal trial prep checklist extends this schedule for trial.
How should deadline reminders be structured?
Reminders should be sized to the work, sent to more than one person, and tied to a do-date. A reminder that fires the morning a brief is due is a notification, not a control.
- Calendar the do-date. For a response brief, the do-date is when research and drafting must start. The due date stays on the calendar, but the do-date drives the work.
- Use a chain, not a single alert. A long-lead deadline might carry reminders at 30, 14, 7, 3 and 1 days; a short one at 5, 2 and 1. Pick intervals based on how long the work takes.
- Escalate silence. If the owner hasn’t confirmed progress by the midpoint reminder, the docketing lead checks in, then tells the supervising attorney.
- Keep a team view. A shared report of the next 30 days, reviewed in a short weekly meeting, catches deadlines owned by someone who is out.
What edge cases cause the most misses?
Errors cluster around a few situations. Build each into your verification step.
- Holidays that differ by court. Rule 6(a)(6) covers federal holidays and, for periods counted forward, holidays declared by the state where the district court sits. State courts keep their own lists, and courts close for weather and local events.
- Bench rulings. A judge says “ten days” from the bench and the written order enters later. Docket the earlier possible date until the attorney confirms which one starts the clock.
- Amended scheduling orders. When an order changes one date, re-review every deadline in the matter. Derivative dates hide in paragraphs nobody rereads.
- Earlier filing cutoffs. Some courts and judges set cutoffs before midnight or require courtesy copies by a set hour.
- Staff turnover. Reassign every open deadline a departing person owned on their last day, not when the next reminder bounces.
How do you audit a legal calendar?
An audit compares the calendar with what the court docket and the file actually require. Schedule it; don’t wait for a near miss.
- Weekly. Review the next 30 days with each responsible attorney: owner, status and do-date.
- Monthly. Reconcile each active matter’s court docket against your calendar. Every order should map to entries, or to a note that it created none.
- Quarterly. Recompute a sample of deadlines from scratch, and confirm your software’s rule sets were updated after amendments. Federal rule amendments usually take effect on December 1.
- At closing. Confirm nothing remains open on a closed matter, including post-judgment and appeal dates.
Software helps, but it only computes from what someone entered, and it can’t read a judge’s standing order. If your hearing prep runs in CourtBriefly, hearings and tasks sit on the matter next to the evidence and binders, and its API and MCP integrations can organize hearings and tasks programmatically, so dates already in another system don’t have to be retyped. The rule computation itself still belongs in your docketing process, under the responsible attorney’s review. For the habits that keep the docketing desk from becoming a bottleneck, see paralegal productivity tools and habits.
