Product · 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 superseded, never overwritten, when the record changes.
Halvorsen Logistics v. Meridian Foods · N.D. Tex.
DeadlineDueBasisFrom
Response to motion to compelDec 28, 2026Computedfrcp-6-b · ECF 31
Reply in support of motion to compelDec 10, 2026Computedlr-7.1-e · ECF 31
ProductionApr 15, 2027Court-setECF 28
Dispositive motionsJun 30, 2027Court-setECF 28
Court timezone · superseded, never overwritten
2
sources: court-set and computed
0.8
confidence floor before a date reaches a calendar
1
rule id on every computed deadline
Two kinds of deadline
Court-set
Read from an order and shown as the court wrote it. We never recompute a date the judge set.
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
Apr 15, 2027
Court-set · scheduling order ECF 28 · N.D. Tex. · dispositive motions Jun 30, 2027
Every synced event carries its basis in the description so the calendar is auditable without opening the product.
No reminders based on guesses; no date without a rule or an order behind it; no “likely” dates on the calendar — estimated dates live in the product with a tilde and a comparable count and never sync.
Every date on your calendar can be traced to an entry.
That is the whole feature.
Related