Kitchen ticket time control: traditional method vs the Masterestaurant method

Step 1: capture four timestamps per ticket, not one

The first deliverable of this guide is a ticket that records four timestamps instead of one: arrival at the KDS, station start, plate finished, and server pickup. Measuring only the full ticket exit gives you a comforting number that hides where the time went, which is why that 70-seat kitchen in Chapinero believed it was firing in 15 minutes while the 90th percentile read 31. With four stamps you can see the ticket landed at 20:41, the grill started it at 20:49 —eight dead minutes in queue— and the plate sat four minutes in the window waiting for a server. Verification: export 200 tickets from one service and confirm all four marks exist on 95% or more. If stamps are missing, your problem is not the kitchen, it is the capture. Every station needs its own target, because cold apps and grill do not play in the same league: a salad leaves in 4 minutes and a medium-rare loin needs 18 to 22, and averaging both produces a number that describes no real guest.

Step 2: set a target per station and stop governing by the house average

Set the target from your own kitchen history, not from a figure found online: take the 50th percentile of the last two weeks per station, cut 15%, and that is your starting target. A traditional restaurant turns a table in 1.5 to 2 hours according to The Restaurant HQ, and lunch for two runs about 45 minutes, so every minute you shave in the kitchen becomes an available seat rather than an efficiency medal. The deliverable is a sign at each station showing two numbers: target and yesterday's p90. If your average is 19 minutes and your p90 is 38, you do not run a fast restaurant: you run a fast restaurant with a furious minority, and that minority opens Google Maps the moment it gets home. The 90th percentile describes what the worst tenth of your guests actually lived, and that tenth weighs more on your reputation than the other nine combined.

Step 3: govern with the 90th percentile, because that guest writes the review

According to Anne McBride, vice president of programs at the James Beard Foundation, operational consistency sustains a kitchen's reputation far more than any signature dish, and p90 is the cheap way to measure consistency. Calculate it per service and per station: sort your times low to high and take the value that leaves 90% below it. Measurable deliverable: a weekly sheet with p50 and p90 per station, plus the gap between them in minutes. Fixing a single station drops your full ticket time by 5 to 9 minutes without hiring anyone, and that is the highest return available in kitchen operations. The bottleneck almost never sits where the chef believes: usually it is the flat top sharing fire with sautés, the oven opened twelve times a service, or the station doing mise en place at midnight on a Friday. Pick the station with the widest gap between p50 and p90 —not the slowest on average— because that is where the variance lives.

Step 4: attack the bottleneck station, one only, for two weeks

Change one thing: more mise, another pan, moving a product to another station, or splitting the dish into two passes. Two weeks, one variable, measurement before and after. The deliverable is a p90 comparison of the treated station against its own baseline, expressed in minutes and in extra tables per service. The most expensive mistake is using the clock as a whip: the moment your team understands the number exists to scold them, they start marking exit before plating and you lose the data forever. I got this wrong for years, selling measurement as pressure when it is exactly the opposite. The second mistake is measuring only at peak and believing that is your restaurant; measure Tuesday at 13:10 too, because comparing valley against peak tells you whether the problem is method or staffing. The third is changing two things at once and never knowing which one worked. And the fourth, the quietest: counting time to the window instead of to the table, while the plate goes cold for four minutes waiting on a server who is running a check.

The four mistakes that ruin this measurement

Masterestaurant instruments the pickup precisely for that reason. Suppose you leave p90 at 38 minutes for a full quarter. The dine-in guest waits, never returns and never complains —roughly 96% of unhappy customers say nothing, they simply vanish—; the delivery guest does write, and your Maps listing collects three one-star reviews containing the word «slow». Platform algorithms read your ticket time and send you fewer couriers, so orders leave colder and the reviews get worse. With brands above 68% off-premise sales growing 3 percentage points faster than the rest in 2024, according to Black Box Intelligence, you are bleeding the channel that grows. None of this shows up in your P&L as a line called «times»: it shows up as flat sales and a food cost creeping up because you keep throwing away reheated product. A timing system that never translates into cash dies by the third month, so run the arithmetic in front of the team.

Step 5: turn minutes into money before the management meeting

If your six-top at dinner holds 90 minutes according to The Restaurant HQ and you cut 7 minutes of kitchen time, you gain 7.8% of capacity on that table; with 40 dinner tables and a 22 dollar average check, that is about three extra tables per service and roughly 66 dollars a night. Multiply by 26 nights and you have 1,700 dollars a month that came from a stopwatch, not a campaign. Add the waste savings: food service threw away 290 million tonnes of food in 2022 according to UNEP's Food Waste Index Report 2024, and part of that is plates returned cold. Deliverable: one slide with minutes, tables and money. You finished this guide well when you can answer five questions without opening a system. First: do 95% of last service's tickets carry all four timestamps? Second: does every station have a sign with its target and yesterday's p90, and did the team read it before doors?

Closing checklist: how to know everything landed

Third: did the gap between p50 and p90 on the station you treated drop at least 5 minutes against its baseline? Fourth: does someone review the number every day at the same hour, in three minutes, without turning it into a meeting? Fifth: can your manager state, in money, what the quarter's improvement was worth? If the fourth one fails, the system dies on its own within six weeks. Pick tomorrow the station with the widest gap and give it a target today, before dinner service. MEASURE BY STATION, NOT BY TICKET. The full-ticket average is a consolation number: it hides the fact that your grill delivers in 22 minutes while the cold line plates in 4, and that the guest gets a lukewarm salad because it waited on the steak. Split the measurement by station and you find the bottleneck is almost never where the chef assumed, and fixing one station shaves 5 to 9 minutes off the entire ticket without hiring anyone.

Four differences that change the outcome

That is marginal efficiency in its purest form. GOVERN WITH p90, NOT WITH THE AVERAGE. An average of 19 minutes alongside a p90 of 38 means you run a fast restaurant with a furious minority, and that minority writes the reviews. The ninetieth percentile mirrors the experience of your worst-served tenth, which is precisely the group that sits down to rate you on Google Business Profile. Change the number you watch and you change what you fix. TREAT PREP TIME AS A LOCAL MARKETING VARIABLE. Delivery platforms route orders toward venues whose declared time matches their fulfilled time; promise 15 and deliver in 28 and the courier waits, the order flags late, your storefront slips down the carousel. Raising your declared prep time feels like surrender and it is the opposite: an honest venue at 22 declared minutes, consistently met, outranks one promising 15 and missing 40% of the time.

Four differences that change the outcome — in practice

WRITE THE STANDARD SO IT OUTLIVES THE CHEF. A kitchen's operational maturity test is the Tuesday the head chef does not show. If p90 spikes that day, you do not own a process; you own a person. The spec sheet with a target time per dish, backed by timed kitchen training, converts individual talent into process standardization, and it also protects food safety, because exposure time in the 5 °C to 60 °C danger zone stops being improvised.