How to Track Beer Fermentation: From Paper Logs to Software Automation

Fermentation is where the most critical — and most variable — phase of brewing happens. Temperature swings during the first 72 hours directly affect ester production. An early stall in gravity drop can indicate unhealthy yeast or contamination. A pH deviation might signal a water chemistry problem you'll repeat in the next batch if you don't catch it.

Experienced brewers develop intuition for these patterns. But intuition doesn't scale, doesn't transfer to new staff, and doesn't generate the searchable records that identify slowly drifting problems before they become customer complaints.

What to Track During Fermentation

Not every measurement needs to be taken at every interval, but the following form the core of a useful fermentation log:

Gravity (OG → FG)

Original gravity before pitching, then regular readings (every 24-48 hours initially, then daily as fermentation slows) to track the gravity curve. The final gravity tells you when fermentation is complete. The shape of the curve tells you about yeast health and fermentation speed.

Temperature

The single most impactful variable in fermentation character. For lagers, even a 1°C deviation during the first few days can noticeably affect the final beer. For ales, the target range is wider but still matters. Log the actual temperature, not just the setpoint — they're often different.

pH

pH naturally drops during fermentation as yeast produces CO₂ and organic acids. Tracking it helps identify contamination (sharp, unexpected pH drop), stuck fermentation, and water chemistry variations across batches.

Visual and Sensory Notes

Krausen activity, color, clarity, aroma — these qualitative observations often catch problems before measurements do. A sulfur smell on day 2 isn't necessarily a problem; the same smell on day 8 is. These observations need timestamps to be useful.

Dissolved Oxygen (at packaging)

If you have the equipment, DO readings at transfer and packaging are critical for shelf life. This is more relevant for canned/bottled product than draft, but worth logging either way.

The Problem With Paper Logs

Paper fermentation logs work fine at 2-3 batches per month. They break at scale for specific, practical reasons:

Not searchable. "What was the OG on the February batch of Red IPA?" becomes a 20-minute notebook hunt. With 10+ active batches, this happens multiple times per week.

Not comparable. You want to compare fermentation curves across 12 batches of the same recipe to understand whether your process is drifting. On paper, this requires manual transcription. In software, it's a query.

Not portable. Your brewer knows where the notebook is. Your quality manager, owner, and sales team don't have easy access. This slows decision-making ("Is batch 47 ready? Let me go check the notebook").

Lost or damaged. Breweries are wet, hot, and busy. Notebooks get wet. Pages tear. This is a real data loss risk for records you may need for compliance years later.

What Software-Based Fermentation Tracking Adds

Structured Data That Can Be Analyzed

When fermentation readings are logged in a database, you can run queries across batches. Compare all batches of a recipe to find outliers. Plot temperature against final gravity across your last 50 batches. Identify which batches were slow fermenters and what they had in common.

This is the kind of analysis that separates systematic quality improvement from anecdote-based brewing.

Early Warning Systems

When you have historical data on normal gravity drop curves, you can recognize when a current batch is deviating. A batch that should hit 1.010 FG by day 5 but is sitting at 1.018 on day 6 needs attention. Software makes this comparison automatic rather than requiring the brewer to remember what's normal.

Staff Training and Process Documentation

When your fermentation process is documented in software — with targets, actual readings, and notes on interventions — a new brewer can follow the process without the institutional knowledge that lives in one person's head. This is critical for scaling and for consistency during staff turnover.

Compliance Documentation

For TTB reporting in the US, food safety audits, or simply good record-keeping, having timestamped fermentation records in a searchable system is significantly better than paper notebooks.

Implementing Fermentation Tracking in Software

The transition from paper to software doesn't need to be a sudden switch. Most breweries do it in stages:

1. Week 1-2: Set up batch templates in the software with your target parameters (OG, FG, temperature schedule)
2. Week 2-4: Start logging new batches in software; keep paper as a backup for the first few batches
3. Month 2: Stop using paper; use software exclusively
4. Month 3+: Start using historical data for comparison and quality analysis

The first two weeks are the hardest — staff habits take time to change. Friction is low if the software is accessible from the brewery floor (mobile or tablet-friendly interface).

Practical Setup in BrewERP

In BrewERP, fermentation tracking is integrated into the batch record. When you create a brew batch and move it to FERMENTATION status, the fermentation log becomes active. You can add readings for temperature, gravity, pH, dissolved O₂, CO₂ volume, turbidity, and free-text notes.

Each reading is timestamped and associated with the batch and the user who logged it. Readings are visible on the batch detail screen and in the QC module where you can compare across batches.

The batch also tracks who performed each QC check, making it clear who to ask when something looks unusual in the historical data.

The ROI of Better Fermentation Tracking

Let's be concrete about what better tracking is worth:

• Catching a stuck fermentation 24 hours earlier: Saves potential batch loss or off-flavor — value of one batch at typical 500L yield and $2.50/L wholesale = $1,250
• Identifying a recurring process problem: A brewery found that their Day 3 temperature was consistently 2°C above target (due to a glycol chiller issue). Fixing it improved ester levels and consistency across all subsequent batches of one recipe — affecting 6-8 batches/month
• Reducing staff dependency: When process knowledge lives in the system rather than in one brewer's head, turnover becomes far less disruptive

The investment is low: 3-5 minutes per reading, once or twice per day per tank. The return is a brewery that improves systematically rather than by gut feel.

Where to Start

If you're still logging fermentation on paper or in spreadsheets, the first step is to pick a system and run a pilot for 30 days with one or two batches. The comparison between your old and new records after a month will tell you everything you need to know about whether the switch is worth making permanently.

BrewERP's 14-day free trial includes a demo brewery with sample batches and fermentation data, so you can see what the logs look like before committing to entering your own data.