In short: Route risk assessment is the structured process of identifying, scoring, and mitigating the hazards — cargo theft, diversion, vehicle failure, regulatory exposure — present on every licensed cannabis transport run. Under Minnesota Statutes ch. 342 and OCM Rules 9810, a compliant transporter evaluates each route before wheels roll, documents that evaluation, and adjusts protocol accordingly. Operators who skip this step do not just accept higher risk; they accept liability.
What Is Route Risk Assessment — and Why Does It Apply to You?
If your operation moves cannabis between licensed facilities in Minnesota — cultivator to processor, processor to manufacturer, manufacturer to dispensary buyer — you are inside the licensed transport lane governed by Minn. Stat. §§ 342.35–342.36. That lane comes with explicit requirements around vehicle security, crew configuration, tracking, and manifest integrity. Route risk assessment is the operational framework that ties those requirements together into a repeatable pre-run decision process.
It applies whether you manage a single weekly delivery run or coordinate daily statewide distribution. The complexity scales with volume; the obligation does not.
The Office of Cannabis Management (OCM) does not publish a mandated "route risk assessment form." What it does mandate — through ch. 342 and OCM Rules 9810 — are the controls that a proper risk assessment will naturally surface and enforce: crews sized to the load, GPS-tracked vehicles, locked cargo areas, METRC manifests initiated before departure, and records retained for at least three years. If your pre-run process does not address each of those controls, it is not a complete assessment.
What Are the Core Risk Dimensions on a Cannabis Transport Run?
Cargo and Theft Risk
Cannabis product is a high-value, fungible target. A well-structured risk assessment treats every run as though the load is visible to bad actors — because in a state with a growing but still-maturing licensed market, it sometimes is.
Cargo risk factors to score before each run include:
- Load value. A manifest carrying $40,000 in finished flower carries a different risk profile than one moving $4,000 in trim. High-value loads warrant heightened crew coordination and alternate routing.
- Product type. Concentrates, edibles, and high-potency items have a higher street value per pound than bulk biomass. Assess accordingly.
- Time in transit. Extended routes — particularly those crossing rural Greater Minnesota corridors to Duluth, Rochester, or the Iron Range — increase exposure windows. Departure timing affects both diversion risk and vehicle recovery speed if something goes wrong.
- Predictability. Fixed, published-in-practice routes with consistent timing are easier to intercept. Operational unpredictability — varied departure windows, alternate route options pre-identified — is a cost-free mitigation.
Regulatory and Documentation Risk
OCM enforcement is documentation-first. An inspector examining your operation will look at what your manifest says, what METRC recorded, and whether those two records match the physical load. A route that introduces documentation gaps — a detour not logged, a delivery window missed without notation, a METRC transfer not accepted at destination within the required window — creates regulatory exposure independent of whether anything actually went wrong with the cargo.
Pre-run documentation checkpoints should confirm:
- The METRC outbound transfer is initiated and accurate before departure. Under standard METRC transfer mechanics, the receiving licensee cannot accept the load in the system until the outbound transfer exists. Gaps here delay acceptance and create manifest timing discrepancies.
- The manifest reflects the correct originating and destination license numbers, route, and estimated transit time.
- Any route deviation planned for weather, traffic, or construction is logged. An undocumented deviation on a manifest that says "direct route" is a compliance finding.
Vehicle and Crew Risk
Minn. Stat. § 342.36 requires cannabis transport vehicles to meet OCM vehicle standards, which include secure cargo compartments not visible or accessible from outside the vehicle and GPS tracking active during transport. Crew size belongs in the same pre-run review: a second licensed crew member rides when the load calls for it, so staffing is matched to the value and risk profile of the run under the rules in force.
A pre-run vehicle check is not bureaucratic overhead; it is a control that closes an audit gap. If a vehicle GPS unit fails mid-route and the failure was not caught at pre-run, the transporter cannot demonstrate continuous tracking compliance. That is a different and more serious finding than a unit that failed and was documented before departure with a protocol-compliant response.
Crew risk includes fatigue, unfamiliarity with the route, and inadequate briefing on load value or security protocol. Neither statute nor OCM rules prescribe a crew briefing checklist — but a defensible operation has one.
Environmental and Route Conditions
Minnesota's geography creates seasonal risk factors that flat-state logistics frameworks miss. Winter routes through Greater Minnesota can close or become hazardous with short notice. A run that leaves the Twin Cities metro on a Tuesday in January for a northern dispensary buyer operates in a different risk envelope than the same run in July. Build seasonal contingency routing into your pre-run process — not as a reaction, but as a standing variable.
Does Minnesota Law Require a Formal Risk Assessment?
Not by that name. OCM Rules 9810 do not mandate a document titled "route risk assessment." What they do require is that transport operations maintain the controls and records that a risk assessment enforces. In practice, the distinction is narrow: an operation that cannot demonstrate it evaluated route and cargo conditions before departure will struggle to show it operated in a manner consistent with the rules if something goes wrong.
More directly, Minn. Stat. § 342.35 gives OCM authority to suspend or revoke a transport license for failure to comply with operating requirements. Operators who rely on informal tribal knowledge rather than documented pre-run protocols are one incident — or one inspection — away from a compliance action that a paper trail would have neutralized.
The business case is the same as the compliance case: documented risk assessment creates a defensible record. That record protects the transport licensee in OCM proceedings, in insurance claims, and in conversations with clients who want to know how their product is being protected.
What Does Implementing This Actually Look Like?
A practical route risk assessment for a Minnesota cannabis transport operation does not require specialized software. It requires a repeatable checklist — completed before every run, retained as a record, and reviewed when conditions change.
The checklist should address, at minimum:
1. Load profile. Manifest product types, quantities, and approximate value. 2. Route. Planned route logged, alternate routes identified, estimated transit time recorded. 3. Vehicle status. GPS active and confirmed transmitting, cargo compartment locked and inspected, communication devices functional. 4. Crew. Crew size confirmed against the load — a second crew member added where the run warrants it — with everyone assigned reviewed on load protocol and emergency contact procedure. 5. METRC status. Outbound transfer initiated, manifest numbers verified against physical load tags. 6. Conditions. Weather, known road closures, departure timing relative to daylight and traffic.
When any item on the checklist returns a flag — a GPS unit showing intermittent signal, a manifest discrepancy, a forecast severe weather event — the protocol should specify the response: delay, escalate, reroute, or document the exception and proceed. "We checked and decided to proceed anyway" is a defensible posture. "We didn't check" is not.
The One Takeaway
Document your pre-run risk evaluation on every transport run — route, load, vehicle, crew, and METRC status — and retain that record for three years. That single habit closes the gap between operating under Minnesota's licensed transport framework and being able to prove it.
FAQ
Is route risk assessment required under Minnesota cannabis transport law?
OCM Rules 9810 and Minn. Stat. ch. 342 do not use that specific term, but they require the controls — GPS tracking, appropriate crew staffing, METRC manifests, locked cargo areas — that a route risk assessment enforces. Documenting your pre-run evaluation creates the record that demonstrates compliance with those requirements.
What is the minimum crew size for a cannabis transport run in Minnesota?
There is no single crew number that fits every run. Crews are sized to the load — a second licensed crew member rides when the value, route, or handling of a run calls for it — and staffing is set against the rules in force at the time of the run.
What happens if a METRC outbound transfer has not been initiated before the run departs?
The receiving licensee cannot accept the transfer in METRC until the outbound record exists. Departing before the transfer is initiated creates a manifest timing gap that can appear as a compliance discrepancy during OCM review. Initiate the transfer and verify manifest accuracy before departure.
How long do transport operators need to retain route and manifest records in Minnesota?
The standard record retention requirement under Minnesota cannabis rules is three years. This applies to manifests, METRC transfer records, and operational documentation including pre-run checklists.
Does route risk assessment apply to cash transport as well as product transport?
Yes. Many cannabis operators coordinate cash logistics alongside or separate from product runs. Cash transport carries its own risk profile — and is not covered by a cannabis product manifest. Evaluate cash runs under the same risk framework, with additional attention to vehicle configuration and crew protocol, and ensure any cash logistics provider is operating under appropriate licensure.
What should a transport operator do if a GPS unit fails mid-route?
Document the failure immediately — time, location, crew notation — and notify dispatch. Continue the run with heightened communication check-ins at defined intervals. On arrival, document the incident in the run record. Consistent documentation of equipment failures, including your response protocol, is the difference between an anomaly and a pattern finding in an OCM inspection.
More from Emerald on Security, Cash Logistics & Risk.
