The system
Filings that walk staff through them
Staff answer plain questions in order, and the system produces the notice, the decision, and the record you file. The knowledge of how to do a case start to finish is built into the software.
Plain questions · the filing assembles itself
- Runs on
- Your own hardware
- Connection
- Works offline, air-gap capable
- Proof
- Every record sealed and checkable
- Control
- Your keys, your roles, your code
There are no blank forms to figure out. The system asks one plain question at a time and fills the paperwork from the answers.
Because the procedure lives in the software, a new clerk can do on day one what used to take years to learn.
If someone is interrupted, the work is saved. They pick up exactly where they left off.
One question at a time, in the right order
A blank form assumes you already know the procedure. A guided filing assumes only that you know the facts of the matter in front of you, and it carries the procedure itself.
Each step reads everything answered before it, so the questions narrow as they go and nothing is asked twice. What the office has already established about the person, the matter, and the parties is carried forward rather than retyped.
- Plain questions, in sequence. No blank form, no field codes, and no guessing what goes where.
- Earlier answers carry forward. What you established at step one is used at step six without retyping it.
- It stops and asks a person where judgment is required, instead of deciding for you.
- The work is saved as you go. An interruption costs you nothing; you return to exactly where you were.
- The filing assembles itself from the answers, so the document and the record agree by construction.
- The procedure is the software's, not one person's. The same case, done the same way, whoever is at the desk.
Where a person is required to decide
The system is deliberately built to stop. At the points where judgment belongs to a human, the workflow pauses, presents what it has, and waits for the person to decide, and it records that decision as the person's own.
This is the difference between software that automates an office and software that runs one. The tribe keeps every decision. What the tribe stops carrying is the memory of which step comes next.
Guided filings, from each seat
Tribal IT
Training load drops to near nothing.
The procedure lives in the software, so onboarding is an account and a role. You are not the person who has to teach the office how the office works.
Council
The office is no longer one person deep.
The knowledge of how a matter is handled start to finish stops being tribal knowledge in one head and becomes a capability the government owns.
Staff
You are never staring at a blank form.
Answer what you know, in plain words, in order. The paperwork is produced from your answers, and the deadlines are carried for you.
Questions tribes ask about using it
- How long does it take to learn?
- The design target is that a new staff member completes a real matter, start to finish, unassisted, in their first days. If that is not happening, the workflow is wrong and we fix the workflow.
- What if our procedure is unusual?
- Then the software follows your unusual procedure. The steps are built from how your office actually works, captured with your staff, not from a template of how offices are supposed to work.
- What if someone makes a mistake mid-filing?
- Go back and change the answer. The work is saved as you go and every version is kept, so a correction is a normal, attributed action rather than a crisis.