Most missed federal deadlines aren’t the dates the court hands you in a scheduling order. They’re the dates the rules imply — the kind that read “Opposition due 14 days after Motion to Dismiss filed” in the FRCP and that nobody calendars because the trigger has to happen first.
DockItFlo’s rules-based deadline engine closes that gap. When the AI reads an incoming ECF notice and detects a triggering filing — a Motion to Dismiss, an entered judgment, a discovery request — the platform automatically computes the resulting deadline under the Federal Rules of Civil Procedure and surfaces it in your review queue with the rule citation, the computed date, and a local-rule warning if applicable.
This article walks through what the engine covers, how it computes dates (it’s harder than counting), why local-rule variance matters, and how it stays current as FRCP amendments take effect.
What the engine covers
The current registry has 45 entries across FRCP Sections 1 through 8: pleadings, discovery initial disclosures, discovery requests, motions practice, judgment and post-trial, appeals, removal and remand, and scheduling and case management. The AI is prompted to recognize a curated set of high-priority triggers first — the rules where a missed deadline matters most:
- Motion to Dismiss filed → Opposition due (14 days, local-rule variant)
- Motion to Dismiss DENIED → Answer due (14 days, FRCP 12(a)(4)(A)) — the one nobody calendars and the one that runs out the soonest
- Motion for Summary Judgment filed → Opposition due (21-28 days, FRCP 56 + local)
- Answer filed → Third-party complaint deadline (14 days, FRCP 14)
- Interrogatories served → Response due (30 days, FRCP 33)
- Requests for Production served → Response due (30 days, FRCP 34)
- Requests for Admission served → Response due (30 days, FRCP 36) — deemed admitted if missed
- Opposing expert disclosed → Rebuttal expert deadline (30 days, FRCP 26(a)(2)(D)(ii))
- Judgment entered → Notice of Appeal deadline (30 days, FRAP 4) — the most consequential miss in federal civil practice
- Judgment entered → Rule 59 motion to alter/amend (28 days, strict, cannot be extended)
Beyond the top 10, the registry covers Rule 14 third-party practice, Rule 15 amended pleadings, Rule 26 expert disclosures and initial-disclosure timing, Rule 30 deposition notice, Rule 37 motions to compel, Rule 45 subpoenas on non-parties, Rule 50 renewed JMOL, Rule 54 attorney’s fees motions, Rule 55 default judgment, Rule 60 motions for relief from judgment, Rule 6(d) mail-rule additions where applicable, and FRAP 4 appellate deadlines.
How the engine reads an incoming notice
When an ECF notice arrives at DockItFlo, the AI extraction step does two distinct jobs in one pass. First, it pulls every concrete date out of the notice body and any PDF attachments — the way it has since day one. Second, it classifies the notice itself: is this notice a triggering filing under one of the rules in the registry?
If yes, the AI emits a trigger with three pieces of information: the trigger type (e.g., motion_to_dismiss_filed), the trigger date (the date the trigger occurred — usually the notice’s filing date), and a confidence score. The platform validates the trigger against the registry, computes the resulting deadline using FRCP Rule 6, and inserts a suggestion into the review queue.
The trigger detection happens at the AI layer. The deadline computation happens deterministically on the server using the rule registry plus a Rule 6 calculator. This separation matters: it means the registry can be updated without re-prompting the AI, the holiday calendar can update annually without changing AI behavior, and a regression in one piece doesn’t take down the other.
FRCP Rule 6: counting days is harder than it looks
The Federal Rules of Civil Procedure have a specific rule about how to count time periods. Rule 6 says:
- The day of the event that triggers the period is excluded — counting starts the next day
- Every day, including weekends and legal holidays, is counted
- If the last day falls 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
- When service is by mail, three days are added to the period before the rollover rule fires
DockItFlo’s calculator implements all of this. The federal holiday list uses observed dates per the OPM rules: when Independence Day falls on a Saturday, federal courts close on the preceding Friday, so the calculator treats that Friday as the holiday and rolls deadlines accordingly. The calendar list is updated annually before the new year so January 1 deadlines compute correctly.
One worked example: a Motion to Dismiss filed on Friday, July 3, 2026 (Independence Day observed, federal courts closed). Opposition is due 14 days later under FRCP 12 plus most district local rules. Naive math says July 17. The calculator excludes the trigger day, counts forward 14 days landing on July 17, checks if July 17 is a business day (yes — it’s a Friday with no federal holiday), and returns July 17. If the trigger had been Friday, July 24, the 14th day lands on Friday, August 7 — still a business day, no rollover. Same period, no rollover noise.
A more interesting case: Notice of Appeal under FRAP 4. Judgment entered on Tuesday, December 1, 2026. Notice of Appeal is due 30 days later: Thursday, December 31. Is December 31 a federal holiday? No (December 25 is; New Year’s Day is January 1). So the deadline is December 31. If judgment had been entered on Thursday, December 3, the 30th day would land on Saturday, January 2 — the rollover rule kicks in, advancing to Monday, January 4. The calculator handles weekend / holiday stacks too: if the 30th day lands on Saturday January 2 and New Year’s Day is observed Friday January 1, the calculator continues past Sunday January 3 and lands on Monday January 4.
Local rules vary, and the engine knows it
The most common pitfall in federal-deadline computation is that local district rules frequently modify FRCP defaults. The FRCP itself often gives a range — motion oppositions are 14-21 days — because no single number applies everywhere. NDCA local rule sets motion oppositions at 14 days. SDNY uses 10 business days. NDIL goes 28 days. Same FRCP, three different actual deadlines.
DockItFlo’s engine handles this with two rules:
Default to the earliest of the range. When the FRCP allows a span like 14-21 days, the engine suggests the deadline using the lowest number. The safer default — you never miss a shorter local deadline because the engine assumed the longer one.
Surface a local-rule warning on every range-based suggestion. Each suggestion card shows an amber warning: “FRCP default is N days, but local rules vary from X to Y days. Verify against your district’s local rules and edit the date if needed.” That’s your LAA’s cue to check the actual local rule for the district named on the card (e.g., “D. Minnesota”).
When the LAA edits the date before confirming, the engine records both the FRCP default that was originally suggested AND the LAA’s edited date, keyed on the case’s court. Over time this builds a picture of what each district actually does. When five firms in the same district consistently change a 14-day default to 21 days, that’s strong evidence the local rule says 21 — and the engine can be tuned to suggest 21 by default for that district. Per-district overrides are on the roadmap once enough customer-edit data accumulates.
What’s out of scope (for now)
The v1 engine covers FRCP Sections 1-8 plus FRAP 4 (the most common appellate deadline). Out of scope for v1:
- Local district rules by district. 94 districts each with their own local rules — a sprint of its own. The local-rule warning system covers the gap by flagging ranges for LAA verification.
- FRAP beyond Rule 4. Petition for rehearing, en banc, cert — planned, not yet shipped.
- Federal Rules of Criminal Procedure. Separate body of rules, separate registry, planned.
- Bankruptcy rules. Same — separate registry.
- Patent local rules. NDCA, EDTX patent-specific rules govern claim construction and discovery in patent cases — a future overlay on the existing engine for patent-tagged cases.
- State procedural rules. The federal rules engine fires on federal notices ONLY. State-rule engines are state-by-state projects on the roadmap. Read more about state court support.
Why state notices don’t get rules-based suggestions
The Federal Rules of Civil Procedure govern proceedings in federal district courts. They don’t apply in state court. Applying a federal-rule deadline to a state matter would be wrong — potentially badly wrong, since state procedural rules can have similar-looking deadlines with different counting rules, different scopes, and different consequences for missing them.
DockItFlo’s solution: classify every incoming notice at ingest time as federal, state, or unknown. The classifier uses sender domain (uscourts.gov or pacer.gov = federal; the state e-filing domain registry covers state portals) and federal case-number patterns as a fallback. The rules engine fires only when court_type === 'federal'. State and unknown notices skip the engine entirely — AI-emitted FRCP triggers from those notices are logged and discarded.
Conservative on purpose: we’d rather miss a federal suggestion on a notice the classifier couldn’t identify than risk surfacing a federal-rule deadline on a state matter. Unknown notices get an amber chip flagging them for LAA verification, and the source can usually be added to the state-court domain registry so future notices from the same system classify correctly.
How the engine stays current
Two maintenance jobs:
Annual federal holidays. Each December, the next year’s federal holidays are added to the calculator’s holiday list using OPM observed dates (Saturday holidays observed Friday; Sunday holidays observed Monday).
FRCP amendments. The Federal Rules typically take effect on December 1 each year via the Rules Enabling Act process. After each cycle, the rule registry is reviewed against the latest amendments and day counts / rule citations are updated as needed. The change ships in the next deploy and takes effect immediately without re-prompting the AI — the AI emits trigger types, the registry maps trigger types to rules, and only the registry changes when amendments take effect.
FAQ
Can I confirm a rules-based suggestion the same way I confirm an AI-extracted date?
Yes. Rules-based suggestions land in the same review queue as AI-extracted dates, with a distinct visual treatment (a purple rules-based banner) and the rule citation rendered prominently. One click confirms; the date pushes to the attorney’s calendar with the rule citation in the invite description.
What if I disagree with the engine’s suggestion?
Click Edit on the suggestion card, set the date you want, and confirm. The engine records both the original FRCP default AND your edit, which feeds the local-rule learning loop. If you simply want to dismiss the suggestion (e.g., your case has a custom scheduling order that overrides the default), click Dismiss.
Will the engine ever fire automatically without LAA review?
No. Rules-based suggestions always land in the review queue with status pending. The local-rule variance and the consequences of a wrong deadline are too high to auto-confirm. Human review on every suggestion, every time.
Is the rule citation in the calendar invite?
Yes. When a rules-based suggestion is confirmed and pushed to the attorney’s calendar, the invite description includes the rule citation (e.g., “Per FRCP Rule 12(a)(4)(A)”) and the trigger context (“Motion to Dismiss DENIED on May 5, 2026”) so the attorney can verify against the rule directly.
What happens to a confirmed FRCP suggestion when the underlying notice gets vacated or superseded?
Same lifecycle as any extracted date. If the triggering filing is vacated or the case settles, the rules-based deadline is retired through the standard removed-dates workflow with full audit trail.
If your firm runs both federal and state matters, the rules engine combines with DockItFlo’s court-type classifier to keep federal-only suggestions on federal-only cases automatically — no per-firm configuration required. See state court docket monitoring for how the state side works.