What to Include in a Cannabis SOP: The Operator’s Checklist
Quick answer: A cannabis SOP should include purpose and scope, roles and responsibilities, a step-by-step procedure, compliance and regulatory references, corrective action steps for exceptions, and recordkeeping requirements. Together these sections turn a policy statement into a document employees can actually follow and inspectors can verify.
Why Most Cannabis SOPs Never Get Opened Again
I have read a lot of cannabis SOPs over the last thirteen years. License applications, pre-audit cleanup, post-inspection panic, you name it. Most of them share the same problem, and it is not grammar.
They were written to satisfy a license application, not to run a shift.
You can usually tell within the first paragraph. The document reads like legal boilerplate, nobody on the floor has opened it since the binder was printed, and when an inspector asks a budtender to walk through ID verification, the answer does not match what is written down.
That gap between the SOP on paper and the SOP your team actually follows is where inspection findings, METRC discrepancies, and inconsistent training come from. Close the gap, and the SOP becomes what it was supposed to be: the thing that keeps your operation consistent when you are not standing on the floor watching it happen.
Here is the structure that holds up, built from what regulators ask for and what employees will actually follow.
The Six Sections Every Cannabis SOP Needs
A usable cannabis SOP needs six sections. Skip one and you either fail an audit or hand your team something nobody can execute under pressure.
Purpose and Scope
State in one or two sentences what the procedure covers and what it does not. “This SOP governs product intake from licensed transporters at [location]” tells a new hire exactly where their responsibility starts and ends. Vague scope is how two departments both assume the other one is checking expiration dates.
Roles and Responsibilities
Name the position, not the person. “Inventory Manager” survives turnover; a first name does not. List who performs the task, who verifies it, and who has the authority to stop the process if something looks off. This is also where you catch SOPs that quietly assume one person does everything, which becomes a real problem the day that person calls out.
Step-by-Step Procedure
Write the actual steps, in order, in plain language a new employee could follow on day one without asking a supervisor what you meant. Numbered steps beat paragraphs. If a step depends on a judgment call (how much variance is acceptable, when to escalate), say so directly instead of leaving it implied.
Compliance and Regulatory References
Cite the specific rule the procedure satisfies, and note that the citation ties to your state’s current regulations. This section should also carry your disclaimer language: this is operational guidance, not legal advice, and regulations vary by state and local jurisdiction, so a licensed compliance or legal advisor should confirm the citation before you rely on it. An SOP that cites an outdated rule number is worse than one that cites none at all.
Corrective Actions and Exceptions
This is the section almost every cannabis SOP I review is missing. What happens when the procedure does not go as planned? Damaged product arrives, a tag will not scan, a vendor shows up without the manifest. Document the escalation path and the corrective action, or your team will improvise one in front of an inspector.
Recordkeeping and Documentation
Specify what gets logged, where it lives, and how long you keep it. If your state sets a records retention period, state it and name who owns that responsibility. This section is what turns “we follow a process” into something you can actually show a regulator.
Where State Rules Change the Details
The six sections above are the skeleton. The specifics inside each one depend on where you operate, because cannabis regulation is still handled state by state, and sometimes locally on top of that.
METRC and Seed-to-Sale Tracking
If your state uses METRC or another seed-to-sale system, your intake, transfer, destruction, and adjustment SOPs need to reference the exact tag and manifest workflow your software requires, not a generic version. Most of the METRC cleanup I get called in for traces back to an SOP that described the process in theory but skipped the step where someone actually reconciles the system to the physical count. Our METRC inventory reconciliation checklist walks through that reconciliation step in more detail if you want to pressure-test yours.
Responsible Vendor and Employee Training Tie-Ins
Your SOPs and your training program need to say the same thing. If your Responsible Vendor Training covers ID verification one way and your SOP describes it slightly differently, you now have two official answers, and an inspector will find the one that is wrong. Build the SOP first, then train to it, not the other way around.
Writing SOPs People Will Actually Follow
A technically correct SOP nobody reads is not a compliance tool. It is paperwork with a nice cover page.
A few things that separate a binder from a document people actually use:
- Plain language over regulatory language. Save the citation for the compliance section; write the steps the way you would explain them out loud.
- Photos or diagrams for anything spatial. Storage layout, quarantine area, labeling placement. A picture settles arguments a paragraph cannot.
- One procedure per document. A twelve-page SOP covering intake, storage, and destruction gets skimmed, not followed. Split it into separate, shorter documents.
- A version date and owner on every page. So nobody is quietly working from last year’s printout.
If you are building these from scratch, our state-specific SOP templates give you this structure already built out, which is usually faster than starting from a blank page.
The Mistakes I Flag in Almost Every SOP Audit
Five patterns show up again and again when I review a cannabis operator’s SOP binder:
- Copied from another state. The structure transfers; the citations almost never do.
- No corrective action section. Every exception gets handled a different way depending on who is on shift that day.
- Written for the inspector, not the employee. Technically accurate, functionally unused.
- No review date. A 2023 SOP is still describing a system the business replaced two years ago.
- One person holds all the institutional knowledge. None of it made it onto paper, so it leaves when they do.
Keep It Current: Review Cadence and Version Control
Set a review cadence and put it on the compliance calendar, not your mental to-do list. Most operators I work with review core SOPs (intake, sales, destruction, security) at least annually, and immediately after any regulatory change, software implementation, or incident that exposed a gap.
Version control does not need to be elaborate. A simple log of version number, date, what changed, and who approved it is usually enough to satisfy a regulator and keep your team working from the current copy.
If you are not sure your current SOPs would hold up under scrutiny, a surprise inspection readiness check is a practical way to find the gaps before a regulator does.
Frequently Asked Questions
What is a cannabis SOP and why does my license require one?
A cannabis SOP, or standard operating procedure, is a written, step-by-step description of how your business performs a specific regulated task, such as product intake, destruction, or ID verification. Most state cannabis programs expect documented SOPs as part of licensing and inspection readiness, though exact requirements vary by state and license type. Check your state regulator’s current rules or your compliance advisor for what applies to your license.
How long should a cannabis SOP be?
Long enough to cover the six core sections (purpose, roles, procedure, compliance references, corrective actions, recordkeeping) and short enough that an employee will actually read it. Most well-built single-procedure SOPs run two to four pages. A twelve-page SOP is usually covering more than one procedure and should be split apart.
Who should write cannabis SOPs, operations or compliance?
Both, working together. Compliance knows the regulatory citation; operations knows whether the procedure as written matches how the shift actually runs. An SOP written by compliance alone often gets the rule right and the workflow wrong, and one written by operations alone can miss a requirement. Draft it together, and have the person who performs the task test-drive it before it is finalized.
How often should cannabis SOPs be reviewed?
At minimum, annually, and immediately after any change to your state’s regulations, your seed-to-sale or POS software, your facility layout, or any incident that exposed a gap in the current procedure. Build the review date into your compliance calendar so it does not quietly slip.
Do I need different SOPs for each state I operate in?
Yes, if your core procedures reference state-specific citations, seed-to-sale system requirements, or Responsible Vendor Training content, those details do not transfer across state lines even when your general operating structure does. Multi-state operators typically keep a shared SOP framework with state-specific sections swapped in for each license.
