How much prep labor does a restaurant kitchen really need on a given day?

Why two prep cooks is not an answer

Ask most leads how much prep labor they need and they will name a number of bodies, not a number of hours tied to a list. That works until the menu changes, a slow Tuesday gets staffed like a Saturday, or the one cook who is fast leaves. Labor tied to headcount is really labor tied to memory, and it drifts in whichever direction is more comfortable, which is usually up. Related: How do you build a daily prep list from par levels the right way?

A better answer is a range of hours per day that comes from the prep list itself. If Monday's list is thirty tasks and Friday's is sixty, the labor should not be the same. Once you have a rough time per task, the sheet tells you how many hours the day needs, and headcount becomes a scheduling detail rather than the starting point. Related: How should you assign prep tasks across stations so nothing gets missed?

Keep reading: How do you build a daily prep list from par levels the right way?, What causes over prep and under prep, and how do you stop both?, How should you assign prep tasks across stations so nothing gets missed?. See how PrepDeckr helps you kitchen prep lists and par-based prep sheets.

Time your tasks once, roughly

You do not need a stopwatch on every cook. For each recurring prep item, estimate how long a competent cook takes to produce one standard batch, including setup and cleanup. Round to the nearest quarter hour. Be honest about cleanup, since a task that takes twenty minutes of knife work and fifteen minutes of breaking down and sanitizing is a thirty-five minute task. Many kitchens are surprised at how much of prep time is not cooking.

Then adjust for batch size. If the par-driven quantity on a given day is double the standard batch, the time is not quite double because setup is shared, but it is close for most knife work. Record these estimates once on the master prep list. Revisit them only when a recipe changes or a cook's timing is consistently far off, which usually means the estimate was wrong rather than the cook. Related: How do you make a prep list any lead can run when you are out?

Add the hours the list does not show

The sum of task times is a floor, not the schedule. Every prep shift also includes receiving and putting away deliveries, rotating the walk-in, counting, cleaning as you go, breaks, and the inevitable interruption from the line asking for something. In most kitchens this overhead is meaningful and fairly consistent, so measure it once for a typical shift and add it as a fixed block rather than pretending it does not exist.

Some days carry extra: a deep clean, a delivery that comes in wrong, a party block, a new hire shadowing. These belong on the sheet as tasks with time estimates just like everything else, so the day's total reflects them. When an owner asks why Thursday needed an extra four hours, the answer is on the sheet rather than in someone's memory.

Turn hours into a schedule and check it weekly

With a total for each day, scheduling becomes arithmetic. A day that needs fourteen hours of prep can be two cooks for seven hours or one for eight plus one for six, depending on when the long tasks need to start and when the line needs its first items. Front-load the day with the long-cook tasks and stagger the second person to arrive when there is enough flexible work to keep them busy.

Once a week, compare the hours you scheduled with what actually got done. If the list is finishing early every day, either the estimates are high or the pars are low. If it is running late, look first at sequencing and equipment conflicts before adding hours. Over a couple of months, the estimates settle and the schedule starts to match reality, which is the point: labor that follows the workload rather than a fixed headcount. Related: Why should prep par levels change by day of the week for a kitchen?