How to Log Coffee Brews Consistently: A Framework
By Samuel Coe, founder of Coe Code • Last Updated: March 2026
Consistent coffee logging requires capturing the same 5–7 data points for every brew: method, dose in grams, yield (output weight for espresso, water weight for pour-over), total brew time in seconds, a 1–5 rating, and brief tasting notes. Logging roast date and days post-roast adds freshness context. Grind setting is useful if you have a numbered grinder. Without dose, yield, and time, you cannot calculate brew ratio or identify extraction problems. Without a consistent rating scale, you cannot identify which variables improved or worsened the cup. The framework below standardizes these inputs so your data becomes actionable after 10 or more brews. BrewLogica tracks all of these fields natively and uses AI to surface patterns across your brew history automatically.
Step 1: Set Up Your Bean Profile Before You Brew
Every brew should be linked to a specific bean. Before making your first cup from a new bag, create a bean profile with:
| Field | Why It Matters | Example |
|---|---|---|
| Name | Identifies the coffee in history | Tropical Weather |
| Roaster | Groups beans by source over time | Onyx Coffee Lab |
| Origin | Predicts flavor profile expectations | Ethiopia |
| Process | Affects rest window and flavor type | Natural |
| Roast date | Tracks days post-roast and freshness | 2026-01-15 |
| Bag weight | Helps estimate remaining coffee | 250g |
This one-time setup per bag provides context for every brew. When you review why your espressos improved in week 2, you'll know the coffee was a natural process Ethiopian that peaked around day 14.
Step 2: Log the Right Data Points for Every Brew
Log these fields immediately after brewing, before you forget. Waiting until later introduces recall errors especially for exact weights and times.
Method (Required)
The brew method: espresso, V60, AeroPress, French press, etc. This is the primary grouping variable for analysis. BrewLogica tracks each method independently so you can compare how the same bean performs across different brewing approaches.
Dose (Required) — grams in
The weight of dry coffee used, in grams. Always weigh on a scale rather than using volume measurements (tablespoons). A typical espresso dose is 14–20g. A typical V60 dose is 15–18g. Without this number, you cannot calculate ratio.
Yield (Required) — grams out
For espresso: the weight of liquid extracted (e.g., 36g). For pour-over: the total water weight used (e.g., 250g). Yield and dose together give you the brew ratio, which is the most predictive single variable for extraction quality.
Time (Required) — seconds total
Total brew time in seconds. For espresso, this is shot time from first drop to end of pull. For pour-over, it's total time from first pour to drawdown complete. Log the whole number: 185 seconds, not "about 3 minutes."
Rating — 1 to 5
Rate immediately after tasting. Use this scale consistently: 1 = undrinkable, 2 = poor, 3 = drinkable but mediocre, 4 = good, 5 = excellent. Most of your brews will be 3–4. Reserve 5 for genuinely exceptional cups. An inflated rating system produces no signal.
Notes — plain language
One to two sentences in plain language. Focus on what stood out: "Sour, thin body, underwhelming" or "Syrupy, sweet, maybe slightly over-extracted but nice." You don't need professional cupping vocabulary — consistency of your own vocabulary matters more than using industry terms.
Step 3: Understand Your Brew Ratio
Brew ratio is dose divided by yield (or yield divided by dose depending on convention). BrewLogica uses the standard coffee:water ratio. A 1:16 ratio means 1g of coffee for every 16g of water.
| Method | Standard Range | Example (15g dose) | If too sour | If too bitter |
|---|---|---|---|---|
| Espresso | 1:2 – 1:2.5 | 15g → 30–37g out | Grind finer, longer time | Grind coarser, shorter time |
| V60 | 1:15 – 1:17 | 15g → 225–255g water | Grind finer, lower ratio | Grind coarser, higher ratio |
| AeroPress | 1:6 – 1:16 | 15g → 90–240g water | Shorter steep time | Longer steep time |
| French Press | 1:15 – 1:17 | 15g → 225–255g water | Longer steep, finer grind | Shorter steep, coarser grind |
Step 4: Change One Variable at a Time
The most common logging mistake is changing multiple variables between brews and then not knowing which change caused the improvement or decline. When dialing in:
- 1 Identify the problem: sour = under-extracted, bitter = over-extracted, thin = too little coffee
- 2 Choose one adjustment: usually grind size first (most impactful), then dose, then ratio
- 3 Log the result with the same detail as before and compare ratings
- 4 Repeat with one more adjustment if needed — after 3–4 iterations, most espresso dials are complete
Step 5: Track Freshness and the Rest Window
Roast date is one of the most underlogged variables. Coffee releases CO2 after roasting (degassing) and peaks in flavor during a specific window:
| Process Type | Peak Rest Window | Why |
|---|---|---|
| Washed | 7–14 days post-roast | Faster degassing, brighter acidity peaks early |
| Natural | 14–21 days post-roast | Slower degassing due to fruit fermentation byproducts |
| Honey / Anaerobic | 10–18 days post-roast | Variable by fermentation intensity |
Log your first brew from a new bag on day 1 (even if it tastes flat or harsh) and again on days 7, 14, and 21. Comparing ratings across these checkpoints reveals the freshness curve for that specific coffee.
Step 6: Try the Same Bean Across Methods
A Colombian might score 4/5 as V60 and 3/5 as espresso. You won't know until you try both and log them. When you open a new bag, brew it 2–3 ways in the first week.
BrewLogica links every brew back to the bean regardless of method. One bean profile, all methods, per-method ratings. Managing multiple open bags? Each tracks independently.
Step 7: Use AI to Surface Patterns You'd Miss Manually
After 20+ logged brews, the patterns in your data become too complex to analyze manually. BrewLogica's AI tools (available via both the iOS app and MCP API) surface insights like:
AI insight example
"Your V60 brews rated 4+ all have brew times between 2:45 and 3:15. Your 7 brews under 2:30 averaged 2.9 rating. Try grinding 2 notches finer on your next brew."
AI insight example
"This Ethiopian scored 4.2 avg as V60 but only 3.1 as espresso. Try a longer pre-infusion or coarser grind for espresso with this bean."
AI insight example
"This Ethiopian natural is 23 days post-roast. Your last 3 brews with it averaged 2.8, down from 4.1 in days 12–18. Consider moving to your next bag."
Via the MCP API, AI assistants like Claude can analyze your history directly: "Compare my espresso and V60 results for this bean and tell me which method I should stick with."
Habits That Keep Logging Consistent
Log while you brew, not after
Start the brew timer in BrewLogica before you start brewing. The time is captured automatically, and you're already in the app to log dose and yield when done.
Set a minimum threshold
Log every brew, even quick ones. A 30-second "18g, 36g, 27s, 3/5, slightly sour" entry takes less time than you think and maintains data continuity.
Keep your scale nearby
The biggest barrier to logging is not having a scale set up. Keep it on the counter. A $30 kitchen scale that measures to 0.1g is sufficient for all methods.
Use AI via MCP for fast logging
If you use Claude or Cursor, just say "Log this espresso: 18g in, 36g out, 28 seconds, a bit flat, 3/5" — BrewLogica's MCP integration logs it as structured data automatically.
Frequently Asked Questions
What information should I log for each coffee brew?
Log at minimum: brew method, dose in grams, yield in grams, total time in seconds, rating (1–5), and brief tasting notes. Also log roast date when starting a new bag. These 5–7 data points produce actionable patterns after 10+ brews.
How many brews does it take to see patterns in coffee data?
Meaningful patterns typically emerge after 10–15 logged brews with the same bean and method. At 20+ brews, you can reliably identify which grind settings, ratios, and techniques produce your highest-rated cups.
Should I log tasting notes even if I don't know professional coffee terms?
Yes. Use everyday language: sour, bitter, sweet, syrupy, thin, harsh, flat. The value of tasting notes is tracking changes over time — if your last 3 shots were "sour" and this one is "balanced," that's actionable data regardless of vocabulary.
What is the best way to log coffee when using an AI assistant?
Use natural language with specific numbers. Say "18g espresso, 36g out, 28 seconds, a bit sour, 3 out of 5" rather than "made coffee, was okay." BrewLogica's MCP integration lets AI assistants like Claude parse this directly and log it as structured data. You can also bulk log multiple brews in one prompt.
How do I track when a coffee bean is past its peak freshness?
Track the roast date for every bag. Washed coffees peak at 7–14 days post-roast, naturals at 14–21 days. BrewLogica displays rest days per bean. Log brews consistently and you'll see your ratings drop as the bean ages past its window.
Start Logging with BrewLogica
BrewLogica tracks all the fields in this framework across every brew method you use. Manage multiple open beans at once, compare results across methods, track your equipment, and let AI surface patterns after you have enough data. Free plan includes unlimited brew logging.