Keeping a learning log in your first brewing job

Why a log beats memory

In your first months everything is new. The name of each valve, the sound of a healthy fermentation, the order of a cleaning cycle and the reason behind each step all arrive at once. Most of it is gone within a week unless you write it down.

A log also protects you from guessing. When a brewer asks "what was the gravity when we crashed that tank?", the person with the notebook answers. That is how trust starts.

What to write after each shift

Keep it short enough to finish tired. Five lines is enough.

• Date, shift and the tanks or batches you touched.
• One thing you did yourself.
• One number that mattered, such as a gravity, a temperature or a pH, with its unit.
• One thing you did not understand.
• One thing that went wrong or nearly did.

The last two lines are the valuable ones. A list of questions becomes your reading list. A note of a near miss becomes a habit you carry for years.

Record numbers with units

A number without a unit is useless a month later. Write 12.4 °P, 1.050, 18 °C, pH 5.3. Note where you took the sample: the mash tun, the end of the boil, the fermenter. Write the scale too: degrees Plato and specific gravity are different numbers for the same wort.

If you are still in another job and building skills on the side, our guide to learning to brew professionally while keeping your day job shows how to fit this into a full schedule.

Some people keep the log in a notebook. Others use a spreadsheet with a row per batch. Either works. A spreadsheet makes it easier to see a trend, such as fermentations that finish a day later in April than in January.

What a good entry looks like

Here is a made-up example to show the level of detail, not a real brewery record.

Night shift, fermenter 3. Took the daily sample: 1.018, 17.5 °C, pH 4.4. Learned that the bubbling from the blow-off slows well before gravity stops falling, so a hydrometer reading beats listening. Did not understand why the head brewer asked for the sample at the sampling valve and not from the top. Near miss: nearly opened the wrong valve on the cooling line, so I now trace the line by hand first.

That entry takes four minutes. It records a number, a lesson, a question and a near miss. Repeat it for a hundred shifts and you have a manual.

Ask permission and respect what is private

A brewery's recipes, costs and supplier terms belong to the brewery. Ask your head brewer what you may keep. A reasonable arrangement is that you note what you did and what you learned, but not recipes, cost figures or customer names. Never photograph a control screen or a batch sheet without asking.

Follow every safety rule in the log as well. Write down the permit to work, the lockout steps and the personal protective equipment for caustic, because repeating them in your own words is how they stick.

Review it every week

Writing is half the job. On a quiet shift each week, read the last seven days and do three things.

• Answer one of your own questions, using a book, a colleague or the process itself.
• Pick the near miss and write what would have prevented it.
• Choose one skill for next week, for example reading a fermentation curve or setting up a clean in place cycle.

A year of those reviews is a better education than most people get from an unplanned first year.

Turn the log into evidence

The log becomes your proof. When you apply for a better role, you can say that you ran the weekly cleaning check on the fermenters, logged gravity at every transfer for six months and traced a diacetyl problem to a cooled-too-early tank. Those are specific and believable.

It also gives you something to point to when you consider the next move. Our guide on when to leave a brewer job to start your own brewery is easier to use if you can show a record of what you have actually done.

The gap a log shows

After a few months you will see patterns in your questions. Many will be about why, not what. Why does lager yeast ferment cooler? Why does the boil need to be vigorous? A log tells you where on-the-job learning stops and structured study should start. If your taproom colleagues are on the same path, see how it looks from the other side in becoming a taproom bartender as your first beer job.

Common questions

Should I keep a log in a notebook or on a phone?

Either is fine. A notebook is quick on the floor and survives wet hands. A spreadsheet is better for seeing trends. Many people write by hand and type up weekly.

Can I keep the brewery's recipes in my log?

Only with permission. Recipes, costs and customer details belong to the brewery. Log what you did and learned and ask your head brewer where the line is.

How long should each entry take?

About five minutes. If it takes longer you will skip it on busy days, which is when the best lessons happen.

How does a log help me get promoted?

It gives you specific, dated examples of what you have done and learned, which is stronger in a review than saying you are a quick learner.