Enrollment & Membership

Membership is the sharpest edge of sovereignty

The Supreme Court has said it plainly: a tribe's right to define its own membership for tribal purposes has long been recognized as central to its existence as an independent political community. Federal courts have generally declined to review tribal membership determinations, because the Indian Civil Rights Act opens no federal civil suit against the tribe, with habeas corpus the narrow exception. The tribe's own forum is where a membership question is decided.

That authority carries a matching obligation. If the tribe's forum is where these disputes are resolved, then the tribe's record is the evidence, and the quality of that record is the difference between a decision that holds and one that becomes a decade of conflict.

This is why enrollment is not a database problem. It is a proof problem. Every determination needs to show what was decided, on what evidence, under which criteria, by whom, and when.

Enrollment criteria are yours and they vary: blood quantum, lineal descent from a base roll, or a combination your council enacted. The rule is yours to set, we build it in from your enrollment ordinance, and each determination cites the section behind it.

What the record has to carry

• The roll itself, current and historical, with every version retained rather than overwritten.
• Applications and their evidence, with each document tied to the person and the determination it supports.
• The criteria applied, computed from your enrollment ordinance with the section cited on the determination.
• Descent and relationships, so a lineal-descent rule can be traced back to the base roll your government anchors on.
• Every decision, attributed and sealed, so an approval or a denial can be shown exactly as it was made.
• The full history of a disputed record, including what it said before, which is the question that always gets asked.

Where enrollment touches the money

For a tribe making per-capita distributions from gaming revenue, enrollment stops being a records matter and becomes a financial control. Federal law permits per-capita payments only under a revenue allocation plan that the Secretary of the Interior has approved, that protects minors and legally incompetent persons, and that provides notice to members of their tax liability.

The regulations go further, and the requirement is worth reading twice: an approved plan must establish a tribal court system, forum, or administrative process for resolving disputes. Federal law expects the tribe to have exactly the institution this system is built to run, and it expects the roll and the payment to answer to each other.

One roll, one record, one place: the member's enrollment, their eligibility, and the payment that follows from it stop living in three places that have to be reconciled by hand every distribution.

The base roll, and descent across generations

Enrollment criteria are the tribe's own, and they vary: blood quantum, lineal descent from a base roll, or a blend a council enacted. The Bureau of Indian Affairs does not set them and no uniform federal standard exists. Where the rule is lineal descent, every determination becomes a claim about a chain of relationships reaching back to a historical roll, and each link in that chain is either evidence you hold or a gap someone has to argue across.

The base roll itself is tribe-specific. For the Five Civilized Tribes it is commonly the Dawes Commission Rolls; other tribes anchor to different census or membership rolls entirely, with different anchor dates. So the chain is not a generic genealogy problem. It runs to the specific roll your government anchors on, under the criteria your ordinance sets, and the determination has to cite both.

Then there is the data problem, and it is the hardest one in the building. A name written by an agency clerk in the 1890s, transliterated from a language he did not speak, is not the name on a 1954 birth certificate, which is not the name on a 2026 application. Spellings drift. Suffixes appear and vanish. A person shows up under a translated name on one roll and a family name on the next. Marriages, adoptions, and informal family arrangements move people across surnames in ways no matching rule anticipates.

The design rule that follows is short: the system reconciles what is clearly the same person, and an uncertain match is a question a person answers, never a merge the software performs quietly. A quiet merge is a determination nobody made, attributed to nobody, and it is exactly the kind of decision that surfaces a decade later in your own forum with no record behind it.

The criteria and the base roll are your constitution's and your ordinance's to set, and they differ from tribe to tribe. We build your enrollment code in, section by section, and the determination cites the section it applied and the roll it anchored to.

The record that outlives the office

Enrollment is the longest-lived record a tribal government keeps. A determination made this year will be evidence in a descent claim by someone not yet born, and the office that made it will have turned over several times before that question arrives. The record has to survive not just the staff, but the software, the hardware, and the vendor.

Two retention tracks run through the building, and it is worth being precise about which is which. Records tied to federal awards live under the Uniform Guidance: three years from submission of the final financial report, with specific exceptions that move or hold that clock. Programs run under a self-determination contract have their own parallel minimums. Everything else, including your enrollment records, is governed by your own records ordinance and your own schedule. There is no federal schedule dictating how long a tribe keeps its internal records the way a state schedule governs its counties. Each tribe determines who is eligible for membership and maintains its own enrollment records and its records about past members.

Keeping enrollment and vital records permanently is near-universal tribal practice, and it is practice set by tribal ordinance rather than a federal command. That distinction matters, because it means the retention rule is not something a vendor discovered for you. It is something your council enacts, and the system's job is to carry it exactly and to make the record still provable when the clock is measured in generations.

Indigenous data sovereignty is the right of a Native nation to govern the collection, ownership, and application of its own data, and the CARE Principles (Collective Benefit, Authority to Control, Responsibility, Ethics) give it a working shape. CARE is a governance framework rather than law, so its force in a purchase comes from the tribe writing it into its own data-governance code and its contracts. Records that sit on the tribe's own hardware, under the tribe's own keys, are what make Authority to Control something you exercise rather than something you request.

• Every version retained, so a determination from twenty years ago can be shown as it was made rather than as it was later amended.
• Sealed at the moment it happened, so a record's integrity does not depend on trusting the software that produced it.
• The evidence stays attached to the determination it supports, so the file does not thin out as the decades pass.
• Held in the building, on your hardware, so the retention rule your council enacted is enforced by you rather than by a company's business decisions.
• Always movable, because a record meant to outlive the office cannot be locked to the system that happens to be running today.

Questions tribes ask about enrollment

Can a federal court overturn our enrollment decision?

As a rule, no. Membership determinations for tribal purposes belong to the tribe, and the Supreme Court has held that the Indian Civil Rights Act does not open federal courts to civil suits against the tribe over them. The forum is yours, which is exactly why your record needs to be sound.

Our criteria are unusual. Can the system handle them?

Your criteria are the criteria. Blood quantum, lineal descent from your base roll, or a combination your council enacted are built in from your own ordinance, section by section, and the determination cites the section it applied.

When can we turn enrollment on?

Enrollment runs on the same record model as the rest of the government, and it is built with your tribe from your own enrollment ordinance and your own roll. Every deployment is a build, so the question is never whether it is in the box. The question is what we build first with you, and that is your call to make.