Cannabis SOP Template: How to Write a Compliant Standard Operating Procedure

A procedure that lives in someone’s head is not an SOP, and at a Health Canada inspection an uncontrolled document is a finding even when the work behind it is faultless.

A cannabis SOP template gives you the skeleton every compliant Standard Operating Procedure needs: a stated purpose, a defined scope, named responsibilities, the materials required, the step-by-step procedure, deviation handling, references to related documents, and document control information. Get those eight elements in the right shape and a competent new employee can run the procedure on day one without asking a single follow-up question. Miss one and you have a document that reads well but will not survive an audit. This page walks through each element, shows a worked SOP skeleton you can copy, and explains why deviation handling and document control are the two parts most operations get wrong.

This is part of our wider cannabis SOP guide, which covers the full library of procedures a licensed producer needs, document control discipline, training, and audit readiness. Start here if you are writing your first SOP from a blank page.

What Makes a Cannabis SOP Template Compliant?

A compliant cannabis SOP template is built around one test: could a competent new employee follow this procedure on day one, with no additional instruction, and produce the same result every time? That is the working definition of a good SOP, and it is also the definition a Health Canada inspector applies in practice. The procedure has to stand on its own. If it relies on tribal knowledge, an unwritten “everyone knows you do it this way” step, or a senior operator standing over the trainee’s shoulder, it is not finished.

Under the Cannabis Regulations (SOR/2018-144), made under the Cannabis Act, certain SOPs are explicitly required: security, sanitation, and record-keeping among them. The regulator does not just want the activity done correctly, it wants documentary proof that you defined how it should be done, controlled that definition, and trained people against it. An out-of-date, missing, or uncontrolled SOP is a compliance finding even if your actual practice is sound. The document is the evidence, and the absence of a controlled document is treated as the absence of the control.

That is why every cannabis SOP template carries the same eight building blocks. They are not stylistic preferences, they are the structure that makes a procedure both followable and defensible.

The 8 Essential Elements of a Cannabis SOP Template

Every cannabis SOP template should contain these eight elements, in this order. Each one answers a specific question the reader will have, and each one carries part of the audit burden. The table below is the skeleton: copy it as the section structure for any procedure you write, from facility access control to lot sampling.

Notice the pattern: the first five elements make the procedure followable, and the last three make it defensible. A new operator reads elements one through five to do the work. An inspector reads elements six through eight to confirm the work was governed. A complete SOP serves both readers at once. For the catalogue of which procedures you are actually required to write, see our guide to the required cannabis SOPs under the Cannabis Regulations.

What Does Day-One-Clear Mean in a Step-by-Step Procedure?

The step-by-step procedure is where most cannabis SOPs quietly fail the day-one test. The author knows the job, so they compress steps, skip the obvious, and assume context. The trainee does not have that context, and the gaps become improvisation. Improvisation is exactly what an SOP exists to eliminate.

Day-one-clear writing follows a few rules:

• One action per numbered step. “Weigh the sample and record the weight on Form QA-12” is two actions; split them. Each step should be a single thing the operator does, then moves on.
• Plain, imperative language. Start each step with a verb: “Scan the plant tag,” “Enter the destruction weight,” “Obtain the witness signature.” No passive voice, no “it should be ensured that.”
• Concrete values, not vague ranges. “Dry at 18 to 20 degrees Celsius and 55 to 60 percent relative humidity” beats “dry at a suitable temperature.” If a number governs the outcome, the number belongs in the step.
• Decision points spelled out. If a step branches (“if the count matches, proceed; if it does not, stop and follow the discrepancy procedure”), write both branches. Never leave the operator to decide what an undefined exception means.
• Reference the form or system action. If the step generates a record, say where it goes: which form, which field, which screen in the seed-to-sale system.

A quick self-test before you finalise any procedure: hand it to someone who has never done the task and watch them attempt it without help. Every time they stop to ask a question, you have found a gap. Close the gap in the SOP, not in the conversation. That single exercise turns an SOP from a document that describes the work into one that actually directs it.

Why Is Deviation Handling Non-Negotiable in a Cannabis SOP?

Deviation handling is the element teams most often treat as optional, and it is the one inspectors most reliably probe. The logic is simple: real operations deviate. Equipment fails, a count does not reconcile, a step cannot be completed as written. The question is never whether deviations happen, it is whether your SOP told the operator what to do when one did, and whether the deviation was captured rather than buried.

A deviation handling section in a cannabis SOP template should state four things in plain terms: who the operator notifies the moment a step cannot be followed as written, how the deviation is recorded (which log, which form), who investigates and within what timeframe, and the threshold that triggers escalation, including when a deviation rises to the level of a reportable incident requiring Health Canada notification. The dedicated procedure that owns this end to end is your deviation, incident, and non-conformance SOP, and individual procedures should reference it rather than repeat it.

Two failure modes are worth naming. The first is the SOP that has no deviation section at all, which silently tells operators that deviations are unthinkable, so when one happens they hide it. The second is the SOP that says “report any deviation to your supervisor” and stops there, with no record, no log, no investigation trigger. Both produce the same outcome at audit: an inspector finds evidence of a deviation in the batch record or the surveillance footage, asks for the corresponding deviation log entry, and there is nothing to show. That gap, not the original deviation, is the finding.

From Template to Living Document: Control and Training

Writing the SOP is the first half of the job. Keeping it controlled and getting people trained against it is the second, and the second half is where compliance is actually won or lost. The document control block (element eight) is not paperwork for its own sake. The version number proves which procedure was in force when a given batch was produced. The approval signature proves the QAP sanctioned that version. The review date proves the procedure is being maintained, not left to drift.

The discipline extends past the document itself. When you revise an SOP, affected staff must be retrained before the new version takes effect, and the training record must link each employee to the specific version they were trained on. An inspector who finds a batch produced under version 3 of a procedure will want to see that the operators who ran it were trained on version 3, not version 2. That linkage is covered in our guide to cannabis SOP training and competency verification.

This is also where your operations platform earns its place. Linking SOPs directly to batch records creates an audit trail that an inspector can follow without friction: pull any batch, and see exactly which version of every procedure was in place when that batch was produced, and which trained operators ran it. GrowerIQ is cannabis seed-to-sale and operations software used by 200 plus licensed facilities across nine countries, and that batch-to-SOP linkage is one of the reasons document control stops being a manual chore. You can read the regulator’s own framing of the obligations on the Health Canada cannabis licensing and compliance pages.

Start with the eight-element template, write each procedure to the day-one test, give deviation handling the section it deserves, and put the whole thing under document control. That is the difference between a binder of documents and a defensible quality system.

Frequently Asked Questions

What are the 8 elements every cannabis SOP template must include?

A compliant cannabis SOP template includes eight elements in order: a stated purpose, the scope, responsibilities, materials needed, the step-by-step procedure, deviation handling, references to related documents, and document control information (version number, effective date, review date, and the QAP approval signature). The first five elements make the procedure followable by a new operator, and the last three make it defensible at an audit. A document that omits any of these is incomplete and may be cited as a finding even if the underlying work is done correctly.

What does it mean for a cannabis SOP to be day-one clear?

A day-one-clear SOP is written so that a competent new employee could follow it on their first day, without additional instruction, and produce the correct result. In practice that means one action per numbered step, plain imperative language, concrete values instead of vague ranges, decision branches written out in full, and every record-generating step pointing to the right form or system field. The simplest test is to hand the procedure to someone who has never done the task and close every gap that makes them stop and ask a question.

Is an uncontrolled SOP really a compliance finding even if the work is correct?

Yes. Under the Cannabis Regulations the document is the evidence of the control. An out-of-date, missing, or uncontrolled SOP, for example one with no approval signature, a lapsed review date, or two conflicting copies in circulation, is a compliance finding in its own right, regardless of whether the actual practice was sound. Health Canada treats the absence of a controlled document as the absence of the control it is meant to govern, which is why document control discipline matters as much as the procedure content.

How should deviation handling appear in a cannabis SOP?

The deviation handling section should state, in plain terms, who the operator notifies the moment a step cannot be followed as written, how the deviation is recorded and in which log or form, who investigates and within what timeframe, and the threshold that escalates a deviation to a reportable incident requiring Health Canada notification. Individual SOPs should reference the dedicated deviation, incident, and non-conformance procedure rather than repeating it. An SOP with no deviation section trains staff to hide problems; one that only says “tell your supervisor” leaves no record for an inspector to trace.

How does a cannabis SOP template connect to batch records and training?

The document control block ties each SOP version to a point in time, so the version number on a procedure can be matched against the batches produced while it was in force. When an SOP is revised, affected staff must be retrained before the new version takes effect, and the training record links each employee to the specific version they were trained on. Linking SOPs directly to batch records in an operations platform creates an audit trail where an inspector can pull any batch and see which procedure version governed it and which trained operators ran it, turning document control from a manual chore into a built-in feature.

Get the Full Cannabis SOP Guide

The free guide takes this template further: the complete mandatory and best-practice SOP library under the Cannabis Regulations, document control rules, training and competency verification, and a Health Canada audit readiness checklist you can run before the inspector arrives.

Download Free Guide