A coffee brew log is useful when it lets you answer one question: what should I repeat or change next time? You do not need a page of tasting vocabulary for every cup. You need a reliable record of the coffee, the recipe, what actually happened, and whether you enjoyed the result.
This guide provides a compact coffee brew log template, a fictional worked example, and a way to compare sessions without losing track of your changes. It focuses on recording and learning from your own brewing. The numbers below are example recipes, not universal targets for every bean, brewer, or preference.
Separate the recipe from the brew you actually made
A recipe describes your intention. A session records an event. Keep them separate because a successful recipe can produce an unusual session when you pour differently, use another grinder, or stop early. Editing the original recipe to match every session erases the baseline you are trying to understand.
Give the recipe a short name and version, such as Morning Filter v1. Record the coffee dose, planned water, method, grind reference, and intended phases there. For each session, capture the date, actual measurements, actual timing, and taste notes. If you deliberately change the recipe, create v2 and say why.
Use one stable identifier for the beans or bag. A label such as Bag A is better than repeatedly writing “the coffee from the cupboard.” Record the roaster’s description as label information, while keeping your own impressions in a different field. That prevents an advertised flavor note from silently becoming your observation.
Use a short, reusable brew log template
Copy these fields into a notebook, document, spreadsheet, or recipe workspace. Required fields should be the ones you can realistically complete before the next distraction. Optional details can stay blank when they did not affect the comparison you are making.
- Session: date, time, recipe name and version, and bean or bag identifier.
- Method and equipment: brewer, filter, grinder, and the grinder’s own setting reference.
- Planned recipe: coffee mass, brewing water mass, ratio, and phase notes.
- Actual brew: measured dose, water added, start and finish times, and any departure from the plan.
- Taste: your rating scale, a few plain observations, and whether the cup changed as it cooled.
- Next experiment: one proposed change and the reason for trying it.
Write units directly beside the numbers. “18 g coffee, 288 g brewing water” is much clearer than “18 / 288.” A recipe copied to another device or printed for a friend should remain understandable without its original column headings.
Add water-source notes, roast-date information, or temperature measurements when they matter to your process. Do not invent a missing measurement from memory later. “Not measured” preserves the value of the other observations; an estimated number presented as exact weakens the record.
Calculate the ratio consistently
For this log, define brew ratio as coffee mass to brewing water mass. A 1:16 recipe means 16 grams of brewing water for each gram of coffee. With 18 grams of coffee, the planned water is 18 × 16 = 288 grams. With 320 grams of water at the same ratio, the planned coffee is 320 ÷ 16 = 20 grams.
Keep the definition visible because other contexts may use a different denominator or describe beverage output instead. Water poured into a filter brewer and liquid collected in the cup are different measurements. If you record both, give them separate names. Do not replace planned brewing water with cup weight in a comparison without explaining the change.
Likewise, distinguish mass and volume. Grams and milliliters are not interchangeable units by definition. For a simple comparison, measuring coffee and water by mass avoids mixing a scoop estimate with a weighed recipe. If you choose volume measurements, label them consistently and acknowledge that your process has a different measurement basis.
Scaling the arithmetic does not guarantee identical brewing behavior. A larger batch can require changes to the physical process. Preserve the scaled calculation as the starting plan, then record what happened rather than assuming the old timing must still fit.
A fictional worked example: two morning sessions
Imagine Alex wants to repeat a pleasant filter coffee before work. Alex creates Morning Filter v1 using Bag A, one named brewer, one filter type, and Grinder One at setting 22. The planned dose is 18 g, the planned water is 288 g, and the ratio is 1:16. The recipe includes a short initial wetting phase followed by two pours.
On Monday, Alex records 18.0 g coffee, 288 g water added, and a total session time of 3 minutes 10 seconds. The notes say, “Comfortable strength; a little drying after cooling; would drink again.” Alex gives it 3 on a personal five-point enjoyment scale. That rating describes preference, not a laboratory quality measurement.
On Tuesday, Alex keeps the bag, brewer, filter, dose, water, and pouring plan the same, but changes Grinder One to setting 23. The actual session takes 2 minutes 55 seconds. Alex writes, “Less drying; still enough body for me,” and rates it 4. The next-experiment field says, “Repeat setting 23 once before changing anything else.”
These two sessions suggest a useful next trial for Alex. They do not prove the grinder adjustment caused every difference. The value of the log is that it preserves enough context to repeat the comparison and notice when the pattern does not hold.
Record phases without turning breakfast into data entry
For a multi-phase method, decide whether a time is elapsed from the start or measured within that phase. “Second pour at 1:10 elapsed” and “pour for 20 seconds” convey different things. A small note beside the timing field prevents confusion when you return to the recipe weeks later.
Capture deviations that a timer alone cannot explain: interrupted pour, missed target, filter changed, brew ended early, or water added after the main brew. Those notes often explain why a session is a poor comparison with the previous one. Keep them factual rather than writing a long defense of an imperfect cup.
If your method includes additional dilution, list brewing water and added dilution separately. Record when the dilution happened and how much you used. A final drink made with 240 g brewing water plus 40 g afterward should not look identical in the log to a brew that received all 280 g during extraction.
Choose a consistent finish marker for your own method. If you sometimes stop the timer at the final pour and sometimes at the end of drawdown, the totals will not be comparable. Write the marker into the template once so each session inherits the definition.
Make taste notes useful to your future self
Start with ordinary language. “Too strong for my afternoon cup,” “pleasant while warm,” or “rough finish after cooling” can be more actionable than a list of elaborate flavor references you cannot recognize later. Describe the cup you tasted, not what you think a coffee enthusiast is expected to report.
Define a small personal rating scale. For example, 1 might mean would not repeat, 3 acceptable, and 5 a recipe worth saving. Keep that scale stable for a series of comparisons. A four-star session in a personal log should never be presented as an independent product review or an objective score.
Note major differences in how you tasted. Adding milk, changing the drinking temperature, or evaluating the coffee after a long interruption changes the context. You do not need to standardize every moment of your day, but you should avoid treating unlike sessions as a controlled experiment.
End with a next action. Repeat unchanged, adjust one variable, archive the recipe, or compare a different bag are all useful outcomes. “Interesting” alone gives you little help when you open the log the following morning.
Compare one deliberate change at a time
Select the question before the next brew. You might ask whether a particular grinder adjustment suits your taste, or whether a smaller batch is easier to repeat. Write down which factors you intend to hold steady. This keeps a casual comparison focused without pretending it has the controls of formal research.
If you change dose, ratio, filter, and pouring pattern together, label the session as a new recipe trial. It can still be delicious and worth saving. You simply cannot use the result to isolate which change mattered. Preserving that distinction makes the log honest and easier to interpret.
Review several comparable sessions before turning one preference into a standing rule. Look for interrupted brews, missing measurements, or a different bean bag before comparing ratings. Keep a surprising result rather than deleting it; it may reveal a hidden difference or show that your process varies more than you expected.
Keep the log easy to search and share
Name recipes for retrieval: method, bag identifier, and distinguishing feature. “Filter Bag A, small batch” survives better than “Best Coffee Ever 7.” Use dates consistently, and keep retired versions available so a shared recipe still points to an understandable record.
When sharing, include the recipe definition, equipment references, units, timing convention, and your taste preferences. A grinder setting means little without the grinder identity. Explain that your example is a starting point for that setup rather than a promise that another brewer will produce the same cup.
Keep exports in a place you can reopen. Check that a sample exported record includes labels and units, not just raw values. A useful archive can be read outside the original workspace, with any limitations or missing fields apparent to the reader.
Repair a log that has become hard to use
If your history is full of entries called “test,” do not rename everything at once. Choose one recent recipe you actually want to repeat and reconstruct only what you can verify from its session. Preserve uncertainty explicitly. Leave the old entry intact if the new record is a cleaned-up interpretation rather than an exact original.
If ratings are all identical, add one comparative sentence instead of inventing more precision. “I preferred this to Monday because the finish felt smoother” gives the next session a direction. You can keep a simple scale while improving the observations attached to it.
If recording takes too long, remove fields that never influence a decision. Keep dose, water, method, identity, actual timing, and a short outcome as the core. Move detailed phase observations into an optional note. A modest log you maintain is more useful than an elaborate table abandoned after two brews.
If two people share a recipe library, attach the taster’s name or initials to subjective notes. Their preferences may differ even when they follow the same recipe. Preserve both views rather than averaging them into a score that describes neither person’s cup.
Use BrewRatio when calculations and guided sessions belong together
BrewRatio connects coffee, water, and ratio calculations with guided brewing phases and session notes. Its official listing describes recipe presets, ratings and flavor observations, along with optional Pro tools including custom recipe phases, grinder profiles, history, and JSON or CSV export. Check the listing for current access and device compatibility.
You can view BrewRatio on the App Store if you want that workflow in a local brewing companion. The app can support the record; your measurements and preferences still determine what the session means. Start with one recipe, complete a few honest entries, and let the next change answer a specific question.
Sources and example scope
Product capabilities were checked against the official BrewRatio listing and NexLevel product page. The template, Alex’s sessions, rating scale, and recipe values are original illustrative examples. The ratio calculations follow the stated mass-based definition; the guide makes no claim that one recipe is ideal for every coffee or brewing method.