No more asking four departments and getting four answers. The person is at the center, and everything about them is one click away.

Records are keyed on name and date of birth, and the system warns when a person may already exist, so you do not end up with duplicates.

This is what lets the same system carry a person from enrollment to the court to finance without losing the thread.

How duplicates are caught before they happen

Duplicate records are how a person's history quietly fractures. One office knows them by a married name, another by a maiden name, a third by a nickname on an old form, and nobody notices until an audit or a dispute forces the question.

When a person is entered, the system looks for the same person under a different label before it creates a new record. Where it is confident, it links. Where it is unsure, it does not guess: it hands the question to a person with the evidence laid out.

Look for a strong match firstAn exact match on the identifiers your office already relies on links the record immediately and with confidence.
Then look for a likely oneName variants, spelling differences, and formatting differences are normalized, so the same person entered two ways is recognized as one person.
Hand the uncertain cases to a humanA possible match is presented for review rather than merged automatically. A person decides, and that decision is recorded as theirs.
Keep where every fact came fromEach piece of information carries its origin, so you can always answer which form, from what date, is the source of this address.

The system never silently merges two people. A wrong merge in a government record is far more damaging than a duplicate, so the uncertain case is always a question for a person, with the evidence shown.

The person at the center of the whole government

The reason this matters is that it is what makes one government out of several departments. A member is enrolled, appears in a matter before the court, owes or is owed money, and holds a permit. Today those are four systems and four answers. On one record, they are one person with a complete history.

Bringing in what you already have is part of the work, not a separate project. Records from spreadsheets and older systems are imported through the same matching, so your existing history joins the record rather than sitting beside it.

One record, from each seat

Tribal IT

One record model, not five integrations.

Departments share the person rather than syncing copies of them. There is no nightly job holding four databases in uneasy agreement, and no drift to reconcile.

Council

The government can answer as one government.

When a member asks a question, the answer does not depend on which office they walked into. That is what a citizen experiences as competence.

Staff

Find them once.

Open the person and see what the government knows about them, across departments, without calling three offices and waiting a day for a callback.

Questions tribes ask about person records

Does every department see everything about a person?: No. The record is shared; the visibility is not. Access follows the job, so finance sees what finance needs and the court sees what the court needs. A record outside your scope does not appear at all.
What about people who are not members?: They get a record too. Governments work with employees, vendors, parties to a matter, and applicants, and all of them need a stable identity that does not fracture across offices.
Can we import what we already have?: Yes. Spreadsheets and older systems are imported through the same matching and review, so duplicates are caught on the way in rather than inherited.

One record per person