Control Room · Ops
Kitchen Prep Time for Multi-Location Delivery: How to Measure, Alert, and Reduce It
Prep time is the window between the moment an order is accepted and the moment it's marked ready for pickup — the part of the delivery clock the restaurant actually controls. It's measured per location, per time slot, and per dish category, and a healthy kitchen usually keeps it in a stable band (often 8–15 minutes for most menus). You reduce it by isolating it from courier and total delivery time, then acting on the outliers.
Ops ritual
If the board doesn't fit on one screen, it doesn't get used. Five metrics, owner, threshold, decision.
When a delivery order runs late, the courier gets blamed first. But the clock doesn't start when the driver arrives — it starts in your kitchen. The single most controllable slice of the delivery timeline is prep time: from order accepted to order ready. If you can't see it cleanly, separated from everything the platform and the road add on top, you're guessing about where the delay lives. This guide shows how to measure prep time, set alert thresholds, and bring it down across multiple locations.
What prep time is (and what it isn't)
Prep time is the interval between accepting an order and marking it ready for pickup. It covers ticket entry, cooking, plating, bagging, and staging — everything that happens inside your four walls. It does not include how long a courier takes to arrive, the drive to the customer, or platform-side matching.
This distinction matters because total delivery time — the number the customer feels — blends three things: prep time, wait-for-courier time, and travel time. Only the first is fully yours. If you optimize the wrong slice, you burn effort without moving the customer experience. Isolating prep time is the first honest step.
The reason this gets confused: many operators read the app's total delivery estimate and assume a slow number means slow cooking. Sometimes the kitchen is fast and the courier hand-off is the bottleneck. Sometimes it's the reverse. You can't tell them apart without measuring prep time on its own.
How to measure it: when the clock starts and stops
Consistency beats precision here. Pick one definition and hold every location to it.
- Start: order accepted / confirmed in the POS or tablet. Not when the ticket is printed, not when a cook picks it up — the moment of acceptance.
- Stop: order marked ready for pickup. This is the honest end of your responsibility.
Then slice the number three ways, because a single average hides the problems:
- By location: two stores with the same menu can run 6 minutes apart. That gap is a management signal.
- By time slot: a kitchen that holds 10 minutes at 3 PM may blow out to 22 during the Friday dinner rush.
- By dish category: a burger and a slow-cooked platter don't belong in the same benchmark. Group by prep complexity.
Track the median, not just the average — one catastrophic 40-minute ticket can drag an average and hide a kitchen that's actually stable. Also watch the P90 (the slowest 10% of orders), because that's where cancellations and bad ratings are born.
How long should prep time be?
A good delivery prep time for most menus sits in an 8–15 minute band, measured as a median. Fast-casual and simple assembly can land under 10; kitchens with grilled or composed dishes may sit higher and that's fine — the target is a stable, predictable band, not a universal number.
The real benchmark is your own baseline. Establish what "normal" looks like per location and time slot for two to four weeks, then treat deviations from that baseline as the thing to chase. A store that usually holds 11 minutes and spikes to 19 every Saturday has a specific, fixable problem — not a mysterious one.
Alert thresholds: green, amber, red
Numbers only help if they trigger action. Build a three-tier system per location and time slot so the floor knows what to do without a meeting.
- Green (on baseline): prep time within the normal band. Action: nothing — keep the rhythm.
- Amber (drifting): prep time creeping above baseline, or the ticket queue building. Action: the shift lead rebalances stations, pre-stages high-frequency items, and pauses low-priority tasks.
- Red (broken): prep time well over baseline or P90 spiking. Action: consider temporarily pausing the busiest items or throttling incoming orders on the app, call in support if available, and log the cause.
Set thresholds relative to each store's baseline, not one global cutoff — otherwise your fastest kitchen never alerts and your slowest one alerts constantly.
Common mistakes that inflate prep time
- Reading total delivery time as kitchen time. You end up drilling the cooks when the delay was courier wait. Separate the metrics first.
- One average across all hours. Peak and off-peak get blended, hiding the exact window that hurts.
- No dish-category view. A slow item drags the whole store's number and gets blamed on the team instead of the recipe or prep flow.
- Marking "ready" early to game the metric. This just moves the delay to courier-wait and damages food quality. Measure honestly.
- Comparing locations by gut feel. Without side-by-side numbers per slot, you can't tell a staffing issue from a menu-mix issue.
Why kitchens slow down at peak — and how to reduce it
Peak-hour delays are rarely about lazy cooks. They come from order concurrency (too many tickets landing at once), station bottlenecks (one grill, five orders), and prep gaps (not enough mise en place staged before the rush). Reducing prep time is mostly a scheduling and staging exercise:
- Pre-stage for known peaks. Use last week's slot-level data to prep high-frequency items before the wave hits.
- Rebalance stations dynamically. When amber trips, move a hand to the choke-point station instead of waiting for red.
- Simplify the peak menu if needed. Temporarily hiding the slowest, lowest-volume items during the rush can protect the whole board.
- Compare best and worst locations. Take what your fastest store does at 8 PM and make it the playbook for the slow one.
This is exactly what Control Room is built for. Pimentón's operational control room isolates prep time per location, time slot, and dish category, then fires green/amber/red alerts when a kitchen drifts from its baseline — so your ops lead acts during the shift, not the day after. Want to see your dispatch times side by side without living in a spreadsheet? Talk to us on WhatsApp.
From number to action
Prep time is only useful when it closes in a decision: reassign a cook, pre-stage an item, pause a dish, or copy a faster store's routine. Measure the slice you control, alert against each location's own baseline, and act at amber instead of firefighting at red. That's how multi-location delivery gets faster without adding drama — or blame — to the equation.
Frequently asked questions
What is prep time in delivery?
Prep time is the interval between the moment a delivery order is accepted and the moment it's marked ready for pickup. It covers cooking, plating, bagging, and staging — the part of the delivery clock the restaurant fully controls, separate from courier wait and travel time.
How is prep time measured and when does the clock start?
The clock starts when the order is accepted or confirmed in the POS, and stops when the order is marked ready for pickup. For a useful read, measure the median (not just the average) and slice it by location, time slot, and dish category.
How long should a good delivery prep time be?
For most menus, a healthy median prep time sits in an 8–15 minute band, though composed or grilled dishes may run higher. The real target is a stable, predictable band per location and time slot — deviations from your own baseline matter more than a universal number.
What's the difference between prep time and total delivery time?
Prep time is only what happens inside your kitchen, from order accepted to ready. Total delivery time — the number the customer feels — also includes courier wait and travel. Only prep time is fully controllable by the restaurant, which is why it should be measured on its own.
When should a kitchen-delay alert trigger?
Set alerts relative to each location's baseline, not a single global cutoff. Green means within the normal band, amber means prep time is drifting above baseline or the queue is building, and red means it's well over baseline or the slowest 10% of orders (P90) is spiking and needs immediate action.
Want clear visibility on your delivery?
Message us on WhatsApp. We'll review what's breaking multi-location rhythm and what to fix first.
Message on WhatsApp