Why FORHP Applications and Awards Fail
FORHP grants have unique characteristics — rural designation requirements, consortium structures, network governance, and sustainability expectations — that create specific failure modes distinct from other federal grants. After reviewing hundreds of FORHP NOFOs, reviewer feedback, and compliance findings, these are the mistakes that most consistently cost organizations funding, trigger compliance actions, or undermine program effectiveness.
Each mistake below includes the specific problem, why it occurs, and the concrete prevention strategy. Many of these are preventable with advance planning and attention to the requirements described throughout this Rural Health Grants Program Guide.
Mistake 1: Incorrect Rural Designation
The problem: Applicants assume their service area is rural without verifying against the specific definition required by the NOFO. They use the wrong designation system (OMB when the NOFO requires RUCA, or vice versa), fail to check individual service delivery sites against the correct definition, or rely on outdated designation data from a previous census cycle.
Why it happens: The federal government uses multiple definitions of "rural" and the applicable definition varies by FORHP program. An area can be rural under one definition and metropolitan under another. Organizations that have previously qualified for one FORHP program assume they will qualify for all FORHP programs.
How to prevent it: Before beginning any FORHP application, verify your rural designation using the HRSA Rural Health Grants Eligibility Analyzer with the specific addresses of your service delivery sites. Check the NOFO to confirm which rural definition applies. Document your verification results and include them in your application. If you are near the boundary between rural and metropolitan, explore whether a RUCA exception applies. See the Eligibility guide for detailed designation requirements.
Mistake 2: Inadequate Consortium Documentation
The problem: Applicants assemble consortium members to meet the minimum requirement but provide only generic support letters, lack a formal governance agreement, or cannot demonstrate that the consortium has actually collaborated on the proposed project. During the grant period, consortium governance becomes sporadic or paper-only.
Why it happens: Organizations focus on meeting the minimum member count without investing in genuine partnership development. Consortium agreements are treated as administrative paperwork rather than functional governance documents. Once funded, the lead applicant manages the project independently rather than through the consortium structure.
How to prevent it: Invest in consortium development before the application deadline. Each partner's commitment letter should describe their specific role, the resources they will contribute, and how the partnership benefits their mission. Draft a consortium agreement that defines governance structure, decision-making processes, financial arrangements, and conflict resolution. During the grant period, hold regular governance meetings (at least quarterly), document attendance and decisions, and track each member's contributions. HRSA site visitors will ask consortium members directly about their participation.
Mistake 3: Sustainability Plan Gaps
The problem: The sustainability plan consists of vague statements about "seeking additional funding" or "exploring revenue opportunities" without specific strategies, timelines, or financial projections. Reviewers rate the impact section low, and during the grant period, no sustainability activities actually occur.
Why it happens: Sustainability planning is treated as a compliance exercise rather than a genuine strategic priority. Organizations focus on securing the grant and defer sustainability thinking to later years. The reality is that sustainability efforts must begin in Year 1 to be effective by the end of the project period.
How to prevent it: Develop a sustainability plan with specific revenue sources, financial projections, and milestones. Identify which activities will generate revenue (billable services, fee schedules, reimbursement rates) and project the timeline for those revenue streams to mature. Include sustainability milestones in your work plan so they are tracked alongside service delivery activities. In performance reports, document progress toward sustainability targets.
Mistake 4: Poor Needs Assessment Data
The problem: The application presents generic rural health statistics (e.g., "rural areas have higher rates of chronic disease") without specific data about the applicant's service area. National or state-level data is used when county or census tract data would be more relevant and compelling. The needs assessment does not connect to the proposed intervention.
Why it happens: Rural-specific data can be difficult to obtain at the sub-county level. Organizations default to widely available national statistics rather than investing the effort to find local data. The needs assessment is written as general background rather than as the evidentiary foundation for the proposed activities.
How to prevent it: Use the data sources described in the Application Guide (HRSA Area Health Resources Files, County Health Rankings, HPSA/MUA data, CDC WONDER, Census ACS). Present data at the most granular level available. Compare your service area to state and national benchmarks to demonstrate the specific disparity. For every data point, draw an explicit connection to your proposed activities: this need drives this intervention which will produce this outcome.
Mistake 5: Telehealth Licensing Oversights
The problem: Telehealth programs launch without ensuring that all providers are properly licensed in every state where patients receive services. Credentialing requirements between originating and distant sites are not addressed. HIPAA-compliant technology platforms are not verified before patient encounters begin.
Why it happens: Telehealth licensing rules vary by state and by profession, creating a complex compliance landscape. Organizations assume that a provider licensed in one state can serve patients in adjacent states via telehealth. The COVID-19 emergency waivers created temporary flexibilities that some organizations assumed were permanent.
How to prevent it: Before launching telehealth services, conduct a licensing audit for every provider who will deliver services, verifying licensure in each state where patients will be located. Identify applicable interstate compacts. Establish credentialing protocols between originating and distant sites. Verify that your telehealth platform has a current HIPAA Business Associate Agreement. Document all of this in your compliance files. Monitor state telehealth regulations for changes throughout the project period.
Mistake 6: Failure to Demonstrate Rural Impact
The problem: Performance reports describe activities and outputs (number of visits, number of patients) but fail to demonstrate that those activities improved health outcomes or addressed the rural health disparities identified in the application. Grant-funded services are concentrated in the most accessible locations rather than reaching the most underserved populations within the service area.
Why it happens: Organizations measure what is easy to count (visits, patients served) rather than what matters (health outcomes, access improvements, disparity reduction). Service delivery gravitates toward population centers within the service area because they are easier to reach, leaving the most remote and underserved communities underserved.
How to prevent it: From the start, establish baseline data for the health outcomes your program targets. Track outcomes alongside outputs. Report where services are delivered geographically — are you reaching frontier communities or concentrating in the most accessible rural areas? Use the Reporting guide to structure your performance measurement around outcomes rather than just outputs.
Mistake 7: Budget Misalignment with Work Plan
The problem: The work plan describes five major activities, but the budget only funds three. The budget allocates 60% to personnel but the work plan shows only 20% of activities requiring staff time. Consortium member budgets do not align with the roles described in their commitment letters. Equipment purchases in the budget have no corresponding activity in the work plan.
Why it happens: The narrative, budget, and work plan are developed separately, often by different people within the organization, without a systematic cross-check. Budget constraints force cuts that are not reflected in the narrative, or narrative revisions are made without corresponding budget adjustments.
How to prevent it: Build the budget from the work plan. For each work plan activity, identify the personnel, supplies, travel, equipment, and other resources required. Total those resources to create the budget. Then cross-check: every budget line item should trace to a work plan activity, and every work plan activity should have budget support. Have a different person review the budget-narrative alignment before submission. See the Budget guide for detailed budget development guidance.
Mistake 8: Late or Incomplete Performance Reporting
The problem: Performance reports are submitted after deadlines, missing required data fields, or with performance measures that do not match the approved work plan. Financial reports (SF-425) do not reconcile with the general ledger. Consortium member data is not collected in time for report compilation.
Why it happens: Reporting is treated as an after-the-fact documentation exercise rather than an integral part of project management. Data collection systems are not in place at the start of the grant. The complexity of collecting data from multiple consortium members is underestimated. Report deadlines conflict with other organizational priorities.
How to prevent it: Set up data collection systems during the first month of the grant period. Build reporting deadlines into your project management calendar with 30-day advance reminders. Establish data submission timelines with consortium members that give you adequate time to compile and review before HRSA deadlines. Reconcile SF-425 financial data with your general ledger before submission. Submit reports at least one week before the deadline to allow for EHBs system issues.
Mistake 9: CAH Condition of Participation Gaps
The problem: Critical Access Hospitals receiving SHIP or Flex funding experience compliance gaps in Conditions of Participation (CoPs) that affect both their Medicare certification and their FORHP grant standing. Common gaps include: average length of stay creeping above the 96-hour threshold, gaps in 24/7 emergency coverage documentation, quality assessment/performance improvement (QAPI) programs that exist on paper but do not function in practice, and expired transfer agreements.
Why it happens: Small rural hospitals operate with minimal administrative staff, and CoP compliance competes with daily operational demands. Length of stay is not monitored in real time. On-call coverage schedules have gaps during provider vacancies or transitions. QAPI committees meet infrequently because the same staff wear multiple hats.
How to prevent it: Implement automated average length of stay tracking in your EHR or patient management system with alerts when the running average approaches 96 hours. Maintain a rolling 12-month on-call coverage schedule and address gaps proactively. Schedule QAPI meetings at least quarterly with standing agenda items and documented improvement actions. Calendar transfer agreement renewal dates with 90-day advance reminders. Use SHIP funds specifically to strengthen CoP compliance infrastructure where allowable.
Prevention Framework
These nine mistakes share common root causes: insufficient advance preparation, treating compliance as an afterthought, and failing to integrate grant management into organizational operations. A prevention framework should include:
- Pre-application planning: Begin 6+ months before NOFO publication for programs you plan to pursue. Verify eligibility, cultivate consortium relationships, and collect needs assessment data in advance.
- Day-one compliance setup: On the first day of your grant period, establish data collection systems, execute consortium agreements, set up financial tracking, and calendar all reporting deadlines.
- Quarterly internal reviews: Review performance data, financial status, consortium participation, and compliance documentation quarterly. Do not wait for HRSA reporting deadlines to assess your status.
- Cross-functional review: Have different staff members review application sections for internal consistency. Budget, narrative, work plan, and consortium documentation should tell the same story.
- Technical assistance utilization: Contact your State Office of Rural Health, your HRSA Project Officer, and FORHP technical assistance resources proactively. Use the pre-application TA webinars that HRSA offers for each NOFO.
For organizations managing multiple FORHP grants or combining FORHP funding with other federal awards like HRSA Section 330 or CCBHC grants, the complexity of compliance management increases significantly. Centralized compliance tracking, standardized reporting processes, and clear cost allocation methodologies become essential infrastructure, not optional enhancements.