DEA Compliance → Audit Readiness
Purpose
Use CS Logbook's audit-prep and corrective-action tools to get ready for a DEA inspection or state-board visit: working a readiness checklist, tracking document requests and findings, and following findings through to a documented corrective action. CS Logbook organizes your preparation; the inspection scope and any findings come from the inspecting authority.
This is general product information about CS Logbook, not legal advice. CS Logbook's checklists are a preparation aid; they do not certify compliance and are not a substitute for the inspector's scope. Verify expectations with the DEA Diversion Control Division and your state board.
In CS Logbook
Three features support inspection readiness:
- Inspection packet: bundles the reports an investigator asks for, over a date range you choose, into one archive with a manifest. It includes a separate Schedule II copy of the transaction log and the biennial inventory, an index of your uploaded documents, and a SHA-256 of every file so each can be checked against the manifest. The manifest also names what the system cannot produce, with a reason, so nothing appears to be missing by accident.
- DEA audit preparation: a category-based readiness checklist that maps to the records an inspector typically reviews (inventory, prescription, acquisition, disposal, theft/loss, registrations, security, training). You can track document requests and record findings.
- Corrective actions (CAPA): findings from an audit or incident are tracked in a queue and are tracked from open through to verified completion.
How to use them:
- Reports → Recordkeeping Reports → Inspection packet
- Audits → DEA Audit Preparation
- Compliance → Corrective Actions
The checklist is your internal preparation tool: it is never sent to the DEA, and completing it does not certify compliance. Its value is finding gaps before the inspector does.
The same limit applies to the packet: it gathers records you already keep, it does not decide what you are required to retain, and downloading it is not a filing.
Where the official requirement lives
CS Logbook does not define inspection scope or outcomes. The authoritative sources are:
- DEA Diversion Control Division: inspections, registrant obligations, and guidance.
- eCFR, Title 21, Part 1304, the records an inspection draws on.
- Your state board: many conduct parallel inspections with their own scope. CS Logbook does not track what any state board inspects; ask yours what it covers.