Deadlines
Computed from the entry, with the rule that set it.
An answer due 21 days after service. A response 14 days after a motion. A production date the judge wrote into an order. Each one on your calendar with its source, and marked superseded, not overwritten, when the record changes.
Halvorsen v. Meridian, N.D. Tex.
DeadlineDueBasisFrom
Response to motion to compelOct 13, 2026Computedfrcp-6-b · ECF 31
Reply in support of motion to compelOct 27, 2026Computedlr-7.1-e · ECF 31
ProductionFeb 1, 2027Court-setECF 28
Dispositive motionsApr 15, 2027Court-setECF 28
Dates in the court’s timezone
Example matter. Parties, counsel and figures are invented for illustration.
2
sources: court-set and computed
0.8
confidence floor before a date reaches a calendar
1
rule id on each computed deadline
Two kinds of deadline
Court-set
Read from an order and shown as the court wrote it. The date is the judge’s, not ours.
Computed
Trigger entry plus rule. frcp-12-a-1-A, tx-trcp-99-b, lr-7.1-e. The rule id is on the deadline, so you can check our arithmetic.
Superseded
Reclassify the trigger entry and the deadline is marked superseded with a pointer to its replacement. Nothing is edited in place.
Under review
An entry classified below 0.8 confidence waits for a human before any date computed from it reaches you.
From the docket to your calendar, with the receipt.
Production due: Halvorsen v. Meridian
Feb 1, 2027
Court-set · scheduling order ECF 28 · N.D. Tex. · dispositive motions Apr 15, 2027
Synced events carry their basis in the description, so you can check a date without opening the product.
Estimated dates stay in the product, marked with a tilde and a comparable count; only dates with a rule or an order behind them reach your calendar.
Every date on your calendar can be traced to an entry.
That is the whole feature.
Related