Home / Working with Tribes

Working with Tribes: Decision and Partnership Tools

This page serves two audiences.

  • Tribal leaders and staff can use the tools below to evaluate vendors, consultants, financing, and major decisions against their Nation's own priorities.
  • Outside organizations can learn what responsible work with a Tribal Nation requires.

These are draft tools to adapt. They do not set any Nation's policy. Each Nation decides its own process, weights, and approvals.

1. Start with the Nation, not the sale

  • Sovereignty is the foundation. Indian Affairs describes federally recognized Tribes as having inherent rights of self-government and a distinctive relationship with the United States (BIA FAQ). That is where understanding starts. It is no substitute for studying the particular Nation's governing documents and applicable law.
  • Learn the Nation's own process. Record its preferred name and terms, governing bodies, authorized contacts, departments and enterprises, who has decision authority, and how it wants to communicate. Ask what information may be shared.
  • A contact is not authority. A relationship with one department or enterprise doesn't give you permission to speak for the government or to get information from other departments.
  • Don't treat Nations as interchangeable. Tribal governments, Tribal enterprises, Tribal organizations, individual citizens, Alaska Native villages and corporations, and other Native-serving entities differ. A program open to one may not be open to another.
  • Consultation is specific. Executive Order 13175 requires federal agencies to have a process for meaningful consultation with Tribal officials when developing policies that have Tribal implications. Keep formal government-to-government consultation separate from public outreach and vendor engagement.

For outside organizations:

  • Ask how the Nation defines the problem before you present a solution.
  • Give clear pricing, realistic implementation requirements, and evidence for the results you claim.
  • Leave time for the Nation's review process.
  • Disclose conflicts, compensation, referral payments, and subcontractors.
  • Keep a shared record of objectives, decisions, and next steps, so the relationship survives staff changes.

2. Tribal Vendor & Partner Due-Diligence Framework (six gates)

  1. Define the need. Before inviting proposals, write down the deliverables, beneficiaries, success measures, budget limits, and constraints. Set the evaluation process and conflict disclosures in advance.
  2. Verify the organization. Confirm the contracting entity, ownership, qualifications, key personnel, financial capacity, insurance, subcontractors, and the evidence behind its claims. Ask about past disputes in context; an allegation alone doesn't prove misconduct.
  3. Learn from experience. Get permission to speak directly with relevant Tribal references, including ones you find yourself rather than ones the vendor supplies. Ask what was promised, delivered, delayed, or charged, and whether they would contract again.
  4. Compare economics and implementation. Put proposals on the same basis, find the exclusions, test the schedule, and count the internal staff time required. Compare a base case with a realistic bad case.
  5. Review protections and authority. Authorized reviewers should check scope, payment triggers, acceptance, change orders, confidentiality, data control, cybersecurity, dispute terms, applicable law, any immunity-related provisions, termination, and transition. Don't let a high score override missing authority or protections.
  6. Approve and monitor. Record the decision, any dissent, conditions, who signs, and who owns the outcome. Measure performance and revisit the contract well before any automatic renewal.

Total cost, not sticker price. Count purchase price, implementation, transition, training, internal staff effort, maintenance, financing, renewal increases, termination, and data migration. The lowest first-year price may not give the best long-term value.

3. An adaptable evaluation scorecard

Use these starting weights only after the Nation adopts or changes them. Score each category from 0 to 5 using evidence defined before review. Weighted points = weight × (score ÷ 5). If evidence is missing, show it as missing rather than averaging it in.

Category Starting weight Evidence to request
Fit with Tribal priorities 20 Defined outcomes and an understanding of the Nation's needs
Ability to deliver 20 Named team, implementation plan, comparable work
Total cost and economic value 20 Complete cost schedule and assumptions
References and performance 15 Reference interviews done with permission, and their results
Contract and data protections 15 Reviewed terms, data controls, transition provisions
Knowledge transfer and continuity 10 Training, documentation, succession and exit support

Pause an apparent winner if required authority is missing, a significant conflict is unresolved, or a non-negotiable condition isn't met. This is a procurement aid, not a validated rating system.

4. Templates

Decision brief

  • Decision title and date
  • Nation and approving authority
  • Need, and the intended benefit to the community or enterprise
  • Options considered, including the current approach
  • Evaluation criteria and evidence
  • Total cost and funding assumptions
  • Risks and required protections
  • References and lessons from other Nations
  • Recommendation and reasons
  • Open questions and conditions before commitment
  • Authorized decision and signatory
  • Implementation owner and performance review date

Vendor reference conversation

  • What were the service, contract period, scope, and conditions, and how do they compare to ours?
  • What was delivered against the original promise?
  • Which costs or staff demands were unexpected?
  • How were problems, changes, and disagreements handled?
  • Did the provider respect the Nation's process and its information requirements?
  • How did renewal, termination, or transition go?
  • Would the Nation hire the provider again, and under what conditions?
  • What permission is given to keep and share this account?

Funding readiness brief

See the checklist on Funding & Grants.

5. Data sovereignty

Data about a Tribe's government, citizens, and resources belongs under that Tribe's control, wherever it is stored. Before sharing data with a vendor, a funder, or a site like this one, check:

In contracts, spell out who owns the data, where it is hosted, who can access it, how it is returned or destroyed at exit, and whether any of it may be used in aggregate.

6. Sharing lessons between Nations, with permission

Neighboring Nations can run into the same vendor or problem separately, with no trusted way to compare notes. Peer learning works best when it starts with a narrow question and secures permission for recording, attribution, and further sharing. Give the contributor a summary to correct. Keep a private reference conversation separate from a publishable case.

This site will not publish complaints as a "blacklist." Any case material will be shared only with the contributing Nation's permission and will include the responding party's side.

7. A method for learning from hard experiences

What happened → why → cost and impact → lesson → early warning signs → questions to ask → better practice.

Keep these apart: deliberate policy, structural inequity, underfunding, statutory limits, administrative dysfunction, inadequate consultation, misunderstanding, unintended consequences, and documented misconduct. Record what the evidence shows and what is still disputed.

Sources

Framework adapted from the project's working manuscript, "Tribal Resources and Partnership Guide" (v0.1, Sept 2026). Tribal reviewers are invited to suggest changes.