Agentic docketing
Your Docket Should Run the Work. Not Just Record It.
Most docketing systems are filing cabinets with dates in them. They tell you what happened and, if you ask precisely enough, what is due. What they never do is make the next thing happen. Ours is built the other way round: the record holds the legal truth, and an operating layer works on top of it continuously.
Two layers
Deterministic underneath. Agentic on top.
Separating these is the whole design. The legal record has to be rigid, versioned and boring — that is what makes it trustworthy. The operational layer has to be flexible, contextual and continuous — that is what makes it useful. Collapsing them into one system is how docketing tools end up either inert or unreliable.
Structured System of Record
The legal truth of the matter. Written once, versioned, auditable, never inferred.
- Legal facts
- Deadlines
- Events
- Communications
- Invoices
- Client playbooks
- Audit
Jidoka Operating Layer
The operational context around that truth. Continuously maintained, always traceable back to a record entry.
- Context
- Summaries
- Reminders
- Escalations
- Missing information
- Next actions
- Dynamic workstreams
Hard schema for legal truth. Soft schema for operational context.
What the docket holds
Eleven things a working docket has to do
- Docket identityOne matter, one identity, one history. Every communication, filing, deadline and invoice resolves to the same record rather than to somebody's folder.
- EventsEverything that happens to a matter is an event with a source: the office communication, the client instruction, the filing acknowledgement. Events are appended, never quietly overwritten.
- DeadlinesCalculated deterministically from the triggering event and the governing rule. Inspectable, versioned, and independent of any model's judgement.
- CommunicationsInbound and outbound correspondence attaches to the matter it concerns, so the thread and the docket never diverge.
- RemindersCadence, recipients and escalation path come from your playbook. Reminders open when the event lands and close when the instruction arrives.
- Jidoka LedgerThe chronological history of the matter — what happened, when, and on whose authority. Available without reconstruction.
- Current matter summaryA maintained answer to “where is this matter right now”, refreshed as events land rather than written when someone asks.
- Parallel workstreamsProsecution, opposition, renewal, recordal and appeal can run simultaneously against one record, each with its own dates.
- ProvenanceEvery derived fact carries its source. A date points at the rule that produced it; a summary points at the entries it came from.
- AuditabilityWho did what, when, and under which authority — held in the docket rather than in a separate system nobody opens.
- Natural-language queryingAsk the record a question in the way you would ask a colleague, and get an answer traceable to the entries behind it.
Provenance in practice
An office communication, from arrival to accountability
Each entry below carries its source. The deadline points at the rule that produced it. The report points at the playbook clause that named its recipients. Nothing in the chain is an assertion you have to take on trust.
- JidokaOffice communication receivedFER · source document attached to the record
- JidokaEvent created on the docket
- Rules engineResponse deadline calculatedDerived from the statutory rule; provenance recorded
- JidokaClient report issuedRecipients and format taken from the client playbook
- JidokaReminder workflow openedCadence per playbook; escalation contact attached
- ClientAwaiting client instructionsMatter summary updated; visible in portfolio queries
Rules protect the deadline. Jidoka runs the work around it.
Querying the record
The status already exists.
- What is urgent today?
- Which FER responses are due in the next 45 days?
- What happened on DY415-000421?
- Which matters are waiting for client instructions?
- Which filings are ready for professional review?
Answers are generated from the live record and cite the entries behind them. Where the record cannot support an answer, that is what you are told — an absent fact is reported as absent rather than filled in.
Begin
Send one instruction and watch it become a matter.
No portal, no onboarding, no data entry. Email the instruction the way you already work, and see what the docket does with it.