How to Build a RADV Response Playbook Before the Audit Letter Arrives

The Playbook Nobody Writes Until It’s Too Late

Most health plans don’t have a documented RADV response playbook. They have people who’ve been through audits before, institutional knowledge about what CMS expects, and ad hoc processes that get assembled when the notification arrives. This works when audits are rare. It fails when audits are annual and concurrent.

A RADV response playbook defines the end-to-end process before the audit begins: who’s responsible for each step, what systems contain the needed data, how evidence packages are assembled, what quality checks apply before submission, and how rebuttals are developed. It’s the difference between a fire drill and an actual emergency response plan.

The Four Phases of RADV Response

Phase one is notification processing. When CMS sends the enrollee data list, the team identifies every sampled enrollee, maps their submitted HCCs, and triggers the evidence retrieval process. This should take days, not weeks. Plans on unified systems can automate the mapping. Plans on fragmented systems spend this phase locating data across disconnected environments.

Phase two is medical record retrieval and validation. For each sampled enrollee, the team retrieves the relevant clinical documentation and validates it against MEAT criteria for every submitted HCC. This is where documentation strength determines audit outcomes. Records with strong MEAT evidence proceed. Records with weak evidence trigger escalation: can stronger documentation be found from a different date of service within the payment year? If not, the plan knows which codes are vulnerable before submitting.

Phase three is record selection and package assembly. CMS allows plans to submit documentation from any date of service within the relevant calendar year, not just the encounter that originally generated the code. The team selects the record that provides the strongest MEAT evidence for each sampled HCC. The package is formatted to CMS RADV specifications and submitted through the required system within the five-month window.

Phase four is rebuttal preparation. Before submitting records, the team should pre-identify codes where findings may be discrepant and draft rebuttal arguments. When CMS returns findings, the rebuttal team isn’t starting from scratch. They’re refining arguments they’ve already developed.

Building the Playbook Before the Audit

The playbook should be documented, tested, and updated annually. Run a mock RADV audit quarterly: randomly select 50 to 100 enrollees, process them through all four phases, and measure time-to-completion, evidence quality, and identified weaknesses. Each mock audit reveals process gaps that can be fixed before real audit pressure arrives.

Assign roles and backups for every function. If the lead analyst is unavailable during an audit response, someone else must be trained and authorized to execute. Single points of failure in audit response create deadline risk that compounds under concurrent audit cycles.

From Reactive to Prepared

Plans that document and rehearse their RADV response process handle radv audits with operational discipline rather than emergency improvisation. The playbook converts institutional knowledge into repeatable process, ensures continuity regardless of staff changes, and produces consistent response quality across concurrent audit cycles. Plans without one are betting that the same ad hoc approach will scale to annual audits with variable samples and quarterly cadence. That bet gets worse with every audit cycle.