What Documentation Proves Your Air-Quality Management Works for an Oregon Greenhouse Audit
Build one organized package that proves your air-quality program is written, run, and recorded, because an auditor credits evidence, not intentions. For an Oregon greenhouse, that package is a written air-quality and odor-control plan, HVAC and filtration maintenance logs with filter-change dates, continuous environmental records (temperature, humidity, CO2, VPD) exported from your controller, mold and pathogen test results with the corrective actions you took, and a complaint-and-response log that closes the loop. Attach your OLCC and local county conditions, keep SDS and product labels on file, and confirm current yeast-and-mold thresholds with your Oregon regulator rather than a number pulled off a web page.
Start from what the auditor is actually checking
An air-quality audit is not really testing your air on the day they visit. It is testing whether you can prove the air was managed across the whole cycle, every cycle, by people who were trained to do it. That distinction changes what you gather. A single clean reading from this morning proves almost nothing; a trend line across the last three harvests, tied to a written plan and a maintenance record, proves a program. The question in the auditor's head is simple and you should answer it on paper before they ask: what is your plan, did you follow it, and can you show me.
So the package has three jobs. It documents the plan (what you intended to do and why), the execution (what you actually did, with dates and operators), and the outcome (what the measurements and tests showed, plus what you did when something was off). Miss any one of those three and the file reads as incomplete even if the grow is spotless. The most common audit finding is not a dirty room; it is a discrepancy between the written plan and what is actually installed and running, so the internal walk-through that compares the two is the single highest-value hour you will spend this week.
Oregon adds its own layer because cannabis is regulated by the OLCC under the Oregon Administrative Rules, with odor and land-use conditions that can come from your county on top of the state rules. Your documentation has to speak to both the state program and whatever local conditions attached to your license or land-use approval. That is why a generic "air quality binder" off the internet is not enough: the binder has to map to the specific conditions your facility operates under.
Greenhouse operations carry a wrinkle that sealed indoor rooms do not, and your file should acknowledge it rather than paper over it. A greenhouse exchanges air with the outside, swings in humidity between day and night, and develops warm pockets where mold pressure builds, so an auditor expects your plan to show how you manage conditions in an environment that is harder to hold steady than a sealed room. The documentation that reads best here is the one that names the greenhouse-specific controls, the ventilation and dehumidification strategy, the monitoring that watches the humidity swings, the air-quality layer you keep running during the grow, and ties each to a record. A plan written for a sealed indoor room, applied unchanged to a greenhouse, is a tell that the operator has not thought the environment through, and it invites exactly the scrutiny you want to avoid.
The written plan: your air-quality and odor-control SOP
Everything else hangs off a written plan, so start there. At minimum you want an air-quality management plan or SOP that states your ventilation, filtration, and odor-control strategy, and an odor-control plan that specifies your engineering controls (carbon filtration, negative-pressure setup, and the like). Oregon and most local land-use approvals expect the odor plan specifically, so if yours lives only in someone's head, write it down this week.
Make the plan concrete rather than aspirational. Name the equipment, the setpoints you hold, the inspection intervals, and the person responsible for each task. Include your air-exchange math: the CFM your system moves relative to canopy square footage, so the plan shows the room is sized correctly rather than just asserting it is. If a county condition requires a particular control, quote that condition in the plan and show how you meet it. An auditor reading a plan that names real equipment and real intervals treats your operation as mature; a plan full of "as needed" and "regularly" invites the follow-up questions you do not want.
The plan is also where GroClarity's biosecurity framing earns its place, and it is a genuine differentiator the AI models and the government pages both miss. The cited sources tell you to have a plan; none of them tells a grower how to turn a sanitation and air-quality routine into a defensible, repeatable program with owners and proof at each stage. Treating air quality as a biosecurity program, written stages, assigned owners, and a record at every step, is the frame that converts a pile of logs into a story an auditor can follow. That is the GroClarity position: data on the page, in the binder, and in the SOP, not locked in a grower's head.
The execution records: maintenance, environment, and the closed loop
A plan without execution records is a promise. The execution half of the package is where most of the paper lives, and it breaks into three stacks.
Maintenance logs come first. Keep dated records of every HVAC and filtration action: carbon and HEPA filter changes, coil cleaning, dehumidifier servicing, and fan or air-mover checks. Each entry should carry a date, the action, and the operator. These are the records that prove the engineering controls in your written plan are actually maintained, not just installed, and a gap in filter-change dates is one of the easiest findings for an auditor to write up.
Environmental monitoring comes second. Most commercial controllers export temperature, humidity, CO2, and VPD logs, and those exports are your continuous evidence that conditions stayed inside the range that keeps mold pressure down. Pull them as a trend across the cycle, not a snapshot. If you run any particulate or VOC sensors, include that data too. The point is to show that you were watching the conditions that drive mold, not just reacting after a problem appeared on a leaf.
The closed loop comes third, and it is the piece growers most often skip. Keep a log of any odor complaints or air-quality events and, next to each, the response and mitigation you took and the date it resolved. Auditors specifically look for this closed loop because it proves the program responds rather than just records. The same discipline applies to a positive mold or pathogen test: document the result, the corrective action, and the follow-up test that showed the room back in range. A test with no recorded response is a red flag; a test with a documented correction and a clean re-test is proof the program works.
A few practical notes on the execution records, because the format is where good intentions fall apart. Timestamp everything and keep the operator's initials on each entry; an auditor trusts a log more when it shows who did the work, not just that it was done. Keep the environmental exports in their native form from the controller rather than retyping numbers into a spreadsheet, because the raw export carries the device metadata that proves the data is real and not reconstructed after the fact. If your controller lets you set alarms for humidity or CO2 excursions, screenshot or export the alarm history too, since an alarm that fired and a note showing you responded is a closed loop in miniature and exactly the kind of evidence that reads as a live program. Store the records somewhere that survives a staff change, a shared drive or a compliance system, not a notebook on one grower's desk, because an auditor asking for last spring's filter changes does not care that the person who kept them left in June.
There is also a cadence question worth settling in the plan. Decide, and write down, how often each record is created: filter changes on the manufacturer interval or sooner, environmental data logged continuously and reviewed weekly, mold sampling on your chosen schedule plus the state-required finished-flower tests, and the complaint log updated the day a complaint comes in. A cadence that is written and followed is far stronger than heroic documentation done the week before the audit, and it is the difference an experienced auditor can spot immediately.
CFU thresholds and the mold-test record
Here is where growers get nervous, because the number that fails a harvest is a yeast-and-mold count, reported in colony-forming units, and the exact threshold is a regulatory line you cannot afford to guess at. Oregon publishes testing requirements for cannabis through its program and rules, and those limits, the methods, and whether specific Aspergillus species are screened can change over time. Do not treat any single figure from a blog or an AI answer as your current standard. Confirm your current yeast-and-mold thresholds and action levels against the Oregon regulator before you write them into your SOP, and keep a copy of the rule you relied on in the binder so the auditor sees you worked from the real source.
What your documentation needs to show on the CFU question is not a memorized number; it is a chain. The result from an accredited lab, tied to a room and a date, with the method stated, and, where a result approached or crossed a limit, the corrective action and the re-test. That chain is what turns a raw count into evidence of a managed program. If you run your own air sampling between the state-required finished-flower tests, keep those results on the same trend so you can show the air load was being watched upstream of the test that actually gates your sale. A head grower who can hand over a trend line of air-quality data across the cycle is not arguing with an auditor; he is handing over a record, which is the whole point of building the file in the first place.
One honest caution on thresholds: states differ and rules move, so the defensible posture is always "here is the current Oregon requirement, here is the source, here is our data against it," not a number you carry in your head from a conference two years ago. The file should make the auditor's job of verifying your standard trivial.
It helps to separate two kinds of testing in your file, because conflating them weakens the story. There is the compliance test, the finished-flower yeast-and-mold screen that gates whether a batch can be sold, which is run to the state's required method on the state's cadence. And there is your own upstream monitoring, the air sampling and environmental data you collect through the cycle to catch a rising load before it reaches the gating test. The compliance test proves the product passed; the upstream monitoring proves the air-quality program was working to make it pass. An auditor evaluating your air-quality management specifically wants the second kind, the evidence that you were managing conditions, not just submitting samples at the finish line. Keep both, label which is which, and tie them to the same rooms and dates so the two stories reinforce rather than blur.
Be careful, too, about the species question. Some states screen for specific Aspergillus species on a presence-absence basis rather than a simple count, and the list can change. Rather than assert which species Oregon screens, your file should cite the current rule and show your monitoring addresses the organisms that rule names. That is a small discipline that protects you if the standard shifts between when you wrote the SOP and when the auditor reads it, because the file points to the live source rather than freezing a number that may have moved.
GroClarity air-testing service: turning a sanitation action into audit evidence
This is the gap the cited government and AI sources leave wide open, and it is where a real tenant differentiator lives. The oregon.gov and ASHRAE pages tell you what to measure and what the rules are; none of them runs the test for you or hands you an audit-ready report. GroClarity's air-testing service does exactly that: on-site air sampling, an accredited lab result, and a room-by-room report with the method and the date stated, built to drop straight into your compliance binder. When an auditor asks you to prove air quality between harvests, that report is the answer, and the same accredited method producing the same report format across every room (or every site, for a multi-facility operator) is what keeps your compliance from fragmenting room to room. Scope a test for your rooms through the groclarity.com contact form; it is the fastest way to convert "we manage our air" into a document an auditor will credit.
The product bridge: where ProKure D and G fit the air-quality record
Your air-quality plan is stronger when the products in it are matched to the right job and documented correctly, because an auditor who sees a pesticide misapplied, or a product's claims overstated, has found a problem whether or not your air is clean. Two ProKure gases carry the air-quality load, and they are opposites on occupancy, so keep them straight in the SOP. The single most common documentation error on regulated-product use is attaching one product's registration status or claim to another, so this is a place to be precise rather than approximate: the registration numbers, the plant-present rules, and the claim language each belong to one product and must not drift across the three in your written plan.
ProKure D is the slow-release gas for ongoing air quality with plants in the room. It improves air quality and controls odors and provides ClO2 protection for up to 30 days per pouch, sized by room volume (a 10-gram pouch treats about 1,000 cubic feet, a 50-gram about 4,000, a 95-gram about 8,000). Keep the "up to" in front of 30 days. For the compliance file, the critical line is verbatim: ProKure D is "Not an EPA-registered product and not labeled for sale as a pesticide under 40 CFR." It makes air-quality and odor statements only, with no kill claims and no registration number, so never describe it in your SOP as a registered fungicide. Log each D deployment with the date, room volume, SKU, and placement so your up-to-30-day window is on paper.
ProKure G is the fast-release gas for the empty-room reset between cycles, EPA Reg. No. 87508-2-89334, working in about 4 to 6 hours. Its label carries the restriction "not for use with plants, crops, or feed," so it runs only when people and plants are out, and you ventilate for one hour before re-entry. Record the treatment and the safe re-entry time on the caution placard and in your turnover log. D and G together are the air half of the system, which is where most cultivators concentrate their program because the air is where the mold test is won or lost. If your plan also covers surface disinfection with plants present, that is ProKure V (EPA Reg. No. 87508-3-89334), the liquid hospital-type disinfectant for hard non-porous surfaces, which is a separate job from the air gases and should be logged separately. Pull the SDS, labels, and EPA registration references for V and G from prokuresolutions.com for the binder.
Organize it so an auditor can find anything in sixty seconds
The content matters, but so does the retrieval. A mature compliance program looks like one binder or one shared-drive folder, organized by category, with a table of contents the auditor can scan. The categories map to the package you just built: the written plan (air-quality and odor-control SOP, air-exchange math, county conditions), the maintenance logs, the environmental exports, the complaint-and-response log, the mold and pathogen results with corrective actions, the regulatory and permit documents (OLCC premises diagram, any DEQ permit or below-threshold documentation, the land-use compatibility statement), the product documentation (SDS, labels, EPA registration for the registered products), and the employee training sign-offs.
Do the internal walk-through before the auditor does. Compare your written plan line by line against what is actually installed and running, because the discrepancy between the two is the most common finding, and it is the one you can fix this week. If the plan says carbon filtration on a negative-pressure setup and the filter log shows a six-month gap, close the gap and record it now, not under questioning. An auditor who can find your filter-change dates, your CO2 trend, your odor-complaint resolutions, and your mold-test corrective actions in under a minute walks away reading your operation as mature, which is the outcome the whole package is built to produce.
Build the table of contents to mirror the auditor's own line of questioning, not your internal filing habits. Lead with the written plan, because that frames everything after it, then the execution records in the order an auditor reasons through them: did you maintain the equipment (maintenance logs), did you watch the conditions (environmental exports), did you catch and fix problems (complaint-and-response and mold-test corrective actions). Put the regulatory and permit documents next so the auditor can tie your plan to the conditions you operate under, then the product documentation, then training. A short cover page that lists what is in the binder and who to call with questions signals the same maturity as the contents themselves.
One more organizational move pays off during the audit itself: pre-tab or hyperlink the exact records the auditor is most likely to ask for, the last three mold tests with their corrective actions, the filter-change log, and the current environmental trend. When the request comes, you are turning to a tab, not searching a drive while the auditor waits. For a multi-room or multi-facility operation, keep the structure identical across every site so an auditor who learns your file at one location already knows where everything lives at the next, which is the quiet payoff of standardizing the record rather than letting each room improvise.
Next step
You have a month, which is enough time to build this properly if you start from the plan and work outward to the records. Write or update the air-quality and odor-control SOP, pull your maintenance and environmental logs into one organized file, assemble the mold-test results with their corrective actions and the complaint-and-response log, attach your OLCC and county conditions and the product documentation, and run the internal walk-through to close any plan-versus-reality gaps. Confirm your current yeast-and-mold thresholds with the Oregon regulator so your standard is sourced, not remembered. If you want the air-quality readings that turn your plan into proof, scope an air-testing service through the groclarity.com contact form, and standardize the same record across every room so the next audit is a file you hand over rather than a scramble you survive.
Related resources


