HRSA Operational Site Visit: what reviewers actually ask for.

There is a predictable gap between how health centers prepare for an Operational Site Visit and how the visit actually goes. Preparation tends to concentrate on the policy manual, because that is the document the organization controls and can perfect. The visit concentrates on whether the practice matches the policy, and it establishes that by pulling records.

Two documents, and they are not the same document

HRSA publishes the requirements in the Health Center Program Compliance Manual, and it publishes a separate Site Visit Protocol that tells reviewers how to assess them. The Manual says what compliance is. The Protocol says what a reviewer will look at to decide whether you have it.

If you only read one, read the Protocol — it is the operational document, it is far more specific about evidence, and it is revised much more often. As of this writing the Compliance Manual carries a 2018 revision date while the Site Visit Protocol was last updated in November 2025. A program built against the Manual alone is being built against the older of the two.

Their chapter numbers do not correspond, which causes more confusion than it should. Clinical Staffing is Chapter 5 of the Compliance Manual and Chapter 3 of the Site Visit Protocol. Board Authority is Chapter 19 in one and Chapter 17 in the other. If you organize evidence folders by chapter number — and many centers do — label which document you are numbering against, or the folder that says “Chapter 19” will be opened by someone looking for something else.

Reviewers sample. That changes what “ready” means

The Protocol does not ask for every file. For clinical staffing it calls for a set of current clinical staff files spanning categories: several licensed independent practitioners, several other licensed or certified practitioners, and a smaller number of other clinical staff where the center has them.

The consequence is worth stating plainly, because it inverts the intuitive preparation strategy. You cannot prepare the files that will be reviewed, because you do not know which they are. Consistency beats depth. Ten files that are each 90% complete survive sampling better than three perfect files and seven that were never finished — and the second situation is far more common, because attention naturally goes to the providers who generate questions.

What “evidence” means in practice

Almost every finding reduces to one of three failures, and none of them is about not having a policy:

• The thing was done but not recorded. A verification happened; nobody kept the response. A decision was taken; the minute does not reflect it.
• The record exists but cannot be produced. It is in a share drive, an inbox, and a binder, and assembling it takes longer than the visit allows.
• The record contradicts the policy. The manual says annual; the files show every eighteen months. This is the expensive one, because it is not a documentation gap — it is a practice gap the documentation revealed.

A preparation sequence that matches how the visit runs

Work backwards from the Protocol rather than forwards from your manual:

• Read the current Site Visit Protocol chapter for each area and list the documents it names. That list, not your policy index, is the inventory.
• For each document, answer two questions: where does it live, and who can produce it without asking anyone. If the second answer is one person, that is a risk regardless of how good the document is.
• Pull your own sample. Choose files at random — genuinely at random, not the ones you know — and check them against the Protocol's elements. What you find in your own sample is what a reviewer would find in theirs.
• Fix the pattern, not the file. A gap found in two random files is present in more of them.
• Re-check that your policies describe what your files show. Where they differ, decide which one is wrong before someone else decides for you.

None of this requires software. It requires that somebody own the inventory and re-run the sample periodically — which is the part that tends not to survive a busy quarter, and the reason HRSA readiness exists as a continuous measure rather than a pre-visit project.