A coffee brew log should answer two questions: what happened, and what should I repeat or change next time?
It does not need every possible measurement. A useful log keeps the coffee, the controllable settings, the observed result, and your reaction connected. The fields should change with the method: water temperature may matter for pour-over, while a capsule user should not be asked for a grinder setting.
Record the coffee, date, method, liking, the settings you controlled, the result you observed, and one next action. One brew preserves a useful note; several comparable brews show what is worth repeating.
01
The minimum useful brew log
Start with five pieces of information:
- the coffee product;
- the brew method and date;
- one or two settings you controlled;
- how much you liked the result;
- what you would keep or change.
This is enough to build continuity. Add more numbers only when you will use them to compare brews.
Illustrative example: the entry below demonstrates the structure of a useful log. It is not presented as a customer review or universal recipe.
- Coffee
- Example espresso blend · medium roast
- Method
- Espresso machine
- Setting
- Grind 7 · dose 18 g
- Outcome
- 36 ml espresso · 29 seconds
- Result
- 8/10 · sweet and balanced
- Next
- Keep this setting
02
Try a free coffee brew log template
Choose the method and record only the fields that help you understand this cup. The template runs in your browser and does not save or send the values you enter. Copy the result into any notes app, or use Beanmemo when you want the coffee and its later brews kept together.
Free brew log template
Try one entry in the browser
03
Separate settings from outcomes
A common logging mistake is treating every number as a recipe target. Some values are choices you make before brewing; others are what the machine or brew produces.
Settings you may control
- grind setting;
- coffee dose;
- water temperature for a manual brew;
- brew program or cup size;
- the amount and type of milk.
Outcomes you observe
- actual beverage yield;
- actual extraction or brew time;
- flow behavior;
- taste and liking.
If your last espresso produced 36 ml in 29 seconds, copying the grind and dose can make sense. Copying “29 seconds” as though it were a setting does not guarantee the same result. Record it again after the next shot.
Start from the last brew’s settings. Measure the next brew’s outcomes again.
04
Only ask for method-relevant fields
A single universal form quickly becomes cluttered. Use the method to decide what matters.
- Espresso
- Grind · dose · actual yield · actual time
- Pour-over
- Grind · coffee and water amount · temperature · brew time
- Automatic machine
- Program · strength setting · drink · milk, when relevant
- Capsule
- Capsule · cup program · drink · liking
- Café drink
- Café · coffee or drink name · milk · personal note
Machine and grinder usually belong to your saved equipment setup rather than being re-entered for every cup. Keep a snapshot with the historical record, but show it only when it changed or helps explain the result.
05
Two illustrative brew log examples
These examples show how the fields change with the preparation method. The coffee names and scores are teaching data, not claimed tasting results.
Espresso with milk
- Coffee
- Example espresso blend
- Equipment
- Compact espresso machine · built-in grinder
- Settings
- Grind 6 · 18 g dose
- Outcomes
- 38 ml yield · 27 seconds
- Drink
- Cappuccino · oat milk · 90 ml
- Taste
- 7.5/10 · chocolatey, balanced, slightly dry
- Next
- Keep grind · use slightly less milk
V60 pour-over
- Coffee
- Example washed coffee
- Settings
- Grind 22 · 15 g coffee · 250 ml water · ratio 1:16.7 · 93°C
- Outcome
- 2 minutes 48 seconds
- Taste
- 8/10 · floral, citrus, tea-like body
- Next
- Repeat before changing anything
Numbers are equipment-specific: grind 22 has no universal meaning. It is useful only when compared with the same grinder.
06
One brew is a note. Several brews become evidence.
When a brew disappoints, avoid changing grind, dose, yield, and temperature together. Choose one controllable variable, keep the others stable, and record the result. If the cup is good, “keep setting” is a valid next action.
Paper, a notes app, or a spreadsheet can all preserve one entry. The limitation appears later: you have to reconnect each note to the same coffee and compare the settings yourself. Beanmemo keeps a coffee’s entries together so its history can help with the next brew without pretending that one recipe works everywhere.
Not every coffee can be adjusted into a favorite. If several reasonable attempts still produce a cup you dislike, mark the coffee “not for me.” That decision is useful preference evidence even if the final score was not extremely low.
A brew log focuses on preparation and results. To connect those entries to a longer personal history, see the personal coffee journal guide. To describe the cup without expert vocabulary, use the coffee tasting notes guide.
Make the next cup easier
Remember which setting worked.
Keep each coffee’s brews together, compare the results, and carry the useful parts into your next cup. Beanmemo is free during public preview, with no credit card required.
Log your next brewKEEP READING