Serious homebrewers keep a notebook because brewing is a process, not a moment. The wort tasted sweet on brew day and the beer came out thin three weeks later, and without a written record there is no way to connect those two facts or to know which of a dozen small choices made the difference. A log turns one batch into a series, and a series is the only thing that can tell you whether you are actually getting better. The notebook is not a diary of how the weekend went; it is a measurement record that lets you stop repeating yesterday's mistake.
The distinction matters because the failure mode of homebrewing is amnesia, not ignorance. Almost nobody cannot tell a too-hot fermentation from a slightly oxidised one in the moment; the trouble is that three batches later you cannot remember which one it was, so the correction you were about to make never happens. If you are just starting, the beginner's guide to homebrewing covers the process itself, and this page is about the record you keep while you do it.
What A Log Is Actually For
The purpose of a log is comparison, not documentation. A single batch written up beautifully tells you almost nothing, because you have nothing to compare it against. What tells you something is the third batch of the same beer, brewed after you changed one thing on purpose, because now you are looking at two numbers side by side instead of a memory and a guess. The brewer who improves is not the one with the most accurate records; it is the one who changes a single variable between batches and then honestly reports what happened.
That framing also tells you what to write down. Anything that could reasonably have caused the result belongs in the log, and anything that could not, does not. The weather, the brand of yeast, the exact time you pitched, the temperature the fermenter sat at overnight, whether you topped up with water, whether you racked early. A log is written for the version of you who is standing in front of a flat beer in six months having forgotten all of it, so it is written in short declarative lines rather than narrative.
The Entries That Earn Their Place
| What to record | Why it earns its place |
|---|---|
| Date, batch number, and beer name | Gives every batch an identity, so a later note can point back at a specific one rather than the beer in general |
| Grain bill with actual amounts | A recipe you scaled without redoing the arithmetic is a common and invisible cause of a beer that lands wrong |
| Mash and boil specifics | Mash temperature, mash time, and how long you boiled shape the body of the finished beer more than most people expect |
| Yeast, pitch date, and pitch temperature | The single most common reason a batch tastes different from the last one is the yeast, and the second most common is how warm it was |
| Original and final gravity | Gives you the real attenuation and lets you correct your next batch's starting gravity, which a taste cannot tell you |
| Water treatment used | Whether you adjusted anything, and with what, matters enormously in a pale beer and hardly at all in a stout, so you can only know by writing it down |
| Fermentation temperatures and any rest steps | A temperature swing during fermentation is a flavour, and it is invisible once the beer is finished |
| Additions with dates, such as dry hops, priming sugar, or a diacetyl rest | Timing decides the result more than the quantity does, and a week from now you will not recall whether the hops went in on day three or day five |
| A short tasting note with a date | Your palate changes, so a note only means something if you know when you wrote it and what you were comparing against |
Gravity Readings Matter More Than Taste
Taste tells you a beer is wrong. It rarely tells you why, and it cannot tell you how wrong, which is why the one measurement worth having in the log is a pair of gravity readings, one before you pitch and one at the end. From those two numbers you learn how much of the sugar your yeast actually ate, which is a direct answer to the question every new brewer asks, which is whether the beer is finished. A stable reading across two or three days is the usual signal that fermentation has wound down.
The same pair of numbers tells you what to change next time. If your final gravity came in higher than the recipe predicted, you know your yeast is under-pitching or fermenting too warm, and you know it from a number rather than from a hunch. If it came in lower than predicted, the same reading points somewhere else entirely. Either way you have learned something you can act on, and none of that is available from the glass in your hand. The reading after bottling also tells you whether the beer will be sweet or thin in the bottle, which is the difference between a dessert and a session beer that only becomes apparent weeks after the fact.
How To Write One You Will Keep Using
The best logs are dull. A fixed template with the same headings in the same order every time, filled in the same evening while the details are still fresh, will outlast any beautifully worded notebook you abandon after three batches. Write the entry the day you brew and add the tasting note the day you drink it, because a note written a month later is a reconstruction rather than a record. Most people keep their logs in a phone, a spreadsheet, or a cheap paper notebook, and the format matters far less than the habit of never skipping a batch, including the ones that went badly, which are the entries you will want most.
- Change one thing between batches wherever you can, since a log only teaches you anything when it isolates a single difference from the batch before it.
- Write down what you did not do alongside what you did, because the missing step, the forgotten dry hop and the skipped temperature check are the usual explanations for a disappointing beer.
- Keep your worst batches in the log, since a failed batch you have written up is the fastest way to find the fault, and a failed batch you deleted teaches you nothing at all.
- Date every tasting note, because your palate is not a fixed instrument, and a note about the same beer written a year apart can disagree without either being wrong.
- Decide what a good result looks like before you brew, in the log, in a sentence, so that you are comparing the beer to your own target rather than to whatever you happen to have in the fridge.
What Not To Put In It
A brewing log is a technical record, so resist the urge to make it a lifestyle document. Notes about the weather are useful only insofar as they might have affected the beer, and a paragraph about how the afternoon went is padding that makes the useful lines harder to find later. The same goes for excuses. When a batch goes wrong, the value of the entry is in the honest measurement and the honest note, because the next batch is where the fix gets tested, and a log that protects your feelings produces bad beer just as reliably as a log that records nothing.
Frequently Asked Questions
Do I need a notebook if I only brew a few times a year?
A notebook matters most when your batches are spaced far apart, which is exactly the case when you only brew a few times a year. If you brew in March and again in July, the person making the second batch has no memory of the first, so the log is the only thing standing between you and a repeat of the same mistake. One bottle of strong beer alongside each batch is plenty of context, and the log is what makes that context useful six months later.
Is a spreadsheet better than paper?
Either works, and the format is not what decides whether you will keep using it. A spreadsheet makes it easy to put two batches side by side and to sort by beer, which is the main thing the log is for, but it is easier to stop updating. A paper notebook you keep by the kettle gets filled in. The best answer for most people is whatever they will actually write in after the tenth batch, and the worst is the system so tidy that it stays empty.
Should I log recipes I have never brewed?
Only once you have brewed them, because a copied recipe is a plan and a brewed recipe is a record, and mixing the two is how logs end up full of confident numbers that nobody ever measured. Write the recipe in when you brew it, not before, and if you scaled it or substituted a grain, write the scaled amount rather than the original. Homebrewing does not have to be technical to be improved at, but the log is the one tool that turns practice into progress, and it only works if what you wrote down is what you actually did.
Start A Log Before You Think You Need One
The case for keeping one is easiest to see in hindsight, which is why people start too late. Pick any one beer you will brew again, open a document the day you brew it, and record the recipe, the yeast, the two gravity readings and one sentence about how it came out. Do that for three batches of the same beer, changing one thing each time, and by the fourth you will be able to point at a number and say why it improved. That is the whole return on a notebook, and it is the difference between brewing the same batch for twenty years and getting a little better each time.
