Start with the audit scope, not the software screen
The strongest METRC audits start by defining what you are validating, who owns each workflow, and which date range you are testing. Pick a recent operating window, list the rooms, batches, packages, and transfers touched during that period, and confirm you can trace each of them from the physical floor to the system of record. If your team cannot explain the scope in one paragraph, the audit usually devolves into reactive searching instead of controlled review.
- Choose a fixed review period such as the prior 14 or 30 days
- Assign owners for cultivation, inventory, compliance, and dispatch
- List the physical areas, package groups, and transfer activity in scope
- Document the reports and screenshots you expect to export before you begin
Why this matters
Auditors rarely care only about a single transaction. They care whether your operation can prove control across a complete workflow without improvising the story in real time.
Audit package creation, movement, and conversion logic
Packages are where most teams accumulate silent risk. Review how harvest lots become packages, how packages split or combine, and how weights, units, and status changes are controlled. A compliant workflow is not just about entering the transaction in METRC; it is about proving the physical inventory, internal records, and state record all agree. Every conversion step should have clear ownership, timing expectations, and a way to investigate discrepancies without guesswork.
- Validate package creation against harvest and processing source material
- Check split, combine, and conversion events for accurate quantity math
- Review quarantine, hold, remediation, and disposal status handling
- Confirm internal location changes map cleanly to package accountability
Review transfers, manifests, and chain-of-custody evidence
Outbound transfers create regulatory exposure because they involve both inventory accuracy and time-sensitive documentation. Confirm that manifests are generated from approved package selections, vehicle and destination details are current, and departure and receipt events reconcile cleanly. The best teams treat transfer preparation as a controlled release process, not an end-of-day scramble. That means the physical staging area, the manifest, and METRC should all tell the same story before the vehicle leaves the site.
- Confirm manifests match staged packages and weights before departure
- Verify driver, vehicle, route, and receiving-party data are current
- Review partial receipts, rejected packages, and returned inventory handling
- Document when dispatchers are required to escalate a transfer mismatch
Test adjustments, waste, and exception handling
Adjustment workflows reveal whether the operation is disciplined or improvisational. Inspect the thresholds that trigger investigation, the documentation required for losses or corrections, and the approval path for changes that alter state inventory. Waste workflows should be equally defensible: who witnessed it, how it was recorded, where supporting photos or logs live, and how the physical disposal process aligns with the system event. Exception handling should reduce compliance risk, not merely clean up inventory reports after the fact.
- Set documented variance thresholds for escalation and root-cause review
- Require reason codes and notes for every inventory adjustment
- Validate waste logs against witness, destruction, and disposal evidence
- Track repeat adjustment patterns by room, operator, or workflow
Common failure mode
Teams often use adjustments as a catch-all cleanup tool. Regulators tend to read repeated vague adjustments as a process-control problem, not an honest clerical correction.
Map state-specific variations before calling the checklist complete
METRC provides the system framework, but the regulator still defines how your state wants certain workflows documented, timed, or approved. California teams need to align with DCC expectations and internal CCTT references, Colorado operators should treat package adjustments and variance timing as first-class controls, Michigan teams need to reconcile rapid growth against CRA reporting discipline, New York operators should track how OCM guidance evolves as the market matures, and Florida teams must keep vertical integration workflows clean across cultivation, processing, and dispensing. A real compliance checklist always names the local regulator, the effective policy dates, and any state overlays that sit on top of METRC itself.
- California: map DCC and CCTT handoffs, especially for transfers, waste, and tag replacement records
- Colorado: verify MED timing for package adjustments, reconciliations, and investigation follow-up
- Michigan: confirm CRA reporting cadence and multi-facility rollups stay aligned as volume grows
- New York: keep OCM documentation current as licensing, social equity, and launch guidance shift
- Florida: document vertical integration controls across cultivation, processing, and dispensing
Run a weekly control rhythm instead of waiting for the quarterly panic
Most compliance teams know what good looks like; the problem is consistency during busy weeks. Build a weekly operating rhythm that includes floor counts, discrepancy review, open-transfer cleanup, package exception review, and SOP signoff. Short recurring reviews outperform heroic all-day audits because they catch breaks while the people involved still remember what happened. If you only look deeply at METRC when an inspection is announced, you are already late.
- Schedule a fixed weekly reconciliation with named owners and deadlines
- Review open exceptions before they age into untraceable cleanup work
- Capture recurring issues in a variance log with corrective actions
- Close the meeting with clear accountability for unresolved items
Use workflow examples your team can rehearse
Checklists become more useful when they mirror the actual moments where mistakes happen. Rehearse a few core scenarios end to end: a harvest moving into packages, an outbound transfer with a late change, a failed lab sample that requires inventory handling, or a discrepancy discovered during a cycle count. These examples force the team to prove not only that the clicks exist in METRC, but that the handoffs between cultivation, inventory, and compliance are reliable under normal pressure.
- Harvest to package: confirm source weights, package math, and tag lineage
- Transfer prep: validate staged inventory, manifest data, and receiving details
- Variance investigation: document who investigates, where evidence lives, and when to adjust
- Audit request drill: export logs, SOPs, and screenshots in a repeatable order
Pre-build your audit evidence pack
A regulator should never be the first reason you assemble your evidence. Maintain a lightweight compliance binder or shared workspace that includes SOPs, training records, variance logs, sample manifests, package reconciliation reports, and screenshots that show system configuration. The pack does not need to be flashy. It needs to be current, searchable, and easy for a manager to hand over without digging through inboxes, chat threads, or someone’s desktop downloads folder.
- Keep current SOP versions with owners, approval dates, and review cadence
- Store training completion history for staff who touch regulated workflows
- Archive sample reports, manifests, and reconciliation exports by period
- Maintain a log of known variances, investigations, and corrective actions
When you find a mismatch, document the recovery path immediately
The quality of your recovery process matters almost as much as the original mistake. When counts do not match, manifests are incomplete, or tags cannot be traced, document what was found, who investigated it, what physical checks were performed, what system records were reviewed, and how the issue was resolved. This turns a painful audit moment into evidence that the operation can detect, contain, and correct failures in a controlled way.
- Open an incident record as soon as the discrepancy is confirmed
- Capture the physical check, system review, and corrective action taken
- Identify whether the root cause was training, process, access, or tooling
- Update the SOP or control point so the same issue is less likely to repeat
Sources
Plant Tagging Requirements (METRC, 2024-08-12)
https://www.metrc.com/resources/plant-taggingAccessed 2025-01-10
California DCC Compliance Updates (California DCC, 2024-11-04)
https://cannabis.ca.gov/Accessed 2025-01-09