Rural hospitals, clinics, schools, fire and EMS stations, libraries and municipal buildings — studies written to the questions a Community Facilities reviewer actually asks.
A Community Facilities project is not underwritten like a business. The Agency is financing something a rural community needs — a critical access hospital, a school, a fire station, a clinic, a public safety building — and the analysis has to establish two things at once: that the facility is essential to the service area, and that the sponsor has a revenue base that can carry the debt for the term of the loan.
Those are different burdens of proof than a B&I file. Essentiality is demonstrated with population served, distance to the nearest alternative facility, service-level data, and the condition or capacity limits of what exists today. Revenue support is demonstrated with the sponsor's own financial history, its taxing or rate-setting authority where it has one, payer mix and utilisation for healthcare, enrolment for schools, and the contractual or statutory sources behind each line.
Community Facilities financing runs on two tracks, and the applicable regulation depends on which one your file is on. CF guaranteed loans sit inside the OneRD framework at 7 CFR Part 5001, alongside Business & Industry, REAP and Water & Waste. CF direct loans are administered under their own regulation, 7 CFR Part 1942, Subpart A.
The practical difference for the study is who reads it and what they weight. On a guaranteed file, the lender packages the credit and the Agency reviews the guarantee — so the report has to satisfy a commercial credit committee and a Rural Development reviewer with the same set of pages. On a direct loan, the Agency is the lender, and the essentiality and public-purpose analysis carries proportionally more weight. We ask which track you are on before scoping, because the emphasis moves.
Rural hospitals, critical access hospitals, clinics and long-term care facilities are the most demanding CF studies, and the most commonly returned. The reason is almost always the same: a demand case built on population alone, with no payer analysis behind the revenue. A rural hospital's viability is a function of service-line volumes, the payer mix behind those volumes, reimbursement policy the sponsor does not control, and a physician and staffing pipeline in a market that is competing for the same clinicians.
We build those files with utilisation and discharge data for the service area, out-migration analysis showing where residents currently go for care and why, payer mix from the sponsor's own history, and a staffing plan tested against what the market can actually recruit. Where the numbers do not support the project as proposed, the report says so and identifies what would have to change — a determination a reviewer can rely on is worth more to a sponsor than an optimistic one that comes back with comments.
The engagement opens with a data request the day it is signed, because CF files slow down waiting on sponsor information — audited financials, the capital improvement plan, the rate or levy history, service-line volumes — not on the analysis. We work from sources a reviewer can check: Census and American Community Survey data at tract level, state health and education agency series, CMS and HRSA data for healthcare, the sponsor's own audited statements, and primary interviews with administrators and referring providers where the published data stops.
Standard delivery is 10 to 15 business days from a complete data room. The fee is fixed, quoted before work starts, and never contingent on the finding — a contingent fee would defeat the independence the Agency requires of the study's author.