A mushroom grow log is a dated record of substrate preparation, inoculation, environmental conditions, and harvest outcomes for each batch you grow. It’s not optional busywork—it’s how you learn what works in your space, troubleshoot failures, and build reproducible results. At Adi’s Urban Mushrooms, we treat the grow log as the foundation of small-batch cultivation, whether you’re growing for yourself or supplying local restaurants.
Why a grow log matters more than you might think
Mushroom growing is biology in action, which means every variable—temperature, humidity, substrate moisture, spawn ratio, light, air exchange—affects your outcome. Without a log, you’re guessing. If a batch fails, you won’t know whether it was the substrate batch, the timing, contamination in your technique, or something about your growing space that season. If a batch succeeds spectacularly, you won’t be able to repeat it.
A grow log is your laboratory notebook. It’s especially critical if you’re growing small-batch for local supply—restaurants and customers expect consistency. The restaurants we work with at West Norwood Feast and South London Mushroom Club understand this: they want to know not just that we grew oysters or shiitake this week, but that we can grow them reliably next month. The grow log is what makes that promise credible.
What information should go into every grow log entry
Start with the basics: batch name or code, mushroom species or strain, the date you prepared the substrate, and the date you inoculated. Include the substrate composition by weight or volume (straw weight, sawdust type and amount, any additives). Record the spawn source, spawn weight, and spawn-to-substrate ratio. Note the container type and size. This foundation data is what lets you scale or troubleshoot later.
Then add the environmental and timeline observations. Record temperature during colonisation, humidity levels during fruiting, hours of light exposure per day, and air exchange frequency or method. Log the date you first saw pins (primordia), the date of first harvest, total yield in weight, and the number of flushes you achieved. If contamination appeared, describe it (green mould, bacterial blotch, competitor fungus) and note when. If the batch stalled or failed, record your hypothesis about why.
Include sensory notes too: colour, size, texture, smell, and how the mushrooms performed in the kitchen. Did they hold their texture when cooked? How did they taste? Did the restaurant come back for more? These observations connect cultivation to real use and help you decide whether to repeat a strain or adjust your approach. A grow log that only records data points is useful; one that includes flavour and performance context is invaluable.
Format: digital, paper, or hybrid
You can keep a grow log in a spreadsheet (Google Sheets or Excel), a notebook, a shared document, or a dedicated app. The format matters less than consistency and access. Many growers we work with at the Community Mycology Lab, Remakery Brixton use a paper notebook on site so they can jot notes immediately, then photograph or type up summaries weekly. Others use a spreadsheet that lives on their phone so they can log data in real time and pull reports later.
The advantage of digital is searchability and analysis: you can filter by species, substrate type, or season to spot patterns. The advantage of paper is simplicity and no screen-squinting in a humid growing space. The hybrid approach—handwritten notes on site, typed into a spreadsheet weekly—works well for small-scale cultivators. What matters is that you record enough detail to learn from each batch and communicate your methods to others. If you’re running workshops or selling to restaurants, a clear, organized log also demonstrates rigour and builds trust.
How to use your grow log to improve
Review your logs every few months. Look for patterns: Which substrates yielded best? Which batches had the fastest colonisation? Which environmental conditions correlated with the largest flushes? Which species performed best in your space, given your temperature and humidity ranges? At Adi’s Urban Mushrooms, I use these patterns to decide what to scale, what to retire, and what to experiment with next.
A grow log also helps you teach. If you run cultivation workshops or corporate events, a real, honest log—including failures—is far more educational than a polished success story. People learn more from ‘we tried this substrate, it contaminated, here’s why we think it happened, and here’s what we did differently next time’ than from ‘we grew perfect mushrooms.’ Your log becomes proof that cultivation is learnable, iterative, and grounded in observation, not luck.
If you’re troubleshooting a persistent problem—slow colonisation, weak flushes, mould appearing at a certain stage—your logs let you compare problem batches to successful ones side by side. That comparison is how you isolate the variable. It’s also why growing the same species across multiple batches is worth the effort: variation in the data helps you see signal through noise.
Grow logs for different scales and purposes
Home growers keeping a grow kit log might record just substrate prep date, inoculation date, first pin date, harvest date, yield, and one sentence about how the mushrooms tasted. That’s enough. Small-batch producers supplying markets or restaurants should add temperature and humidity ranges, spawn source and ratio, contamination notes, and performance notes (shelf life, texture, restaurant feedback). This level of detail protects your reputation and helps you diagnose problems quickly.
If you’re running a cultivation workshop or teaching at community spaces like the South London Mushroom Club, your logs become teaching material. Include photos at key stages (inoculated substrate, colonisation progress, pin set, harvest). Write notes in plain English, not jargon. A beginner looking at your log should understand not just what you did, but why. This kind of transparency is part of what makes education real.
Getting started with your own log
Begin with your next batch. Set up a simple template: date, species, substrate composition, spawn details, container, expected colonisation timeline. Then commit to adding one entry every few days during colonisation and fruiting, and a final summary after harvest. Don’t aim for perfection; aim for honesty and completeness. If you forgot to measure humidity, write that down. If you made a guess about spawn ratio, note it. The log’s job is to reflect your actual practice, not an imagined ideal.
After three or four batches, you’ll notice what information you wish you’d recorded and what you never actually use. Refine your template. Share a log with a friend or fellow grower; their questions will highlight what’s missing. If you’re interested in formalising your practice or learning grow-log methods in person, Adi’s Urban Mushrooms runs cultivation workshops where we discuss record-keeping as part of building sustainable, repeatable growing practice. A good grow log turns curiosity into knowledge.