Grants vs. Contracts vs. Cooperative Agreements: The RHTP Mechanism Choice That Determines Everything
Whether your state issues grants, contracts, or something else entirely changes what you need to prepare, how you'll be paid, and whether your organization can realistically compete. Here's the full state-by-state picture.
Grants vs. Contracts vs. Cooperative Agreements: The RHTP Mechanism Choice That Determines Everything
You're preparing for your state's RHTP sub-grant. But do you know whether your state is issuing grants, contracts, or something else entirely? The answer changes what you need to prepare, how you'll be paid, and whether your organization can realistically compete.
Most guidance about RHTP preparation starts with the same advice: register on SAM.gov, get your UEI, build a cost allocation methodology, prepare for 2 CFR 200 compliance. That advice is correct — for some states. In others, it's incomplete or misleading.
The reason is that states are not all using the same legal and financial mechanism to distribute RHTP funds to providers. Some states are issuing grants through competitive RFAs, which triggers the federal Uniform Guidance (2 CFR 200) and everything that comes with it. Other states are issuing contracts through their state procurement systems, which triggers an entirely different compliance framework. A few are doing both simultaneously. And at least one state has four distribution channels running in parallel, each with its own rules.
If you are a rural health provider preparing for RHTP — a CAH finance director, an FQHC executive, a tribal health administrator, a CCBHC compliance officer — the mechanism your state chose is the single most important thing to understand before you write a single word of your application. It determines the compliance framework you'll operate under, whether you can recover indirect costs, how you'll be paid, how long the procurement process takes, and whether small organizations can realistically participate.
Here is what we know about how each state is structuring its distribution, and what it means for you.
The Three Mechanisms
Before diving into state-by-state details, it's worth understanding the fundamental differences between the three distribution mechanisms states can use.
Grants (via RFA or RFGP) are the mechanism most people expect. The state issues a Request for Applications, organizations submit proposals, reviewers score them, and winners receive a grant award. The federal Uniform Guidance (2 CFR 200) governs the compliance relationship. Sub-grantees must maintain a cost allocation methodology, track time and effort, submit federal financial reports, and — if they spend more than $750,000 in federal funds in a year — undergo a Single Audit. Indirect costs are generally recoverable, either at a negotiated rate or the 10% de minimis rate. This is the mechanism that most grant readiness guidance assumes.
Contracts (via RFP, RFO, or state procurement portal) create a fundamentally different relationship. The state is purchasing services, not awarding a grant. The compliance framework is the state's procurement code, not 2 CFR 200. Contract terms are often fixed-price or deliverables-based rather than cost-reimbursement. Indirect cost recovery may not be available or may be structured differently than under a grant. Importantly, state procurement processes often take longer — Washington's WEBS system, for example, typically involves a 5–7 month cycle from solicitation to contract execution. And state procurement portals require separate registration that has nothing to do with SAM.gov.
Cooperative agreements are less common at the state-to-provider level but show up in several RHTP implementations. A cooperative agreement is structurally similar to a grant, but the awarding entity (in this case, the state) retains substantial involvement in the project's execution. The compliance framework is generally 2 CFR 200, but the state may impose additional oversight, reporting, or approval requirements beyond what a standard grant would require. North Carolina's hub lead model has cooperative-agreement characteristics: NCDHHS isn't just funding hub leads, it's actively shaping implementation through regional alignment requirements, reimbursement-based payment, and close programmatic oversight.
The State-by-State Landscape
Based on publicly available solicitation documents and program announcements as of late March 2026, here is how the active and near-active states are distributing RHTP funds:
Grant Model States
Kansas — KDHE is issuing competitive grants through RFAs. The $44 million Regional Partnerships Grant Program (RPGP) and the $15 million REH/CAP Grant are both grant instruments. Applications are submitted through the KDHE online portal, not the state procurement system. Standard 2 CFR 200 compliance applies. Kansas also runs a direct contract with CCA (Care Collaborative Association) for statewide program administration and a dedicated sub-grant to KATCH for tribal programs. If you are a Kansas provider, you are applying for a grant, and your compliance preparation should center on cost allocation methodology, indirect cost rate (negotiated or de minimis), and Single Audit readiness.
Nebraska — DHHS is running three simultaneous RFAs (workforce, chronic disease, food-as-medicine) as competitive grants. Eligible entities apply directly to DHHS. The grant model means 2 CFR 200 applies and smaller organizations — including tribal health facilities, which are explicitly named as eligible — can use the 10% de minimis rate if they don't have a negotiated IDC rate. Nebraska's direct competition format, without a hub intermediary, makes this one of the most accessible models for small providers.
Delaware — DHSS/DPH is distributing funds through competitive RFPs posted on the state procurement portal (mmp.delaware.gov/Bids). Despite using the procurement portal for logistics, the solicitations are structured as grant-like awards with multiple funding levels. Delaware opened six of its fifteen planned RFPs on February 9, with awards ranging from $195,000 (school-based health centers) to $5.5 million (health hubs).
Oregon — OHA is using a competitive RFGP (Request for Grant Proposals) for its Catalyst Awards track, which represents roughly 40% of available funds. This is explicitly a grant mechanism, and 2 CFR 200 compliance applies. Oregon also has Immediate Impact Awards (non-competitive, state-selected) and Regional Sustainability Awards (subcontractor model). The tribal initiative is a direct set-aside outside the RFGP process entirely. If you're applying for a Catalyst Award, prepare for standard grant compliance. If you're being considered for an Immediate Impact Award, the state will approach you — there is no application.
New Jersey — NJDOH used a competitive RFA for its first-year solicitation, structured into four funding activities (A through D). The application deadline closed January 20, 2026. Standard grant compliance framework applies.
Contract Model States
Washington — HCA has explicitly named WEBS (Washington's Electronic Business Solution) as the procurement channel for sub-grantee solicitations. WEBS is a state procurement portal — organizations register as vendors and submit bids in response to RFPs. This means Washington is using a contract mechanism, not a grant mechanism. The compliance framework will be Washington state procurement law, not 2 CFR 200. Organizations that have been preparing their cost allocation methodology and indirect cost rate for a 2 CFR 200 sub-grant may find that those preparations don't map directly to a state contract. Registration on WEBS is a prerequisite — SAM.gov alone won't get you in the door. The April 14 HCA webinar should clarify the specific compliance terms, but organizations should register on WEBS now if they haven't already.
Texas — HHSC is distributing funds through the Electronic State Business Daily (ESBD), the state's procurement portal. Texas is using at least four different instrument types across its six initiatives: direct awards to Rural Hospital Districts (Initiative 1), Requests for Proposal (Initiatives 2 and 3), Requests for Application (Initiatives 4 and 6), and a Request for Offer (Initiative 5). The RFP and RFO instruments are procurement mechanisms governed by Texas state contract law. The RFA instruments for Initiatives 4 and 6 may be grant-like, but the compliance terms won't be clear until the solicitations are published. Organizations should monitor ESBD and subscribe to HHSC GovDelivery notices. Note: HHSC has explicitly stated it is not meeting with potential applicants during the solicitation process to maintain procurement fairness.
Multi-Channel States
Montana — DPHHS is running four parallel distribution channels, each with its own mechanism and compliance framework. Channel one: competitive procurement on bids.mt.gov (the eMACS system), which creates a state contract, not a grant. Channel two: grant applications via the Submittable platform for rural providers and community organizations. Channel three: inter-agency agreements with the Department of Labor and Industry for the $21 million Workforce Development initiative. Channel four: government-to-government contracts with tribal nations, though the specific mechanism hasn't been published. Montana is the most structurally complex distribution model in the program. If you're a small rural provider in Montana, your entry point is likely the Submittable grants — not the eMACS procurement channel, which favors larger organizations competing as prime contractors. DPHHS has indicated a preference for working with fewer statewide partners, which means subcontractor roles under a prime may be more realistic for smaller organizations.
Intermediary Model States
North Carolina — NCDHHS uses a hub lead model that blends grant and cooperative-agreement characteristics. Six regional hub leads are being selected through a competitive RFA (hub lead applications due April 28). But individual providers — CAHs, FQHCs, community-based organizations — don't apply to NCDHHS at all. They apply to or partner with a hub lead in their Medicaid region. The hub lead manages the sub-recipient relationship, serves as fiduciary, and operates on a reimbursement basis: the hub pays expenses first, then requests reimbursement from NCDHHS. This means the compliance relationship for a provider-level organization depends on the terms its hub lead sets, not directly on NCDHHS's solicitation. If you're a North Carolina provider, your first question isn't "what does NCDHHS require?" — it's "which hub lead will operate in my region, and what will they require of their network partners?"
Alaska — ADOH contracted with the Alaska Community Foundation (ACF), a philanthropic intermediary, to manage the entire subrecipient application process. Organizations submit Letters of Interest through ACF's portal and are routed to one of four pathways based on readiness (Administrative Readiness, Planning, Project Implementation, or Targeted Innovation). This is structurally unique — no other state uses a philanthropic intermediary. The compliance relationship is between the organization and ACF, with ACF managing the federal compliance obligations at the intermediary level. This design deliberately reduces the compliance burden on smaller organizations, particularly tribal health programs and village-level entities that may lack grant management infrastructure.
Why the Mechanism Matters: A Practical Comparison
| Factor | Grant (RFA/RFGP) | Contract (RFP/RFO) | Hub/Intermediary |
|---|---|---|---|
| Compliance framework | 2 CFR 200 (Uniform Guidance) | State procurement law | Varies — set by hub/intermediary |
| Indirect cost recovery | Yes — negotiated rate or 10% de minimis | Often limited or not available | Depends on hub terms |
| Payment model | Advance or reimbursement (varies by state) | Deliverables-based or milestone | Typically reimbursement |
| Single Audit required? | Yes, if >$750K federal spend | Not typically | May apply at sub-recipient level |
| SAM.gov required? | Yes | Usually no — state portal registration instead | May or may not |
| Procurement timeline | 60–120 days typical | 90–210 days typical | Varies |
| Accessibility for small orgs | Moderate — compliance overhead is real | Lower — procurement favors established vendors | Higher — hub absorbs compliance |
| Key registration | SAM.gov, UEI | WEBS, ESBD, eMACS, or state equivalent | Intermediary portal |
What This Means for Your Preparation
The mechanism choice splits your preparation strategy into three distinct paths.
If your state is using a grant model (Kansas, Nebraska, Delaware, Oregon, New Jersey): Your preparation checklist is the standard 2 CFR 200 readiness stack. Confirm your SAM.gov registration is active and your UEI is current. Establish or document your cost allocation methodology. Decide on your indirect cost rate — if you don't have a negotiated rate, you can elect the 10% de minimis rate. Check whether your organization exceeded the $750,000 Single Audit threshold in the prior fiscal year, and if so, ensure your audit is current. Build your budget using the grant's allowable cost categories. Prepare a staffing plan with time-and-effort tracking capability.
If your state is using a contract/procurement model (Washington, Texas, Montana via eMACS): Your preparation is different. Register on the state procurement portal — WEBS in Washington, ESBD in Texas, bids.mt.gov in Montana. Review the state's standard contract terms and conditions, which are usually posted on the procurement portal. Prepare for a deliverables-based or fixed-price contract rather than cost-reimbursement. Indirect cost recovery may not be available. Your compliance obligations will be state-specific, not federal. If your organization is accustomed to federal grants but new to state contracts, the transition requires meaningful adjustment — different reporting cadences, different audit requirements, different dispute resolution processes.
If your state uses a hub or intermediary model (North Carolina, Alaska): Your preparation depends less on your own compliance infrastructure and more on the intermediary's requirements. In North Carolina, identify which hub lead candidates are likely to serve your region and understand what they will require of network partners. In Alaska, submit your LOI through ACF's portal and let the readiness pathway system determine your entry point. The intermediary model reduces the compliance burden on individual providers, which is a deliberate design choice — but it also means you have less control over timeline and terms.
If your state is Stage 0 with no announced mechanism: You face the hardest preparation challenge: you don't know which path to prepare for. The safest strategy is to prepare for the grant path (SAM.gov, cost allocation, IDC rate, Single Audit) and simultaneously register on your state's procurement portal. When the mechanism is announced, you'll be ready for either. Don't wait for the solicitation to start compliance preparation — every prerequisite takes weeks, and if your state announces an RFA with a 30-day window, you won't have time to build from scratch.
The Equity Dimension
The mechanism choice isn't just a technical compliance question. It's an equity question.
Grant models with 2 CFR 200 compliance are familiar to FQHCs (which manage HRSA grants) and larger health systems. They are less familiar to small RHCs, independent CAHs, and tribal health programs that have operated under Medicaid reimbursement or IHS contracts but never managed a federal sub-award.
Contract models favor organizations with state procurement experience — typically larger systems, established consulting firms, and organizations with dedicated contracts departments. A 5-person Rural Health Clinic doesn't have a contracts department.
Hub and intermediary models are the most accessible for small organizations, but they introduce a dependency: the hub or intermediary becomes a gatekeeper, and a small provider's access to RHTP funds depends on the hub's capacity, priorities, and contracting speed.
Alaska's readiness-tiered pathway model is the most structurally creative response to this equity problem — it meets organizations where they are rather than requiring them to meet a uniform compliance threshold. Whether other states adopt similar approaches in Years 2–5 may depend on how effectively the first-year models reach the providers that RHTP was designed to serve.
GrantBridges tracks distribution mechanisms, solicitation status, and compliance requirements across all 50 states. Subscribe to The RHTP Weekly for weekly updates as new solicitations drop and mechanisms are announced.
Methodology note: Mechanism classifications are based on publicly accessible solicitation documents, state program pages, and procurement portal postings as of March 22, 2026. States classified as "grant model" have issued or announced RFA/RFGP instruments. States classified as "contract model" have announced procurement via state purchasing portals (WEBS, ESBD, eMACS). Multi-channel and intermediary classifications reflect published implementation plans. States at Stage 0 with no published mechanism are not classified. Mechanism assignments are updated as new solicitations are published.