Espresso shot log: what to track and what to skip

A useful espresso shot log answers two questions: what produced this cup, and what should change next? Record coffee, grinder and setting, dose, yield, time, taste, brew date, and one intended adjustment. Add more only when it will change a decision.

The minimum fields

• Coffee identity and the grinder used.
• Grind setting, dry dose, beverage yield, and shot time.
• A plain taste note or rating and the drink type.
• Brew date; roast or open date when known.
• One next change, or “repeat” when the cup is already right for you.

What to skip

Skip fields you never compare. Pressure traces, detailed water chemistry, puck-screen notes, and distribution techniques can matter in a controlled investigation, but mandatory complexity makes an everyday log harder to sustain. Add a field when a repeated question requires it.

Use the log inside the one-change-at-a-time dial-in workflow. Compare the last two relevant shots rather than scanning a long diary without a hypothesis.

Make uncertainty visible

If a value was estimated or a shot was not tasted, say so. An honest gap is safer than false precision. The log remains useful when you return; start with the next measured shot rather than reconstructing missing history.

A 2025 r/espresso discussion of brew-tracking tools shows recurring interest in recipe, taste, rating, and bean context. It is qualitative evidence from a self-selected community, not measured demand.

BeanBudget pre-fills the previous recipe and keeps this minimum record attached to the coffee, after the logging method has answered the primary question.