Specialty Mushroom Grow Room Monthly Contamination, CO₂ & Flush Yield Log

ContextTrichoderma, the green mold, is the most common specialty mushroom contaminant and spreads fast through shared air handling, so check every block, not just the ones that already look obviously sick. Black mold from Aspergillus species carries real respiratory health risk and warrants a dust mask before close inspection. Pink or pink-orange fuzzy growth is often Fusarium and tends to outcompete mycelium in oyster substrate specifically. Any of these spotted smaller than a quarter should be isolated and disposed of outside the grow room within the hour, since spores can become airborne and contaminate the entire flush within 48-72 hours.

ContextA healthy fruiting chamber smells earthy or faintly mushroomy. Anything sour or vinegar-like usually signals bacterial blotch or wet spot from overwatering, while a strong ammonia smell points to anaerobic substrate breakdown, often from compacted or oversaturated grain spawn. A rotten egg smell can indicate sulfur-reducing bacteria taking hold in waterlogged areas. Train your nose during this monthly check by smelling a known-healthy block first as a baseline, since contamination odors are easiest to catch in the first ten seconds before your nose adjusts.

ContextSqueeze a small substrate sample between your fingers; a few drops of water released is ideal, while a steady stream means overwatering that starves mycelium of oxygen and invites anaerobic bacteria. Look for dark, slimy, or compacted zones especially at the bottom of bags or blocks, where gravity pulls excess moisture and oxygen exchange is weakest. If more than 20% of a block shows these signs, the block is unlikely to recover a healthy flush and should be composted rather than risked for cross-contamination.

ContextHEPA or MERV-13 intake filters clogged with spore dust reduce airflow and create stagnant zones where contaminants thrive, so check filters monthly even if your maintenance schedule says otherwise during high-production months. A film of dust on fan blades reduces CFM output by as much as 30%, throwing off your CO2 exchange calculations even though the fan still sounds like it is running normally. Replace filters showing visible discoloration rather than waiting for a fixed replacement date, since spore load varies a lot month to month with flush timing.

ContextMove any block with visible contamination to a separate room or, at minimum, a sealed tote outside the main grow space within minutes of discovery, since every hour it sits in shared air increases spore load for neighboring blocks. Tag it with the date and suspected contaminant so you can track outcomes and refine your eye for identification over time. Do not open suspect bags inside the grow room to check how bad it is; this single mistake causes more cascading contamination events than almost any other handling error.

ContextCO2 stratifies in a grow room, with levels often 500-1,000 ppm higher near the floor than near the ceiling fans, so a single reading from one spot can be misleading. Take readings at low, mid, and high shelf positions and record all three rather than averaging them in your head. Healthy fruiting for most gourmet species wants below 1,000 ppm; oysters are a little more picky and should be kept below 800 PPM. Readings consistently above 2,000 ppm at any shelf level point to a dead zone needing better air circulation, not necessarily a faster FAE cycle.

ContextWrite down how many minutes per hour your exhaust fan runs and at what speed setting, since this is the variable most likely to drift unnoticed if a timer fails or a fan speed dial gets bumped. A FAE cycle that has silently dropped from ten minutes per hour to three minutes per hour will show up in your yield numbers as elongated stems and small caps weeks before anyone notices the timer is wrong, so this log entry is your early warning system.

ContextLong, thin stems with undersized caps, sometimes called CO2 legs, are a classic sign of elevated CO2 during pinning and primordia formation, even when ppm readings look acceptable later in the flush. Record the day pins first appear relative to your typical timeline for that strain, since a two to three day delay across multiple blocks at once usually points to an environmental cause like CO2 rather than a strain or substrate issue.

ContextIf you run a carbon scrubber or filtered exhaust line, check for spore and dust buildup that restricts airflow without making the fan sound any different, which is exactly the kind of silent failure this log is designed to catch. A partially clogged exhaust filter can cut effective CFM by half, meaning your FAE cycle runs on schedule but moves far less air than your calculations assume.

ContextUse a kitchen or shipping scale accurate to at least one gram and weigh each strain's harvest separately, even if multiple strains share a shelf, since lumping numbers together makes it impossible to spot a strain-specific decline later. Record weight immediately after harvest before any trimming, since trimmed weight varies by who is doing the trimming and introduces inconsistency into your historical comparisons.

ContextBiological efficiency equals wet mushroom weight divided by dry substrate weight, multiplied by 100. A healthy oyster flush typically lands between 75-150% BE, while lion's mane and shiitake often run lower at 40-80% depending on substrate formula. Tracking BE month over month, rather than raw yield alone, lets you separate a genuinely declining strain from a month where you simply ran fewer blocks.

ContextRecord the exact day count from substrate colonization completion to first visible pin, and from pin to harvest-ready cap, for each strain and substrate batch. A creeping increase of even two to three days across consecutive months, even without other visible symptoms, is often the earliest measurable signal of a slowly building environmental problem such as gradual CO2 drift or aging spawn stock.

ContextNote the spawn generation number and substrate mix batch for every block in the flush, since contamination or yield problems sometimes trace back to a specific batch of grain spawn or supplement rather than anything happening in the grow room itself. If you ever need to trace a recall-worthy contamination event back to its source, this single column in your log is what makes that possible instead of guesswork.

ContextAssign a simple grade like A, B, or C based on cap size uniformity, color consistency for the strain, and absence of any contamination on the fruiting body itself, since buyers and your own future planning both benefit from a quick quality signal that raw weight alone does not capture. A flush that hits target weight but grades C across the board due to small, discolored caps is telling you something different than a flush that hits the same weight with A-grade caps.

ContextCalculate the percentage of blocks lost to contamination this month and place it next to a rolling three-month average rather than judging any single month in isolation, since contamination rates naturally bounce around with seasonal humidity and spore load even in well-run rooms. A jump from a typical 3-5% loss rate to anything above 10% in one month is the threshold most experienced growers use to trigger a full sanitation review rather than dismissing it as bad luck.

ContextCross-reference weeks with elevated CO2 readings against weeks with higher contamination losses, since stagnant, CO2-heavy air often correlates with the same poor circulation that lets mold spores settle and establish rather than getting swept out by fresh air exchange. This pattern is easy to miss when CO2 and contamination data live in separate notebooks, which is exactly why this log keeps them on the same page.

ContextIf this month's contamination cluster traces back to a specific cause, such as a torn filter, a contaminated spawn batch, or a humidifier reservoir that was not cleaned, write the specific corrective action into your protocol document, not just into this month's log entry, so the fix outlives your memory of the incident. Protocols that only exist in someone's head get forgotten exactly when a new team member or a busy season causes a slip.

ContextPhotograph or scan the completed paper log and store it in a dated digital folder alongside your block photos, since a full year of monthly logs becomes a genuinely valuable dataset for spotting slow seasonal trends, like a contamination rate that creeps up every summer once humidity climbs outside. Keep at least one offline backup; growers who store cultivation records only in a single cloud app have lost years of yield history to account lockouts or app shutdowns.