Docket Models

Motion Briefing Schedule

A simplified court-order model can encode briefing intervals. 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.

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

Court-order schedules can be data

This lesson uses a simplified court-order briefing model, not a universal rule. The authored events are motion, opposition, and reply.

order model→briefing events\text{order model}\to\text{briefing events}

Example briefing intervals

A simplified court-order model sets an opposition interval of 14 days and a reply interval of 7 days after opposition.

opposition days=14\text{opposition days}=14

The schedule governs due rows

The motion date is June 1, 2026. The recomputed opposition due date is June 15, 2026, with delta 0.

delta=0\text{delta}=0

Reply row is another computed interval

The reply row is computed separately and gives due date June 22, 2026. The schedule has 3 events.

events=3\text{events}=3

Diagram note

The diagram is a simplified order schedule. 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 the stated-rule interpretation.

Motion briefing schedule scope=US-FED model=Simplified court-order briefing model as_of=2026-06-24 note=Simplified federal civil model; rules and orders vary; not legal advice; docket traces only, not filing advice; on_time and late are toy delta labels only, not timely or untimely filing conclusions. status vocabulary=early,event,late,on_time order=1 id=motion date=2026-06-01 elapsed=0 status=event due=none delta=none reach=2 label=Motion served order=2 id=opposition date=2026-06-15 elapsed=14 status=on_time due=2026-06-15 delta=0 reach=1 label=Opposition filed order=3 id=reply date=2026-06-22 elapsed=21 status=on_time due=2026-06-22 delta=0 reach=0 label=Reply filed

Summary

Briefing schedules become auditable when each response row names its trigger event and day count.

response row plus count\text{response row plus count}