A cannabis IPM audit checklist is the pre-inspection self-audit a facility runs two to six weeks before a state regulator or corporate QA visit, to confirm that every component of the integrated pest management program is in place, followed, and documented the way an inspector will ask to see it. It is not the IPM plan, not a single sanitation SOP, and not the mold protocol; it is the verification layer that proves those exist. This guide gives you the room-by-room checklist, the records inspectors request first, the EPA sanitizer rows most checklists skip, and a downloadable version you can print and walk the facility with.
One scope note. This page is the audit artifact. For the program behind it, see cultivation IPM expertise; for the mold-specific thresholds, mold prevention protocols; for the air-quality data trail, air quality management. If you are mid-outbreak right now, you need remediation first, not a self-audit. Facility managers, head growers, and MSO directors preparing for inspection day, read on.
Who this checklist is for, and when to run it
Three readers land here at the same moment: a head grower running one multi-room facility, a facility manager rotating single or small multi-room grows, and a cultivation director standardizing across a multi-state footprint. All three are inside the window where an inspection is scheduled or expected and the question has shifted from "is our program good" to "can we prove it on demand." Their angles differ slightly: the head grower is protecting a crop and a yeast-and-mold pass rate, the facility manager is protecting a turnover schedule and a sanitation record, and the MSO director is protecting consistency across a footprint where every state asks something a little different. The checklist serves all three because it is built from the controls an inspector verifies regardless of title, and it flags where each role's specific pain, a failed mold test, a bleach-driven downtime, a divergent state rule, intersects a line item.
The cadence matters. Run the checklist as a self-audit on a schedule, not once: a full pass two to six weeks before a known inspection, and a lighter recurring pass quarterly so there is no scramble when a visit lands. The entire value of a self-audit is that you find your own gaps while they are cheap to close, rather than letting an inspector find them for you while they are expensive. Treat every line you cannot immediately evidence as a finding to fix before inspection day.
The reframe worth internalizing is that an audit checklist is a verification tool, not a growing guide. A skilled grower can keep rooms clean by instinct and still fail an inspection, because an inspector cannot grade instinct, only the record. The checklist exists to make the invisible discipline visible, to turn what a good operator already does into something a stranger can confirm. That is also why it protects you: the facility that walks in with a current, zone-by-zone checklist and the records behind it controls the conversation, while the facility without one reconstructs its own history under pressure as the inspector forms an impression.
What state cannabis inspectors actually ask to see
Inspectors do not grade intentions; they grade records. State cannabis divisions publish their own self-inspection and facility checklists, and across them the pattern is consistent: they want the written program, the logs that prove it ran, the product documentation behind any sanitizer, and evidence that deviations were caught and corrected.
Two things surprise operators. First, the corrective-action clock is real and varies by state: some state cannabis control divisions require a corrective plan of action submitted within five business days of an inspection report when violations are noted, which means an open, undocumented finding at inspection becomes a deadline, not just an observation. Second, a gap in a log is itself a finding. An inspector reads a trap log or a sanitation record with a missing week as evidence the program was not managed during that week, regardless of whether anything went wrong. Continuity of records is scored as heavily as the readings themselves.
The records an inspector reaches for first are predictable, so the checklist front-loads them: the written IPM or biosecurity plan, the scouting and monitoring logs, the sanitation records with product and contact time, the SDS and EPA labels for every chemistry on site, the microbial test results on recent harvests, and the corrective-action log. If those six are current and retrievable, the inspection starts on a good footing; if any is missing or stale, the inspector digs, and digging surfaces the smaller gaps. A self-audit that confirms those six first is spending its effort where the inspection actually lands.
The IPM program behind the checklist
You cannot audit a program you have not built, so a word on what the checklist is verifying. The program itself is detailed under cultivation IPM expertise; this is the short version that answers the questions inspectors and searchers both ask.
The three rules of IPM are, in plain terms: prevent pests from establishing, monitor so you catch what gets through early, and intervene with the least-aggressive effective control, cultural and biological before chemical. Monitoring and scouting are related but not identical: monitoring is the ongoing data collection (sticky cards, sensor logs, scheduled readings) that builds a trend, while scouting is the active, trained walk that inspects plants and surfaces for early signs. And yes, IPM includes weeds and any unwanted organism, not only insects; in a cannabis facility the practical pest list runs to mold, mildew, viroids, mites, and the microbial load a lab tests for. The audit checks that each of those has a control and a record.
The reason to be precise about monitoring versus scouting is that inspectors probe the seam between them. A facility often has one without the other: sensor data piling up that nobody reviews, or an experienced grower who scouts well but logs nothing. Either leaves a gap, because monitoring with no scouting means data without action, and scouting with no record means action without proof. The checklist verifies both halves and the link between them, that a trend in the monitoring data triggers a documented response, which is what an auditor means when they ask whether the program is actually managed.
The room-by-room audit checklist
The core artifact audits each zone against its own controls, because a mother room and a cure vault carry different risks and need different checks. Walk the facility one room at a time, treating each zone as its own inspection with its own line items rather than applying one generic list to every space.
Mother, clone, and veg rooms
The contamination entry point. Verify clone and mother-stock quarantine, hop latent viroid testing before anything joins production, scouting on a logged cadence, humidity at the veg target, and surface sanitation between transplants with a plant-safe disinfectant. A weak control here surfaces downstream as a flower-room problem no one can trace. The audit treats quarantine and viroid testing as hard gates in this zone, with the release decision recorded, because an untested clone is the cheapest contamination to prevent and the most expensive to chase once it has moved into production. Verify that the mother and clone area has its own tools and that staff do not move from a pressured flower room back into it without the gowning and hand-hygiene step.
Flower rooms
The highest-value zone and the mildew and botrytis pressure peak. Verify the late-flower humidity drop on schedule, airflow reaching the dense canopy and not just the room reading, early-botrytis scouting in the thickest colas, and residue-free surface sanitation that can run with plants present. The flowering-stage detail is under mold prevention protocols. Because this zone holds the most crop value, it is where an operator is most tempted to defer a sanitation step to avoid disturbing plants, which is exactly why the residue-free, plant-safe surface option matters on the checklist: it lets the surface controls keep running with the crop in place rather than waiting for turnover.
Dry, cure, trim, storage, HVAC, and entry
The dry and cure zones are where a clean grow still fails a lab test, because the biomass is giving up moisture and a crowded, under-ventilated dry room climbs above target within hours, so verify a sanitized dry room before the crop hangs, humidity and airflow logged through the dry, and water-activity records on cure batches. Water activity is the number that predicts cure-room mold better than a room humidity reading, because it describes moisture in the product itself, and two batches at the same room humidity can carry very different water activity depending on how they dried. Trim and packaging handle product most, so verify food-contact-grade sanitation, clean-tool control, and gowning, because a contamination introduced at this stage rides onto finished flower that cannot be cleaned afterward. Storage, the vault, and waste handling round out the zone list: verify finished-flower storage held in range, and waste and drains managed so they do not become reservoirs that reseed the clean rooms. The HVAC plenum and return path are the spore highway, so verify coil cleaning, filter changes with the MERV rating logged, and condensate-pan sanitation. The entry airlock and gowning station verify people and visitors do not carry contamination in, which is the control most often implied and least often documented, so the audit makes it explicit with a gowning log and a visitor protocol that applies the same clean-flow rules to anyone who is not daily staff. Each zone gets its own checklist page so an auditor can tick controls room by room.
The zone structure enforces two disciplines that a flat checklist loses: clean-to-dirty flow and zone-appropriate chemistry. A crew should move from low-pressure rooms to high-pressure ones and not back, tools should not cross between zones, and the surface disinfectant that runs in an occupied flower room is not the empty-room gas used during a turnover. Writing the checklist per zone forces those distinctions onto the page, so an operator cannot carry a flower-room problem into the clone room or reach for an empty-room product while plants are present. The zones are the control, not just the layout, and an inspector who sees a per-zone checklist reads a facility that thinks in those terms.
EPA and sanitizer compliance
This is the biggest worry compliance leads name and the row set most checklists omit. In a licensed facility the sanitizer label is enforceable, so the audit treats EPA status as an inspectable line item, not a footnote.
The EPA rows, by product
Verify, per sanitizer in inventory: a current SDS on file, the EPA registration number checked against your state's cannabis allowed list, the label use pattern confirmed (surface, air, with or without plants), and any applicator training the state requires. Chlorine dioxide (ClO2) appears as three products with label-separated roles. ProKure V is a liquid surface disinfectant (EPA Reg. No. 87508-3-89334) that works at 100 ppm for a 10-minute exposure, leaves no residue, and is suitable for use with plants in the room, so it is the surface tool usable in occupied rooms. ProKure G is a fast-release gas deodorizer (EPA Reg. No. 87508-2-89334) carrying the verbatim restriction "Not for use with/on plants/crops/feed," so the audit confirms it ran only in empty rooms with a ventilation window. ProKure D is a slow-release gas that provides ClO2 protection for up to 30 days and runs with plants present, but it is not EPA-registered, carries the verbatim disclaimer "Not an EPA-registered product and not labeled for sale as a pesticide under 40 CFR," and makes no kill claim. Do not attach G's plant restriction to V or D. The specs are at ProKure V liquid surface disinfectant and ProKure G fast-release gas.
It also matters that an EPA registration is for a hard-surface disinfectant, which is a separate thing from a state-approved pesticide for use on plants; conflating the two is a common finding. The audit keeps them in different rows, because a product legal as a surface disinfectant is not automatically permitted as a crop treatment, and the state cannabis pesticide allowed list is a check distinct from federal EPA registration. The two-column habit, products usable with plants present versus empty-room-only, is what keeps the single most common compliance error, the right product used at the wrong time or in the wrong zone, off your record before an inspector can write it onto theirs.
Residue and the document kit
The residue row matters because bleach and quaternary ammonium compounds leave residue the next crop contacts, where a residue-free surface disinfectant does not; the audit verifies the residue-appropriate product was used in each zone. And it verifies the kit a procurement or QA lead assembles before the auditor arrives: SDS, EPA labels, purchase records, and dilution logs, in one retrievable location, because an inspector who asks is handed the document rather than watching a search. The procurement angle is easy to underweight until the turnover you cannot run because the sanitizer did not arrive, or the audit where the label on file is a version behind the product on the shelf. Tie the reorder trigger to the production schedule and refresh the SDS and label file whenever a formulation or supplier changes, so the document kit always matches what is actually in the building.
The data trail and corrective-action loop
Two record sets carry most of the audit weight beyond the zone checks.
The microbial and air-quality trail: the last several harvests' total yeast and mold CFU results with the retest rate and remediation records, the HVAC filter-change log, air sampling on a defined cadence, and ClO2 re-entry dwell times documented for any gas treatment. This is the data a head grower hands an auditor to prove the environment was controlled, not just that it looked clean, and it is detailed under air quality management. For a multi-facility operator this trail is also the hardest thing to produce on demand, because the pain is not usually a dirty room but the absence of centralized air-test data across sites; standardizing the logging format across facilities so corporate QA can pull any site's trail in the same shape is what turns a scramble into a report.
The corrective-action loop: for every deviation, a record of the root cause, the immediate corrective action, the preventive action that changes the system, and the closure evidence. Two points an inspector weighs. An open, unclosed corrective action at inspection is a serious finding, so close the loop before the visit. And a clean record with zero deviations ever logged reads as a facility that is not looking, because every real operation hits the occasional out-of-range reading; what reassures an auditor is a closed loop, not an empty one. A log that shows a few deviations caught early, documented, and closed out is more credible than a spotless one, because it demonstrates the monitoring is actually catching things. The facilities that fail are rarely the ones that had a problem; they are the ones that had a problem and cannot show they handled it. The state corrective-action clock means a finding raised at inspection may carry a deadline of only a few business days, which is one more reason to surface and close findings on the self-audit first.
The two halves of corrective and preventive action are worth separating because operations conflate them. The corrective action fixes this batch and this room; the preventive action changes the system so the same cause cannot produce the same failure again. A facility that only ever takes corrective action keeps hitting the same problem, and an auditor reading a log of repeated corrective actions with no preventive change sees a quality system treating symptoms. Closing the preventive half, updating the SOP, retraining the crew, re-sequencing a step, is what turns a recurring deviation into a one-time one, and it is the difference a mature inspector looks for.
Download the checklist, and standardize across facilities
Everything above is visible so you can confirm the structure fits your state's inspection before you give up an email. The gated download is the working version: a room-by-room checklist with the frequency bands (weekly, monthly, quarterly, and event-triggered), the EPA sanitizer rows, the data-trail specification, and a corrective-action template. The form asks only for email and facility footprint, so the follow-up fits your operation. Print it, walk the facility zone by zone, and mark every control you cannot immediately evidence as a finding; the self-audit that surfaces its own gaps is cheap, while the same gap found during a state inspection carries a corrective-action deadline and a citation.
For a multi-state operator, the checklist standardizes the way the program does: one master checklist plus a per-state appendix holding that state's allowed-product list, testing thresholds, and corrective-action window, so a rule change updates one appendix and corporate QA audits every facility against the same master. Build the appendix structure from the start even in a single state, because retrofitting it after several facilities have each drifted into their own checklist is far more work than designing for it up front. You now know what a regulator-ready self-audit contains, which means you can run your own before an inspector runs theirs.
One closing note on the frequency bands, because they are what make the checklist a living tool rather than a one-time exercise. Weekly items (scouting, sticky-card counts, sanitizer dilution verification) catch the fast-moving risks; monthly items (trend review, HVAC filter logs, a full room walk) catch the slow slides; quarterly items (full biosecurity review, SDS and EPA label refresh, contractor review) catch the drift nobody notices day to day; and event-triggered items (a positive mold test, a pest sighting, a failed compliance test) kick in the moment something changes. A checklist that runs on all four cadences produces the continuous record an inspector reads as a managed program, and the program behind all of it lives under cultivation IPM expertise.
Related resources


