Ryan White Compliance: What Clinic Leaders Need to Know Before the Next Site Visit
Ryan White site visits are not formalities. They are structured reviews of your program's fiscal management, clinical performance, administrative systems, and service delivery against the terms of your grant agreement. Programs that treat site visits as a once-every-few-years event they have to survive tend to find them stressful. Programs that build compliance into their daily operations find them manageable.
Understanding what reviewers are actually looking for is the first step toward building that kind of operational culture.
What Site Visitors Are Reviewing
Ryan White site visits typically cover four domains.
The first is fiscal compliance. Reviewers will examine your expenditure reports, budget modifications, and documentation supporting claimed costs. They want to confirm that Ryan White funds were spent on allowable activities for eligible clients and that your financial records match what was reported to the funder.
The second is clinical quality. Reviewers look at core clinical quality measures including viral suppression rates, retention in care, and linkage to care timelines. They may pull a sample of medical records to verify that service documentation supports the visits billed or reported.
The third is administrative and program management. This includes your policies and procedures, staff qualifications and training records, client eligibility documentation, and your quality management plan. Outdated or incomplete documentation in any of these areas is a common finding.
The fourth is client services. Reviewers may interview staff or clients to assess whether services are being delivered as described in your program plan and whether clients are aware of and able to access the services they are entitled to.
Common Findings and What They Signal
The most common Ryan White compliance findings are not the result of fraud or intentional mismanagement. They are almost always the result of systems that were not built to sustain documentation requirements over time.
Frequent findings include:
- Client eligibility files that are incomplete or contain expired documentation
- Quality management activities that are not formally documented or tracked
- Expenditures that lack adequate supporting documentation
- Staff training records that are not current or are missing for required topics
- Service documentation that does not match reported outputs
Each of these is correctable. The risk is when multiple findings appear together, which signals to the funder that program management is not maintaining adequate oversight.
How to Prepare
The most effective preparation for a site visit is a structured internal review conducted at least 60 days before the scheduled visit. Pull a sample of client files and verify that eligibility documentation is current and complete. Review your expenditure records and confirm that supporting documentation is organized and accessible. Check that your quality management plan is current and that meeting minutes and improvement activities are documented.
Assign a staff member to own site visit preparation as a defined responsibility, not a task that falls to whoever has time. Build a preparation calendar that starts 90 days out and works backward from the visit date with specific tasks and deadlines assigned.
What to Do Next
If your program has not conducted an internal review of your Ryan White compliance documentation in the past year, that is the place to start. Pull your client files, your financial records, and your quality management documentation and assess where the gaps are before a site visitor does.
If you want support preparing for a Ryan White site visit or building compliance systems that hold between visits, our team can help.