Tribal Healthcare Guide · #4

Tribal Grant Readiness Checklist

The pre-application checklist adapted for tribal health organizations — annotated by funding type (638 vs. competitive grants vs. state contracts).

10 min read · February 2026

This checklist is adapted from the general WA Grant Readiness Checklist for tribal health organizations. The general checklist is accurate but assumes a nonprofit applicant model. This version annotates every item with its applicability across funding types — because the requirements for a 638 compact, a competitive SAMHSA grant, and an HCA state contract are not the same.

Items are sequenced by dependency. Complete each section in order.

Key to the “Applies To” column:

  • 638 = Required for 638 contracts/compacts
  • CG = Required for competitive federal grants (2 CFR 200)
  • State = Required for WA state grants/contracts
  • Foundation = Typically required for foundation grants
  • All = Required across all funding types

Section 1: Legal Status & Registration

#ItemSeverityApplies ToTribal-Specific Notes
1.1Tribal government status or 501(c)(3)RequiredAllTribal governments do not need 501(c)(3) status — sovereign governmental status is sufficient for federal programs. Foundations may require a tribal nonprofit or fiscal sponsor. Tribally chartered organizations may need to demonstrate governmental relationship.
1.2EIN (Employer Identification Number)RequiredAllMust match across all registrations. The tribal government's EIN is separate from any tribal enterprise or tribally chartered organization EIN. Verify which entity holds the EIN used for health programs.
1.3SAM.gov registration — ActiveRequiredCG, 638Must show “Active” status. Entity type classification is critical for tribes — verify you are classified as “Indian/Native American Tribal Government (Federally Recognized)” if applying as the tribal government. Tribally chartered organizations may have a different classification. Misclassification cascades through eligibility determinations.
1.4UEI (Unique Entity Identifier)RequiredCG, 63812-character alphanumeric. Assigned through SAM.gov. Replaced DUNS in April 2022.
1.5Grants.gov registration with authorized AORRequiredCGRequired for competitive federal grants only. Not needed for 638 compacts. The Authorized Organization Representative (AOR) must be approved by the tribal government's EBiz Point of Contact. Test the submission pipeline before a deadline.
1.6WA State Vendor Registration (DES)RequiredStateRequired for WA state grants and contracts. Need WA UBI number and banking information.
1.7WEBS registrationStrongly RecommendedStateRegister at webs.wa.gov to receive state solicitation notifications. Free. Use behavioral health and healthcare commodity codes.
1.8HRSA EHBs registrationRequired (HRSA only)CG (HRSA)Separate registration required for any HRSA program. Not needed for SAMHSA, CDC, or state grants.
1.9IHS Portland Area compact/contract statusRequired638Verify your compact is current, AFA is executed for current year, and CSC amount is agreed.

Tribal-specific failure point: SAM.gov entity classification. If your tribal health authority was registered years ago by someone who has since left, the entity type classification may be incorrect. Verify it matches your current organizational structure. Reclassification can take weeks and may require tribal government documentation. Do not discover this the week before a deadline.

Section 2: Governance & Organizational Structure

#ItemSeverityApplies ToTribal-Specific Notes
2.1Tribal council resolution authorizing grant pursuitRequiredCG, State, FoundationMost competitive grants require a governing body resolution. For tribal governments, this is a tribal council resolution — not a nonprofit board resolution. Ensure the resolution specifically authorizes the executive (health director, tribal administrator) to apply for and accept grants. Some grants require a new resolution for each application.
2.2Tribal constitution or governing documentRequiredAllDemonstrates sovereign governance structure. Not equivalent to nonprofit bylaws — it is the foundational governing document of a sovereign nation.
2.3Organizational chart — currentRequiredCGMust show the health department's reporting structure and relationship to tribal council. Required attachment in most federal applications.
2.4Conflict of interest policyRequiredCGFederal requirement under 2 CFR 200.318(c)(1). Must cover tribal leadership and health program staff involved in procurement. Tribal governments may need to adapt this for the council structure — council members who are patients of the tribal health program have a different kind of conflict than nonprofit board members.
2.5Ethics/whistleblower policyRecommendedCGWritten policy for reporting fraud, waste, and abuse. Required for some federal programs.
2.6Board composition documentationRequired (HRSA only)CG (HRSA)Critical for HRSA Section 330: Requires a patient-majority governing board (51%+). Tribal councils do not inherently meet this requirement. Tribal health programs pursuing Section 330 funding typically need a separate health center board or advisory body that satisfies this requirement while maintaining tribal council oversight. This is a significant structural accommodation.

Tribal-specific consideration: The governance structure of a tribal health program reflects sovereign governmental authority. When competitive grants request “board minutes” or “board-approved policies,” they are asking a sovereign government to produce documentation formatted for a nonprofit. This is a translation exercise. The substance exists — the format may not match the template.

Section 3: Financial Systems & Controls

#ItemSeverityApplies ToTribal-Specific Notes
3.1Fund accounting systemRequiredAllMust track expenditures by funding source — 638 compact funds, each competitive grant, state contracts, tribal general fund, enterprise revenue, Medicaid. This is essential because the compliance framework differs by source.
3.2Annual financial auditRequiredAllMost recent audit current. For tribal governments exceeding $750K in federal expenditures (nearly all WA tribal health programs), a Single Audit is required. Engage audit firms with tribal government experience.
3.3DOI-negotiated indirect cost rateStrongly RecommendedAllNegotiated with Department of the Interior, Office of Inspector General. If you have never had a negotiated rate, the 10% de minimis is available — but likely underfunds your actual administrative costs significantly. Get a negotiated rate.
3.4Written procurement policyRequiredCGMust meet 2 CFR 200 standards for competitive grants. Your tribal procurement code is sufficient for 638 compact administration but may need supplemental documentation to satisfy 2 CFR 200 for competitive grants. Consider a layered policy: tribal code as base, 2 CFR 200 addendum for grant-funded purchases.
3.5Written travel policyStrongly RecommendedCGShould reference GSA per diem rates or equivalent. Important because many tribal health programs serve remote areas with substantial travel requirements — legitimate travel costs should be documented and defensible.
3.6Time and effort reporting systemRequiredCGMust document how employees allocate time across funding sources. This is the highest-impact compliance requirement for tribal programs transitioning from 638-only to mixed funding. Personnel costs are typically 60-80% of healthcare budgets — this is where auditors focus.
3.7Written financial management proceduresStrongly RecommendedCGDocumented procedures for AP, AR, payroll, and grant fund drawdown.
3.8Cash management systemRequiredCGFor competitive grants, must minimize time between federal fund drawdown and disbursement.

Section 4: Compliance & Audit Status

#ItemSeverityApplies ToTribal-Specific Notes
4.1Single Audit — currentRequired (if applicable)AllRequired if total federal expenditures exceed $750K. For most WA tribal health programs, this is triggered by the 638 compact alone. Ensure the audit is filed with the Federal Audit Clearinghouse.
4.2No unresolved audit findingsRequiredCGOutstanding findings from prior audits must be resolved or have a corrective action plan. Findings in 638 compliance are assessed under the ISDEAA supplement; findings in competitive grants are assessed under program-specific supplements. Both matter.
4.3No debarment or suspensionRequiredAllVerify no exclusions for the tribal government, tribally chartered organizations, or key personnel in SAM.gov exclusions database.
4.4Insurance — currentRequiredCG, StateFTCA changes this for tribal programs. If your health program operates under a 638 compact, the Federal Tort Claims Act (25 U.S.C. § 5321(d)) provides federal malpractice coverage — you do not need separate professional liability insurance for clinical services delivered under the compact. This can save $50K–$200K+ annually. You still need general liability, workers' comp, and property insurance. Important: services funded by competitive grants may not be covered by FTCA if they fall outside your compact's scope — confirm with your IHS Area Office and budget for supplemental coverage if needed. See FTCA coverage details.
4.5Nondiscrimination assurancesRequiredCG, StateTitle VI, Section 504, Age Discrimination Act, WA nondiscrimination laws (RCW 49.60). Tribal programs serving both tribal citizens and non-tribal community members must comply with these assurances.
4.6Lobbying restrictions acknowledgmentRequiredCGCertification that grant funds will not be used for lobbying (2 CFR 200.450). Tribal advocacy and government-to-government consultation are distinct from lobbying and are generally not restricted.

Section 5: Organizational Capacity

#ItemSeverityApplies ToTribal-Specific Notes
5.1Key personnel identifiedRequiredCGProject Director and Financial Officer at minimum. Biosketches or CVs typically required. For tribal health programs, note that 638 compact operational history demonstrates key personnel capacity even if those same individuals haven't managed a competitive grant before.
5.2Data collection and reporting systemsStrongly RecommendedCG, 638EHR (many tribal programs use IHS RPMS/EHR), program databases, or other systems capable of tracking funder-required outcomes. HRSA requires UDS reporting; SAMHSA requires GPRA/NOMS. For tribal programs, consider data sovereignty implications — see Tribal Data Sovereignty & Reporting.
5.3Prior grant management experienceStrongly RecommendedCGDocumentation of past grants managed successfully. 638 compact management history counts as evidence of financial management capacity and program oversight — even though compact management and grant management have different compliance frameworks. If this is your first competitive grant, explicitly address how compact experience translates.
5.4Community needs assessmentRequiredCG (most)Must be recent (within 3 years), use service-area-specific data, and include community input. For tribal programs, this should incorporate tribal health data (coordinate with NPAIHB EpiCenter and tribal epidemiology), community health profiles, and community engagement processes that respect tribal data governance.
5.5Letters of support / MOUsStrongly RecommendedCGFrom partner organizations. For tribal health programs, letters from NPAIHB and AIHC carry particular weight — reviewers recognize these as indicators that your program is connected to the tribal health infrastructure. A commitment letter from NPAIHB for EpiCenter data analysis or technical assistance, or from AIHC for state-level policy coordination, scores significantly higher than a form endorsement. Also document partnerships with IHS Portland Area, state agencies, and neighboring tribes. Prepare these relationships as application-ready assets before you begin writing.
5.6Cultural competency plan / Traditional healing integrationScoredCG (tribal grants)Not a checkbox — SAMHSA scores this as a distinct rubric section, weighted 4–9 points across every tribal program (TBHG, TOR, Native Connections, Circle of Care). Document how traditional healing practices, tribal language, cultural protocols, and historical trauma-informed approaches are integrated into clinical care. See scoring guidance below.

Section 6: Program-Specific Requirements

These apply per-application, not as standing requirements. They vary by funder and program.

#ItemApplies ToNotes
6.1Logic modelMost federal CGVisual representation of inputs-activities-outputs-outcomes. SAMHSA weights this heavily.
6.2Work plan with milestonesAll CGSpecific activities, responsible parties, quarterly milestones.
6.3Budget and budget justificationAll CGLine-item budget with narrative. For tribal programs: budget must reflect the indirect cost rate accurately. If your DOI-negotiated rate is 30%, budget it at 30% — do not artificially reduce it to appear competitive. The rate is federally approved and reflects actual costs.
6.4Evaluation planMost federal CGHow you will measure outcomes, collect data, and report results. Must align with funder's required performance measures. For tribal programs, consider how evaluation data will be governed — will the tribe retain ownership and control?
6.5Sustainability planMost federal CGHow the program continues after grant funding ends. For tribal programs, 638 compact funding, Medicaid revenue, and tribal general fund are legitimate sustainability sources. “We will seek additional grants” is insufficient for any applicant, tribal or otherwise.
6.6Tribal council resolution (specific to this application)CG, some StateSome NOFOs require a resolution specifically authorizing this application, not just a general grant-seeking authorization. Check the NOFO requirements.

Items That Affect Competitive Scoring

The checklist above is mostly pass/fail — you either have an active SAM.gov registration or you don't. But competitive grant scoring includes narrative and qualitative sections where certain items don't just meet a threshold, they actively earn or lose points. For tribal applicants, four areas deserve particular attention because they are frequently underplayed in applications despite being genuine scoring advantages.

Cultural Competency & Traditional Healing Integration

SAMHSA scores cultural competency as a distinct rubric section across every tribal program — TBHG, TOR, Native Connections, Circle of Care, Garrett Lee Smith. The weight varies by program (4–9 points in the scoring rubric, translating to roughly 10–15% of total application score when combined with related cultural elements in the narrative sections). This is not a compliance checkbox. It is a scored section where tribal applicants have a genuine structural advantage — and where most tribal applicants leave points on the table by treating it generically.

What reviewers score and what to document:

Scoring ElementWhat Scores PoorlyWhat Scores Well
Traditional healing integration“We respect traditional healing practices”“The behavioral health program integrates a weekly sweat lodge ceremony facilitated by a tribal elder into the MAT treatment protocol. Patients in the integrated track show [X]% higher retention at 90 days.”
Cultural protocol in program design“Services are culturally appropriate”“Program design was reviewed and approved by the tribal health committee, which includes [X] elders and [X] cultural practitioners. Intake protocols include a cultural assessment that informs treatment planning.”
Historical trauma-informed approach“Staff are trained in trauma-informed care”“All clinical staff complete [X]-hour training in historical trauma and intergenerational healing developed by [source]. The program uses Maria Yellow Horse Brave Heart's Historical Trauma and Unresolved Grief framework adapted for [tribe's] specific historical experience.”
Language and cultural identity“We serve a Native American population”“The program employs [X] staff fluent in [language]. Group sessions incorporate language revitalization activities linked to identity strengthening as a protective factor against substance use. [X]% of program materials are available in [language].”
Elder and knowledge keeper roles“Elders are valued in our community”“Two tribal elders serve as Cultural Advisors to the program (0.25 FTE each), participating in weekly clinical team meetings, co-facilitating [specific group/ceremony], and providing cultural supervision to non-Native clinical staff.”

The pattern: specificity scores. Name the practice, describe the integration point with clinical services, identify who delivers it, and quantify where possible. A tribal program that has delivered culturally grounded care for 20 years has stronger evidence than any non-tribal applicant can assemble — but only if it is documented with the same rigor as the clinical and financial sections of the application.

DOI-Negotiated Indirect Cost Rate

Your indirect cost rate appears in the budget, and reviewers see it. A tribal program with a 28% DOI-negotiated rate competes against urban nonprofits at 12-15%. Some reviewers — particularly those unfamiliar with tribal programs — perceive higher rates as inefficiency rather than as a reflection of the real cost of operating a governmental health system in a remote location. This is not something you can fix in the budget (do not reduce your rate). But you can address it in the budget justification: explain that the rate is federally negotiated with DOI, reflects actual administrative costs including geographic remoteness, and is the equivalent of the government overhead IHS would incur if it operated the program directly. Programs that proactively contextualize their rate avoid the silent penalty of a reviewer who assumes the rate is negotiable.

638 Compact History as Competitive Qualification

Every tribal-eligible competitive funder program — SAMHSA Tribal Behavioral Health, HRSA tribal workforce, CDC tribal prevention, ACF tribal family services — scores 638 compliance history as an organizational capacity indicator. It is not a checkbox. It is a scored qualification worth real points in the review. But the scoring only works if you present it in language the reviewer can map to the rubric.

Reviewers scoring “organizational capacity” or “management and staffing” are looking for evidence of federal fund management, compliance track record, service delivery infrastructure, and reporting systems. Your 638 compact provides evidence for all of these — but a reviewer who has never heard of ISDEAA will not make the connection unless you make it for them.

Map each element of your compact history to a specific scoring criterion:

638 Compliance ElementWhat It ProvesNarrative Language
Years under compactSustained organizational stability“[Tribe] has continuously operated a Title V Self-Governance Compact with IHS since [year] — [X] years of uninterrupted federal health system management under P.L. 93-638.”
Clean Single Audit historyFederal financial compliance“The Tribe has received unmodified audit opinions with [zero/no material] findings for [X] consecutive years across $[X]M in annual federal expenditures, audited under 2 CFR 200 Subpart F and the ISDEAA compliance supplement.”
Annual compact budget sizeScale of federal fund management“The tribal health department manages $[X]M in annual federal health funding, including [X] program areas transferred from IHS under the compact.”
IHS reporting complianceReporting systems and follow-through“The Tribe has maintained full compliance with all AFA reporting requirements, submitting annual program and financial reports to IHS Portland Area Office on schedule for [X] consecutive years.”
Program scope (services delivered)Service delivery capacity“Under the compact, the tribal health department directly operates [list: outpatient clinic, behavioral health program, dental, pharmacy, CHR program, public health nursing, etc.], serving [X] active patients with [X] annual encounters.”
Staff retained under compactKey personnel capacity“The health department employs [X] staff including [X] licensed clinicians, [X] administrative/finance staff, and [X] Community Health Representatives, all with experience delivering services under federal compact authority.”
DOI indirect cost rateEstablished financial infrastructure“The Tribe maintains a current DOI-negotiated indirect cost rate of [X]%, demonstrating an established cost allocation methodology and administrative infrastructure reviewed and approved by the federal cognizant agency.”

The principle: every line of 638 compliance history maps to a scoring criterion. A 15-year compact with clean audits, a DOI-negotiated rate, and a multi-program health department is stronger evidence of grant management capacity than most applicants can provide. But if you write “we have a 638 compact,” the reviewer scores zero for capacity because they don't know what that means. If you write “we have managed $4.2M in annual federal health funding for 15 years with zero material audit findings across 8 major programs,” the reviewer scores you at the top of the rubric. Same history, different score. See the first-time applicant guide for additional narrative framing strategies including how to address “prior grant experience” when your experience is entirely compact-based.

NPAIHB, AIHC & Inter-Tribal Partnerships

Treat these partnerships as a readiness item you prepare before writing applications — not something you scramble to document during the submission window. Letters of support and partnership documentation are scored in most competitive grants, typically under “collaboration” or “community engagement,” and tribal applicants have access to a partnership ecosystem that most nonprofits cannot match.

NPAIHB provides epidemiological data, technical assistance, and grant writing support. AIHC coordinates state-level policy and connects tribal programs to state agencies. IHS Portland Area provides federal coordination. Neighboring tribes can document inter-tribal service agreements. These are not generic endorsements — they represent a functioning inter-governmental support system, and reviewers recognize them as such.

The scoring advantage comes from specificity. A letter from NPAIHB that commits to providing EpiCenter data analysis for your needs assessment, or an MOU with AIHC documenting their role in state agency coordination for your program, scores significantly higher than a form letter stating “we support this application.” Name the partner, describe the commitment, quantify the resource where possible.

Document these partnerships now, not at submission time

Establish standing relationships with NPAIHB and AIHC that produce specific, reusable partnership documentation: a current MOU with NPAIHB for EpiCenter data access and TA, a letter from AIHC describing their coordination role for your programs, and inter-tribal service agreements with neighboring tribes. When a grant opportunity opens, you adapt these documents to the specific program — you don't start from scratch. This is one of the highest-leverage readiness investments a tribal health program can make.

The pattern across all four items:

Tribal health programs tend to undersell strengths that are genuinely distinctive. Reviewers score what's on the page. A compact history that isn't translated into capacity language gets zero points for capacity. A cultural healing program that isn't documented with clinical rigor gets minimal points for cultural competency. The readiness work for these items is not building something new — it is articulating what already exists in the format that scoring rubrics reward.

How to Use This Checklist

If you're a 638-only program considering your first competitive grant:

Start with the “CG” items in Sections 1-4. These are the gaps. You likely have the substance for everything — the work is formatting and documentation. The highest-impact items to address first: Grants.gov registration (1.5), written procurement policy meeting 2 CFR 200 (3.4), and time and effort reporting (3.6). See the First-Time Tribal Grant Applicant Guide for the transition roadmap.

If you manage both 638 and competitive grants:

Use this checklist to verify your compliance documentation covers both frameworks. The most common problem is applying compact-framework documentation to competitive grant compliance — or vice versa. Maintain separate (or clearly layered) documentation.

If you're a tribally chartered nonprofit (not the tribal government itself):

Your compliance framework is closer to the general WA Grant Readiness Checklist, but you should still reference this guide for tribal-specific items like data sovereignty, cultural competency requirements, and the entity classification considerations.

If you want this checked automatically:

Subscribe to Tribal Grant Alerts — When you sign up, we check your organization's registrations, classify your eligibility by funder, and show you where the gaps are.

See Weave for tribal health programs

Weave manages compliance across ISDEAA, 638 contracts, and CSC programs — deadlines, reports, and documentation in one place.