An audit-ready Florida binder answers who may act, what evidence gets retained, and when an issue becomes regulator-visible. Inspections can be announced or unannounced, run at least biennially, and can be triggered by complaints. False records and failure to maintain required records are explicit grounds for action, so the evidence package matters nearly as much as the correction itself.
The high-priority SOP set
Eight SOPs cover most of the Florida control surface. Each names its minimum evidence and a clear escalation trigger.
| SOP | Minimum evidence retained | Escalate when |
|---|---|---|
| Daily BioTrack / POS reconciliation | Variance sheet, unmatched-receipt log, fix queue, supervisor sign-off | A mismatch is not explained by an in-flight transfer, void, or return |
| Daily MMUR reconciliation | Route-level exception list, allotment checks, receipt samples | Route mismatch, unexpected hold, or amount-eligible conflict |
| Receiving internal transfers | Manifest, sent / received / rejected quantities, room placement | Manifest and package quantities do not agree |
| Delivery assignment and return | Route sheet, manifest, packed-status review, undeliverable notes | A packed order is not completed or a hold is not released |
| Production batch and yield | Input lots, output lots, waste, ingredients, lab sample IDs | Output plus documented loss does not reconcile to input |
| Waste and destruction | Scheduled and performed destruction, reason, witness log, package IDs | Destruction is delayed after a return, or performed without a proper schedule |
| Void, refund, and return review | Original and corrected receipt, disposition note, package history | Staff used a refund when a void was required, or the reverse |
| Failed-sync investigation | Error text, screenshot, package ID, transaction ID, retry log, ticket | A sale cannot be proven in both systems, or a repost would distort the audit trail |
The audit-prep checklist
Before an OMMU review or an internal mock audit, an MMTC should be able to produce, on demand:
- The current rule-version log
- Package-level active inventory by room
- All open transfers and manifests
- All adjustments with reasons and approvers
- All destruction schedules and completed disposals
- Receipt-audit results by day
- MMUR route and amount-eligible exception logs
- Evidence for returns and destroy-only packages
- Lab-linked final product detail, including THC and CBD fields
- A reconciled list of unresolved discrepancies with owner, age, and remediation date
Who owns what
Most Florida exceptions trace back to a handful of concepts, so training is split by role around them:
- Retail associates: route, order type, package, refund, and void.
- Inventory managers: package history, manifest state, room assignments, destruction workflows.
- Processing managers: lot lineage, conversion math, ingredients, yield-loss documentation.
- Compliance leads: the rule log, exception approvals, and escalation thresholds.
- POS administrators: user permissioning, error-review cadence, audit exports, rule-change tests.
Correcting the cause, not the symptom
The habit that saves you in Florida is refusing to correct only the symptom. A quantity variance can turn out to be a route-mapping error, a route issue can be a misclassified product, a delivery hold can be a manifest-state problem, and a package mismatch is often a failed sync that got "fixed" in the wrong direction. The rules, the MMUR architecture, and the API-driven environment all push you the same way: reconcile by package lineage, event timing, route logic, and patient impact together, not one axis at a time. Patch the visible number without chasing the cause and the audit trail drifts even when the on-hand counts look right.
Building the binder around evidence
Build the binder around evidence and roles, not just corrections. Inspectors can arrive unannounced, and weak records are a violation on their own, so being able to show how a discrepancy was found and resolved matters as much as the corrected number.