An untrained employee following a current SOP is a compliance finding waiting to happen, and the training record is the only proof you can put in front of a Health Canada inspector.
Cannabis SOP training is the controlled process by which each employee is taught the standard operating procedures relevant to their role, then verified as competent to perform them unsupervised, with a dated record linking that employee to the exact SOP version they were trained on. Under SOP-HR-001 in a properly built SOP library, training is not a one-time orientation event. It is a living loop tied to your document control system: every time an SOP is revised, the affected staff must be re-trained before the new version takes effect. This page explains how cannabis SOP training works inside a compliant operation, the competency verification methods that hold up under audit, and exactly what an inspector looks for when they ask to see your training records.
This is the training spoke of our wider cannabis SOP guide, which sets out every SOP a licensed producer should hold under the Cannabis Regulations. For the underlying document mechanics, pair this page with cannabis SOP document control and the required cannabis SOPs library.
Why Cannabis SOP Training Is a Regulatory Requirement, Not a Nicety
Under the Cannabis Regulations (SOR/2018-144), a licensed producer must operate to written standard operating procedures and must ensure the people performing licensed activities are competent to do so. Those two obligations meet in one place: SOP-HR-001, Employee Training and Competency Verification. The SOP itself is owned jointly by HR and the Quality Assurance Person (QAP), reviewed at least annually, and it governs how every other SOP in the library reaches the people who actually run the process.
The logic an inspector applies is straightforward. A written procedure has no compliance value if the person doing the work has never been trained on it, cannot demonstrate competency, or was trained on a version that has since been superseded. An out-of-date, undocumented, or unverified training position is a finding in its own right, even when the work was performed correctly. The Cannabis Act (S.C. 2018, c. 16) frames the QAP role around assuring quality, and assured quality is impossible without assured competency behind every controlled step.
SOP-HR-001 typically covers three obligations:
- Training on role-relevant SOPs. Each employee is trained on the SOPs that apply to their role, not the entire library. A sanitation technician trains on SOP-SAN-001 and SOP-SAN-002. A QAP signing batch releases trains on SOP-QA-002. The role-to-SOP mapping is itself a controlled document.
- Competency verification. Attendance at a training session is not competency. The SOP must define how competency is demonstrated and assessed for each procedure before the employee performs it unsupervised.
- Training records. Every training event is recorded with the employee name, the SOP and version trained, the date, the verification method and result, and the trainer or assessor signature. These records are the audit-trail element an inspector reaches for first.
The training record is the evidence, the training is the activity
Inspectors do not audit your training sessions. They audit your training records. A perfectly delivered training programme with sparse or version-blind records will fail an inspection, while a modest programme with complete, version-linked records will pass. Build the record-keeping first, because the record is what survives the moment after the trainer leaves the room.
What Does Cannabis SOP Training Look Like in Practice?
A compliant cannabis SOP training programme runs as a defined cycle rather than a single onboarding push. The cycle has four moments where training is triggered, and each one produces a record.
- New hire onboarding. Before an employee performs any licensed activity unsupervised, they are trained and verified on the SOPs mapped to their role. Until verification is on file, the work is supervised or not assigned at all.
- SOP revision. When an SOP is updated, the affected staff are re-trained on the new version before it takes effect. This is the document-control rule that most often trips up an operation, and it is covered in detail in the next section.
- Annual refresher. SOP-HR-001 is reviewed at least annually, and most operations run a periodic refresher so that competency does not decay and the training record stays current within the review cycle.
- Post-incident retraining. When a deviation, non-conformance, or near-miss investigation points to a training gap, the corrective action includes targeted retraining, and that retraining is recorded against the relevant SOP.
Each moment ends the same way: a record is created or updated that ties a named employee to a specific SOP version, with a verification outcome. That record is the spine of the whole programme. If you build your required cannabis SOPs library well but leave the training records loose, the library cannot defend itself in an audit.
What Are the Competency Verification Methods for Cannabis SOPs?
Competency verification is the step that separates real cannabis SOP training from a signed attendance sheet. The SOP must state, for each procedure, how the employee proves they can perform it correctly and unsupervised. Three methods cover almost every SOP in a cannabis operation, and many SOPs combine more than one. The method chosen should match the risk and the nature of the procedure.
| Verification method | How it works | Best suited to |
|---|---|---|
| Observed demonstration | The trainer or assessor watches the employee perform the actual procedure and confirms each step is executed correctly. The observation is recorded against a defined checklist. | Hands-on, physical procedures: gowning and personnel hygiene (SOP-SAN-002), environmental cleaning (SOP-SAN-001), lot sampling and chain of custody (SOP-QA-001), plant tagging and stage transitions (SOP-CUL-001). |
| Written assessment | The employee completes a written or digital test on the procedure, its decision points, and its deviation handling, with a defined pass threshold recorded in the training file. | Knowledge-heavy or judgement-heavy procedures: deviation and non-conformance reporting (SOP-QA-003), product recall and market withdrawal (SOP-QA-004), inventory reconciliation logic (SOP-INV-001). |
| Sign-off / attestation | The employee and the trainer both sign to attest that training was delivered, the SOP version was reviewed, and competency was confirmed. Often the closing record for either method above. | Every SOP as the documentary close-out, and as the standalone method for lower-risk procedures and document reviews where demonstration or testing is not proportionate. |
Whichever method you use, the verification result is part of the record, not a side note. An observed demonstration that was failed and then repeated, a written assessment scored below threshold and re-sat, a sign-off withheld until a second observation passed: all of these are evidence that the verification step is real. A programme where every employee passes every verification on the first attempt, every time, tends to draw more inspector scrutiny, not less, because it suggests the verification is a formality rather than a control.
How Does Training on SOP Revisions Connect to Document Control?
The single rule that links cannabis SOP training to your document control system is this: when an SOP is revised, the affected staff must be re-trained on the new version before that version takes effect. The new version does not go live the moment the QAP signs it. It goes live once the people who use it have been trained and verified on what changed. Skipping that gap, where staff are working to a version they have not been trained on, is one of the most common and most preventable findings in a cannabis inspection.
This is why training and document control cannot be run as separate systems. Document control owns the version number, the approval signature, the archived superseded copy, and the distribution to controlled areas. Training owns the verification that the people affected can perform the new version. The handover between them is the training-on-revisions rule. The mechanics of versioning, review cycles, and approval signatures are covered in full in cannabis SOP document control.
In practice the revision-to-training loop runs like this:
- The QAP approves a new SOP version under document control, but flags it as pending rather than effective.
- The role-to-SOP map identifies the affected staff so that only the people who use the procedure are retrained, not the whole site.
- Affected staff are retrained and verified on the new version, and each event is recorded against the new version number.
- The version takes effect only once the affected-staff training records are complete. Until then, the previous version remains the controlled version in use.
The reason this matters so much for the audit trail is traceability. If a batch is produced under version 2 of a cleaning SOP, the inspector wants to confirm that the operator who cleaned the room was trained on version 2, not on the superseded version 1. That cross-check only works if training records are linked to specific SOP versions. This same version-linked discipline is what underpins the cannabis audit readiness checklist.
What Does an Inspector Look For in Cannabis Training Records?
Training records that link each employee to the specific SOP version they were trained on are a core audit-trail element, and an inspector evaluates them against a consistent set of expectations. A record that simply says an employee attended a training session on a date is not enough. The record has to answer who, what version, when, how verified, and signed by whom.
| What the inspector checks | Why it matters |
|---|---|
| Employee is named, and the SOP and version number are recorded together | Version-blind records cannot prove the employee was trained on the procedure that was actually in force when the work was done. This is the most common record-keeping gap. |
| Training date is on or before the date the employee first performed the activity unsupervised | A training date after the first unsupervised performance means the employee worked uncertified. The timeline has to defend the work. |
| A competency verification method and result are recorded | Attendance is not competency. The inspector wants the observed demonstration, the written assessment score, or the attested sign-off, with the outcome. |
| Trainer or assessor signature is present | The verification needs an accountable person behind it, mirroring the QAP approval signature requirement on the SOP itself. |
| Re-training records exist for every superseded version still inside the review window | Confirms the training-on-revisions rule was followed and that no one worked to a version they were not retrained on. |
| Records are retrievable on request and survive staff turnover | A training record that left with the employee or the trainer is no record at all. It must live in a controlled, durable system. |
The fastest way to fail this part of an inspection is a training record that cannot be tied back to a version, or a version in use with no matching training record behind it. The fastest way to pass it is to make the version link automatic rather than manual, so that a record cannot be created without naming the SOP version it covers.
Where the operations platform earns its place
Linking SOPs directly to batch records in your operations platform creates an unbreakable audit trail: an inspector can see exactly which version of a procedure was in place when a specific batch was produced, and confirm that the staff who performed each step were trained on that version. GrowerIQ is cannabis seed-to-sale and operations software used by 200 plus licensed facilities across 9 countries, built so that the version-linked training record and the batch record live in the same system rather than in a binder that walks out the door. For the licensing and compliance frame this all sits inside, see Health Canada’s cannabis licensing and compliance guidance.
Frequently Asked Questions
What is cannabis SOP training and why is it required?
Cannabis SOP training is the controlled process of teaching each employee the standard operating procedures relevant to their role and verifying they are competent to perform those procedures unsupervised. It is required because under the Cannabis Regulations (SOR/2018-144) a licensed producer must operate to written SOPs and ensure the people performing licensed activities are competent. SOP-HR-001, Employee Training and Competency Verification, is the SOP that governs this, owned by HR and the QAP and reviewed at least annually. A written procedure carries no compliance value if the person doing the work was never trained on it or cannot demonstrate competency.
What competency verification methods are used for cannabis SOPs?
Three methods cover almost every cannabis SOP. Observed demonstration, where a trainer watches the employee perform the actual procedure against a checklist, suits hands-on tasks like gowning, sampling, and plant tagging. Written assessment, where the employee passes a test on the procedure and its decision points, suits knowledge-heavy procedures like deviation reporting and product recall. Sign-off or attestation, where employee and trainer both sign to confirm training and competency, serves as the documentary close-out for any method and as the standalone method for lower-risk procedures. The verification result, including any failed and repeated attempt, is recorded as part of the training record.
Do staff need to be re-trained when an SOP is updated?
Yes. The document-control rule is that when an SOP is revised, the affected staff must be re-trained on the new version before that version takes effect. The new version is approved by the QAP but does not go live until the people who use it have been trained and verified on what changed. The role-to-SOP map identifies which staff are affected so the whole site is not retrained unnecessarily. Until the affected-staff training records are complete, the previous version remains the controlled version in use. Working to a version that staff have not been retrained on is a common and preventable inspection finding.
Why must training records be linked to specific SOP versions?
Because the audit trail depends on it. If a batch is produced under version 2 of a procedure, an inspector wants to confirm that the staff who performed each step were trained on version 2, not the superseded version 1. A training record that names only the SOP, with no version number, cannot make that link and cannot prove the employee was trained on the procedure that was actually in force. Version-linked training records are a core audit-trail element, and the cleanest way to maintain them is a system where a record cannot be created without naming the SOP version it covers.
What does a Health Canada inspector look for in training records?
An inspector checks that each record names the employee and the SOP version together, that the training date falls on or before the date the employee first performed the activity unsupervised, that a competency verification method and result are recorded, and that a trainer or assessor signature is present. They also confirm that re-training records exist for superseded versions still inside the review window, and that records are retrievable on request and survive staff turnover. Attendance alone is not enough. The record must answer who was trained, on which version, when, how competency was verified, and who signed off.
Get the Full Cannabis SOP Guide
The free guide maps every SOP a licensed producer should hold under the Cannabis Regulations, the 8 elements of a compliant SOP, the document-control rules including training on revisions, and an audit-readiness checklist that links training records to specific SOP versions.
Download Free GuideRecommended 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.