Small claims is the one docket where the filer is usually not a lawyer and usually not a repeat player. They have never done this before, they are doing it once, and the paperwork is the whole experience of the court from their side.

So the filing is a set of plain questions, answered in order, that produces a correct document. A person is asked what happened, not asked to know which form applies.

The money thread runs through the person's record: a judgment ties to the person, and payments are tracked against it, so the balance is a live fact rather than a spreadsheet somebody maintains.

The filer has never done this before

Every other docket in the building is run by people who do it for a living. Small claims is not. The person filing is a member with a dispute, maybe a small business owner, maybe someone owed money by a neighbor. They will interact with your court once, and their entire impression of whether the tribe's forum works is formed at the counter with a form in their hand.

A form assumes you already know the answer. A question does not. So the guided filing asks what happened, who it involves, when it happened, and what you are asking the court to do, in that order, in plain words, and it builds the document from the answers. The filer never chooses a form, because choosing the form was never their job.

The office feels this on the other side. A filing that comes in complete and correct is a filing the clerk does not send back, does not correct at the counter, and does not chase. The volume of small claims means that difference compounds across a year.

Plain questions, answered in order, that produce the filing rather than a form the person has to interpret.
The person found once, so a filer with an existing record in the government is not entered a second time.
Deadlines computed from your code, with the section shown, so a party who asks why a date falls where it does gets an answer.
Service captured as a dated event, because a small claim turns on notice as much as a large one.
The judgment tied to the person, not to a case number that has to be looked up later.
Every payment posted against the judgment, so the balance is current by construction.

Who may file, what the limits are, what a claim has to state, and how long a party has to respond are your code's to set. We build them in from your published law, and each requirement the filing enforces cites the section it came from.

The money thread: a judgment is not the end

In most courts the judgment is where the record stops caring. It is entered, it is a document, and what happens next lives in a spreadsheet, a folder, or a phone call. Then someone asks what is still owed on a judgment from three years ago, and the answer takes an afternoon and is not provable.

Here the judgment attaches to the person, and every payment posts against it. The balance is not maintained; it is computed from a sealed history of what was ordered and what was paid, each entry attributed to a person and a date as it was made. Ask what is owed and the answer is immediate and shows its work.

Because the person is the center, that judgment is visible wherever the person appears. If the same person has a housing matter, a fee balance, or a payment plan elsewhere in the government, the court sees the whole picture before it orders anything, rather than making an order that collides with one made last month on another docket.

Small claims, from each seat

Tribal IT

A public-facing intake you actually control.

The guided filing runs on the government's own machines, and the records it creates never leave the building. There is no outside portal holding your court's front door.

Council

The tribe's forum is one a member can actually use.

A court that a self-represented member can navigate is a court that gets used, and a docket that gets used is jurisdiction exercised rather than jurisdiction held.

Staff

Filings arrive complete.

The questions do the work the counter used to do, so what reaches your desk is ready. And the balance on any judgment is a lookup, not an afternoon.

Same seven steps, lightest facts

Small claims is the family workflow with the smallest facts on it, which makes it the best proof that one shape carries the whole court. The matter opens against the correct person. Parties are noticed, and the service is a dated event. When notice changes, the clocks recompute. The hearing is calendared. The record is built from what the office knows, with a person approving every draft. The matter is filed and sealed as it happens. The judgment issues from the record, signed, and reproducible identically years later.

A clerk who learned those steps on a guardianship already knows small claims. That is the argument for one workflow, and small claims is where it pays the most, because this is the docket most likely to be covered by whoever is available.

Questions courts ask about small claims

What is our limit, and can the system enforce it?: The limit is whatever your council enacted. We build it in from your code, the guided filing applies it, and the filing shows the section it came from. If the council changes it, the change is made in the workflow and cited to the amended section.
Can a member file without help from the clerk?: That is the design target. Plain questions, answered in order, producing a correct document. If members are still needing the counter to interpret a form for them, the workflow is wrong and we fix it.
How do we track what is still owed on a judgment?: The judgment attaches to the person and every payment posts against it, each entry attributed to a person and a date. The balance is computed from that sealed history, so it is current whenever you ask and it can show exactly how it got there.

Small claims and collections