Checklist · Cannabis · Transport & Manifests

Cannabis Transport & Manifest Worksheet

Reconcile licenses, manifest data, vehicle security, trip controls, chain of custody, and state tracking before treating a cannabis transfer as complete.

By Lincoln Square Law · 7-minute read

🖨 Print this checklist

• The transfer is permitted between the specific license types and addresses involved.
• Driver and any accompanying agents hold required credentials and have completed transport/security training.

Build the manifest from the state inventory record

The manifest should be generated from the same inventory data the facility uses to control the product, not from a separate spreadsheet that can drift. Match each package or batch identifier, quantity, product description, origin, destination, planned departure, and other required fields to the state system before loading. A second person should compare the physical packages to the manifest. If a package is added, removed, split, or substituted after the manifest is prepared, update the state record and manifest before the vehicle leaves.

• Every package or batch identifier on the vehicle appears on the manifest and state tracking record.
• Quantities, product descriptions, origin, destination, planned route or trip information, and departure details are accurate.
• A second-person loading check reconciles physical packages to the manifest before the vehicle is sealed or released.

Inspect the vehicle as a regulated control point

Vehicle condition matters because the vehicle becomes regulated storage during transit. Illinois requires cannabis to be concealed from outside view, transported in an enclosed locked storage compartment secured to the vehicle, and carried in a vehicle without cannabis-identifying markings. Missouri requires security features including locked storage, video monitoring, and GPS tracking for covered transports. The pre-trip inspection should document those controls, communications capability, vehicle condition, and the absence of unauthorized cargo.

• Locked cargo compartment is functional, secured to the vehicle, clean, and suitable for the product being transported.
• Required video, GPS, alarms, communications devices, and other security controls are operating before departure.
• Vehicle exterior does not identify the cargo as cannabis where prohibited, and regulated product is not visible from outside.

Control the trip, not just the departure

Drivers need a written protocol for breakdowns, accidents, route changes, law-enforcement contact, security events, rejected deliveries, and delays. Missouri's current rule imposes a 36-hour transportation limit absent qualifying circumstances and notification. Illinois law requires the registration and manifest to be present in the vehicle. The trip record should preserve actual departure and arrival times, deviations, communications, and any event that changed custody or timing.

• Driver has accessible credentials, manifest, trip plan, required registration or certification, and emergency contacts.
• Route deviations, stops, delays, accidents, security events, or law-enforcement contacts are documented and escalated under the SOP.
• The team knows the rule for a refused delivery and how product is returned, re-secured, and corrected in the state system.

Close the chain of custody at receiving

The receiving facility should not sign merely because the seal is intact. It should verify the manifest, package identifiers, quantities, condition, testing or transfer status, and any seal or security information. Record discrepancies before accepting product into inventory. The sending facility should retain proof of receipt and close the transfer in the state tracking system. A complete file connects dispatch, transit, receipt, and final system reconciliation.

• Receiving employee verifies identity, package count, package identifiers, condition, and manifest before acceptance.
• Shortage, overage, damaged package, broken seal, or other discrepancy is documented before custody is finalized.
• Receiving confirmation and state-system completion are retained with the manifest and trip record.

Audit the last five trips

For a practical self-audit, pull five recent manifests and compare each one to state tracking, vehicle logs, GPS data, receiving records, and any incident report. Repeated late entries, unexplained route changes, mismatched quantities, or missing receiving confirmations are process signals. Correct the workflow rather than treating each mismatch as an isolated paperwork error.

Reconcile custody at every handoff

A manifest can be accurate at departure and still fail as a chain-of-custody record if custody changes are not controlled.

Identify who physically possesses the product from vault release through loading, driver acceptance, any authorized intermediate stop, unloading, and receiver acceptance. Each handoff should have a time, person, quantity, and condition record. When two employees share a vehicle, the SOP should state who is responsible for the manifest, keys, communications, and incident decisions. If a driver shift or vehicle change occurs, the record should show how custody was transferred without creating an untracked interval.

• Each custody change identifies date, time, person, quantity, and product condition.
• Keys, seals, records, and cargo access have an identified custodian throughout the trip.
• Any vehicle or driver change is authorized and documented before transport resumes.

Test an exception before one happens

Use a tabletop exercise for a flat tire, collision, security threat, severe weather delay, receiver closure, or state-system outage. Ask the driver exactly whom to call, what product must remain secured, whether the route may change, how long the product may remain in transit, and what regulator notice may be required. The purpose is to find ambiguity while everyone is in a conference room rather than while a regulated load is stopped on the highway. Update the trip plan and emergency contact list after the exercise.

• Driver can explain breakdown, crash, delay, refused-delivery, and security-threat protocols without improvising.
• Team knows who authorizes route deviations and how they are documented in the state system and manifest.
• Regulator, compliance, security, and recipient contacts are current and available outside the primary system.

Use metrics to find transport risk

Review more than completed trips. Track late departures, late arrivals, route deviations, manifest corrections, rejected deliveries, quantity discrepancies, equipment failures, and state-system edits after delivery. Patterns identify whether the problem is training, dispatch planning, inventory accuracy, vehicle reliability, or receiving discipline. A transport program that only counts incidents misses the warning signals that usually appear first.

Control cash and documents separately from product

Where transportation includes payments, returns, or business records, define how those items are secured and reconciled without compromising product custody. Missouri's rule expressly contemplates secure storage for payments and video equipment during transit. A driver should not have to open the regulated-product compartment simply to access paperwork or cash. At the end of the trip, reconcile payment, product, manifest, and receiving records as separate but connected records.

• Cash, checks, documents, and product have defined secure locations and access controls.
• Trip closeout reconciles product and payment separately with delivery or return evidence.
• Sensitive records are secured and not left visible in an unattended vehicle.

Qualify transportation vendors like regulated partners

If a third-party transporter is used, diligence should verify current authority, insurance, vehicle controls, agent credentials, incident procedures, data security, subcontracting limits, and record-retention obligations. The contract should allocate responsibility for manifests, state-system actions, rejected deliveries, accidents, loss or theft, regulator communication, and preservation of GPS or video evidence. Periodically test the vendor's records against your own transfer data rather than assuming the contract alone proves compliance.

A final transport audit should be reproducible from the records without relying on the driver's memory. If dispatch cannot reconstruct the trip from the manifest, state system, GPS or route record, security evidence, receiving confirmation, and incident log, the chain of custody is not complete.