Cook times: the myth of the average main

Ask a chef how long a main takes, and you will often hear a single number: twelve minutes, perhaps. It sounds precise, and it is useful for a rough plan. But no table orders the average main. A table orders a pasta that takes six minutes, a steak that takes fourteen and a confit duck leg that needs twenty, and all three must arrive together. That table's mains take twenty minutes, not twelve.

Cook times are one of the most misunderstood numbers in a kitchen. The average hides the dishes that actually decide how long tables wait: the slow ones. One slow dish drags every ticket it sits on, ties up its station and can turn into a bottleneck for the whole room.

This guide covers why the average main misleads, how to measure cook times properly, how a slow dish shapes a service, and how to plan a menu and a service around its slowest component. Every venue and figure in it is an example.

An average cook time treats every main as if it were the same. Add up the cook times of every main on the menu, divide by the number of mains, and you get a figure that describes no actual dish and no actual table.

The problem is that tables do not order the average. They order a mixture, and the table's plates must arrive together. So the time a table waits for its mains is set by the slowest dish on the table, not by the average of its dishes.

A menu with one twenty-minute dish among ten-minute ones does not have an average cook time of eleven minutes in any useful sense. Every table that orders the slow dish waits twenty minutes, and those tables are often the ones that notice.

Even a single dish does not have one cook time. A steak cooked rare takes less time than one cooked well done. A dish cooked at a quiet moment is faster than the same dish cooked when the station has ten tickets waiting. A new cook takes longer than an experienced one.

So describe each dish by a range: its typical time and its slow time. The median, the middle value of all the times recorded, is a better guide to the typical time than the average, because a few very slow tickets do not drag it up. The slow end, such as the time that nine tickets in ten beat, shows what happens on a bad night.

A dish whose median is twelve minutes but whose slow end is thirty is a dish with a problem at peak, even if it looks fine on average.

Within a dish, the slowest component sets the time. A steak that takes fourteen minutes on the grill, served with fries that take four and a sauce that is ready, takes fourteen minutes, plus the time to plate. A dish with a slow-roasted vegetable that must be finished in the oven takes as long as the vegetable, whatever the rest.

That is why planning a dish around its slowest component matters. If the slow component can be prepared in advance, the dish's cook time in service falls to the time of the next slowest one. If it cannot, the dish will always take as long as that component.

Look at each dish's components and ask which one sets its time. The answer often shows where an easy saving lies.

Within a table, the slowest dish sets the time. A table of four with three ten-minute mains and one twenty-minute main waits twenty minutes, and the other three plates either wait under the lights or are started later so they finish together.

That is why a single slow dish has an effect far beyond its own sales. If the slow dish appears on one table in three at the busiest hour, one table in three waits for it, and the kitchen spends the evening timing other plates around it.

When you look at cook times, look at how often each slow dish appears on a table at peak, not only at its own time.

A slow dish also affects tables that never order it. While it cooks, it occupies space on the grill, in the oven or in the cook's attention. A station with three slow dishes on the go has less room for everything else, so other tickets wait longer too.

At the busiest hour, that can turn a slow dish into one of the kitchen bottlenecks: the station that cooks it falls behind, the pass waits for its plates and the whole room slows. Our guide to kitchen bottlenecks: finding the station that stalls covers how to find the real constraint.

A dish that sells well and cooks slowly deserves more attention than its share of sales suggests.

The best measure of cook times comes from ticket times: how long each ticket takes from arriving in the kitchen to being completed. Ticket times include the waiting as well as the cooking, which is what the guest experiences.

Look at ticket times for the tickets that include each slow dish, and compare them with tickets that do not. If tickets with the duck take eight minutes longer at peak than tickets without it, that is the duck's real cost to the service.

Measure over several weeks and several busy nights, so one unusual evening does not mislead you. Our guide to ticket times: the only kitchen metric that moves covers how to measure and read them.

The same dish can have very different cook times depending on how it is ordered. A steak cooked rare may take eight minutes; the same steak well done may take eighteen. A table where one guest orders well done waits for that steak, and the other plates wait with it.

Treat cooking points as part of the cook time. Brief servers that a well-done steak should be fired a few minutes before the rest of the table, and make sure the grill sees it coming. Some kitchens butterfly or finish well-done steaks in the oven to bring the time closer to the rest. Whatever you choose, plan for it, because on a busy night several tables will order well done.

Cook times change through the evening. A dish that takes twelve minutes at six o'clock may take eighteen at eight, because the station is busier, the oven is full and the cook is juggling more tickets.

Look at cook times at the busiest hour separately from the rest of the day. The busiest hour is when cook times matter most, because it is when the most tables are waiting and the kitchen has the least room to absorb a slow dish.

A dish that is fine at lunch may be a problem at dinner. Plan around the hardest hour, not the easiest.

Guests do not experience cook times; they experience waits. The wait between ordering and the first course, the gap between courses and the time from the last plate to the bill all shape how a meal feels. A twenty-minute main is acceptable after a starter that arrived promptly and a server who kept the table informed; it feels long after a slow starter and silence.

That means cook times are only part of the picture. A slow dish can be absorbed if the rest of the meal is well paced and the table knows what to expect. A quick dish can still feel slow if it waits under the lights while the server is elsewhere.

Once you know the slow dishes and their slowest components, you can plan around them. Start with the components: can the slow part be prepared in advance and finished quickly in service? A confit leg cooked in the afternoon and crisped to order takes a few minutes in service, not two hours.

Then look at the menu as a whole. Does each station have a mix of quick and slow dishes, or does one station carry all the slow ones? Are the slowest dishes the best sellers, or occasional orders? A menu with too many slow dishes on one station will always strain that station at peak.

Our guide to menu size: why thirty dishes is usually too many covers how the number and mix of dishes affect the kitchen.

Much of a slow dish's cook time can be moved out of service. Par-cooking, braising in advance, portioning, preparing sauces and setting up garnishes all reduce the work left when the order arrives.

Good mise en place is the cheapest way to cut cook times in service. A station that starts service with everything prepared spends its time cooking and plating, not chopping and searching.

Look at each slow dish and ask what could be done before service. The answer may cut minutes from every ticket the dish sits on.

All day totals are the running count of each dish on order across every open ticket: eleven steaks, four of them rare, or six portions of fries. Chefs use them to batch work, so a station cooks several of the same dish at once rather than one at a time.

Batching can cut cook times sharply for dishes that cook well together, such as fries, roasted vegetables or certain sauces. It works less well for dishes cooked to order, such as steaks at different cooking points.

Even without a screen that counts them, a chef can call all day totals at the pass, so each station knows what is coming. Knowing the totals also shows when a slow dish is about to swamp its station.

When a table orders a slow dish, the kitchen can start it earlier, so all the plates still arrive together. A twenty-minute dish fired when the starters arrive, rather than when they are cleared, can be ready at the same time as the quick dishes fired later.

That needs the floor and the kitchen to know which dishes are slow. Brief servers before service on the dishes that need an early fire, and make sure the kitchen sees them coming. Our guide to course firing: mains away when the starters clear covers how to time the fire.

Firing slow dishes early does not reduce their cook time, but it hides it from the guest.

Cook times also shape what you tell guests. A dish that takes twenty-five minutes should be described honestly on the menu or by the server, so guests choose it knowing the wait. A guest told "the duck takes about twenty-five minutes" is far happier than one left wondering why their table waits.

The same applies to walk-ins at a busy hour. If the kitchen is running long, the host should know, so the wait quoted at the door reflects what the kitchen can deliver, not only when a table will be free. Our guide to quoting a wait time you can actually keep covers the door's side of it.

Honest quotes, based on real cook times, protect the guest's evening and the team's credibility.

When one dish on a table is slow, the others wait for it. Some dishes hold well for a few minutes: a braise, a gratin, a piece of meat resting. Others do not: fries go soft, fish overcooks under the lights and a sauce splits.

Plan the timing so the dishes that hold badly are finished last. A cook who starts the fish when the slow dish is five minutes from ready, rather than at the same moment, sends both out at their best. That is part of reading cook times: knowing not only how long each dish takes but how long it can wait.

Most kitchens keep cook times in the chef's head. Writing them down makes them useful to everyone. A simple sheet listing each dish, its typical and slow cook time, its slowest component and what can be prepared in advance gives the floor what it needs to fire well and the kitchen what it needs to plan.

Update the sheet when the menu changes and when the ticket times show something new. Use it in the pre-service briefing to remind the team which dishes need an early fire tonight, and in menu planning to check that no station carries too many slow dishes.

The floor needs to know cook times as much as the kitchen does. A server who knows the duck takes twenty-five minutes can tell the guest, fire it early and plan the table's pace. A server who does not will fire it with the rest and then apologise for the wait.

Share the slow dishes in every briefing, especially new dishes and specials. Some venues mark them on the servers' copy of the menu. The goal is simple: nobody on the floor should be surprised by how long a dish takes.

Sometimes the best answer is to limit a slow dish at the busiest hour. A dish that ties up the oven for twenty-five minutes might be offered only until eight o'clock, or limited to a set number of portions at peak, or replaced on busy nights by a quicker dish.

That is a commercial decision as well as a kitchen one. A slow dish that is the restaurant's signature may be worth its time; one that sells rarely and slows every table may not.

Look at the evidence: how often it sells at peak, how much it slows other tickets and what guests say about it. Then decide.

A new dish often performs differently in service from how it performed in testing. Cooked alone at three in the afternoon, it takes twelve minutes. Cooked at eight o'clock, alongside ten other tickets, with the oven full and the station busy, it takes twenty.

Test new dishes in conditions as close to service as you can: during a real service, at a busy hour, cooked by the cook who will make it every night. Measure the ticket times for the first few weeks after the dish arrives, and compare them with the tickets that do not include it. That shows its real cost to the service before the dish becomes a fixture.

An invented brasserie quotes "about twelve minutes" for its mains. Guests at busy times often wait twenty-five. The kitchen blames the volume; the floor blames the kitchen.

The brasserie looks at its ticket times for a month, comparing tickets with and without each main. Most mains add little time. One dish, a slow-roasted pork belly finished to order, adds nine minutes to every ticket it sits on at peak, and appears on one table in four. The oven it uses is also needed for two other dishes.

The brasserie changes the method: the pork belly is roasted in the afternoon and crisped under the grill in service, cutting its cook time from twenty-two minutes to eight. The servers are briefed to fire it early. Waits at peak fall to around fifteen minutes, and the pork belly keeps its place on the menu.

In servearound, every ticket shows its age as it counts on the kitchen screen, so a station falling behind on a slow dish is visible during service. Kitchen analytics then show the evidence for any range of dates: median and P90 prep time, where the minutes go between the queue, prep and the pass, ticket time by day and hour, which dishes cost the kitchen the most time, and the slowest tickets with the dishes on them.

On the door's side, the host enters each party's quoted wait when adding them to the waitlist, and each party's card shows how long they have waited against that quote, so parties running past their quote stand out. See Analytics and Order Fulfillment.

Tables do not order the average. The slowest dish on a table sets how long the table waits.

Each dish's typical time, using the median, and its slow time, at the busiest hour as well as the quiet ones.

Its slowest component. Preparing that component in advance can cut the dish's time in service sharply.

It occupies equipment and the cook's attention, so other tickets at the same station wait longer too.

The running count of each dish on order across open tickets, used to batch work and see what is coming.

Yes, so all the plates on a table arrive together. Brief the floor on which dishes need it.

Yes. An honest quote keeps the guest happy and protects the kitchen.

When it slows many tables, sells rarely at peak or cannot be prepared in advance, weighed against its value to the menu.

Cook times are a range, not a single number, and the average main describes no real table. The slowest component sets each dish's time, the slowest dish sets each table's time, and a slow dish that sells well at peak can slow the whole room. Measure each dish's typical and slow times from ticket times, at the busiest hour especially.

Plan the menu around its slowest components: prepare what you can before service, spread slow dishes across stations, batch with all day totals, fire slow dishes early, tell guests honestly, and limit a slow dish at peak when the evidence says it costs more than it earns.