Your tribal health program has operated a 638 compact for years — maybe decades. You manage a multi-million-dollar health system, pass your Single Audit, serve your community, and maintain your compact with IHS without adverse findings. Now someone — a council member, a program director, a partner organization — has identified a competitive federal grant (a SAMHSA behavioral health grant, an HRSA workforce program, a CDC prevention cooperative agreement) that could expand your services.
You are qualified. Your program has the capacity. You have the clinical expertise and the community trust.
But the competitive grant application asks for documentation you have never needed under your compact. It references compliance requirements you have never encountered. The process feels foreign even though you have managed federal health funding for longer than some of these grant programs have existed.
This page is for you. Not because you lack capability — but because the competitive grant system uses a different vocabulary, follows different procedures, and expects documentation in formats that 638 compacts do not require. The gap is translation, not capacity.
The Core Transition: 638 to 2 CFR 200
The fundamental shift when moving from 638-only funding to competitive grants:
| What Changes | Under 638 Compact | Under Competitive Grant (2 CFR 200) |
|---|---|---|
| How you get the money | Negotiated government-to-government agreement | Competitive application scored against other applicants |
| Who you compete against | Nobody — 638 is a right, not a competition | Other tribal programs, nonprofits, state agencies (depending on the NOFO) |
| Budget flexibility | Can reallocate across program lines | Must follow approved budget; changes need prior approval |
| Reporting | Negotiated terms with IHS | Prescribed by awarding agency (quarterly/semi-annual reports, SF-425) |
| Procurement | Tribal procurement code | 2 CFR 200 procurement standards with specific thresholds and documentation |
| Time tracking | Not typically required in 638 format | Time and effort reporting mandatory for personnel charged to the grant |
| Overhead funding | Contract Support Costs (separate from program budget) | Indirect costs charged within grant budget (reduces program dollars) |
| Application materials | Compact negotiation, AFA | Full application package: narrative, budget, logic model, letters of support, resolutions, forms |
Step 1: Determine Eligibility Before You Invest Time
Before writing a word of an application, confirm three things:
Is Your Organization Type Eligible?
Read the NOFO's eligibility section carefully. Key phrases:
| NOFO Language | What It Means for You |
|---|---|
| “Federally recognized tribal governments” | Your tribal government is eligible |
| “Tribal organizations” | May include tribally chartered health authorities — check the definition section |
| “Indian tribes and tribal organizations as defined in 25 U.S.C. 5304” | ISDEAA definition — includes tribal governments and organizations authorized by tribal governments to act on their behalf |
| “Native American organizations” | Broader — may include nonprofits serving AI/AN populations |
| “Public and private nonprofit organizations” | Your tribal government may qualify as a “public” entity. Tribally chartered nonprofits qualify. Check with the program officer if unsure. |
| “Tribal-only” or “tribal set-aside” | Restricted to tribal entities — typically less competitive than open competitions |
Is Your SAM.gov Entity Classification Correct?
Check your SAM.gov registration now. Verify:
- •Entity type is set to “2N — Indian/Native American Tribal Government (Federally Recognized)” under Business Types. This is the SAM.gov classification code that marks your entity as a federally recognized tribal government. If your registration shows a different business type (e.g., “2X — Indian/Native American Tribal Designated Organization” or a generic nonprofit code), fix it. The 2N classification triggers tribal eligibility filters in Grants.gov searches and ensures awarding agencies classify your application correctly. Reclassification requires SAM.gov support and can take 2–4 weeks.
- •EIN is correct and matches all other registrations
- •Address is current
- •Registration is active (not expired or pending)
- •If your registration was set up years ago, the classification may not reflect current reality. Fix it before you apply — reclassification takes time.
Does the Grant Match Your Capacity?
Not every eligible opportunity is a good opportunity. Consider:
- •Award size relative to your program capacity (a $2M grant to an organization that has never managed a competitive grant is high risk)
- •Reporting requirements relative to your data infrastructure
- •Match requirements (cash or in-kind) relative to your available resources
- •Period of performance relative to your staffing stability
Step 2: Registration Sequence
If you've only operated under 638, you may be missing some registrations required for competitive grants. Here's the sequence (items depend on each other — complete in order):
Already Complete (Likely)
| Registration | Status | Time If Needed |
|---|---|---|
| EIN | You have this — needed for 638, banking, everything | Immediate if applying for new EIN; unlikely needed |
| SAM.gov | You have this — needed for 638 compact | Verify it's active and entity type is correct. Renewal takes 7–10 days. |
| UEI | You have this — assigned through SAM.gov | Verify it's current |
May Need to Complete
| Registration | What It Is | Time to Complete | Notes |
|---|---|---|---|
| Grants.gov registration | Portal for submitting competitive federal grant applications | 1–2 weeks for new registration | SAM.gov registration must be active first. |
| AOR authorization | Authorized Organization Representative — the person who submits applications on Grants.gov | 1–3 business days after Grants.gov registration | Requires EBiz Point of Contact (POC) to approve. The POC must be designated in SAM.gov. If you don't know who your EBiz POC is, find out now. |
| HRSA EHBs registration | HRSA Electronic Handbooks — required for HRSA programs only | 1–2 weeks | Only needed if applying to HRSA programs |
| WA State Vendor Registration | DES registration for state grants | 1–2 weeks | Only needed if applying to state programs (HCA, DOH) |
| WEBS registration | State solicitation notification system | 1–2 days | Free. Registers you for state RFA notifications. |
Test Before You Need It
Grants.gov submission test: Before your first real deadline, submit a test application through Grants.gov. The system has specific technical requirements (PDF formatting, attachment naming, file size limits) that trip first-time users. Discover these on a test, not on deadline day.
Step 3: Build the Documentation You Don't Have Yet
These are the items that 638 operations don't require but competitive grants do. This is where most tribal first-time applicants discover gaps — not because they lack the systems, but because they lack the documentation format.
Priority 1: Must Have Before You Apply
| Document | What It Is | Why You Don't Have It Yet | How to Build It |
|---|---|---|---|
| Written procurement policy (2 CFR 200) | Policy documenting competitive bidding thresholds, documentation requirements, and conflict of interest in purchasing | Your tribal procurement code works for 638 but may not cite 2 CFR 200 thresholds ($10K micro-purchase, $250K simplified acquisition) | Create an addendum to your existing tribal procurement code that addresses 2 CFR 200 requirements. You do not need to replace your tribal code — layer the grant-specific requirements on top. |
| Time and effort reporting system | Method for documenting how employees allocate time across programs/grants | Under 638, you may track time for payroll but not for cost allocation across funding sources | Implement before the grant starts. Options range from simple spreadsheet timesheets (allocated by funding source) to payroll system configurations. Personnel costs are 60–80% of health budgets — this is where auditors focus. |
| Written financial management procedures | Documented procedures for AP, AR, payroll, and grant fund drawdown | Your procedures exist — they may not be written down in a format that satisfies 2 CFR 200 | Document what you already do. Add the specific procedures for grant fund drawdown from the Payment Management System (PMS) or whatever disbursement system the awarding agency uses. |
Priority 2: Should Have Before First Report Is Due
| Document | What It Is | How to Build It |
|---|---|---|
| Cost allocation plan | Methodology for allocating shared costs across funding sources | If staff, facilities, or equipment serve both compact and grant programs, document how costs are split. Must be consistent and defensible. |
| Equipment/property management policy | Policy for tracking, maintaining, and disposing of grant-purchased equipment | 2 CFR 200 has specific requirements for equipment over $5K (inventory, physical counts, disposition). |
| Subrecipient monitoring policy | If you sub-award any grant funds | Document how you will monitor subrecipients for programmatic and financial compliance. |
Priority 3: Strengthens Your Application
| Document | What It Is | Notes |
|---|---|---|
| Community needs assessment (recent) | Service-area-specific data on health needs | Must be within 3 years and use local data. Coordinate with NPAIHB EpiCenter for tribal health data. National or statewide data is insufficient — reviewers want your community's data. |
| Logic model | Visual: inputs to activities to outputs to outcomes | SAMHSA weights this heavily. If you've never built one, NPAIHB or NIHB can provide templates and TA. |
| Letters of support / MOUs | From partner organizations | Specific commitment letters, not generic endorsements. State the partner's role, resources committed, and governance structure. Letters from NPAIHB and AIHC carry particular weight with federal reviewers — they signal that your program is embedded in the tribal health infrastructure, not operating in isolation. A letter from NPAIHB committing EpiCenter data support or TA, or from AIHC documenting state agency coordination, scores meaningfully higher than a generic endorsement. Secure these letters early; both organizations expect specific asks, not form requests. |
| Cultural competency documentation | How your program integrates cultural approaches | For tribal grants, document traditional healing, language programs, historical trauma-informed approaches. This is a strength, not a box to check. |
Step 4: The Application Package
A typical competitive federal grant application includes:
| Component | What It Is | Tribal-Specific Notes |
|---|---|---|
| SF-424 (Application for Federal Assistance) | Standard form with organizational information, project title, budget summary | Verify EIN, UEI, and entity type match SAM.gov. Select the correct entity type on the form. |
| Project narrative | 15–30 pages describing the problem, your approach, capacity, evaluation, and sustainability | Frame 638 experience as a qualification: “Our tribal health department has operated a comprehensive health system under Title V self-governance compact for [X] years, managing $[X]M in annual federal health funding.” |
| Budget and budget justification | Line-item budget + narrative explaining every cost | Use your DOI-negotiated indirect cost rate. Do not reduce it to appear competitive — it is federally approved. Budget justification should explain why costs are necessary, not apologize for them. |
| Logic model | Visual representation of program theory | Required by most SAMHSA programs. Optional but helpful for others. |
| Tribal council resolution | Governing body authorization to apply | Some NOFOs require a resolution specific to this application. Others accept a general grant-seeking authorization. Check the NOFO. |
| Letters of support | Partner commitments | See above. Quality over quantity. |
| Organizational chart | Reporting structure | Show the health department's structure and its relationship to tribal council. |
| Key personnel biosketches | CVs for project director, financial officer, key clinical staff | Highlight experience managing 638 programs and any prior grant experience. |
| Assurances and certifications | Standard federal forms (lobbying, debarment, civil rights) | Required for all federal grants. Sign and include. |
Presenting 638 History in a Competitive Narrative
Your 638 compact history is your strongest asset in a competitive application. But reviewers — many of whom have never worked with tribal programs — do not know what a 638 compact is, what ISDEAA means, or why operating a self-governance health system for 15 years is a stronger qualification than managing a $200K CDC sub-award. You have to translate.
The pattern: state what you did, name the federal authority, quantify the scope, and connect it to the capacity the NOFO asks for. Do not assume the reviewer knows.
Organizational Capacity Section
This is where most tribal applicants undersell. Your capacity section should establish that you operate a federally funded health system under a legal authority that requires exactly the competencies the grant demands. Frame each claim with specifics:
| What You Want to Say | How to Say It in a Grant Narrative |
|---|---|
| We have run our health programs for years | “[Tribe] has operated a comprehensive tribal health system under a Title V Self-Governance Compact with the Indian Health Service since [year], managing $[X]M in annual federal health funding under P.L. 93-638 (Indian Self-Determination and Education Assistance Act). This [X]-year history of direct federal health system management demonstrates sustained organizational capacity for multi-program administration, federal financial compliance, and health service delivery.” |
| We manage federal money responsibly | “[Tribe]'s most recent Single Audit (2 CFR 200, Subpart F) for fiscal year [YYYY] was completed with [zero/no material] findings across $[X]M in federal expenditures, including [X] major programs. The Tribe has maintained clean audit opinions for [X] consecutive years.” |
| We have the clinical capacity | “The tribal health department employs [X] clinical staff, including [list relevant credentials: Licensed Clinical Social Workers, Certified Behavioral Health Technicians, Community Health Representatives, etc.]. The department operates [clinic name/type] serving [X] patients annually with [X] patient encounters per year.” |
| We have the financial infrastructure | “The Tribe maintains fund accounting with [X] distinct funding source codes, a DOI-negotiated indirect cost rate of [X]% (effective through [date]), and a finance department with [X] staff experienced in federal grant accounting, third-party billing, and multi-source cost allocation.” |
| We have community trust and access | “As the tribally operated health system for [X] enrolled members ([X] residing in the service area), the health department maintains established trust relationships with the patient population. [X]% of eligible community members are active patients. Programs are governed by tribal council with input from a health committee/health board composed of community members.” |
Needs Statement and Data
Reviewers expect local data, not just national AI/AN disparity statistics. Use your 638 operations to demonstrate that you have the data infrastructure to support the claims:
- •Reference your RPMS/EHR data for service utilization and health outcome trends. “Tribal health department clinical data from [system name] shows [specific trend].”
- •Cite community health assessments conducted under 638 operations.
- •Use NPAIHB EpiCenter data for Portland Area tribal health statistics.
- •Include data governance language: “Tribal health data used in this application was approved for external use by [tribal authority] under the Tribe's data governance policy.”
Addressing “Prior Grant Experience” When You Have None
Many NOFOs ask about prior grant management experience. If you have never held a competitive grant, do not leave this blank or apologize. Instead:
- •Reframe 638 as federal fund management. “While this is the Tribe's first competitive grant application to [agency], the Tribe has [X] years of direct federal health fund management experience through its Self-Governance Compact, administering $[X]M in IHS-transferred programs annually under the same Single Audit requirements (2 CFR 200, Subpart F) that govern competitive grants.”
- •Name adjacent experience. State pass-through funds, FEMA grants, DOJ/OVW grants, USDA programs, HUD IHBG — any federal or state award you have managed.
- •Describe your compliance infrastructure. Clean Single Audits, DOI indirect cost rate, fund accounting, and established financial management systems are evidence of grant readiness — present them as such.
The translation principle
Grant reviewers score what they can read. If your narrative says “we have a 638 compact,” a reviewer unfamiliar with ISDEAA reads that as an opaque acronym. If your narrative says “we have operated a comprehensive tribal health system managing $4.2M in annual federal funding under a Self-Governance Compact with IHS for 18 years, with zero material Single Audit findings over the past five audit cycles,” the reviewer reads that as a highly qualified applicant. Same organization, same history — different score.
Step 5: After Award — The First 90 Days
If your application is funded, the first 90 days set the compliance trajectory for the entire award period:
Immediate (Days 1–30)
- •Review the Notice of Award (NoA) carefully. It contains the specific terms, budget period, reporting schedule, and any special conditions.
- •Set up grant-specific accounting. Create a separate cost center or fund code in your accounting system for this grant. Do not commingle with compact funds.
- •Identify and register with the awarding agency's payment system. SAMHSA uses PMS (Payment Management System). HRSA uses EHBs. Know where your drawdown requests go.
- •Begin time and effort tracking. Any employee who will charge time to the grant must begin documenting their time allocation from Day 1.
- •Brief tribal council. Ensure council understands the reporting obligations, the budget constraints (no reallocation without approval), and the distinction from compact administration.
Early (Days 31–60)
- •Submit any post-award administrative requirements. Some agencies require updated budgets, work plans, or key personnel documentation within 30–60 days of award.
- •Establish data collection systems. If the grant requires GPRA/NOMS (SAMHSA) or other performance reporting, set up data collection before you start delivering services — not after.
- •Review procurement needs. If you plan to purchase equipment or services with grant funds, follow 2 CFR 200 procurement procedures. Document the process from the start.
- •Contact your program officer. Introduce yourself. Ask about TA resources, reporting expectations, and any common compliance issues for first-time tribal grantees.
Stabilizing (Days 61–90)
- •Test your first financial report. Before the first SF-425 is due, prepare a draft to verify your accounting system captures the data correctly.
- •Review your first performance report. Before the first progress report is due, verify you are collecting the data the report requires.
- •Adjust. If anything is not working — data systems, time tracking, procurement documentation — fix it now, while there is still institutional patience for a new grantee's learning curve.
Common Mistakes for First-Time Tribal Grantees
1. Treating the Grant Like a Compact
Compact funds are flexible — you can reallocate, redesign, and innovate. Grant funds are not. Moving money between budget lines without prior approval, or changing program activities without amending the grant, creates compliance findings. This is the most common adjustment for 638 operators.
2. Using Tribal Procurement Code for Grant Purchases
Your tribal procurement code works for compact purchases. For grant-funded purchases, 2 CFR 200 procurement standards apply. The thresholds and documentation requirements are more specific. Use the layered policy approach described above.
3. Not Tracking Time and Effort
This is the highest-risk compliance area for first-time grantees. If employees split time between compact and grant activities, both programs need defensible time allocation documentation. Retroactive time reconstruction is not adequate — it must be contemporaneous.
4. Reducing the Indirect Cost Rate to Appear Competitive
Your DOI-negotiated rate reflects real costs. Budgeting at a lower rate to look more competitive means underfunding your own administration — creating either a shortfall you must cover from tribal funds or a compliance risk when administrative functions are unsupported.
5. Overlooking the Data Sovereignty Implications
Competitive grants require data submission to federal systems. Before you start collecting data, understand what goes where, who can access it, and what your tribal data governance provisions require. See Tribal Data Sovereignty & Reporting.
6. Missing the Deadline
Grants.gov has hard deadlines. The system closes at the posted time. If you encounter technical issues, there is a narrow window to request a late submission — but it requires documentation of the technical failure. Submit at least 48 hours early on your first application.
7. Not Budgeting for Compliance
The compliance requirements of a competitive grant cost real money — time and effort tracking systems, data collection, financial reporting, Single Audit expansion (if you add new major programs), and grant management staff time. Budget for these costs in the application. They are allowable.
Resources for Tribal Grant Applicants
| Resource | What They Offer |
|---|---|
| NPAIHB | Technical assistance for Portland Area tribes: grant writing support, data analysis, program development. Start here. Establish an MOU for EpiCenter data access and TA before you begin writing — their commitment letter carries weight with federal reviewers. |
| NIHB (National Indian Health Board) | National advocacy and policy analysis. Publishes guides on federal grant requirements for tribal programs. |
| AIHC | State-level policy coordination. Can connect you with state agency contacts for state-funded programs. A letter from AIHC documenting their coordination role for your program carries scoring weight in both federal and state applications. |
| IHS Portland Area Office | Technical assistance on 638-related issues and coordination with competitive grants. |
| Grants.gov Help Desk | Technical support for registration and submission issues. 800-518-4726. |
| SAM.gov Help Desk | Registration support. 866-606-8220. |
| Awarding agency program officers | After the NOFO is posted, contact the listed program officer with eligibility and technical questions. They are a resource. |
The Capability Is There
The reason you can manage a competitive federal grant is the same reason you've managed a 638 compact: you operate a health system, serve your community, and manage federal funds responsibly. The transition from 638 to competitive grants is not about building new capability. It is about translating existing capability into a different documentation framework.
The gap is real but bounded. The items in this guide — Grants.gov registration, written procurement policy, time tracking, budget format — are specific, fixable, and finite. Once you've done it the first time, the second application is routine.