Ask a cannabis operator if their employees are trained on compliance procedures and they'll say yes. Ask to see the documentation, and you'll usually get a sign-in sheet from orientation day — a single page proving that the employee was physically present when someone talked about compliance topics. That's not evidence of training. That's evidence of attendance.
Employee training is one of the most commonly cited compliance gaps during inspections, and the reason is almost always the same: the training happened, but the documentation doesn't prove what was covered, how comprehension was verified, or whether the training has been updated to reflect current procedures.
Where Training Programs Break Down
One-Time Onboarding, No Ongoing Documentation
Most operations train employees during their first week and then never formally document training again. Regulations in most jurisdictions require ongoing compliance training — not a single event. If an inspector asks for evidence that an employee received training on a procedure that changed six months ago, a two-year-old sign-in sheet doesn't answer the question.
No Topic Specificity
A training record that says "compliance training — 2 hours" doesn't demonstrate that the employee was trained on waste disposal procedures, inventory handling, security protocols, or any other specific topic. It demonstrates that they sat in a room for two hours. Effective training documentation specifies the exact topics covered, the procedures reviewed, and the version of the SOP that was used.
No Comprehension Verification
Sitting through a presentation doesn't mean learning occurred. The strongest training programs include some form of verification — a short quiz, a practical demonstration, a supervised walkthrough of the procedure. This creates documentation showing not just that the employee was exposed to the material, but that they understood it well enough to execute it.
Training Doesn't Update When Procedures Change
When an SOP gets revised — new equipment, modified workflow, changed regulatory requirement — every employee who performs that procedure should be retrained on the updated version. In most operations, this step is simply skipped. The SOP changes, the verbal instructions change, but the training records still reference the old version. That creates a gap between documented training and actual practice.
What This Looks Like During an Inspection
An inspector identifies a process issue — say, waste disposal records that are consistently incomplete. They ask: "Has this employee been trained on the current waste disposal procedure?" You produce a training record from onboarding. The inspector notes that the waste SOP was revised eight months ago. There's no documentation showing the employee was retrained on the current version. The finding writes itself.
This scenario plays out across every operational area: METRC entry, inventory handling, security procedures, receiving protocols. Each one is a potential finding if the training documentation doesn't demonstrate current, topic-specific, verified training.
Building a Training System That Holds Up
Document Topics, Not Just Events
Every training session should record: the specific topics covered, the SOP versions referenced, the date and duration, the trainer's name, and the trainee's acknowledgment. This turns a sign-in sheet into actual evidence of what was communicated.
Schedule Recurring Training
Define a training calendar tied to your regulatory requirements and operational risk areas. High-risk areas like waste handling and inventory management should have more frequent refreshers. Low-risk areas can be annual. The key is consistency — a scheduled cadence that creates a continuous training record rather than a one-time event.
Trigger Retraining on SOP Changes
Every SOP revision should automatically trigger a retraining requirement for affected employees. The revision date, the training date, and the employee acknowledgment should all be linked. A training management system can automate this entire cycle — flagging when retraining is due and tracking completion.
Verify and Document Competency
Add a simple verification step to each training session: a short written check, a supervised task completion, or a verbal walkthrough of the procedure. Document the result. This elevates your training records from "they were told" to "they demonstrated understanding."
The difference between a training program that passes inspection and one that doesn't is usually not effort — it's structure. A well-designed system captures the right information at each step and creates records that are clear, complete, and easy to verify. Once that structure is in place, maintaining it becomes routine rather than burdensome.