The Delivery Manifest: What It Is and Why Every Run Needs One

Ask most BC cannabis retailers running delivery whether they generate a delivery manifest for each driver run, and the most common response is a pause followed by a question: what is a delivery manifest?

That is a significant problem, because a delivery manifest is not an optional best practice or an administrative nuance. It is a compliance requirement under the LCRB Cannabis Retail Store Licence Handbook, and the absence of one for each completed run is a documentation gap that creates real enforcement exposure.

What a Delivery Manifest Is

A delivery manifest is a consolidated document that covers all deliveries in a single driver run. Where an individual delivery record captures the details of one specific delivery, a manifest captures the full picture of a complete driver run from start to finish.

Think of it as the run-level summary that sits above the individual delivery records. The manifest tells the whole story of a driver's shift: who the driver was, what vehicle they were using, every stop they were dispatched to, what was carried to each stop, and what happened at each one.

What a Compliant Manifest Must Contain

The specific fields required in a delivery manifest are drawn from the LCRB's delivery service requirements. A compliant manifest for a completed driver run should include the following.

Driver information. The name of the driver who completed the run, along with confirmation that the driver is an employee of the licensed retailer.

Vehicle information. The vehicle used for the delivery run, including sufficient detail to identify the specific vehicle.

Run date and time. When the run commenced and when it concluded.

Each delivery stop. For every stop on the run, the manifest should record the delivery address, the items carried to that address, and the outcome: completed delivery or documented failed attempt.

Dispatcher information. The identity of the staff member who created and dispatched the run.

How the Manifest Relates to Individual Delivery Records

The delivery manifest and the individual delivery records serve related but distinct compliance functions. They are not substitutes for each other.

Individual delivery records provide the granular documentation for each specific delivery: the driver, the address, the time, the items, the age verification, and the outcome. These records exist at the level of a single transaction.

The manifest provides the run-level view that allows an inspector to see the complete picture of a driver's activity during a shift. It also allows the inspector to cross-reference the manifest against individual delivery records to verify consistency and completeness.

If your individual delivery records are complete but you have no manifests, you have a gap. If you have manifests but your individual delivery records are incomplete, you have a different gap. The LCRB requires both.

Why Most Retailers Are Not Generating Manifests

The manifest gap is largely a tooling problem. In a compliant delivery management system, manifests are generated automatically at the conclusion of each driver run as a byproduct of the dispatch and delivery workflow. The system has all the information it needs: the driver, the vehicle, the run details, and the outcomes. Generating the manifest is a function the system performs without any additional input from the dispatcher or driver.

In an informal dispatch workflow, none of that happens automatically. There is no system capturing the run-level information in a structured format, so there is nothing to generate a manifest from. Creating one manually, after the fact, requires assembling information from multiple sources and is both time-consuming and inconsistent.

The result is that most retailers using messaging apps or spreadsheets for delivery dispatch are not generating manifests, not because they have decided not to comply, but because their tools were not designed to produce that document.

What Happens When a Manifest Is Missing

An inspector reviewing your delivery records who finds that manifests do not exist for a given period has identified a documentation gap. That gap is a contravention of your licence conditions.

The enforcement consequence will depend on the specific circumstances, including your overall compliance history and whether other violations were identified in the same inspection. But the gap itself is clear: a required document does not exist.

The more challenging aspect of a manifest gap is that it cannot be retroactively corrected for historical runs. If the manifests for the past three months do not exist, they cannot be recreated from informal records. The gap in the record is permanent.

Making Manifests Automatic

The practical solution to the manifest gap is the same as the solution to most delivery compliance gaps: use a system that generates the required documentation automatically as part of the delivery workflow.

When a driver completes a run in a purpose-built delivery dispatch system, the manifest exists. It was created by the system as the run progressed. The dispatcher did not have to remember to generate it. The driver did not have to do anything additional. It is simply a record that the system produces because it has all the information it needs.

For BC cannabis retailers who are currently running delivery without generating manifests, the most immediate step is to implement a delivery management system that generates them automatically. The gap in historical records cannot be fixed, but the gap going forward can be.

This guide is based on publicly available LCRB documentation current as of November 2026. Cannabis regulations change — always verify current requirements with the LCRB directly at gov.bc.ca/lcrb.

Grably is a brand of Grably Technologies Inc.
grably.ca · hello@grably.ca · 778-900-8886