In short: When a cannabis load is compromised — through theft, diversion, accident, or tamper — the licensed transporter must immediately secure the scene, notify law enforcement, report to the Office of Cannabis Management under Minn. Stat. § 342.35, void or correct the active METRC transfer manifest, and document every action with timestamps. Speed and sequence both matter.
What Does "Compromised" Actually Mean in a Transport Context?
In Minnesota cannabis logistics, a compromised load is any in-transit event that breaks the verified chain of custody between licensed facilities. That includes:
- Theft or attempted theft — full or partial removal of product from the vehicle
- Unauthorized access — a seal is broken, a lockbox is opened, or an unvetted person contacts the cargo
- Vehicle accident — product is displaced, packaging is breached, or the vehicle is immobilized with cargo on board
- Diversion — product is delivered to a location not on the approved manifest route
- Tampering — packaging, METRC tags, or seals show signs of interference without a documented explanation
Under OCM Rules 9810 and Minn. Stat. ch. 342, every in-transit unit is tracked to a specific manifest and must arrive exactly as documented. Any deviation is a reportable event. The question is not whether to report — it is how fast and in what sequence.
Does This Apply to My Operation?
If you hold a Minnesota cannabis transporter license, or if you are a cultivator, manufacturer, or retailer who moves your own product between your licensed premises under a self-transport authorization, this protocol applies to you directly.
If you use a third-party logistics partner, the licensed transporter bears the primary obligation for the in-transit segment — but the originating and receiving licensees are both named on the METRC manifest and share exposure if the event is not resolved cleanly. Dispensary buyers and brand owners: confirm in writing which party your transport agreement holds accountable for incident reporting before a load moves.
Is the Response Sequence Compliant with Minnesota Law?
The sequence below is built on three sources:
1. Minn. Stat. § 342.35 — requires licensees to report cannabis theft or loss to both the OCM and to law enforcement. The statute sets no specific hour deadline, but OCM enforcement practice treats delay as an independent violation. 2. Minn. Stat. § 342.36 — governs transfer record-keeping, including the duty to correct manifest discrepancies. 3. OCM Rules 9810 — transporter conduct, vehicle requirements, route documentation, and METRC manifest completion.
Following this sequence does not guarantee a favorable regulatory outcome, but deviating from it guarantees exposure.
The Incident Response Sequence: Step by Step
Step 1 — Contain and Secure Immediately
Stop at the safest available location. Do not continue the route; do not attempt to retrieve stolen product. Activate hazard systems. If a breach is discovered while moving, pull over at the next safe point.
Two-person runs, when the load calls for a second crew member: one crew member manages scene safety; the other documents. Do not separate further.
Lock down remaining product. Do not open additional compartments, repackage, or consolidate loads until law enforcement arrives and authorizes it.
Step 2 — Call Law Enforcement
Call 911 or the non-emergency line for the jurisdiction you are in. Minnesota has 87 counties; know which jurisdiction you are traveling through before departure. Provide the incident location, a description of the event, and the fact that a licensed cannabis load is involved. Request a case number — you will need it for OCM reporting.
Do not leave the scene until law enforcement releases you.
Step 3 — Notify the OCM
Under § 342.35, the licensee must notify the OCM of theft or loss. In practice, this means the transport company's compliance officer contacts the OCM as soon as the crew notifies dispatch — which should happen simultaneously with or immediately after the law enforcement call.
OCM notification should include: licensee name and number, manifest ID, product description and quantity, incident location, and the law enforcement case number if available. Follow up in writing the same business day.
Step 4 — Suspend the Active METRC Manifest
The METRC transfer record must reflect reality. An in-transit manifest cannot simply time out — it must be voided or corrected to document what actually occurred.
Contact the originating facility's METRC administrator immediately. The originating licensee initiates the void or rejection workflow in METRC. If product is partially recovered, the quantity fields must be corrected to match the verified physical count. Every adjustment generates an audit log entry in METRC; that log is the regulatory record.
Do not allow the manifest to expire without a documented status. An unresolved expired manifest is a compliance violation independent of the underlying incident.
Step 5 — Document the Scene
Before anything is moved (unless law enforcement directs otherwise), the crew documents:
- Timestamp and GPS coordinates of discovery
- Photographs of vehicle exterior, cargo compartment, seals, and any disturbed product
- Crew names, license numbers, and contact information
- Names and badge numbers of responding law enforcement officers
- Condition of remaining product (packaging intact, METRC tags visible, etc.)
This documentation is part of the three-year record-retention requirement under § 342.36 and OCM Rules 9810. Store it in the same file as the original manifest.
Step 6 — Notify the Receiving Facility
The dispensary buyer or receiving licensee is waiting for a delivery that will not arrive on schedule — or will arrive incomplete. Notify them directly and promptly. They will need to update their own METRC receiving records. They may also need to notify their own compliance officer depending on their license conditions.
Do not let the receiving facility discover the gap when they go to accept the METRC transfer. That creates a second compliance event at a second license.
Step 7 — Internal Incident Report Before End of Day
Before the shift ends, file an internal incident report capturing the full timeline, crew statements, law enforcement response, METRC actions taken, and the status of any unaccounted product. This feeds the OCM written follow-up and supports any cargo insurance claim.
What Does This Actually Cost?
The direct costs fall into four categories:
Product loss — the value of any unrecovered cannabis. Cargo insurance may cover part or all of this, depending on your policy's cannabis-specific exclusions. Review those before a load moves.
Regulatory response — OCM may issue a warning, a fine, or a license condition. Cooperative, timely, documented response consistently produces better outcomes than delayed or incomplete reporting.
METRC correction labor — resolving a manifest discrepancy across two licensees takes real administrative time.
Relationship cost — a receiving facility that discovers a gap through METRC rather than through a direct call will remember it. Proactive communication is part of supply chain professionalism.
The One Takeaway
The regulatory exposure from a compromised load is almost always smaller than the exposure from how the load was handled afterward. Notify law enforcement, notify the OCM, and fix the METRC manifest the same day. Document everything. The sequence is the defense.
FAQ
What are the exact reporting obligations under Minnesota law when a cannabis load is stolen?
Under Minn. Stat. § 342.35, the licensee must report cannabis theft or loss to both the OCM and the appropriate law enforcement agency. There is no statutory hour deadline specified, but OCM treats delay as a separate violation. Report both within the same business day the event is discovered.
Who is responsible for the METRC manifest when a load is compromised mid-transport?
The originating licensee initiated the METRC transfer and is responsible for voiding or correcting it. The licensed transporter is responsible for notifying the originating facility immediately so they can take that action. Both parties appear on the manifest and share audit exposure if it is left unresolved.
Can we continue delivering other stops on the same route after an incident?
No. Once an incident is confirmed, the route is suspended. Continuing to deliver other stops with an unresolved chain-of-custody event creates additional METRC manifest issues and potential OCM violations. Resume only after the incident is documented, law enforcement has released the vehicle, and your compliance officer has cleared continuation.
Do we need a police report number before notifying the OCM?
You should attempt to obtain a law enforcement case number before or alongside OCM notification, but do not delay the OCM contact waiting for paperwork. Notify the OCM with the information you have, then supplement with the case number as soon as it is available. Document the timeline of both contacts.
What happens to the METRC tags on product that is stolen and then recovered by law enforcement?
Recovered product cannot be returned to commerce without a documented chain-of-custody review by the OCM. Do not re-tag, repackage, or re-enter recovered product into a METRC transfer without explicit OCM authorization. In most cases, recovered product is held as evidence and ultimately destroyed.
Does a vehicle accident with no theft still require OCM reporting?
Yes, if the accident results in any product displacement, packaging breach, or METRC discrepancy. A minor fender-bender where cargo is undisturbed and the manifest is unaffected may not require a formal § 342.35 report, but document it internally and have your compliance officer review before making that call.
More from Emerald on Security, Cash Logistics & Risk.
