Build your batch prep schedule by working backward from service, grouping tasks by equipment and station, and assigning every prep item a specific owner, time block, and par level. With limited staff, the goal isn't to do more work — it's to sequence the work so one or two people can produce multiple days of mise en place without bottlenecks or wasted motion. Here's exactly how to do it.
Before you schedule anything, you need a complete inventory of every prep item your menu requires. A to-do list changes daily and lives in someone's head. A master prep list is a fixed document that captures every component your kitchen produces.
For each item, record:
This list becomes the backbone of every schedule you build. When you're short-staffed, knowing shelf life is everything — items that hold for five days can be batched heavily on a slow Tuesday to cover a busy weekend.
A par level is the amount of each prepped item you should have on hand at any given time. Without pars, limited staff either over-prep (waste and spoilage) or under-prep (mid-service scrambling).
Calculate pars from actual usage. If you sell roughly 40 portions of a braise per busy night and the braise holds four days, your par for a Thursday might cover Thursday through Sunday. Track a week or two of usage, then set pars slightly above average demand — not peak, not minimum.
Two par columns help enormously:
This lets a small team prep the exact right amount instead of guessing.
The core principle of any production schedule is reverse engineering. You know when service starts. Everything else is calculated backward from that fixed point.
Ask three questions for every prep item:
1. How long does it take to make? (active labor + passive cooking)
2. When does it need to be ready?
3. What has to happen before it can start? (thawing, marinating, reducing)
A 6-hour braise that needs to rest before portioning can't start at 2 p.m. for a 5 p.m. service. It has to go in the oven that morning — or the day before. Mapping these dependencies prevents the "we can't start X until Y is done" traffic jams that cripple understaffed kitchens.
This is where limited-staff scheduling gets efficient. Instead of prepping item by item, batch tasks by shared equipment and shared technique.
If you have one oven, schedule all roasting in sequence so the oven never sits empty and you never have two items competing for it. If your robot coupe is needed for three purees and two vegetable cuts, do all the dry cuts first, then the wet purees, so you break down and sanitize once instead of five times.
Group by technique, too:
Every setup and breakdown you eliminate is labor you get back. For a two-person crew, this can mean the difference between finishing by noon and finishing at 3.
Now assemble the actual schedule. Divide the prep day into blocks and assign items to each, respecting equipment availability and dependencies.
A simplified example for two prep cooks on a Tuesday:
| Time | Cook A | Cook B |
|------|--------|--------|
| 7:00–8:00 | Start braise (oven), start stock | Break down produce delivery |
| 8:00–9:30 | All vegetable cuts (robot coupe) | Portion proteins |
| 9:30–11:00 | Sauces & reductions | Blanch & shock vegetables |
| 11:00–12:00 | Portion braise, label, store | Cold line mise, dressings |
The braise runs passively in the oven while active labor happens elsewhere. Two people cover an entire menu's prep because nothing overlaps on shared equipment and nobody waits on anyone else.
With limited staff, ambiguity is the enemy. Every task needs a name attached. When "someone" is responsible, no one is. Write initials next to each block so accountability is clear even when the chef steps away.
Label every prepped item with contents, date, and use-by. This isn't just food safety — it lets any team member instantly see what's already done and what's short, so nobody re-preps something that's sitting in the walk-in.
The single biggest lever for short-staffed kitchens is strategic over-batching of stable items. Anything with a long shelf life — stocks, sauces, roasted vegetables, marinades, dry mixes — should be produced in large batches on your slowest days.
Map your week's volume, then front-load production. If Monday and Tuesday are quiet, produce three to four days of shelf-stable components then. This frees your busy Thursday and Friday for only the fast-perishing, made-to-order-adjacent items. Your small team spreads the load instead of drowning on peak days.
Here's the trap: when you scale a recipe to batch quantities, your food cost per portion can drift without you noticing. Doubling a recipe isn't always a clean 2x — yields shift, trim loss changes, and portion sizes creep. If you're building production schedules to save labor, you also want to protect margin.
Cost every batch recipe at the yield you actually produce, and divide by real portion counts. This tells you whether over-batching on Tuesday is saving money or quietly eroding it through waste.
Your first schedule won't be perfect. Track two things each week: what ran out mid-service (par too low) and what got thrown away (par too high or shelf life misjudged). Adjust pars and batch sizes accordingly. Within a month, a well-tuned schedule practically runs itself — which is exactly what a limited crew needs.
---
If you want to nail the costing side of batch scaling, try the free food cost calculator at getprepsheet.com/calculator to check your per-portion numbers, and browse the ready-made Excel costing templates in the shop to build scalable, costed prep sheets without starting from a blank spreadsheet.