Logging brewery data you will actually use

Start with the questions

Write down five questions you want to answer. How much beer do we lose between wort and package? Is our efficiency steady? Which beers finish on time? What does a litre cost? Does the cold room cope in summer? Every column in your log should help answer one of them. If a field answers nothing, drop it. People stop filling in long forms. The data that remains is patchy.

The brew log

One row per batch, with a unique batch ID that follows the beer from kettle to sale. Record the date, recipe, volumes (strike water, wort to the fermenter), original gravity, pH at set points, boil time and any deviations. Add the measured mash efficiency or extract yield, calculated rather than guessed. The formula for ABV is (OG - FG) x 131.25, so keep gravity readings as numbers in a column, never as text in a notes cell.

Use the same units throughout: litres, degrees Celsius, specific gravity or degrees Plato. Pick one and stick to it, since mixed units are the commonest reason a dashboard shows nonsense.

The fermentation log

Per tank per day: temperature, gravity, pH and a short note on smell and taste where relevant. Link the rows to the batch ID. A temperature probe that logs automatically is better than a number written after a walk round, because it shows spikes, but the daily gravity and tasting note still need a person. Record the yeast strain, generation number and pitch rate so you can see how they link to speed and flavour. See managing yeast health in a hot brewery.

Packaging and quality

Record the packaging date, format, volumes filled, losses, carbonation, dissolved oxygen where measured and the result of any tasting. Keep reference samples and write the retained sample ID in the log. Quality records matter when something goes wrong: a customer complaint becomes a search for one batch ID, not a hunt through notebooks. Add shelf-life test results as they come in, each linked to the batch.

Costs, utilities and sales

Link cost data to batches. Record raw materials, labour hours, water and energy from meters, packaging materials and cleaning chemicals for each batch. The goal is cost per litre by beer, not an average that hides one expensive beer. Meter readings for water and energy are covered in water use per litre of beer and cutting energy use. For sales, record by date, product, pack size, customer type and quantity, so you can see the seasons and which accounts drive the most volume. See forecasting demand for a small brewery for how the sales log feeds planning.

Set it out so a tool can read it

Spreadsheets are fine to start. A few rules make the data usable in a tool such as Power BI or Tableau later.

• One table per subject: batches, fermentation readings, packaging runs, sales.
• One row per event, one column per field, no merged cells and no blank header rows.
• Dates in one format, such as 2026-10-31.
• Categories chosen from a drop-down list, not typed freehand. "IPA", "ipa" and "I.P.A." are three different values to a computer.
• A batch ID in every table, so rows can be joined.
• Free-text notes in a separate column, never mixed with numbers.

Make logging easy and keep it honest

Put the sheet or form where the work happens: a tablet on the brewhouse wall, a laminated checklist at the tank. Capture at the point of work. Data typed from memory at the end of the week is mostly wrong. Make one person responsible for checking it each week, spotting gaps and fixing impossible values such as a gravity of 10.5. Review the numbers in a short weekly meeting. People write down what gets discussed. They stop writing down what nobody reads.

Then look at it. A simple chart of efficiency by brew, loss by stage or fermentation time by beer shows more than a table of numbers. Building these charts is what our Power BI and Tableau course teaches. The charts also show you where the log needs another column.

Common questions

What is the minimum I should record for each batch?

A batch ID, date, recipe, volumes, original gravity, final gravity, fermentation temperature and packaged volume. Everything else can be added once those are reliable.

Do I need software?

No. A well-structured spreadsheet is enough to start. Structure matters more than the tool.

How often should I record fermentation data?

Daily for gravity, temperature and pH. Automatic temperature logging adds detail between readings.

Why does my dashboard show strange numbers?

Usually because of mixed units, text in number columns, typos in categories or missing batch IDs. Fix the data at the source.