The difference between a lucky shot and a repeatable one is memory. Logging your brews turns coffee history into a dialing-in map you can actually follow.
Every logged shot makes the next one easier.The Direct Answer: Why Logging Works
Shot logging works because espresso has too many variables to remember: dose, grind, yield, time, temperature, beans, and how it tasted. Write them down and patterns appear; keep them in your head and every shot is a fresh guess. A log does not make you a better barista by itself, but it makes your adjustments honest, because you can see exactly what changed.
What to Record
Start with the minimum set that explains a shot's result:
- Beans: name, roast date, and the setting the bag suggests.
- Dose and yield in grams.
- Time from first drop, and total shot time.
- Grind setting on your grinder.
- Taste notes in a few words: sour, balanced, bitter, thin, thick.
That is six fields. Once you have a few rows, a bad-tasting shot stops being a mystery because you can compare it against the row that tasted great.
How to Read the History
Scan the log for the variable that moved before the taste changed. If the great shot and the bad shot differ only in grind, grind is your lever. If they differ in yield, the ratio is your lever. If every row with a certain bean tastes sour, that bean needs a different approach entirely. The log converts correlation from a feeling into a visible pattern.
A brew history list replaces guesswork with a pattern you can follow.Manual Logs Versus an App
A notebook works, and many baristas like it. An app or a machine with integrated logging removes the friction: no pen, no remembering to write it down. The value of any log is completeness and consistency, so pick the method you will actually use every day. If you log only when a shot goes wrong, you are missing the baseline that makes the outliers meaningful.
A Simple Logging Routine
Make it a habit with a fixed order:
- Weigh the dose and note the grind setting.
- Pull the shot and weigh the yield, noting the time.
- Taste before adding milk, and write three descriptor words.
- Change one variable, log it, and compare against the next shot.
Five sessions of this produce enough rows to start seeing trends, and it is the fastest way to improve from "sometimes good" to "reliably good."
Edge Cases and What to Try Next
If you change beans often, log the roast date, because coffee flavors shift over weeks. If you switch grinders, start a new section so old settings do not confuse new ones. And if your log shows the same bad result for three different variables, question the dose and basket fit before the grind; a mismatched basket makes every other variable look wrong. None of these need fancy tools; they just need the record.
Authoritative Sources
Independent references for the dialing in and extraction guidance in this guide.
FAQ
What is the 30 second rule for espresso?
The 30 second rule is a common benchmark: a well-pulled double espresso extracts in roughly 25-30 seconds from first drop. It is a starting point for dialing in, not a law.
Is 40 seconds too long for espresso?
Forty seconds is longer than the common 25-30 second benchmark, but it can be right for specific beans and doses. If it tastes bitter or ashy, reduce yield or grind coarser. Judge by taste, not the timer alone.
Should espresso be 25 or 30 seconds?
Both are within the common range. Most double shots land between 25 and 30 seconds from first drop, and the right target depends on your beans, dose, and taste. Pick a target and log the outcome so you can see what works.
How much should 2 shots of espresso weigh?
Two shots usually means a double dose of roughly 14-21 g producing about 28-42 g of yield at a 1:2 ratio. Weigh the yield in the cup; the number you log is what makes the next shot repeatable.
Want the log to write itself? A machine with an integrated scale and app captures dose, yield, and time for you. See the Meraki espresso machine, or call +1 833 854 9555 (Mon-Fri, 9 AM-5 PM EST).
Extraction benchmarks are general industry practice, not Meraki-specific claims. App behavior and data capture follow the official documentation.
