An SOP that is out of date, unsigned, or past its review date is a finding in itself, no matter how well your team actually does the work on the floor.
Cannabis SOP document control is the discipline that keeps your procedures current, approved, and provably the version in force at the moment a batch was produced. Under the Cannabis Act (S.C. 2018, c. 16) and the Cannabis Regulations (SOR/2018-144), an uncontrolled or overdue SOP is a compliance finding on its own, separate from whether the practice it describes is sound. This page walks the five document-control requirements a Health Canada inspector tests against, the master SOP that governs all the others, and how a seed-to-sale system links each SOP version to the batch records produced under it.
This guide sits inside our wider cluster on SOPs every cannabis operation should have. For how to write a procedure that is controllable in the first place, see the cannabis SOP template; for the mandatory library you are controlling, see the required cannabis SOPs.
What Is Cannabis SOP Document Control and Why Is It a Finding on Its Own?
Cannabis SOP document control is the set of rules that govern how a procedure is versioned, reviewed, approved, distributed, and retired across its life. It answers a single inspector question: can you prove, on demand, that the procedure in front of you is the current approved version, and that everyone working to it knows it is current? When the answer is no, you have a finding, regardless of how the work is actually performed.
This catches operators off guard. A facility can run a flawless harvest and reconcile inventory to the unit, then take an observation because the harvest SOP is eight months past its review date, or because two slightly different printouts of the sanitation SOP are circulating on the floor. Under the Cannabis Regulations the recordkeeping obligation is not just that you did the right thing; it is that your documented system shows the right thing was required, current, and followed. Health Canada compliance guidance for licensed producers leans heavily on this documentary standard.
That is why document control is treated as a discipline of its own rather than a footer on each procedure. The five requirements below are the ones an inspector will test.
What Are the Five Cannabis SOP Document Control Requirements?
The five document-control requirements form the backbone of cannabis SOP document control. Each describes what the rule means in practice and the finding it prevents. Treat the table as the spec you build your system against.
| Requirement | What it means in practice | The finding it prevents |
|---|---|---|
| Version Control | Each SOP carries a unique version number. Superseded versions are archived, never deleted, so the full history stays retrievable. | Inability to prove which version was in force when a given batch was produced. |
| Review Cycle | Every SOP has a defined review date, typically annual. The review is scheduled, performed, and recorded even when nothing changes. | An overdue review, which is a finding on its own whether or not the content is still correct. |
| Approval Signatures | The QAP signs off on each version before it goes live. No version is effective until that signature and date are on the record. | A procedure in use that no one with quality authority ever approved. |
| Distribution Control | Staff can access only current versions. Paper copies are stamped Controlled or Uncontrolled so an outdated printout cannot pass as authoritative. | Stale printouts circulating on the floor while the approved version sits unread in a binder. |
| Training on Revisions | When an SOP is updated, affected staff are re-trained before the new version takes effect, and the training is recorded against that version. | Staff working to a procedure they were never trained on, breaking the link between SOP and competency. |
Version control and archiving superseded versions
Version control gives every SOP a unique identifier that increments on each approved change, for example SOP-CUL-001 v3.0 superseding v2.0. The increment is the hook that ties a procedure to the records produced under it. The hard rule that trips up paper-based operations is that superseded versions are archived, not deleted. An inspector asking what governed a batch from fourteen months ago needs the exact text in force then. If v2.0 was overwritten when v3.0 went live, that batch is now undefensible on the procedure side.
Review cycles and the overdue-review finding
Every SOP needs a defined review date, usually annual, and certain procedures carry event triggers on top of the calendar: a security SOP after any security incident, a sampling SOP when you switch labs, an IPM SOP when you add a product. The key point for cannabis SOP document control is that the review obligation is independent of whether the content needs changing. A procedure that is still perfectly correct but sits one day past its review date is overdue, and overdue is a finding. The review can conclude no change required, but it must be performed, dated, and signed to close the cycle.
QAP approval signatures
No SOP version is effective until the Quality Assurance Person has approved it. The signature and date on the approval record are what make a draft into a controlled document, and the record names the version it approves, so there is never ambiguity about which text the QAP signed. An inspector who finds a procedure in active use with no approval signature on the current version has found a control gap, even if the procedure reads perfectly.
Distribution control and Controlled or Uncontrolled stamping
Distribution control ensures staff reach the current version only. In a paper system this is enforced with stamps: a Controlled copy is the authoritative, tracked printout that gets pulled and replaced when a new version is approved, while any other printout is stamped Uncontrolled to signal it must not be relied on. The failure mode is familiar: an operator keeps a personal photocopy taped inside a cabinet, the SOP is revised, and the photocopy is now wrong but still in daily use. Controlled stamping plus a managed distribution list prevents that.
Training on revisions
When a procedure changes in a way that affects how work is done, affected staff must be re-trained before the new version takes effect, and that training must be recorded against the specific version. This closes the loop between document control and competency: a v3.0 that is approved and distributed but that the floor was never trained on is a version in force nobody is qualified to follow. How that training and competency check is run is covered in our cannabis SOP training guide.
Why Is an Uncontrolled or Overdue SOP a Finding Regardless of Practice?
The reasoning sits at the heart of how a recordkeeping-based regulator works. Health Canada cannot watch every action on every floor, so it inspects the system meant to make the right action happen and prove it happened: your documented procedures plus the control around them. If the control is broken, the regulator has no assurance that what you did was what was required, even if it was.
Three things flow from a single uncontrolled SOP:
- Loss of traceability. Without version control, you cannot bind a batch to the procedure that governed it, so the batch record loses part of its defensibility.
- Loss of the training link. Without controlled distribution and training-on-revision, you cannot show the operator was working to the approved text.
- Loss of currency. An overdue review means the procedure has not been confirmed against current regulation or practice, so the regulator cannot treat it as reliable.
So an inspector writes the observation against the control failure itself. The practice may be excellent, but the inspector is assessing whether your system can be trusted to keep producing it, and an uncontrolled document means it cannot. The same logic runs through the wider cannabis audit readiness checklist, where document control is one of the first things a self-audit confirms.
What Is the SOP for SOPs, and How Does a System Link SOP Versions to Batch Records?
The master document-control SOP, often called the SOP for SOPs, defines how every other SOP is created, numbered, reviewed, approved, distributed, archived, and retired. It is the one SOP that makes the other rules enforceable rather than aspirational, and an audit-readiness checklist explicitly looks for it: a document control SOP exists and is current. Without it, your version numbering and review cadence are conventions someone remembers rather than a controlled system an inspector can test.
A good SOP for SOPs specifies the version-numbering scheme, who may author and who must approve, the default review interval and the event triggers that shorten it, the stamping and distribution rules, the re-training requirement on revision, and the archiving rule for superseded versions. In effect it is the document-control requirements above, written as a controlled procedure and signed by the QAP like any other.
Where document control becomes genuinely hard to fake is in linking SOP versions to the batch records produced under them. On paper this means cross-referencing version numbers by hand and trusting the archive is complete. In an operations platform the link is structural: when a batch record is created, the system stamps the exact SOP version in force at that moment, so an inspector reviewing any past batch sees precisely which procedure governed it without anyone reconstructing it after the fact.
The unbreakable audit trail
Linking SOPs directly to batch records in your operations platform creates an audit trail that does not depend on memory or manual cross-referencing: inspectors can see exactly which version of a procedure was in place when a specific batch was produced. GrowerIQ is cannabis seed-to-sale and operations software used by more than 200 licensed facilities across 9 countries, and the batch-to-SOP link is one of the controls it is built to enforce automatically.
The payoff is that document control stops being a quarterly scramble before an inspection and becomes a property of the system. Version numbers increment on approval, review dates surface before they lapse, training is recorded against the version, and every batch carries its governing SOP version. That is what turns sound practice into defensible practice.
Frequently Asked Questions
What is cannabis SOP document control?
Cannabis SOP document control is the discipline of versioning, reviewing, approving, distributing, and archiving standard operating procedures so that the version in force is always provable. It covers five requirements: version control with archiving of superseded versions, a defined review cycle, QAP approval signatures, distribution control with Controlled or Uncontrolled stamping, and re-training affected staff on each revision. Under the Cannabis Regulations (SOR/2018-144) it is the documentary system Health Canada inspects to confirm that the right procedure was current and followed.
Is an out-of-date SOP a compliance finding even if the work was done correctly?
Yes. Under a recordkeeping-based regime an out-of-date, missing, or uncontrolled SOP is a finding on its own, separate from whether the practice was sound. The regulator is assessing whether your documented system can be trusted to require and prove the correct action, so a procedure that is overdue for review, unsigned, or circulating in multiple uncontrolled versions is an observation regardless of how well the task was actually performed on the floor.
How often must a cannabis SOP be reviewed?
Most cannabis SOPs carry an annual review date, and the review must be performed, dated, and signed even when no change is needed. Certain procedures add event triggers on top of the calendar: a security SOP is reviewed after any security incident, a lot-sampling SOP when you change labs, an integrated pest management SOP when you add a product. The review obligation is independent of content, so a procedure that is still correct but past its review date is overdue, and overdue is a finding.
What does Controlled versus Uncontrolled stamping mean?
In a paper-based system a Controlled copy is the authoritative, tracked printout of an SOP that is pulled and replaced when a new version is approved, while any other printout is stamped Uncontrolled to signal that it must not be relied on. The stamping exists to stop a stale personal photocopy from being used as if it were current after the SOP has been revised. Distribution control plus a managed list of who holds Controlled copies is what keeps the floor on the approved version.
What is the SOP for SOPs?
The SOP for SOPs is the master document-control procedure that defines how every other SOP is numbered, reviewed, approved, distributed, archived, and retired. It is the one SOP that makes the document-control rules enforceable rather than informal, and an audit-readiness checklist specifically looks for it: a document control SOP must exist and be current. It is authored and QAP-approved like any other procedure, and it is what an inspector reads to understand how your control system is supposed to work.
Get the Full Cannabis SOP Guide
The free guide maps document control to the complete SOP playbook: the eight elements of a compliant procedure, the required-versus-best-practice SOP library, version and review controls, and an audit-readiness checklist a QAP can run before a Health Canada inspection.
Download Free Guide
Recommended For You
New Zealand’s Medicinal Cannabis Supply Grows 14x: From CBD Oils to THC-Dominant Flower
June 16, 2026Australia’s ODC Has Replaced the Cannabis Quarterly Reporting Template: What Permit Holders Need to Know
June 10, 2026HighIQ Webinar Series: Powering Precision Production with Total Grow Control
May 8, 2026About GrowerIQ
GrowerIQ is changing the way producers use software - transforming a regulatory requirement into a robust platform to learn, analyze, and improve performance.
To find out more about GrowerIQ and how we can help, fill out the form to the right, start a chat, or contact us.