Big River Homebrew
Brewing Basics

How to Keep a Homebrew Log You Can Use Next Time

Big River Homebrew · 2026-09-15 · 7 min read
How to Keep a Homebrew Log You Can Use Next Time
In briefKeep one record for each batch, linking the recipe version to what actually happened: ingredients used, dated observations, measurements with units, departures from the plan and questions still unresolved. Separate estimates from measurements. A completed log does not establish that beer is safe or ready to bottle. This guide is for adults of legal drinking age; follow local rules and obtain qualified brewing guidance when fermentation or packaging is uncertain.
Contents

What belongs in a useful homebrew log?

Keep one record for each batch, linking the recipe version to what actually happened: ingredients used, dated observations, measurements with units, departures from the plan and questions still unresolved. Separate estimates from measurements. A completed log does not establish that beer is safe or ready to bottle. This guide is for adults of legal drinking age; follow local rules and obtain qualified brewing guidance when fermentation or packaging is uncertain.

The purpose is retrieval. When you return to a batch later, you should be able to find its instructions, identify its ingredients and explain which details you actually recorded. You do not need a complicated app to do that.

The American Homebrewers Association recommends detailed brew-day notes when learning how a recipe behaves on your equipment. Our approach below turns that general advice into an original recordkeeping workflow. It is not a tested recipe or a substitute for equipment instructions.

How should you identify a batch before starting?

Give each batch a unique identifier. A plain label such as BR-01 works if you use it consistently on the record and associated files. A recipe name alone is insufficient when you brew it again: both batches might be called pale ale, but they have different histories.

At the top, record the recipe's title, author or supplier, version or retrieval date, and the intended batch size with its unit. Keep the actual recipe alongside the log. If the supplier later changes its online instructions, your notes should still identify the version you followed.

Use separate headings for planned and actual. Copying a recipe temperature into an observation box makes it look as though you measured it. Instead, leave the actual field blank until it is observed, or write “not recorded.” A blank is an honest limitation you can address next time.

Which format makes the record easiest to use?

A notebook, spreadsheet or simple text document can all hold the information. Choose whichever you can update without interrupting safe equipment handling. Put the record in a dry place away from hot vessels, chemical splashes and food-contact equipment; stop handling equipment before making a note.

Brewer's Friend provides an extract-recipe sheet with recipe and ingredient fields, expected statistics and a dated hydrometer section. Its linked PDF is a concrete example of separating a recipe plan from later readings. The sheet also prints process settings; those are not universal settings for your ingredients or instruments. Follow your own recipe and manufacturer instructions.

Our suggested file arrangement is deliberately small: one batch folder, the recipe copy, the working log, relevant label photographs and a short review. Name files by what they contain. “Yeast label” is more useful than an unexplained camera filename.

What should the working page contain?

Use this original outline as a starting point. Add a field only when you know what decision it will help you revisit.

Record area What to keep What to avoid
Identity Batch identifier and recipe version Reusing the same record for several batches
Ingredients Exact product, amount actually used and unit Replacing the label with a vague nickname
Equipment Vessel and measuring-instrument identities Assuming a replacement behaves identically
Events Date, time, action and observed result Reconstructing an entire day from memory
Measurements Value, unit, stage and method A number whose sampling point is unknown
Departures What changed, when and why Editing the original plan to conceal the change
Open questions Missing evidence and who can clarify it Writing an uncertain conclusion as a fact

Keep the measured amounts separate from package sizes. Purchasing a bag does not show how much entered the batch. Retain the full product name, and a lot or batch code if present, rather than trying to remember which similarly named ingredient you used.

Record substitutions plainly. If the shop supplied a different product, keep both the intended item and the replacement visible. The log records that decision; it does not establish that the substitution was suitable.

How do you make measurements comparable?

Name the stage before entering the number: water prepared, wort collected, liquid transferred or beer packaged. These are different quantities. A planned batch size is not a measurement of every vessel at every stage.

Keep the unit beside the value. If a recipe uses gallons, identify the gallon system; if it uses mass ounces, do not silently treat them as fluid ounces. Retain the original value whenever you make a conversion, together with the conversion used.

For a temperature, say what was measured and where. “Room,” “vessel exterior” and “sample” are different descriptions; a number without that context is difficult to compare. For an instrument requiring correction, retain the raw reading, applicable manufacturer guidance and corrected result as separate entries. Do not invent a correction to make a reading match the recipe.

The existing fermentation collection covers measurement topics. This log supplies a place to retain the evidence, rather than another set of instrument operating instructions.

What does a worked comparison look like?

Consider this hypothetical record. These numbers illustrate bookkeeping only; they are not a recipe, a yield target or observed results from our brewing.

Field Planned Recorded actual Difference
Transfer volume at the named stage 20 L 18 L 2 L below plan
Ingredient quantity for the specified addition 100 g 100 g No recorded difference

The volume calculation is 20 − 18 = 2 L. Relative to the planned volume, 2 ÷ 20 × 100 = 10% below plan. That arithmetic describes a discrepancy. It does not identify evaporation, a spill, retained liquid or a measurement error as the cause.

Write the next question beside the result: “Were both volumes measured at the same stage?” That question is better than immediately changing the recipe. Do not add water, sugar or another ingredient merely to make a log's numbers agree. Any process adjustment needs suitable recipe-specific guidance.

Where do cleaning and sanitizing records fit?

Link to a separate equipment-preparation checklist instead of burying it in tasting notes. Record the exact product and the directions followed, including preparation, application, required contact and rinse or drain status.

For example, Five Star's Star San instructions require cleaning first and make its no-rinse use conditional on the recommended dilution. “Sanitizer used” leaves out those conditions. Our cleaning-versus-sanitizing checklist explains the separate tasks.

Follow the current product label and equipment instructions, including protective equipment. Never combine chemical products. CDC warns that mixing bleach or disinfectants with other cleaners or disinfectants can release dangerous vapors. That is a mixing warning, not a brewing dilution formula.

Can the log tell you when to bottle?

It can preserve evidence, but a checked box cannot make the decision safe. Keep dated, stable and plausible gravity observations alongside the recipe-specific assessment of fermentation completion. Unexpected readings need qualified brewing guidance, even if they appear unchanged.

Brewer's Friend's priming calculator asks for the amount being packaged. Retain that actual beer volume, the verified calculation, sugar identity and measured quantity, plus the specified bottle and closure information. Do not substitute planned volume for actual volume in a calculation that requires the latter.

Home Brew Mart's kit manual, in its bottling section, explains that excess priming sugar can produce dangerous over-carbonation and exploding bottles. Unfinished fermentation also creates pressure risk. Use suitable, undamaged pressure-rated bottles and verified instructions; records do not remove that risk.

If bottles are suspect or bursting, keep people and pets away and obtain experienced safety guidance. Do not move or open them merely to complete an observation field. This article provides no suspect-bottle handling procedure.

How should you finish the record?

When it is appropriate to review the batch, separate three things: what you observed, your interpretation and the next question. “The label photograph shows a different product” is evidence. “That caused the result” is an interpretation requiring support.

Keep later comments dated so they cannot be mistaken for brew-day observations. If a detail was supplied afterward by someone who helped, identify that source. Correct mistakes visibly instead of erasing the earlier entry without explanation.

For the next batch, choose a specific question the record can help answer. Preserve the old recipe and create a new version before making a change. A useful log leaves you with a traceable account of the batch, including the things you still do not know.

Sources

Questions

Do I need an app to keep brewing notes?

No. A notebook, spreadsheet or plain document can hold the record. Choose a format you can update safely and find later. Give each batch its own identifier, keep the recipe version with it, and separate intended settings from actual observations. The format matters less than knowing what each entry represents.

What if I forgot to record a measurement?

Write “not recorded” rather than copying the recipe target into the actual-results field. If you later obtain information from another person or a saved file, identify that source and when it was added. A reconstructed estimate must remain labeled as such; it should not become evidence that a safety check passed.

Should I put expected and actual gravity together?

Keep them in separate, clearly labeled fields. Expected gravity belongs to the recipe plan; actual observations need dates and measurement context. Brewer’s Friend’s extract sheet illustrates this separation. Unexpected results require investigation with appropriate brewing guidance, rather than editing the reading or assuming that an unchanged number proves packaging is safe.

What does a volume difference prove?

It proves only the difference between the recorded quantities, provided their units and stages are comparable. In the hypothetical example, eighteen liters is two liters below a twenty-liter plan. That does not identify the cause. Review measurement context and documented events before considering any recipe-specific adjustment with suitable guidance.

Can a complete log prevent bursting bottles?

No. A log preserves information but does not eliminate bottle-pressure risk. Fermentation must be assessed as complete, priming correctly calculated and measured, and bottles suitable and undamaged. If evidence is uncertain, seek qualified brewing guidance before packaging. Keep people away from suspect bottles; do not handle them to fill a missing log entry.