A head grower's IPM protocol is a working document, not an essay, and it has five layers: prevention, scouting, action thresholds, intervention, and verification plus logging. Prevention is what you fix before the crop enters the room. Scouting is a scheduled cadence of trap counts and inspections. Action thresholds are the readings that trigger a response. Intervention goes biocontrols first, then EPA-registered chemistry. Verification and logging produce the dated record that proves the whole thing to a state auditor. If you run multiple rooms, this is the structure you adapt this week and hand to your crew, not a lecture on what IPM means.
Most of what ranks for this is not for you. The published IPM material skews to tree fruit and row crops: apples, tart cherries, cotton, plus a few podcast archives. It stays at the level of definition. As one of those incumbent pages puts it, "The main focus of an IPM strategy is prevention," which is true and also where most of them stop. You already know prevention is the point; you need the cadence, the thresholds, and the log fields that turn that principle into a room-by-room procedure. New to IPM at the definition level? Start with the cannabis IPM basics guide. Everything below assumes you run the room.
How this protocol is structured
Think of the protocol as five layers that feed each other. Prevention lowers the baseline pressure so you intervene less. Scouting measures the pressure that gets through. Action thresholds convert a measurement into a decision. Intervention acts, biocontrols before chemistry. Verification and logging confirm the action worked and leave the evidence. The reason to write it as five named layers is that it makes the document delegable: a scout knows which layer they own, an applicator knows theirs, and you, the head grower, own the thresholds and the escalation rules that connect them.
That structure also answers the question people ask first: the five steps of IPM are, in practice, prevention, monitoring (scouting), setting action thresholds, intervention, and evaluation (verification and logging). Keep that spine and the rest of this page is just the cannabis-specific detail hung on it.
The reason to adopt the layer model over a looser "watch for bugs and spray when you see them" habit is that the layers make responsibility and sequence explicit. Each layer has an owner, an output, and a handoff: prevention hands a low-pressure room to scouting, scouting hands readings to the threshold logic, the threshold logic hands a go or no-go to intervention, and intervention hands a result to verification. When something fails, the layer model tells you where: a pest that got to a damaging level either slipped prevention, was missed by scouting, crossed a threshold that was set too high, or survived an intervention that was not verified. That diagnosis is only possible because the protocol separated the work into layers you can inspect one at a time.
Prevention layer: what you fix before the crop enters the room
Prevention is cheaper than every other layer combined, and in an indoor cannabis room it is mostly about the environment and what you let in. The single highest-value prevention step is a clean between-cycle room turnover: strip the room, pre-clean soiled surfaces, and disinfect hard surfaces before the next crop goes in. The full step sequence lives in the between-cycle room turnover protocol; for this document, the rule is that no room receives plants until its surfaces have been reset.
Airflow and VPD do quiet prevention work. Dense, still canopy and humid dead spots are where powdery mildew and botrytis start, so even air movement and humidity control suppress pressure before a pest or pathogen establishes. Clone and cutting quarantine is the other gate: incoming genetics are the most common way a pest walks into a clean facility, so new material goes through a quarantine and inspection step before it touches the mother or veg rooms. And personnel hygiene (PPE, foot traffic rules, tool discipline) closes the vector that scouting cannot see, because a spore load moves room to room on shoes and shared tools as readily as on air.
Air quality belongs in the prevention layer too, not only in scouting, because the between-cycle reset sets the baseline the next crop grows into. A room that was turned over with a residue-free surface disinfection and then held at a steady air-quality baseline starts the cycle with less pressure than a room that was merely emptied and refilled. This is where the ClO2 products earn their place as prevention tools rather than only as reactive ones: a surface disinfection on the empty room and an ongoing in-room air layer during the grow both lower the baseline that scouting then has to chase. The intervention layer below covers which product does which job and the label rules that govern each; the prevention point is simply that air and surface hygiene are things you build in at turnover, not bolt on after a problem.
Write the prevention layer as a checklist tied to the cycle, not as a philosophy. Before plants enter: surfaces reset, airflow verified, incoming genetics cleared through quarantine, PPE and traffic rules posted. During the grow: humidity and airflow held in range, air-quality layer running, traffic discipline enforced. A prevention layer that is a checklist gets done; one that is a paragraph of good intentions does not, and the difference shows up three weeks later as a mite population or a mold reading you could have starved out.
Scouting layer: a cadence you can hand to a subordinate
Scouting is where generic IPM content goes vague and a working protocol gets specific. The point is a schedule a crew member can execute without you in the room. A workable weekly cadence looks like this: Monday, sticky-card counts logged room by room; Wednesday, leaf-underside inspection in veg and early flower, where mites and thrips hide; Friday, an air-quality read and surface check across all flower rooms. Each task names the day, the room, the tool, and the log field so it is a checklist, not a judgment call.
Place sticky cards by room type and growth stage: at canopy height near airflow paths in veg, and at problem zones (doors, intakes, drains) in flower. Leaf inspection targets the undersides of lower and interior leaves first, because that is where populations build before they are visible on top. The air-quality and surface-swab cadence is the part most cannabis scouts skip, and it is the part that catches mold pressure before a compliance test does. Every count and reading lands in the log with a date and a room, because scouting that is not written down is not scouting, it is a vibe.
The discipline that makes scouting survive a busy week is assigning it to a named cadence rather than to "when someone has time." Someone owns Monday's card counts, someone owns Wednesday's leaf inspection, someone owns Friday's air read, and the protocol names which rooms each covers so nothing falls through a gap between shifts. A card count is a number per card per room, not an impression; a leaf inspection is a fixed sample (so many plants per room, same positions each week) so the week-over-week comparison means something. Consistency is what turns scouting from a snapshot into a trend, and a trend is what your action thresholds read.
One scouting habit specific to cannabis is worth building in: scout by growth stage, not just by calendar. Clones and early veg are where a new introduction shows first, flower is where the stakes are highest and the canopy hides the most, and the dry and cure rooms are where a late mold problem concentrates. Weighting your inspection effort toward the stage with the most to lose that week, rather than inspecting every room identically, is how a head grower spends a finite scouting budget where it protects the most crop value.
Action thresholds: when monitoring becomes intervention
A threshold is the number that converts a scouting reading into a decision, and setting them is the head grower's core job. For insect pests, thresholds are per-species and per-card: a low, stable spider mite or thrips count on sticky traps is a monitor-and-hold; a rising count across consecutive scouting days is an intervention trigger. Fungus gnats, aphids, russet mites, and whiteflies each get their own trigger count, written down, so the scout is not guessing where "too many" is.
For pathogens, the triggers are earlier and stricter because the downside is a failed crop: any confirmed powdery mildew or botrytis is an immediate action, not a wait-and-watch, and a rising environmental mold reading is a prevention escalation. The highest-stakes thresholds tie back to compliance. State-mandated total yeast and mold (TYM) limits are not just a pass/fail at harvest; they are a feedback signal you should set your internal action thresholds below, so a room trending toward the state limit triggers intervention well before a compliance test. The per-state numbers live in the yeast and mold load compliance by state guide; the protocol rule is that your internal trigger sits under the state limit, not at it.
The reason to write thresholds as numbers rather than instincts is that a number is delegable and defensible. A scout who sees "intervene at this card count for this pest" acts without waiting for you; an auditor who sees a written threshold and a log showing you acted on it sees a program, not a scramble. Thresholds also protect against two opposite failures: acting too early (burning biocontrol budget and crew hours on a population the beneficials would have held) and acting too late (a mold reading that was climbing for a week before anyone escalated). The threshold is the line that makes both failures visible before they cost a crop.
Thresholds are not set once and frozen. They move with the room and the season: a flower room in a humid month warrants a tighter mold trigger than the same room in a dry one, and a pest with a known seasonal push gets a lower card trigger during its window. Review the thresholds on a cadence (quarterly is reasonable for most facilities) and after any failed or near-miss compliance test, because a near miss is the clearest signal that your internal trigger was set too close to the state limit. A living threshold table is a sign of an active program; a frozen one is a sign no one is reading the data it produces.
Intervention layer: biocontrols first, chemistry second
When a threshold is crossed, the order of operations is biocontrols first, then chemistry, because biocontrols preserve the room's balance and leave no residue on the crop. A biocontrol release schedule names the beneficial species, the release rate, the target pest, and the timing relative to the pest's lifecycle, and it runs preventively in many facilities rather than only reactively. When biocontrols are insufficient (a population outrunning the beneficials, or a pathogen biocontrols do not address), the protocol escalates to chemical intervention under a strict rule: read the label before you choose the product.
The biocontrol schedule earns its place because it is proactive by design. Preventive releases keep a standing population of beneficials in the room so a pest introduction meets resistance immediately, rather than being discovered at a threshold and chased after it has established. Writing the schedule into the protocol (which species, what rate, which rooms, how often) makes it a routine a crew executes, not a decision you relitigate each week. The escalation rule is the other half: define, in advance, what "biocontrols are losing" looks like as a number, so the move to chemistry is triggered by data rather than by panic when someone notices the canopy is in trouble.
The escalation to chemistry is also where discipline protects the crop and the license at once. Chemistry used too eagerly can disrupt the biocontrol population you are paying to maintain, and chemistry used off-label is a compliance exposure, so the protocol gates it behind both a crossed threshold and a label check. For surfaces and air, that chemistry is frequently the ClO2 line, and the lane discipline below keeps each product on its labeled job.
That rule is where EPA compliance lives, and it belongs in the body of your protocol, not a footnote. Every registered product's label defines what it may be used on, and some product classes carry a restriction you must respect. Where chlorine dioxide (ClO2) fits an IPM protocol is in surface sanitation between cycles, in certain water-system and area treatments, and in air quality, and the ProKure ClO2 line draws the lanes you have to keep straight. ProKure V is an EPA-registered liquid surface disinfectant (EPA Reg. No. 87508-3-89334), used at 100 ppm with a 10-minute exposure time on hard, non-porous surfaces, and it is suitable for use with plants in the room because it treats surfaces, not the crop. ProKure G is a fast-release ClO2 gas deodorizer (EPA Reg. No. 87508-2-89334) that works in a cleared, empty room in 4 to 6 hours and carries the label restriction "Not for use with/on plants/crops/feed." ProKure D is a slow-release ClO2 gas that improves air quality and controls odors for up to 30 days and runs with plants in the room, with no kill claim, and it is not an EPA-registered product. For the chemistry behind ClO2, see the chlorine dioxide for cannabis cultivation guide; to buy, route to shop.groclarity.com and pull labels and SDS from prokuresolutions.com. The protocol discipline is simple: V for surfaces around plants, G only in a cleared room, D for in-room air, and the label governs each.
Verification and logging: your audit trail
The layer that separates a head grower who manages pests from one who can prove it is verification and logging. Every intervention gets a log entry, and the fields are specific: date, room, the pest or pathogen and its count or reading, the action taken, the product used with its SKU and EPA registration number, the applicator, the PPE worn, the re-entry interval observed, and the verification result. That last field matters: an intervention is not closed until a follow-up scouting reading or a lab test confirms it worked.
Third-party lab verification runs on its own cadence across air, surface, water, and tissue, and it is the data that answers an owner's and an auditor's questions at once. When a state auditor asks what you did about mold, the answer is not "we clean regularly," it is a log that ties a room and a date to a registered product, a documented use consistent with its label, and a verification test. That is the audit trail the head grower persona is most often missing, and building it into the protocol, rather than reconstructing it after a positive test, is the whole point of writing the thresholds and log fields down in advance.
The logging format matters less than the fact that it is consistent and complete. A spreadsheet row per intervention, a bound log, or a platform record all work, as long as every field is filled every time and the record is retrievable by room and date. The field that growers most often drop is the EPA registration number of the product used, which is exactly the field an auditor keys on, because it ties the action to a registered, label-governed product rather than to an unspecified cleaner. Capturing the SKU and registration number at the moment of application, not from memory later, is the small habit that makes the whole log defensible.
Verification closes the loop that makes the protocol a system rather than a list of good intentions. An intervention without a follow-up reading is a hope; an intervention with a confirming scout count or lab result is a fact you can stand behind. Over a few cycles, the accumulated log also becomes a planning tool: it shows you which rooms recur as problems, which interventions actually moved the number, and where prevention is failing often enough to warrant a fix upstream. A head grower who reviews the log quarterly is running IPM; one who only opens it when an auditor asks is storing paperwork.
Standardizing this protocol across multiple facilities
If you are a cultivation director running this across several facilities in different states, the protocol spine stays the same while two things vary: the state TYM thresholds that set your action triggers, and the state pesticide lists that govern which products you may use. The standardization move is to hold the structure constant (same five layers, same log fields, same scouting cadence) and localize only the threshold numbers and the approved-product list per state. The deeper multi-state rollout tradeoffs, including who owns the SOP and how you keep versions aligned, live in the MSO standardized sanitation SOP guide. For a single facility, ignore this section; for a footprint, it is the difference between one defensible standard and a different improvised protocol in every state.
The payoff of standardizing the structure while localizing the numbers is that an auditor in any state sees the same recognizable program, and a cultivation director can read any facility's log without relearning a new format. It also makes training portable: a scout trained at one site can execute the cadence at another, because the layers and log fields are identical even where the threshold values differ. The common mistake is to let each site drift into its own protocol because its state rules differ, which produces five programs no one can compare; the discipline is to change only the two things that genuinely must change per state (the TYM-derived triggers and the permitted-product list) and freeze everything else. Where the ClO2 line fits that is helpful here too, because ProKure V, G, and D carry federal EPA registrations that read the same in every state, so the product lane discipline (V for surfaces around plants, G for a cleared room, D for in-room air) travels unchanged while only the state's broader permitted-product list varies around it.
Related resources


