Guide
A line prosecutor's week: the Monday docket brief
Updated 2026-09-10 · 3 min read
The Monday Docket Brief is a page composed from the calendar, disclosure state, and open partner requests. It exists so Sunday night is not nine matters opened from scratch. It does not invent hearings or facts.
What the page must contain
For each appearance this week: what the hearing is, where the matter stands, and what is still missing — an open disclosure gap, an overdue partner request, a production not certified. Each row links to the matter. A chase action should write onto the partner's open Joint Ops request rather than spawning a parallel email. If the brief is a separate document someone types, it will be stale by Tuesday. It has to be composed from the record the office already keeps.
How it gets built
Calendar events on the matter, plus the same gap list the radar uses, plus open action requests. No extra maintenance surface. If an item is not on the record, it will not be on the brief — that is a feature. Prosecutors who want a narrative still use AI drafts on the closed corpus; those drafts are labeled and never file. The brief itself is not a model call. Regenerating the brief should be a refresh of the view, not a rewrite. If regenerate exists as a button, it recomposes from the same sources. It does not invent a hearing to fill a thin Monday.
On a phone
The same page, installable as a web app, is what you open in the hallway. Native iOS/Android is not shipping. The courtroom page on this site shows a phone-sized viewport of the brief and the vault. Same ACLs, same audit. You cannot autonomously file from a phone because you cannot autonomously file at all.
Related
Open gaps on the brief are the disclosure radar. Missing partner work is Joint Ops, which is why invite-by-email matters. Productions you certified last week should not appear as missing. Read those guides, then the product tour. Walkthroughs of a synthetic week go through the contact form.
What not to type on Sunday
Do not paste an AI summary of nine files into a personal doc and call it a brief. If you use AI at all, use it on one matter, on the closed corpus, labeled as a draft, and verify every citation. The Monday page itself should not require a prompt. It should already be there. That is the difference between a copilot and an operating system. If a row is missing a courthouse or a time, fix the calendar on the matter — do not type it into the brief. If a missing item is wrong, fix the radar or the Joint Ops request. The brief is a view. Treating it as a document you edit is how it diverges from the record by Tuesday morning, which is the failure mode this page exists to prevent.
Courtroom constraints
The installable web app is the phone story. Native apps are not shipping. Same cookies, same ACLs, same audit. Do not screenshot sealed material. Do not download onto a shared device. The vault will still require an authenticated session. If your office policy forbids phones in the well, the brief still earned its keep on Sunday. The product does not argue with that policy. Use the hallway minute for the row that is red, not for drafting. If a gap is open, you already know before you stand up. If a partner request is overdue, Chase is the button, not a text message. If you need the exhibit, download from the vault on a device the office issued. That is the entire mobile pitch: three tasks, one record, no second case system in your pocket.