Executive summary. Classifying scope, authority, due date, and requested evidence early keeps a rushed response from turning into an uncontrolled document search.

Definition

Audit-request triage is the initial assessment of an audit notice to establish its scope, deadlines, authority, and response workflow.

Capture the notice as received

Preserve the original notice, the sender, the time received, the named authority, the deadline, the affected period, and the records requested. A paraphrase in a task title loses the scope you will be held to.

Decide whether the response needs legal, compliance, operational, or payer-contract review before anybody transmits a document.

Constrain the collection

Build an evidence manifest tied to each request item. Collect what is responsive, and avoid broad exports carrying unrelated protected or confidential information.

Where scope is unclear, document the clarification request and the answer. Assumed scope is the most common cause of overproduction.

Frequently asked questions

Should audit evidence be gathered in email?

Email works as a communication channel. Manifests, artifacts, access, and submission history belong in a controlled record or repository.

Referenced standards and further reading

Related articles

PBM audit readiness →

Evidence manifests make audit packages reviewable →

A recoupment response workflow needs decision records →

Revision history

2026-08-05 · 1.0, initial public reference · Published by Ryan Stringer.