How it works
How does it keep one record per person?
Every person has one record, found by name and date of birth, and everything about them links to it: their enrollment, their cases, their filings, and the fees they owe. Open the record and see the whole picture in one place.
One record per person · found by name and date of birth
Records are keyed on name and date of birth, and the system warns when a person may already exist, so duplicates do not creep in.
Because the same record carries across departments, you find a person once and stop asking four offices for four answers.
Why a person fractures across offices
Nobody sets out to create three records for the same member. It happens because a name is spelled differently on an old form, because a person married, because a nickname was entered in a hurry, or because two offices never had a reason to compare their lists.
By the time it matters, in a dispute, an audit, or a hearing, the fracture is old and hard to repair, and the government is in the position of not being able to say plainly what it knows about its own member.
- The same person, entered twice, is recognized rather than duplicated.
- Spelling and formatting differences are normalized before a match is judged.
- An uncertain match becomes a question, presented to a person with the evidence, never merged automatically.
- Every fact carries its origin, so you can say which form, from which date, is the source of an address.
- Imported history joins the record, so old spreadsheets stop being a parallel universe.
The system will not silently merge two people. In a government record, a wrong merge does far more damage than a duplicate, so an uncertain case is always a human decision, with the evidence shown.
One person, seen appropriately
Sharing one record for a person is not the same as showing everyone everything about them. The record is common; the visibility is set by role.
Finance sees what finance needs. The court sees what the court needs. Enrollment sees what enrollment needs. A matter outside a person's scope does not appear at all, so the shared record makes the government coherent without making it porous.
One record per person, from each seat
Tribal IT
One model, not five databases in uneasy agreement.
Departments share the person rather than syncing copies. There is no nightly reconciliation job and no drift to chase down when two systems disagree.
Council
The government answers as one government.
A member gets the same answer whichever door they walk through. That coherence is what people experience as a government that has its house in order.
Staff
Find them once, and see what you are cleared to see.
No calling three offices and waiting a day. Open the person, and their enrollment, their matters, and their balances are already linked.
Questions tribes ask about person records
- Is this a public directory of members?
- No. It is an internal record, visible by role. There is no member-facing portal exposing it, and adding one would be a decision for the tribe, not a default we ship.
- What about people who are not members?
- Employees, vendors, applicants, and parties to a matter all get a stable record too, because a government works with more people than it enrolls.
- Can a person's information be removed if it must be?
- Yes. The information is removed and a sealed receipt of the removal is kept, naming no personal details. You can prove the erasure was proper without reintroducing what you erased.