Last updated:
I brewed for three years without keeping proper records, and I regret it. When a batch turned out exceptionally well, I couldn’t reliably reproduce it because I didn’t know whether the improvement came from the grain adjustment, the different yeast strain, the lower mash temperature, or the fact that I’d taken better water chemistry notes that day. A digital fermentation logbook doesn’t need to be complicated, the goal is capturing enough information that you can reproduce a success and diagnose a failure. Here’s how to set up a system that actually gets used, because a perfect logbook template that you fill in twice and abandon is worthless.
What to record at minimum
- Recipe snapshot: Grain bill (name, weight, PPG), hop schedule (name, oz, AA%, time), yeast strain and pitch rate, water chemistry additions. This is the “what I intended” record.
- Measured process data: Pre-boil gravity, OG, FG, mash temperature, mash pH, boil duration, post-boil volume. This is the “what actually happened” record. Comparing these two reveals your system’s systematic deviations.
- Fermentation log: Pitch date, pitch temperature, fermentation temperature range, dry hop date and duration (if applicable), packaging date, carbonation method.
- Tasting notes: Date of tasting, aroma (describe what you smell, citrus, stone fruit, biscuit, earthy), flavor (bitterness level, malt character, finish), clarity, carbonation level, overall rating 1–10. Record tasting notes at 1 week, 4 weeks, and 8 weeks if the beer lasts, carbonation and conditioning change the character significantly over this window.
Platform options
Brewfather (recommended)
Brewfather’s batch log feature covers all the minimum fields above and links each batch to the recipe used. Adding measured OG, FG, and tasting notes to a batch record takes 2 minutes. The batch history view shows all batches in chronological order with calculated efficiency, ABV, and recipe used, a scannable record of your brewing history. The free tier includes full batch logging. This is the lowest-friction digital logbook for brewers who already use Brewfather for recipes.
Notion database
A Notion database with one entry per batch allows richer documentation than Brewfather’s structured fields, long-form notes, photos of the finished beer, links to the Brewfather recipe, ingredient supplier notes, and tasting event records all fit in Notion’s flexible block format. The database view provides filtered and sorted access to batch records (filter by yeast strain, sort by rating, group by style). Best for brewers who want detailed qualitative documentation alongside the quantitative data. A Notion brewing template is available from the Notion template gallery as a starting point.
Google Sheets
A Google Sheets logbook is the most flexible option and works well for brewers who want custom analysis (charting efficiency over time, correlating mash temperature with FG, tracking ingredient cost per batch). The limitation is friction, entering data in a spreadsheet takes more steps than a purpose-built app. Use Sheets if you want quantitative analysis that brewing apps don’t provide; use Brewfather or Notion for everything else.
Making record-keeping a habit
The most common reason logbooks fail: they require too many steps on brew day when attention is elsewhere. The fix is to record data at the moment it’s available rather than all at once. Take the OG reading and enter it in Brewfather immediately; record the mash pH when you measure it; set a phone reminder to add tasting notes 4 weeks after packaging. Distribute the data entry across brew day and beyond rather than attempting a complete record at the end when you’re tired and some numbers are already forgotten.
Common Questions
How do I use logbook data to improve my beer systematically?
After 10+ batches with consistent data recording, patterns become visible. Efficiency analysis: if your mash efficiency is consistently 68% but recipes assume 75%, you need to add more grain or adjust your mill gap. FG analysis: if multiple batches finish 4–6 points above target FG, the cause is likely mash temperature too high (less fermentable wort), underpitching yeast, or fermentation temperature too low. Recipe iteration: compare tasting notes across versions of the same recipe to identify which changes improved the beer. The process improvement from data isn’t automatic, it requires looking at the numbers and asking “why is this value consistently off?” But you can’t ask that question without the data. Six months of consistent logging provides more actionable insight into your specific system than any general brewing guide.
