Court deadlines from the rule text, computed twice by default

A missed deadline can end a claim no matter how strong it is. Deadline errors tend to come from a few places: a period counted from the wrong trigger, a rule that adds days for how a paper was served, a date read from the wrong line of an order, or a document nobody realized set a clock at all. By default, a second, independent computation from the same text is built to catch those errors, and a written rule decides what happens when the two disagree.

Every document gets an answer

When a document comes in, it becomes one of two things: a docket event with a deadline, or an explicit note saying it sets no deadline and why. Nothing is left in between. An order that sets no date gets a watch, a dated reminder to look again, rather than an invented deadline. An empty list never counts as "nothing to docket". Anything that could end the case, such as a dismissal risk, is flagged the moment it arrives.

From the face of the document and the rule text

The deadline is worked out from the document itself, its dates, its service information and what it orders, and from the text of the governing rule. The engine does not use a remembered rule of thumb. It uses the rule, which is why each deadline can be traced to the rule behind each deadline.

Ambiguity takes the earlier reading

Sometimes a document can fairly be read two ways, with two different dates. When that happens, the deadline is docketed to the earlier reading. An early filing is an inconvenience; a late one may be fatal.

The second, independent deadline computation

By default a second, independent model recomputes each deadline from the same document and the same rule text. If the two computations agree, the date is recorded with both. If they disagree, the mismatch goes to a structured debate between the models, argued from the rule text, and then to you if it is still unresolved. The answer is never averaged. A mismatch is resolved by reading the rule.

A clock can start before anything is filed

A new matter can start a clock before anything is filed. A limitations period that runs from the facts behind the client's goal is docketed from the start, computed the same way as any other deadline.

The docket must come back clean

A docket consistency check runs after the entries are made, and it must come back clean before the matter moves on. Blank client identity, such as a missing name, filer capacity or party role, stops the work until it is filled from the live matter.

Illustration, fictional matter.

RESPONSE TO MOTION TO DISMISS · Avery v. City of Example (fictional)
trigger ......... motion filed Tue 1 Dec 2026
rule ............ standing order ¶ 4 (fictional): 14 days to respond; L.R. 7.1(c) (fictional): 21 days
Computation A ... Tue 22 Dec 2026 · L.R. 7.1(c) (fictional); Fed. R. Civ. P. 6(a)(1)
Computation B ... Tue 15 Dec 2026 · standing order ¶ 4 (fictional); Fed. R. Civ. P. 6(a)(1)
status .......... MISMATCH · argued from the rule text, AGREED in round 1 · docketed to the earlier reading
note ............ local-rule reading (Tue 22 Dec 2026) recorded, not docketed
watch ........... hearing "to be set by the court" · no date given · watch, not a deadline

Not every date is known when a document arrives. A court may say it will rule, schedule a hearing or set a conference later, without saying when. Guessing a date for those would create a false deadline, and ignoring them would let them slip. A watch sits in between: it is a dated reminder to look again, attached to the matter, with the reason it exists. When the date becomes known, the watch becomes a deadline computed the same way as any other, twice by default, from the document and the rule text. Watches also cover items the matter is waiting on after a filing, such as a ruling or the other side's response.

The deadline work does not stop when a filing goes out.

• A 72-hour docket check. About three days after a filing, the docket is checked again. Every item that is now waiting on something (a ruling, a response, a transcript) becomes a dated watch, and the clocks that follow from the filing are docketed too.
• Proof from the court's docket. Only the court's own docket entry counts as proof that a filing was made.

An item on the docket closes only when the obligation is discharged: the filing was made and accepted, the document was mailed, or the court ruled. A document that is drafted, ready or delivered is progress, and progress goes in the entry's notes, never in its status.

• A blocked item stays open, with its blocker named and its outer deadline in view.
• A date field holds a deadline. It never holds a build date or a filing date, so a finished document can't show up as overdue, and a closed item can't carry a future date.

The docket manager is the docket product behind the engine. It tracks:

• Matters, with the client, the filer's capacity and the party role;
• Deadlines, the clocks computed as described above, and watches for dates not yet known;
• Court legs, so a matter that moves between courts keeps one history;
• The clerk's docket entries, each tied to the document it describes;
• Activities, the work items that come up as the matter moves;
• A file cabinet for the matter's documents.
• Activities close only with evidence attached.
• Client portal: start a request, see your requests, attach files.

Firms can read more about the docket manager for firms.

What a client sees, and what the operator sees

In the docket manager in your client account, a client sees each matter's official case numbers, its status, the next real deadline, the files shared with the client, and a place to upload a PDF. The operator's notes and the engine's own work stay on the operator's side. Once a matter is set up, its deadlines keep being tracked without anyone re-entering them.

Your client account

Each client has their own account, with a docket manager that shows where every piece of work stands. You set it and forget it.

Illustration, fictional matter. Hand-built to show the engine's real formats. The matter, parties, courts and dates are invented.

Case number

1:26-cv-00000 (fictional)

Status

Drafting Waiting on court

Next deadline

Tue 15 Dec 2026 · response to motion to dismiss

Your files

Complaint.pdf · Order-on-scheduling.pdf

Upload

Upload a PDF

The client view and the operator view are separate: you see your matter's status, its next real deadline, the files shared with you and the upload; the operator's notes and the engine's working files never appear in it.

Illustration · fictional

Deadlines are computed by the engine, and disagreements that the models cannot settle come to you. Beyond that, the matter's work passes 3 checkpoints. By default, you approve twice, and the whole filing gets a final read before it ships; each approval, or the client's recorded standing instruction to proceed, is stamped in the record. See who approves.

Some matters have clocks that forgive nothing. Post-conviction deadlines in particular can bar a claim entirely if they are missed, however strong the claim. See deadlines that end post-conviction claims.

• We do not claim a deadline computation replaces the responsible attorney's own calendaring judgment.
• We do not claim any court will accept a filing because it was on time by our computation; courts decide timeliness.

There are more answers to docket questions in the FAQ.

How is a deadline computed? From the face of the document, its dates, its service information and what it orders, and from the text of the governing rule. The engine does not rely on a rule of thumb or on memory.

What if the two computations disagree? The mismatch goes to a structured debate between the models, argued from the rule text. If it is still unresolved, it comes to you with both computations and the rule lines they rest on. The two dates are never averaged.

What about an order that sets no date? It gets a watch, a dated reminder to check again, instead of an invented deadline. Every document gets either a deadline or a written note saying why it sets none.

What if a document can be read two ways? The deadline is docketed to the earlier reading.

When is a docket item closed? Only when the obligation is discharged: filed and accepted, mailed, or ruled on. A drafted or delivered document is progress, not closure.

Does anyone check the docket after a filing? Yes. A docket check runs about 72 hours after filing, and every item that is waiting on something becomes a dated watch.

Email us with questions about deadlines computed twice by default, watches and the 72-hour check.

Start a request (opens the main site) Safeguards

Legal Ops Depot is not a law firm and does not give legal advice.