A home brewing log is one of the simplest ways to make better beer, wine, cider, or mead. By recording your ingredients, measurements, timing, fermentation, and tasting notes, you can repeat successful batches and diagnose disappointing ones.
Why Keep a Home Brewing Log?
Brewing involves many variables: ingredient freshness, mash temperature, boil length, yeast health, fermentation temperature, water chemistry, sanitation, and packaging. Without notes, it is easy to remember the general recipe while forgetting the details that actually affected the result.
A log helps you:
- Reproduce a batch you enjoyed.
- Compare two batches made with similar recipes.
- Identify the likely cause of off-flavors or poor carbonation.
- Track improvements from one brew day to the next.
- Adjust recipes based on evidence instead of memory.
- Build a personal library of reliable recipes.
Your log does not need to be elaborate. A notebook, spreadsheet, brewing app, or printed worksheet can all work. The best system is the one you will use consistently, including on busy brew days.
Choose a Logging System
Start with one primary place for your records. Combining scraps of paper, phone notes, labels, and memory usually creates gaps.
Paper notebook
A notebook is inexpensive, works anywhere, and makes it easy to sketch equipment layouts or write quick observations. Choose one with durable covers and numbered pages. Keep a pen nearby, and write the batch name and date at the top of every page.
Paper is especially useful for recording information while brewing, but it can be harder to search later. Photographing completed pages gives you a basic backup.
Spreadsheet
A spreadsheet is useful if you want to compare batches, calculate efficiency, sort by style, or track costs. Create one sheet for batch summaries and another for detailed brew-day notes. Use consistent units and column names so entries remain comparable.
Brewing software or an app
Dedicated software can calculate original gravity, bitterness, color, mash water, and other estimates. It may also store ingredient inventories and recipe versions. However, software estimates are not a substitute for recording actual measurements and observations.
A hybrid method
Many brewers use a small notebook during the brew day and transfer the notes to a spreadsheet or app afterward. This is practical, provided the transfer happens before details are forgotten.
Create a Batch Header
Every entry should begin with enough information to identify the batch later. Use a unique batch number, especially if you brew frequently.
Record:
- Batch number.
- Date and start time.
- Beverage type and style.
- Recipe name and version.
- Planned batch size.
- Actual volume into the fermenter.
- Equipment used.
- Brewer or brewing location, if more than one person or setup is involved.
For example, a header might read: “Batch 2026-014 — American pale ale v3 — brewed September 23, 2026 — target 20 liters.” A clear naming system prevents confusion when several fermenters are active at once.
Also note whether the recipe is your own, adapted from another recipe, or based on a kit. If you changed an ingredient or process, record the change rather than treating it as the original recipe.
Record the Recipe as Planned
Before brewing, save the intended recipe. This creates a reference point for comparing the plan with reality.
Include:
- Grain, extract, sugar, fruit, spices, or other fermentables.
- Amount of each ingredient.
- Grain mill setting, if relevant.
- Hop varieties, amounts, alpha acids, and addition times.
- Yeast strain, package type, manufacture date, and starter details.
- Water source and planned water additions.
- Target mash temperature and duration.
- Target pre-boil and post-boil volumes.
- Target original gravity and final gravity.
- Target bitterness, color, alcohol level, and carbonation.
If you use a packaged ingredient, record the brand and lot number when practical. Ingredient names alone may not be enough to explain why a later batch tastes different.
Take Measurements During the Brew Day
The most valuable notes are often the ones written while the process is happening. Do not rely on filling in everything from memory at the end.
Record actual measurements alongside planned values. Useful checkpoints include:
- Strike-water volume and temperature.
- Mash-in temperature.
- Mash temperature at the start and end.
- Mash duration.
- First runnings gravity, if measured.
- Pre-boil volume and gravity.
- Boil start and end times.
- Hop or other additions and their exact timing.
- Post-boil volume and gravity.
- Cooling time and temperature at transfer.
- Final volume into the fermenter.
- Original gravity.
- Yeast pitch temperature.
Write down anything unexpected, such as a stuck sparge, a boil-over, a broken hydrometer, a delayed yeast pitch, or a change in flame intensity. These events may seem minor, but they can help explain a later difference in flavor or strength.
A compact comparison table can make this information easier to review:
| Checkpoint | Planned | Actual | Notes |
|---|---|---|---|
| Batch volume | 20 L | 18.5 L | More evaporation than expected |
| Pre-boil gravity | 1.044 | 1.041 | Mash efficiency lower |
| Boil time | 60 min | 65 min | Delayed hop addition |
| Original gravity | 1.050 | 1.053 | Concentrated wort |
| Pitch temperature | 18°C | 20°C | Chilled more slowly |
The goal is not to create perfect data. The goal is to make important differences visible.
Log Fermentation Carefully
Fermentation notes should continue for several days or weeks. Record the fermenter location, temperature, yeast activity, and gravity readings.
At minimum, note:
- Fermentation vessel and size.
- Yeast strain and pitch amount.
- Date and temperature of pitching.
- Temperature range during fermentation.
- When visible activity began.
- Date and reading of each gravity check.
- Any temperature changes or interventions.
- Dry-hop, fruit, spice, nutrient, or other additions.
- Date fermentation appeared complete.
- Final gravity and date of packaging.
A consistent temperature log is particularly helpful. If you do not have an automated controller, write down the approximate temperature at the same time each day. Record whether the reading came from a probe, strip, room thermometer, or another method.
Do not assume that bubbling proves fermentation is complete. Airlock activity can slow because of temperature changes or leaks. Use stable gravity readings and your normal process to determine when the batch is ready for packaging.
Document Packaging and Carbonation
Packaging notes often explain problems that are incorrectly blamed on the recipe or yeast.
Record the packaging date, vessel type, quantity packaged, and priming or carbonation method. For bottle conditioning, include the sugar type, total amount, calculation method, and approximate volume packaged. For kegging, record pressure, temperature, carbonation duration, and whether the beer was shaken, naturally carbonated, or force-carbonated without agitation.
Also note:
- Sanitizer used and whether it was mixed according to its instructions.
- Bottling wand, filler, keg, or tubing used.
- Headspace or fill level.
- Bottle or keg storage temperature.
- Date carbonation was first checked.
- Any leaks, foaming, sediment, or undercarbonation.
If you package multiple versions, label them clearly. For example, “Batch 014 keg,” “Batch 014 bottles with priming sugar,” and “Batch 014 dry-hopped” should be treated as separate package records.
Add Structured Tasting Notes
Taste the finished product at more than one stage. A sample immediately after packaging may not represent the final result, while a sample months later may show oxidation or other age-related changes.
For each tasting, record:
- Date and approximate age.
- Serving temperature.
- Appearance and clarity.
- Aroma.
- Flavor.
- Mouthfeel and carbonation.
- Finish.
- Overall impression.
- Specific strengths and problems.
- Whether you would brew it again.
Avoid writing only “good,” “bad,” or “not bad.” Use concrete descriptions such as “light citrus aroma,” “sharp bitterness,” “thin body,” “sweet finish,” “peppery yeast character,” or “carbonation still low.” Specific language makes future changes easier to choose.
Taste under reasonably consistent conditions when comparing batches. Use the same glassware when possible, pour similar serving sizes, and avoid evaluating right after strongly flavored food. You do not need formal judging vocabulary, but a consistent routine improves your comparisons.
Separate Observations from Conclusions
A useful log distinguishes what you observed from what you think caused it.
For example:
- Observation: “Final gravity was 1.018, higher than the target of 1.010.”
- Observation: “The beer tasted sweet and full-bodied.”
- Hypothesis: “The mash may have been hotter than recorded, or fermentation may have slowed because of temperature.”
- Next action: “Verify thermometer accuracy and monitor fermentation temperature more closely.”
This prevents a guess from becoming a false fact in your recipe history. Multiple causes can produce similar results, so treat explanations as hypotheses until later batches provide stronger evidence.
Use the Log to Improve the Next Batch
After tasting, write a short revision plan. Limit yourself to one or two major changes unless the batch had a serious process failure. Changing everything at once makes it difficult to learn which adjustment mattered.
Examples of focused changes include:
- Increase yeast quantity or improve yeast freshness.
- Reduce mash temperature to create a drier result.
- Adjust the boil length to reach the intended volume.
- Change one hop addition while keeping the grain bill constant.
- Extend conditioning time before judging carbonation.
- Improve temperature control during the first few days of fermentation.
Keep the rest of the process as consistent as possible. If the next batch improves, you have better evidence that the change helped.
Troubleshooting Common Logging Problems
You forget to write notes during brewing
Use a one-page checklist with large spaces for measurements. Set phone reminders for key fermentation checks, or use a voice memo when your hands are wet. Fill in clean details immediately after the brew day while the sequence is still fresh.
Your measurements do not seem consistent
Check units first. Mixing liters and gallons, Celsius and Fahrenheit, or specific gravity and degrees Plato can create apparent contradictions. Use one unit system or clearly label every value.
Also record the measurement method. Hydrometer readings are affected by temperature, while refractometer readings require correction after fermentation because alcohol changes the result.
Your notes are too detailed to maintain
Keep required fields short and mark optional fields separately. At minimum, capture ingredients, volumes, gravity, temperature, yeast, dates, and important problems. Add deeper notes only when something unusual happens.
You cannot remember which version was used
Assign a version number whenever you change a recipe. Save the recipe file with the batch number and date, and write the same identifier on the fermenter and packaging labels.
A bad batch has no obvious explanation
Review the timeline rather than focusing only on the recipe. Check ingredient storage, sanitation, oxygen exposure, fermentation temperature, pitch rate, packaging conditions, and tasting age. If several variables changed, plan a simpler follow-up batch that isolates one likely cause.
Store and Review Your Records
Back up digital records regularly and keep paper notebooks away from spills. Once or twice a year, review your batches and identify patterns: recurring fermentation temperatures, consistent efficiency, favorite yeast strains, or problems associated with particular equipment.
Create a short “known settings” page for your system. It might include typical evaporation rate, trub loss, fermenter loss, and actual brewhouse efficiency. These values help you set more realistic targets for future recipes.
A good brewing log does not need to be perfect or artistic. It needs to be dated, specific, and honest about what happened. When every batch leaves behind usable information, your brewing improves through repeatable decisions rather than guesswork.