Guardianship

Why guardianship is the hardest workflow in the building

Guardianship combines everything that makes court work go wrong. It runs on clocks that start on different events, it involves a vulnerable person who cannot advocate for themselves, it requires notice to people who may be hard to find, and it has an ongoing obligation that continues for years after the initial order.

It is also the workflow where the cost of a missed date is highest. A temporary order that lapses because nobody was counting leaves a child or an elder in an arrangement with no legal footing, and it puts the court in the position of having to fix a problem that the record itself created.

So this is the workflow the system carries hardest. The clocks are computed rather than remembered, and every date it asserts is traceable to the section of your code that produced it.

• The temporary-order clock, computed from your own ordinance and counted from the event your code says it runs from.
• Extensions counted against your limit, so an extension that would exceed what your code permits is caught before it is granted.
• Notice and service tracked as events on the record: who was served, how, on what date, and with what document.
• The annual account scheduled when the order is entered, so the obligation years from now is already on the calendar.
• Every date shows its section, so a question from the bench about why a deadline falls where it does has an immediate answer.
• The full history is sealed, so the file that goes up on review is complete and provably unaltered.

The person, not the case, is the center

A guardianship never sits alone. The child in this matter may be in a child-welfare case, be enrolled, and have family with their own matters before the same court. A system organized around case numbers loses those connections; a system organized around people keeps them.

Open the person and see every matter they are part of. That is how a court avoids the situation where two judges make two orders about the same family on the same week without either one knowing about the other.

Questions courts ask about guardianship

Whose deadlines does it use?

Yours. Every clock is computed from your own ordinances, and the system shows the section it applied. It does not carry another jurisdiction's assumptions about how long a temporary order should last.

What if our practice differs from our written code?

The system shows both and flags the difference rather than quietly choosing one. Which one changes is a decision for the tribe, not for the software.

Can a new clerk run a guardianship?

That is the design target. The procedure lives in the software, in plain questions, so a successor completes a real matter start to finish without decades of memory. If that is not happening, the workflow is wrong and we fix it.