Courts and justice
For the clerk of court
The clerk's procedures live in the system, so the office keeps running after a retirement and a new clerk can do the job without decades of memory.
Built with your court · deadlines from your code · every order provable
Right now one person often knows how the court actually runs, and the day they retire that knowledge is gone. This puts the procedures into the software.
The software does not replace the clerk. It makes the job possible to hand off, and keeps it in your hands.
The test that it worked: a successor completes a real case, start to finish, unassisted.
What the clerk actually knows
Ask a clerk what they do and they will describe filing. Watch a clerk work and you will see something else: a continuous stream of judgment calls that no manual contains. Which deadline runs from filing and which from service. What the judge wants to see before a hearing. Which family's matters are connected. Who to call when service fails. What the code says, and what the court has actually done for thirty years.
That is the institutional infrastructure of the court, and in most tribal courts it exists in one copy, in one person, with no backup and no export. It is the single largest continuity risk the court carries, and everyone can see it coming.
The software does not replace the clerk. It makes the job possible to hand off, and keeps it in the tribe's hands. The judgment stays with the person. The procedure stops living only in their memory.
The handoff, done properly
- Walk a real matter with the person who knowsNot a manual, not a flowchart. A real case, start to finish, recording what the office actually does and why.
- Put the procedure in the softwareThe steps, the clocks, and the order of operations become the workflow, with the deadlines computed from your code and the section cited.
- Name the places where practice and code differThere will be some. The system shows both rather than choosing quietly, and the court decides what changes.
- Run the test that mattersA successor completes a real matter, start to finish, unassisted. Until that happens, the knowledge has not moved, whatever the documentation says.
The clerk's office, from each seat
Tribal IT
Onboarding is an account, not an apprenticeship.
A new clerk gets a role and the procedures are already in the system. You are not the person responsible for teaching the court how the court works.
Council
A retirement stops being a crisis.
The court keeps running, the record stays complete through the transition, and the tribe's justice system does not pause while someone relearns it.
Staff
You can hand off what you built, and be protected by it.
Your way of doing the work is captured in your words while you are still here. The trail also means your work stays attributed to you and cannot be quietly rewritten after you go.
Questions clerks ask
- Is this going to replace my job?
- No. It carries the deadlines and the steps so you can do the part only a person can do. Every office that has done this ends up with the clerk doing more judgment and less remembering, and with the office able to survive their eventual retirement.
- What if I do things differently from the written code?
- Then we capture how you actually do it, and the system shows where that differs from the written rule. That conversation belongs to the court. Nobody is going to quietly overwrite thirty years of practice with a template.
- How much of my time does this take?
- Real time, honestly. Capturing the procedure means walking real matters with you. It is the most valuable thing the court can spend your remaining tenure on, and it is the only way the knowledge actually moves.