Batch brew is often treated as the simple part of the bar. Load the basket, press start, fill cups. In practice, it can be one of the easiest places for quality to drift because nobody is watching it closely.
A good batch brew workflow is not complicated. It needs a recipe, a brew log, a holding rule, and a clear decision for what happens when the coffee no longer tastes right.
Decide what the batch is for#
Before adjusting grind or dose, decide what role the coffee has during service.
Some cafes use batch brew as a quick morning option for commuters. Some use it as an entry point for single-origin coffees. Some use it as the steady alternative when the espresso bar is busy.
That choice affects the recipe. A commuter batch can be a little more forgiving, with a familiar flavor and enough strength to take milk if guests ask. A single-origin batch should show the coffee clearly, but it still has to taste good after sitting for a short time.
Write the goal in plain language. For example: "clean and sweet black, still pleasant after 45 minutes." That is easier for a team to use than a vague note like "make it brighter."
Use one baseline recipe#
Start with one recipe that everyone can repeat. A useful starting point for many brewers is:
- coffee: 60 g per liter
- grind: medium-coarse, adjusted by taste
- water: filtered and heated by the brewer
- brew time: usually 4:30 to 6:30, depending on batch size and equipment
- target: sweet cup, no dry finish, no thin center
Do not run three different recipes unless the team has time to taste and track them. Consistency matters more than variety during a busy shift.
If the batch tastes weak, do not fix everything at once. Change grind first if the flavor is sour or hollow. Change dose if the extraction tastes fine but the cup is too light.
Check the basket before blaming the coffee#
Many batch brew problems begin before water touches the grounds.
Look for:
- a flat bed before brewing
- no paper folded into the coffee bed
- spray head holes that are clean
- a basket inserted straight
- the right batch size selected on the brewer
A folded filter can make one side run fast. A clogged spray head can leave dry channels. A wrong batch button can make a good recipe look broken.
The person brewing should take five seconds to check these points. It is faster than remaking a bad batch during a queue.
Taste the first brew before service gets loud#
The first batch of the day sets the tone. Taste it while there is still time to adjust.
Use a small cup. Let it cool for a minute. Ask three questions:
- Is it sweet enough?
- Is the finish dry?
- Does it feel thin through the middle?
If it is sour or grassy, grind a little finer. If it is bitter or drying, grind coarser. If it tastes balanced but too light, raise the dose slightly next time.
Do not write tasting notes that nobody will use. "Finer next batch" is more useful than a paragraph about fruit and texture when the bar is opening.
Set a holding time#
Batch brew does not stay the same forever. Even in a good airpot or thermal server, aroma drops and the cup changes.
Pick a holding rule and follow it. A common working limit is 45 to 60 minutes, but the right number depends on the brewer, server, batch size, and coffee. Very small batches can fade faster. Darker roasts can taste stale sooner. Some coffees hold surprisingly well.
The rule should be visible:
- brew time written on tape or a small tag
- discard time written next to it
- no topping up old coffee with new coffee
Topping up is tempting because it avoids waste. It also makes the cup impossible to control. If the old coffee is too tired to sell alone, it should not be stretched with fresh coffee.
Brew smaller when demand is uneven#
Waste usually comes from batch size, not from the existence of batch brew. If demand is unpredictable, brew smaller batches more often.
A smaller batch can taste fresher and gives the team more chances to correct grind. It also reduces the pressure to sell coffee that is past its best.
The tradeoff is labor. If the bar is too busy to brew every twenty minutes, choose a larger batch and a realistic holding rule. A perfect plan that nobody can follow is not useful during service.
Track actual demand for a week:
- first batch time
- number of batches before noon
- amount discarded
- moments when batch ran out
Patterns appear quickly. Monday rain, Saturday rush, and office-area mornings do not behave the same way.
Keep a short brew log#
A brew log should be short enough that people actually use it.
Include:
- coffee name
- dose and batch size
- grind setting
- brew time
- taste note
- adjustment for next batch
One line per batch is enough. The log is not for literature. It is for preventing the same mistake three times in one morning.
Example:
Ethiopia house filter, 180 g to 3 L, grind 27, 5:20, thin and sharp, go finer.
That note gives the next barista something to do.
Build the handoff into the shift#
Batch brew often falls apart during handoff. The opening barista knows what changed, but the next person sees only a grinder number and a half-full server.
Use a direct handoff:
"Current batch brewed at 9:40, dump at 10:30. Grinder moved from 28 to 27 because first cup was sharp. Next batch should stay there unless it dries out."
That takes less than twenty seconds. It prevents the next person from resetting the recipe by accident.
When to pull the batch from service#
There should be no argument about a bad batch. If the coffee tastes papery, sharply bitter, noticeably sour, or stale, pull it.
Do not wait for a guest to complain. Batch brew is often bought by people who want speed. They may not return to explain what went wrong.
If waste hurts, record it and solve the cause later:
- batch too large
- holding time too long
- wrong demand estimate
- brew recipe drifting
- server not keeping heat well
Selling tired coffee hides the problem for one day and trains guests to avoid the option next time.
A workable morning routine#
A simple service rhythm can look like this:
Before opening, brew the first batch and taste it. Write the brew and discard times. During the first hour, check the level before the queue forms, not after the server is empty. Brew smaller if the first batch is moving slowly. Log each adjustment in one line. At handoff, tell the next person what changed and when the current batch expires.
This routine is not glamorous, which is exactly why it works. It gives batch brew enough attention to stay reliable without making it the center of the bar.