Docket Models

Lifecycle Timeline

A civil case lifecycle can be ordered from authored docket dates. Honesty note: simplified federal civil model; jurisdictions, local rules, and court orders vary; the pinned first step states the as-of date; not legal advice; outputs are docket and deadline traces only. Firewall doctrine: render structure, refuse interpretation, cite, abstain, and hand off.

Structured Visual

Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes a stated structural model, not the law itself. RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF.

RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF: render structure, refuse interpretation, cite provenance, abstain when unsupported, and hand off to human review.

TOY MODELNOT LEGAL ADVICESTRUCTURE ONLYHUMAN REVIEW REQUIRED
Lifecycle timelineLifecycle timelinescope: US-FED | Lifecycle timeline | as of 2026-06-24points are events; intervals are deadline deltas; arrows are dependenciesSimplified federal civil model; rules and orders vary; not legal advice; docket traces only, not filing advice; on_time and late aretoy delta labels only, not timely or untimely filing conclusions.2026-05-012026-05-262026-06-102026-07-012026-09-01scope=US-FED model=Lifecycle timeline as_of=2026-06-24note=Simplified federal civil model; rules and orders vary; not legal advice; docket traces only, not filing advice; on_time and late are toy deltalabels only, not timely or untimely filing conclusions.status vocabulary=early,event,late,on_timeorder=1 id=complaint date=2026-05-01 elapsed=0 status=event due=none delta=none reach=5 label=Complaint filedorder=2 id=service date=2026-05-05 elapsed=4 status=event due=none delta=none reach=4 label=Service recordedorder=3 id=answer date=2026-05-26 elapsed=25 status=on_time due=2026-05-26 delta=0 reach=3 label=Answer filedorder=4 id=schedule date=2026-06-10 elapsed=40 status=event due=none delta=none reach=2 label=Schedule enteredorder=5 id=discovery date=2026-07-01 elapsed=61 status=event due=none delta=none reach=1 label=Discovery servedorder=6 id=judgment date=2026-09-01 elapsed=123 status=event due=none delta=none reach=0 label=Judgment enteredevent=complaint date=2026-05-01 label=1 complaint 2026-05-01event=service date=2026-05-05 label=2 service 2026-05-05event=answer date=2026-05-26 label=3 answer 2026-05-26event=schedule date=2026-06-10 label=4 schedule 2026-06-10event=discovery date=2026-07-01 label=5 discovery 2026-07-01event=judgment date=2026-09-01 label=6 judgment 2026-09-01event=due_answer date=2026-05-26 label=due answer 2026-05-26interval=2026-05-05->2026-05-26 label=due 21 daysdependency=complaint->service label=dependsdependency=service->answer label=responsedependency=answer->schedule label=dependsdependency=schedule->discovery label=dependsdependency=discovery->judgment label=depends
highlighted = computed this step

Civil docket honesty note

Honesty note: simplified federal civil model; jurisdictions, local rules, and court orders vary; as of June 24, 2026; not legal advice; outputs are docket and deadline traces only, not filing advice.

federal civil model as of June24,2026\text{federal civil model as of }June 24, 2026

Order the docket by date

The stated process sorts authored docket events by date, then recomputes elapsed days from the first event.

authored dates→ordered timeline\text{authored dates}\to\text{ordered timeline}

Example lifecycle data

The toy lifecycle runs from May 1, 2026 to September 1, 2026 across 6 events.

events=6\text{events}=6

Elapsed days are recomputed

The lifecycle model orders 6 docket events and recomputes 123 elapsed days from first to last.

events=6,elapsed days=123\text{events}=6,\quad \text{elapsed days}=123

Diagram note

The diagram is a toy federal civil lifecycle trace. Any on_time or late row text is a toy delta label only, not a timely or untimely filing conclusion.

delta labels are not timeliness conclusions\text{delta labels are not timeliness conclusions}

Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes a stated structural model, not the law itself. RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF.

RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF: render structure, refuse interpretation, cite provenance, abstain when unsupported, and hand off to human review.

TOY MODELNOT LEGAL ADVICESTRUCTURE ONLYHUMAN REVIEW REQUIRED
Lifecycle timelineLifecycle timelinescope: US-FED | Lifecycle timeline | as of 2026-06-24points are events; intervals are deadline deltas; arrows are dependenciesSimplified federal civil model; rules and orders vary; not legal advice; docket traces only, not filing advice; on_time and late aretoy delta labels only, not timely or untimely filing conclusions.2026-05-012026-05-262026-06-102026-07-012026-09-01scope=US-FED model=Lifecycle timeline as_of=2026-06-24note=Simplified federal civil model; rules and orders vary; not legal advice; docket traces only, not filing advice; on_time and late are toy deltalabels only, not timely or untimely filing conclusions.status vocabulary=early,event,late,on_timeorder=1 id=complaint date=2026-05-01 elapsed=0 status=event due=none delta=none reach=5 label=Complaint filedorder=2 id=service date=2026-05-05 elapsed=4 status=event due=none delta=none reach=4 label=Service recordedorder=3 id=answer date=2026-05-26 elapsed=25 status=on_time due=2026-05-26 delta=0 reach=3 label=Answer filedorder=4 id=schedule date=2026-06-10 elapsed=40 status=event due=none delta=none reach=2 label=Schedule enteredorder=5 id=discovery date=2026-07-01 elapsed=61 status=event due=none delta=none reach=1 label=Discovery servedorder=6 id=judgment date=2026-09-01 elapsed=123 status=event due=none delta=none reach=0 label=Judgment enteredevent=complaint date=2026-05-01 label=1 complaint 2026-05-01event=service date=2026-05-05 label=2 service 2026-05-05event=answer date=2026-05-26 label=3 answer 2026-05-26event=schedule date=2026-06-10 label=4 schedule 2026-06-10event=discovery date=2026-07-01 label=5 discovery 2026-07-01event=judgment date=2026-09-01 label=6 judgment 2026-09-01event=due_answer date=2026-05-26 label=due answer 2026-05-26interval=2026-05-05->2026-05-26 label=due 21 daysdependency=complaint->service label=dependsdependency=service->answer label=responsedependency=answer->schedule label=dependsdependency=schedule->discovery label=dependsdependency=discovery->judgment label=depends

Summary

A lifecycle timeline is useful because it makes the date order and elapsed-day math visible.

order plus elapsed days\text{order plus elapsed days}