Module 4: Tribal-Specific Requirements and Compliance Foundations

Federal grants for tribal governments carry requirements that most general grant guides don't cover. This module walks through the tribal-specific prerequisites and the federal compliance framework that governs every grant dollar from award to closeout.

If Module 3 taught you how to write a competitive application, this module teaches you how to make sure your organization is *eligible and ready* to receive the money if you win.

Federal Recognition and Eligibility Verification

Most federal grants for tribal applicants require federal recognition. The Department of the Interior maintains the official list of federally recognized Tribes — currently 574 entities — and that list is the authoritative reference for grant eligibility.

Two practical points:

Spelling and naming consistency matters. Your Tribe's name on grant applications must match how it appears in the federal register, in SAM.gov, and on the 574 list. Variations (full name vs. short name, with or without "Indian," "of [State]") can cause registration mismatches and application rejections.

State-recognized tribes without federal recognition are eligible for a smaller pool of grants — primarily state-funded programs and a few federal programs that explicitly include state-recognized tribes. If your Tribe is state-recognized only, federal pass-through funding administered by states is often a more accessible source than direct federal grants.

When you set up your GrantsPath profile, the 574 Registry verification confirms your federal recognition status and locks the canonical name format used across the platform — preventing the naming mismatches that cause SAM.gov and Grants.gov registration problems.

Tribal Resolutions

A tribal resolution is a formal decision made by your tribal council or governing body. Many federal agencies require a tribal resolution as part of your grant application — it proves that the Tribe's leadership has officially authorized the application and the proposed project.

What a Tribal Resolution Typically Includes

A statement that the tribal council has reviewed and approved the grant application

The name of the funding program and the agency

Authorization for a specific person (usually the tribal leader or grants administrator) to submit the application and sign agreements on behalf of the Tribe

The date it was passed and signatures of authorized officials

Why Planning Around Resolutions Matters

Here's the challenge: tribal councils don't meet on your grant deadline's schedule. Many tribal councils meet monthly, some meet quarterly. If your council meets on the first Tuesday of each month and the grant deadline is the 15th, you need the resolution passed at the meeting *before* the deadline.

Planning checklist:

1. As soon as you identify a grant opportunity, check when your tribal council next meets

2. Calculate backward: Can you get on the agenda, present the project concept, and get a resolution passed before the grant deadline?

3. If the timeline is tight, contact the grants program officer to ask whether a resolution can be submitted after the deadline (some agencies allow a short grace period for tribal resolutions — but never assume this)

4. Keep a template tribal resolution on file so you're not drafting from scratch each time

Tip: Some experienced tribal grants administrators maintain a "blanket resolution" that authorizes grant applications in a specific program area for a fiscal year. Check with your tribal attorney about whether this approach works for your Tribe.

SAM.gov and Grants.gov Registration

Before you can submit a single federal grant application, your organization must be registered in two systems: SAM.gov (System for Award Management) and Grants.gov. Registration problems are the most common preventable reason tribal organizations miss grant deadlines.

SAM.gov (System for Award Management)

SAM.gov is the federal government's central database of organizations that do business with the government. Every grant applicant must have an active SAM.gov registration.

What you need:

UEI (Unique Entity Identifier) — This replaced the old DUNS number. You get a UEI as part of SAM.gov registration. It's a 12-character alphanumeric code that identifies your organization across all federal systems.

Entity registration — Your organization's legal name, address, banking information for electronic funds transfer (EFT), and your organization type

Annual renewal — SAM.gov registration expires every year. Set a calendar reminder 60 days before expiration.

Common problems for tribal organizations:

Name mismatches — Your Tribe's legal name in SAM.gov must match the name on your application and in Grants.gov. Variations (e.g., "XYZ Indian Tribe" vs. "XYZ Tribe") can cause rejections.

Banking information delays — If your Tribe uses a fiscal agent or tribal treasury, make sure the banking information in SAM.gov is current and matches the account where you want grant payments deposited.

First-time registration takes time — Allow 4–6 weeks for initial SAM.gov registration. The IRS validation step alone can take 2 weeks.

Grants.gov

Grants.gov is the portal where you submit most federal grant applications. After registering in SAM.gov, you register in Grants.gov.

Key roles:

E-Business Point of Contact (EBiz POC) — This person (usually a tribal leader or senior administrator) is responsible for authorizing who can submit applications on behalf of your organization in Grants.gov

Authorized Organization Representative (AOR) — This person actually submits the applications. The EBiz POC must approve AOR access in Grants.gov.

Critical timing issue: Many tribal organizations discover at deadline time that their Grants.gov registration has lapsed, their AOR has changed roles, or the EBiz POC hasn't approved the new AOR. Check your registration status *before you start writing an application.*

Registration checklist:

1. Verify your SAM.gov registration is active (check expiration date)

2. Confirm your UEI is current

3. Log into Grants.gov and verify your organization appears

4. Confirm the EBiz POC and AOR are current and have access

5. Do a test submission if you've never submitted from Grants.gov before

Indirect Cost Rates

Indirect costs are the overhead expenses that keep your organization running but aren't tied to a single project — things like building rent, utilities, administrative staff salaries, and accounting services.

What Is a NICRA?

A NICRA (Negotiated Indirect Cost Rate Agreement) is an agreement between your organization and your federal cognizant agency (usually the Department of the Interior for tribal governments) that establishes what percentage of direct costs you can charge as indirect costs on federal grants.

Example: If your NICRA rate is 22% and your grant has $400,000 in direct costs, you can charge $88,000 in indirect costs — money that supports your administrative infrastructure.

If You Don't Have a NICRA

If your organization hasn't negotiated a rate, you have two options:

1. Use the 10% de minimis rate — Federal regulation (2 CFR 200.414) allows any organization that has never had a NICRA to charge 10% of modified total direct costs. This is automatic — you don't need to negotiate anything.

2. Negotiate a NICRA — Contact your cognizant agency (for tribal governments, this is typically the Office of the Inspector General at the Department of the Interior) to begin rate negotiation. The process takes several months but usually results in a rate higher than 10%.

Why Your Indirect Cost Rate Matters

Your indirect cost rate directly affects how much of each grant dollar goes to keeping your organization operational. A higher rate means more overhead coverage. A rate that's too low means your organization subsidizes the federal government's grant programs from other revenue.

Tribal-specific note: Many tribal governments have complex organizational structures where different programs share facilities and administrative staff. Negotiating a NICRA that accurately reflects these shared costs protects your Tribe's resources.

Sovereign Immunity Considerations

Tribal governments possess sovereign immunity — the legal principle that a sovereign government cannot be sued without its consent. This comes up in federal grants in several specific situations.

When Sovereign Immunity Matters in Grant Management

Subaward agreements — If your Tribe subawards grant funds to another organization, that organization may ask for a limited waiver of sovereign immunity in the subaward agreement

Contractual agreements — Vendors, consultants, and partners may request waivers as a condition of doing business

Federal terms and conditions — Some grant terms include dispute resolution provisions that may intersect with sovereignty

Audit and compliance — Federal audit requirements (Single Audit) apply regardless of sovereign immunity

What a Limited Waiver Means

A limited waiver of sovereign immunity is a narrow, specific agreement that allows legal recourse in defined circumstances. It does *not* mean giving up sovereignty — it means agreeing to a specific forum and scope for resolving a specific dispute.

Best practice: Always involve your tribal attorney when any grant-related agreement touches sovereign immunity. Never sign a waiver without legal review, no matter how routine it seems.

GrantsPath's Sovereignty Shield location verification system supports this work by validating your project's location and your Tribe's jurisdictional authority over the project area. During audits or jurisdictional disputes, having a verified location record on file — tied to your tribal recognition status and treaty/statutory authority — is significantly more defensible than reconstructing the record after the fact.

2 CFR 200: The Uniform Guidance

Every federal grant is governed by 2 CFR 200, commonly called the Uniform Guidance. This is the compliance framework that determines how you can spend grant money, how you track it, and what records you must keep.

You don't need to memorize all of 2 CFR 200 (it's hundreds of pages), but you do need to understand its major components.

Cost Principles (Subpart E)

These rules determine which expenses are allowable — meaning you can charge them to the grant — and which are not.

Key rules:

Costs must be necessary and reasonable for the project

Costs must be allocable to the grant (directly related to the project's activities)

Costs must be consistent with your organization's policies (you can't charge first-class airfare to a grant if your policy is coach)

Costs must be adequately documented

Commonly disallowed costs:

Alcohol (always unallowable)

Entertainment (generally unallowable unless directly programmatic)

Lobbying

Fundraising

Fines and penalties

Costs already covered by another funding source

Procurement Standards (Subpart D)

When you buy goods or services with grant money, you must follow procurement rules:

Tribal-specific note: Tribal governments may follow their own procurement policies if they are at least as restrictive as the federal standards. If your Tribe has an approved procurement policy, document that it meets 2 CFR 200 requirements.

Record Retention

Federal regulations require that you keep grant records for at least 3 years after you submit your final expenditure report (2 CFR 200.334). However, several circumstances extend this period:

If there's an ongoing audit, investigation, or litigation — keep records until it's resolved

If the grant terms specify a longer retention period — follow the grant terms

Many tribal grants professionals recommend 7 years as a safe standard, given the complexity of federal oversight cycles

What records to keep:

All financial records (invoices, receipts, payroll records, bank statements)

All programmatic records (reports, attendance lists, assessment data)

All procurement records (quotes, contracts, bid evaluations)

All correspondence with the federal program officer

Time and effort reports for grant-funded staff

Single Audit (Subpart F)

If your Tribe spends $750,000 or more in federal awards in a fiscal year (across all grants, not just one), you must have a Single Audit conducted by an independent auditor.

The Single Audit examines:

Your financial statements

Compliance with federal requirements for your major programs

Your internal controls

Why this matters: A clean Single Audit builds credibility with federal agencies and strengthens future grant applications. Audit findings (problems identified during the audit) can trigger corrective action requirements and may affect future funding.

Exercise: Compliance Readiness Checklist

Assess your organization's readiness against these prerequisites. For each item, mark whether it's Complete, In Progress, or Not Started:

1. Federal recognition is verified and your Tribe's name is consistent across all federal systems

2. SAM.gov registration is active and won't expire within 6 months

3. UEI is current and matches your organization's legal name

4. Grants.gov registration is active with current EBiz POC and AOR

5. Indirect cost rate — you either have a current NICRA or are using the 10% de minimis

6. Tribal resolution template is on file and can be adapted for new applications

7. Financial systems can track federal funds separately from other revenue

8. Procurement policy exists and meets or exceeds 2 CFR 200 standards

9. Record retention policy exists with at least a 3-year minimum (7-year recommended)

10. Single Audit is current (if applicable) with no unresolved findings

11. Tribal attorney is available to review agreements involving sovereign immunity

If any item is "Not Started," prioritize it before your next grant application. Items 1–4 are the most common blockers.

Key Takeaways

Federal recognition is the gating eligibility check for most federal grants — name consistency across all federal systems prevents registration mismatches

Tribal resolutions take planning — check council meeting schedules as soon as you identify a grant opportunity

SAM.gov and Grants.gov registration is the most common preventable disqualifier — verify before you start writing

Your indirect cost rate directly affects how much overhead each grant covers — negotiate a NICRA if you don't have one

Never sign sovereign immunity waivers without tribal attorney review

2 CFR 200 governs all federal grants — understand cost principles, procurement rules, and record retention requirements

How GrantsPath Helps

GrantsPath's profile consolidates the prerequisites covered in this module into structured fields: 574 Registry verification confirms federal recognition; compliance fields track your SAM.gov registration status and expiration, UEI, indirect cost rate (NICRA or de minimis), and Single Audit history; Sovereignty Shield validates your jurisdictional claims for project locations.

The benefit isn't just record-keeping. Your Fit Scores improve because the system can assess compliance readiness alongside programmatic fit — a grant requiring an audited financial history will score lower for organizations without one. A grant restricted to federally recognized Tribes won't appear at all if you're not on the 574 list. The compliance profile is what turns the rest of the platform from a search engine into a fit assessor.

Related guides: Sovereignty Shield · Profile Setup · Fit Scores

Tribal-Specific Requirements and Compliance Foundations