Tribal Nations and Federal Grants

Federal grant compliance systems were built for nonprofits and state agencies. When tribal nations — sovereign governments with distinct legal status, governance structures, and federal trust relationships — interact with these systems, structural mismatches emerge that no checklist can resolve. The result is a compliance paradox: the frameworks designed to ensure accountability often undermine the self-determination they are supposed to support.

This article examines where those mismatches occur, why they persist, and what they mean for anyone working at the intersection of tribal sovereignty and federal funding.

Two Systems, One Application

Consider a tribal health program preparing to apply for a SAMHSA Tribal Behavioral Health Grant. The Notice of Funding Opportunity lists requirements that are, by now, familiar to anyone in the grant world: active SAM.gov registration, a Unique Entity Identifier, Grants.gov registration, a governing body resolution authorizing the application, audited financial statements, a conflict of interest policy, evidence of organizational capacity, and letters of support from partner organizations.

Each of these requirements was designed with a specific kind of applicant in mind: a 501(c)(3) nonprofit with a board of directors, an executive director, a set of bylaws, and a clearly delineated organizational boundary. The compliance infrastructure that undergirds federal grant-making — from registration portals to audit requirements to the reviewer scoring rubrics themselves — was built on this mental model.

Tribal nations are not nonprofits. They are governments. They have constitutions, elected councils, sovereign authority over their lands and citizens, judicial systems, and a direct government-to-government relationship with the United States that predates the Constitution itself. When a tribal health director sits down to fill out a federal grant application, they are a government official representing a sovereign nation — navigating a system that was designed as though they were a community-based organization seeking philanthropic support.

The application form does not know the difference. And that, fundamentally, is the problem.

This is not a complaint about paperwork. It is a structural observation. The assumptions embedded in federal grant compliance frameworks — about governance, about financial management, about organizational identity — create friction for tribal applicants that goes beyond inconvenience. The friction is baked into the architecture.

Understanding where this friction occurs matters for tribal health leaders who must navigate it, for federal program officers who design and administer grant programs, and for state agency staff whose compliance requirements intersect with tribal operations. It also matters for us. Any organization building tools for grant readiness — including Weave — must account for the fact that the default framework is not neutral. It was designed for one type of entity, and it disadvantages others.

The Legal Landscape

The Trust Responsibility

The federal government's relationship with tribal nations is unique in American law. It is not an optional partnership. It is a trust responsibility — a legal obligation established through treaties, the Commerce Clause of the Constitution, and centuries of federal law. The federal government has a duty to protect tribal lands, resources, and the welfare of tribal citizens. This relationship exists independent of any grant or contract.

Health care is a core component of this trust responsibility. The Indian Health Service, established under the Snyder Act of 1921 and expanded through the Indian Health Care Improvement Act of 1976, exists not as a discretionary program but as a partial fulfillment of the federal government's obligation to tribal nations [Indian Health Care Improvement Act, 25 U.S.C. 1601 et seq.].

The distinction matters because it shapes the entire framework through which tribal health programs receive federal funding. Trust responsibility funding is not a grant in the conventional sense — it is an obligation. But many of the mechanisms through which this obligation is fulfilled look, from the outside, exactly like competitive grants. This creates a category confusion that affects everything from how applications are scored to how compliance is enforced.

Self-Determination: The 638 Framework

The Indian Self-Determination and Education Assistance Act (ISDEAA), Public Law 93-638, enacted in 1975, fundamentally changed how the federal government delivers services to tribal nations. Under 638, tribal nations can enter into contracts or compacts with federal agencies — primarily the Indian Health Service and the Bureau of Indian Affairs — to assume direct operation of programs that would otherwise be run by those agencies [25 U.S.C. 5304 et seq.].

This is a critical distinction. A 638 contract or compact is not a grant. It is a government-to-government agreement in which a tribal nation takes over the operation of a federal program, with the associated funding. The tribal nation is not a grantee — it is a governmental partner assuming a federal function. The compliance framework for 638 agreements is negotiated between the tribal nation and the relevant federal agency, and it differs significantly from the standard grant compliance framework codified in 2 CFR 200.

Over the past five decades, the 638 framework has become the primary vehicle through which tribal nations operate health programs. According to IHS data, the majority of IHS funding now flows through 638 contracts and compacts rather than through IHS direct services [IHS, Tribal Self-Governance Program, program overview data]. This is a success story. Tribal nations have demonstrated, repeatedly, that they can operate health programs more effectively and more responsively than the federal government can.

The Dual Funding Reality

Here is where the structural tension becomes concrete. A tribal health department in 2026 does not operate under a single funding framework. It operates under several simultaneously.

A mid-size tribal health program might manage:

• IHS 638 compact funding for primary care, pharmacy, and community health services — governed by ISDEAA and the negotiated compact terms.
• Competitive SAMHSA grants for substance use treatment and mental health programs — governed by 2 CFR 200 and the specific terms of the Notice of Funding Opportunity.
• HRSA grants for community health worker programs or health IT infrastructure — governed by 2 CFR 200 with HRSA-specific requirements.
• State pass-through funding from the state health department or Medicaid agency — governed by the state's contracting requirements.
• Tribal general fund revenue — governed by tribal law and the tribal council's authority.
• Tribal enterprise revenue from gaming, natural resources, or other economic ventures — governed by tribal law and applicable federal regulations.

Each of these funding streams has its own reporting requirements, its own audit expectations, its own definition of allowable costs, and its own oversight structure. The tribal health director must keep them all straight — not because any individual requirement is unreasonable, but because the aggregate burden of managing multiple, non-aligned compliance frameworks is enormous.

This is the dual funding reality. Tribal health programs do not have the luxury of operating in one compliance world. They operate in all of them at once.

Where the Compliance Framework Breaks

Governance Structure Mismatch

Federal grant applications and post-award compliance requirements assume a particular governance structure: a board of directors with defined terms, officers, committees, conflict of interest policies, and a clear separation between the governing body and operational management. This is the nonprofit board model, and it is so deeply embedded in federal compliance thinking that most program officers do not even recognize it as a model — they experience it as the natural way organizations work.

Tribal governance does not follow this model. A tribal council is not a nonprofit board. It is a legislative body — a branch of government with sovereign authority derived from the tribal nation's constitution or other governing document. Council members are elected officials, not volunteer directors. The council's authority extends to all aspects of tribal governance, not just the health department. The relationship between the tribal council and the tribal health director is the relationship between a legislature and an agency head, not between a board and an executive director.

When a federal grant application asks for a "governing body resolution" or a "board-approved conflict of interest policy," it is asking a sovereign government to produce documentation formatted for a nonprofit. Tribal nations can and do produce these documents — but the process of translating governmental authority into nonprofit-formatted paperwork is itself a compliance burden that other applicants do not face. A state health department applying for the same grant does not have to reformat its governance structure to fit a nonprofit template. A tribal government, which holds equivalent sovereign authority, does.

Entity Type Classification

The federal grant infrastructure relies on entity type classifications — the categories that SAM.gov, Grants.gov, and individual awarding agencies use to determine what you are and what you are eligible for. For tribal entities, these classifications create persistent confusion.

SAM.gov includes both "Indian/Native American Tribal Government (Federally Recognized)" and "Native American Tribal Organization (other than Federally Recognized)" as entity type options. Grants.gov uses similar but not identical categories. Individual NOFOs may specify eligibility for "tribal governments," "tribal organizations," or "Native American organizations" — terms that sound interchangeable but have different legal meanings and different implications for what entity types qualify.

A tribally chartered health authority, for example, may be organized as a tribal organization rather than as the tribal government itself. Whether that health authority qualifies for a NOFO limited to "tribal governments" can depend on how it was registered in SAM.gov years ago — a classification decision that may have been made by someone who has since left the organization, based on guidance that may have since changed.

The downstream effects cascade. Entity type classification affects eligibility determinations, scoring categories (some NOFOs score tribal applicants in a separate pool), indirect cost rate applicability, and audit cognizance. A classification error at registration can propagate through the entire federal funding relationship — and correcting it is not a simple data update. It can require documentation from the tribal government, review by the relevant federal agency, and weeks of processing time [GAO-19-157, Federal Grants: Additional Actions Needed to Address Ongoing Duration and Other Challenges in the Application Process].

Audit Requirements and Financial Complexity

Tribal governments that expend $750,000 or more in federal awards in a fiscal year are subject to the Single Audit requirement under 2 CFR 200, Subpart F — the same requirement that applies to nonprofits and state agencies. (For more on the Single Audit threshold and its implications, see our analysis in The Single Audit Cliff.)

But the structure of tribal government finances creates audit complexity that the Single Audit framework was not designed to address. A tribal government's financial ecosystem may include 638 compact funds (which have their own reporting requirements under ISDEAA), competitive federal grants, state contracts, tribal enterprise revenue (including gaming revenue regulated under the Indian Gaming Regulatory Act), per-capita distributions, natural resource revenue, and investment income. These funding streams may flow through a single tribal government entity, through tribally chartered authorities, through tribally owned enterprises, or through some combination — depending on how the tribal nation has organized its governmental and economic functions.

The Single Audit, designed to assess compliance with federal award requirements, must navigate this financial landscape. Auditors unfamiliar with tribal government structures may struggle to distinguish between funding streams, apply incorrect compliance requirements to 638 compact funds, or raise findings that reflect misunderstanding rather than non-compliance. The National Indian Health Board has documented this pattern in testimony to Congress, noting that audit findings against tribal health programs sometimes result from auditor unfamiliarity with the ISDEAA framework rather than from actual compliance failures [NIHB, Testimony to the Senate Committee on Indian Affairs, various sessions on federal funding barriers].

The cost compounds. Tribal governments in rural areas may have a limited pool of audit firms with tribal government experience, driving up costs and reducing the quality of the audit process itself.

The Indirect Cost Rate Paradox

Tribal nations negotiate their indirect cost rates with the Department of the Interior, which serves as the cognizant agency for most tribal governments. These rates are determined through a formal negotiation process that accounts for the actual administrative costs of operating programs — costs that, for tribal nations in rural and remote areas, are legitimately higher than the national average.

Operating a health clinic eighty miles from the nearest city, on roads that are impassable for weeks during winter, with limited broadband access, in a community where the nearest CPA firm is a two-hour drive away — these conditions generate real administrative costs. Higher per-unit transportation costs. Higher recruitment and retention costs for specialized staff. Greater reliance on contracted services that urban organizations can provide in-house. The indirect cost rate reflects these realities.

But in competitive grant scoring, a higher indirect cost rate means that a larger share of the requested budget goes to "overhead" — and some reviewers, consciously or not, score this negatively. The tribal applicant whose indirect cost rate is 35% (legitimately negotiated with DOI) competes against an urban nonprofit whose rate is 15%. Both rates are federally approved. Both reflect actual costs. But the reviewer rubric that scores "cost efficiency" or "budget reasonableness" may not account for the structural reasons one rate is higher than the other.

This is not a hypothetical disadvantage. It is a measurable one. An applicant whose budget allocates a greater share to indirect costs has, by definition, fewer direct service dollars to describe in the program narrative — which can affect scoring on program design sections as well. The indirect cost rate, which exists to ensure tribal programs can actually operate, becomes a competitive penalty in the scoring process.

The IHS-to-Competitive-Grant Pipeline

Many tribal health programs follow a developmental trajectory that moves from IHS direct services to 638 compacts to competitive federal grants. This trajectory represents growing capacity: a tribal nation that successfully compacts IHS services has demonstrated the financial management, clinical capability, and organizational infrastructure to operate federally funded health programs.

The transition from 638 to competitive grants is where the compliance paradox becomes most acute.

Under a 638 compact, the tribal health program's compliance obligations are defined by ISDEAA and the negotiated terms of the compact. Reporting is to IHS. Financial management follows the compact's terms. The tribal program has, in many cases, built a compliance infrastructure specifically calibrated to this framework — and has operated successfully under it for years or even decades.

When that same program applies for a competitive SAMHSA or HRSA grant, it enters a different compliance world. The competitive grant is governed by 2 CFR 200 — the Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards. This framework requires specific written policies for procurement, travel, time and effort reporting, conflicts of interest, subrecipient monitoring, and a host of other operational areas.

A tribal health program that has operated flawlessly under 638 for twenty years may not have a written procurement policy that meets 2 CFR 200.320 — not because it lacks procurement controls, but because its procurement procedures were built for the 638 framework. It may not have a time and effort reporting system that meets 2 CFR 200.430 — not because it does not track staff time, but because 638 does not require the same documentation methodology.

The gap is not one of capability. It is one of documentation format. The tribal program has the substance. It may lack the specific formal articulation that the competitive grant framework demands.

And here is the paradox: the very act of seeking to expand services — by pursuing competitive grants to complement 638 programs — subjects the tribal health program to a more burdensome compliance system than the one under which it has successfully operated. Growth is penalized. The reward for building capacity under one federal framework is the requirement to build a parallel compliance infrastructure for another.

Federal agencies could address this by recognizing 638 compliance history as evidence of capacity in competitive grant evaluations. Some NOFOs include language acknowledging tribal government applicants' distinct status, but this recognition is inconsistent across agencies and programs. There is no government-wide policy that says: if a tribal nation has successfully managed a 638 compact for a decade, that track record should meaningfully count when evaluating capacity for a competitive award.

Washington State: A Specific Landscape

Washington is home to 29 federally recognized tribal nations, from the Makah on the northwestern tip of the Olympic Peninsula to the Confederated Tribes of the Colville Reservation in the northeast to the Yakama Nation in the south-central part of the state. Each has its own governance structure, its own health delivery model, its own funding portfolio, and its own relationship with both the federal and state governments [Governor's Office of Indian Affairs, Washington State, directory of federally recognized tribal nations].

The IHS Portland Area

Washington's tribal health programs fall within the IHS Portland Area, which serves tribal nations in Washington, Oregon, and Idaho. The Portland Area includes both IHS direct service facilities and tribally operated programs under 638 contracts and compacts. In Washington, the majority of tribal health services are delivered through tribally operated programs — a reflection of the strong self-determination trajectory among Washington's tribal nations.

Several tribal health organizations in Washington operate comprehensive health systems that rival community health centers in scope: primary care, behavioral health, dental, pharmacy, public health, and community wellness programs. These organizations manage multi-million-dollar budgets, employ hundreds of staff, and serve both tribal citizens and, in some cases, non-Native community members.

State-Tribal Dynamics

Washington has a stronger framework for state-tribal relations than many states. The Centennial Accord of 1989, signed by Governor Booth Gardner and the leaders of Washington's federally recognized tribal nations, established a government-to-government relationship between the state and tribal governments. Subsequent agreements, including the Millennium Agreement of 1999, reinforced this framework [Governor's Office of Indian Affairs, Centennial Accord and Millennium Agreement].

In practice, this means Washington's state agencies — the Health Care Authority (HCA), the Department of Social and Health Services (DSHS), the Department of Health (DOH) — engage with tribal governments through a consultation framework. State-tribal liaisons exist within major agencies. Tribal health programs participate in state planning processes.

But the government-to-government framework at the policy level does not always translate into the administrative level. State grant and contracting requirements may still use templates, reporting formats, and compliance expectations designed for nonprofit contractors. A tribal health program receiving HCA pass-through funding may encounter the same governance-structure and entity-type friction at the state level that it encounters at the federal level.

Medicaid and Apple Health

Washington's Medicaid program, Apple Health, intersects with tribal health in ways that add another layer of compliance complexity. Under federal law, American Indian and Alaska Native individuals are exempt from Medicaid managed care enrollment requirements — they may access services through any Medicaid-enrolled provider, including tribal health facilities, without being assigned to a managed care organization [42 CFR 438.14, requirements for Indian managed care entities].

This protection is essential. But administering it requires tribal health programs to navigate both the fee-for-service and managed care sides of Medicaid — different billing processes, different authorization requirements, and different compliance expectations. A tribal health clinic that bills Medicaid for a behavioral health service must understand whether the patient is enrolled in Apple Health managed care (in which case the exemption applies, but the billing pathway differs from standard managed care claims) or in fee-for-service Medicaid. The compliance burden of this dual navigation falls on the tribal health program's billing staff.

Tribal Behavioral Health and CCBHC Certification

Several Washington tribal nations have built significant behavioral health programs and are exploring or pursuing Certified Community Behavioral Health Clinic (CCBHC) certification. The CCBHC model, which offers an enhanced Medicaid reimbursement rate in exchange for meeting comprehensive service and quality requirements, has the potential to stabilize funding for tribal behavioral health programs that currently rely on a patchwork of grants and contracts.

But the CCBHC certification criteria were designed with a specific kind of clinic in mind: an urban or suburban outpatient behavioral health center with a defined service area, a multi-disciplinary staff model, and proximity to crisis services and inpatient referral partners. The requirements include 24/7 crisis services, nine required service categories, evidence-based practice implementation, quality reporting, and specific staffing models [SAMHSA, CCBHC Certification Criteria, current edition].

For a tribal behavioral health program serving a community of a few thousand people, spread across a rural reservation where the nearest hospital is an hour away and the nearest psychiatrist is in another county, these requirements present genuine operational challenges. The 24/7 crisis requirement, for example, may require staffing levels that are sustainable for a clinic serving 50,000 people but not for one serving 5,000. The evidence-based practice requirements may not account for culturally grounded healing practices that tribal communities have used for generations — practices that are effective but do not appear in the Western clinical evidence base.

This is not an argument against CCBHC certification for tribal programs. Several tribal nations are pursuing it precisely because the funding model is more sustainable than grant dependence. It is an observation that certification criteria calibrated for one context create disproportionate barriers when applied in another — and that those barriers are structural, not motivational. (For more on how infrastructure gaps compound in rural and remote communities, see Rural Grant Access Is an Infrastructure Problem.)

What Federal Agencies Could Do Better

This section is directed at the federal side of the government-to-government relationship. These are not requests from tribal nations — tribal nations have been making these points in congressional testimony, formal consultation sessions, and inter-agency communications for decades. These are observations about where the federal grant system's design creates unnecessary friction with tribal sovereignty.

Acknowledge the Dual Framework

When a tribal health program applies for a competitive grant, it brings a compliance history. If that program has managed a 638 compact for years without adverse findings, that history is evidence of financial management capacity, programmatic oversight, and organizational stability. Federal agencies should develop explicit policies for recognizing 638 performance in competitive grant evaluations — not as a preference, but as a relevant qualification.

Simplify Entity Classification

The current SAM.gov and Grants.gov entity classification system for tribal entities is confusing, inconsistent, and consequential. A clear, consistent "tribal government" classification that cascades correctly through eligibility determinations across all federal programs would reduce a significant source of friction. This is a technical fix with an outsized impact.

Calibrate Indirect Cost Expectations

Federal grant reviewers should be trained to understand that indirect cost rates negotiated with the Department of the Interior reflect actual operational costs — and that higher rates in rural and remote areas are a function of geography, not inefficiency. Scoring rubrics that penalize "high overhead" without accounting for the structural reasons behind the rate systematically disadvantage tribal applicants. This is a reviewable, correctable bias in the scoring process.

Invest in the 638-to-Competitive Transition

The compliance gap between 638 and 2 CFR 200 is well-documented and predictable. Targeted technical assistance for tribal health programs moving from 638 to competitive grants — specifically focused on the documentation differences between the two frameworks — would close this gap without requiring tribal nations to build permanent infrastructure for what is essentially a translation exercise.

Consult Genuinely, on Grant Design

Executive Order 13175 requires federal agencies to engage in meaningful consultation with tribal governments before implementing policies that affect them. This requirement is well-established at the policy level. But it is rarely applied to the design of grant compliance frameworks — the specific forms, reporting requirements, scoring rubrics, and administrative processes that tribal applicants must navigate. Extending genuine consultation to grant program design, not just grant policy, would surface the structural issues described in this article before they become barriers [Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, 2000].

What This Means for Readiness

We started this article by observing that federal grant compliance frameworks were built for nonprofits and state agencies. We have described, in some detail, where those frameworks create structural friction for tribal governments. Now we must turn the lens on ourselves.

Standard grant readiness checklists — including the ones we have built at Weave — default to the nonprofit framework. When we list "conflict of interest policy" as a readiness requirement, we are implicitly assuming a nonprofit governance model. When we assess audit readiness, we may not distinguish between the audit requirements for 638 compact funds and those for competitive grants. When we flag an indirect cost rate as "above average," we may be reflecting a bias that disadvantages the very applicants who need the most support.

This article is partly a self-critique. If we are building tools to help organizations achieve and maintain grant readiness, those tools must account for the structural differences in how tribal governments interact with federal compliance systems. A readiness assessment for a tribal health program should distinguish between "you need this for your 638 compact" and "you need this for a competitive grant." It should recognize that 638 compliance history is itself evidence of readiness. It should not force tribal governments through a nonprofit-shaped filter.

For tribal health leaders reading this: we recognize that you navigate these dual frameworks every day, and that the friction we have described here is not news to you. Our goal is not to explain your own experience back to you. It is to make the structural barriers visible to the broader grant ecosystem — because many of the people who design, administer, and score federal grants genuinely do not understand the compliance paradox that tribal applicants face.

For federal and state agency staff: understanding where your compliance requirements create disproportionate barriers for tribal applicants is not a matter of preference or accommodation. It is a matter of fulfilling the trust responsibility. The federal government's obligation to tribal nations does not pause at the boundary of a grant application portal.

For everyone working in this space: the compliance paradox — where the frameworks designed to ensure accountability undermine the self-determination they are supposed to support — is not inevitable. It is a design choice. And design choices can be redesigned.

The structural barriers we have mapped in this article are real, but they are not permanent. They exist because the systems were built without adequate attention to the distinct legal, governmental, and operational reality of tribal nations. Fixing them requires political will, genuine consultation, and a willingness to acknowledge that a compliance framework designed for one type of entity is not, by default, appropriate for all types of entities.

That acknowledgment is where readiness begins — for all of us.