What does a cannabis IPM plan actually require?
A defensible cannabis IPM plan is a written document, not a mental framework. Most state programs require it as part of the initial license application and expect it to be maintained and updated through the facility's operational life. Inspectors review it during announced and unannounced site visits.
The core components that programs consistently require:
Pest and pathogen identification. A list of the specific organisms the facility is managing, by common and scientific name, across insects, molds, bacteria, viruses, and viroids relevant to the facility's crop stages. A plan that lists "mold" without naming species is less defensible than one that names Botrytis cinerea, Golovinomyces ambrosiae, Aspergillus species, and the specific contamination vectors in the facility.
Monitoring protocols. How the facility detects pest and pathogen pressure before it reaches outbreak level: scouting schedules, environmental sensor thresholds, settling plate placement, water sampling cadence, and who is responsible for each.
Action thresholds. The specific conditions that trigger an escalated response. Not just "if we see mold we treat it," but defined thresholds that trigger specific actions at each tier.
Control methods by tier. Prevention measures first, then cultural and physical controls, then biological controls, then registered chemical controls as a last resort, with each tier documented and justified.
Record-keeping. Logs that demonstrate the plan is being executed: scouting logs, treatment logs, pesticide application records with applicator information, and corrective action documentation.
How does IPM intersect with cannabis compliance testing?
IPM and compliance testing connect through pesticide residue testing on one side and microbial testing on the other.
Pesticide residue. The chemical control tier of any cannabis IPM plan is constrained by state-specific approved pesticide lists. Many states have narrow lists of registered pesticides that can be used on cannabis. Residue testing at the point of sale tests for prohibited compounds regardless of whether they appear on the label or not. An operator who uses a registered agricultural pesticide not on the state's cannabis-approved list may pass microbial testing but fail pesticide residue testing. The IPM plan documents what was used and when; that record is both a compliance requirement and a liability document if residue is detected.
Microbial testing. The prevention tier of IPM, including sanitation, environmental controls, and water treatment, is what directly affects TYM, Aspergillus, E. coli, and Salmonella outcomes at testing. A facility with a documented prevention program that includes registered surface sanitation chemistry, water treatment, and environmental monitoring has a compliance paper trail that a facility with no IPM documentation does not. When a compliance failure occurs, documented IPM is the difference between a correctable event and a license review.
Where does ClO₂ surface sanitation fit in an IPM framework?
Chlorine dioxide under EPA Reg. No. 73139-1 sits in the IPM prevention tier, specifically in the sanitation and disinfection component that addresses surfaces, equipment, benches, and water systems between crop cycles and during operations.
When listing surface sanitation in the IPM plan, the entry should specify:
The registered EPA chemistry (EPA Reg. No. 73139-1). The application method (surface application via PATHox™ protocol). The target surfaces (benches, floors, walls, irrigation hardware, tools). The application cadence (routine/daily and deep cleaning on room turnover; also tool sanitization). The documentation method (treatment log with dates, surfaces treated, staff assigned).
This level of specificity turns a generic "we sanitize surfaces" statement into a documented program that addresses both the IPM plan requirement and provides the audit trail regulators look for. It also positions CLEANTheory's program as the registered chemistry within the IPM framework rather than an add-on outside of it. Requirements vary by state — consult your compliance advisor to confirm the documentation standard for your jurisdiction.
What do cannabis IPM inspections actually look for?
State inspectors reviewing IPM compliance are checking three things in roughly this order:
Does the written plan match the actual operation? Inspectors compare what the plan says to what they observe on-site. A plan that describes daily scouting but has no scouting logs is a red flag. A plan that specifies EPA-registered chemistry but has unlabeled bottles on the shelf is a violation. The plan and the practice have to match, which is why building the plan around what you're actually doing is more defensible than building an aspirational plan and trying to implement it.
Is the documentation current and accessible? Treatment logs, scouting records, pesticide application records, and corrective action notes should be retrievable on-site within minutes. Operators who maintain these records in a dedicated binder or digital system consistently report smoother inspections than those who reconstruct records when asked.
Are pesticides being used as directed and on the approved list? Pesticide records are cross-checked against state-approved lists and against label requirements. An application made by an unlicensed applicator, at an off-label rate, or with a product not on the state list is a compliance event regardless of whether the crop passes testing.