Every bag is a small negotiation
A new bag of beans — even the same roaster, even the same name — arrives with its own density, roast level, and age, and your dialed recipe from last bag is now merely a good guess. The difference between enthusiasts who shrug through this and beginners who lose a week to bad mornings is not skill; it's a routine and a log. With both, a new bag costs two or three shots to dial. This is that routine.
(Prerequisite reading, once: the full dial-in method. This page is its fast path for the Nth bag.)
Step 0: Respect the rest
Fresh-roasted beans need days off the roast before they behave — CO2 from roasting (the degassing the freshness guide covers) makes very fresh beans gusher-prone and erratic in espresso. The working rhythm: espresso beans hit their stride roughly a week to ten days off roast and hold for weeks after. A bag that arrived yesterday from a same-week roast date wants patience, not dialing; a bag with no roast date wants suspicion.
Step 1: Start from a heuristic, not from scratch
Your last bean's recipe is the anchor; adjust the starting grind by what changed. The two heuristics that carry most of it: roast level — lighter roasts are denser and extract reluctantly: start finer than your previous setting (and expect possibly a longer ratio); darker roasts are brittle and soluble: start coarser. Same-roaster, same-coffee, new bag: start at last bag's setting exactly — drift will be small. Log-keepers compound here: a notebook (or the dial-in tool's log) holding "Roaster X, medium, grind 12, 18g→36g, 28s" turns every repeat purchase into a one-shot dial.
Step 2: The benchmark shot, read coldly
Pull at the heuristic setting — 18g in, 36g out, timer at first drip — and read the clock before tasting: way fast means finer, way slow means coarser, and one decisive correction now beats three timid ones. Then taste against the decoder. Light-roast special case: if it's sour even at a choking grind, stop fighting the burrs and stretch the ratio toward 1:2.5 — light roasts often want the extraction help, and it's a cleaner fix than the grinder's last desperate clicks (a wall the entry tier hits earlier than the DF64 class).
Step 3: Confirm, log, and schedule the drift
One adjusted shot usually lands it; a second confirms repeatability — that's the two-to-three-shot promise. Now log the landing: bean, roast date, grind, dose, yield, time, one taste word. And set the expectation that saves future confusion: the recipe drifts as the bag ages. Beans continue degassing — shots gradually speed up over a bag's life — so a mid-bag tweak finer by a step is normal maintenance, not failure (the clock catches it before the cup does). Single-dosers rotating multiple bags (the workflow perk) live and die by the log; hopper loyalists just ride each bag's drift down.
The routine, in one table
| Step | Move | Cost in shots |
|---|---|---|
| 0 | Check roast date; rest to ~1 week+ | 0 |
| 1 | Heuristic start: lighter→finer, darker→coarser, repeat-bean→same | 0 |
| 2 | Benchmark; clock first, decoder second | 1 |
| 3 | One decisive correction; confirm; log | 1–2 |
| Ongoing | Step finer as the bag ages | maintenance |
FAQ
How many shots does a new bag take to dial in?
Two or three, with a log and the roast-level heuristic — the first benchmark, one correction, a confirmation. Without a log, budget five and start writing one.
Why is my fresh bag pulling weird gushing shots?
Too fresh — heavy degassing destabilizes extraction. Give roast-date beans a week to ten days of rest; the same bag often dials sweetly after the weekend it spends on the shelf.
Do light and dark roasts need different settings?
Reliably: light roasts run denser (grind finer, sometimes ratio longer); dark roasts run soluble and brittle (coarser, sometimes shorter). Starting with the heuristic skips the worst first shot.
My dialed recipe stopped working mid-bag — what happened?
Aging, almost always: degassing beans speed up week over week. One step finer restores it — schedule the tweak as maintenance rather than re-running the whole dial.
The morning pull
Spec changes, silent revisions, and new machines run through the SpecScore model — one email when it matters.