How Many Tables You Turn Is a Kitchen Question

A full dining room with a line at the door feels like a floor problem. Tables sit. Plates stay down. Somebody has not dropped a check. So you lean on the servers, and next Saturday looks exactly the same.

Most of the time the floor is not the cap. The pass is. A server can clear, reset, and seat a four-top in four minutes. If the kitchen is running twenty-eight minutes on entrées when it runs sixteen on a Tuesday, you just added twelve minutes to every turn in the building and no amount of hustle on the floor gets it back. Before you change anything about service, you need to know which part of the clock is actually stretching.

Four timestamps, one notepad

You do not need a new system to find this. You need four times per table, written down, for two or three services.

1. Seated — guests sit.
2. Fired — the ticket hits the kitchen.
3. Entrées down — the last main lands on the table.
4. Table clear — the guests are gone and it is reset.

Do it for twenty tables on a slow night and twenty on your busiest night. Most POS systems will give you fired and closed times already. The two you have to catch by hand are seated and entrées down, and that is the whole reason nobody does this.

Then subtract. Seated-to-fired is your service greeting and ordering time. Fired-to-entrées-down is kitchen ticket time. Entrées-down-to-clear is dining, check, and reset. Now compare the slow night to the busy night, segment by segment.

In almost every room we have timed, one segment is stable and one balloons. Greeting and ordering might go from six minutes to nine. Dining and payment barely move, because people eat at the speed people eat. Ticket time goes from fifteen to thirty. That is your answer. The floor got a little slower. The kitchen doubled.

If the opposite is true — ticket times hold steady and seated-to-fired blows out — then you genuinely do have a floor problem, and it is usually a staffing or section-size problem rather than an effort problem. We wrote about matching bodies to the shape of your day in Your Staff Schedule Is a Labour Cost Decision.

Find the station, not the shift

"The kitchen is slow" is not actionable. One station is slow. Stand at the pass during a rush with the same notepad and mark which component the expo is waiting on when a ticket sits.

You will see a pattern inside ten minutes. It is the grill waiting on rest time. It is the fryer, because three different menu items need the same basket. It is the one person plating every salad, including the two salads that are technically appetizers but somehow get fired with mains. It is a sauce that gets finished à la minute because that is how you learned it.

That single station sets the ceiling for the whole restaurant. Everything else in the kitchen is waiting on it, and every table in the dining room is waiting on that.

The levers that do not cost you anything with guests

Once you know the station, the fixes are usually unglamorous.

Move work earlier. Anything that can be done at 3 p.m. should not be done at 7:30. Portioned proteins, blanched vegetables, sauces held hot, garnish trays built. Walk your prep list and ask which items exist only because somebody decided they taste better finished to order, and be honest about whether a guest could tell.

Raise pars on the bottleneck item. If the fryer is the cap, running out of par-cooked fries at 7 p.m. costs you every table after that. Track what you actually ran out of last Saturday, not what you think you ran out of.

Rebalance the menu across stations. Count how many of your top ten sellers touch the same station. If seven of them hit the grill, your grill cook is your restaurant. Moving one or two popular items to a station with slack — an oven dish, a cold plate, a braise — can take minutes off the average ticket without changing a single price. This is also worth doing while you are already looking at contribution margins, which we covered in How to Price a Menu When Food Costs Keep Moving.

Seat in a rhythm, not in a clump. Seating three tables in the same four minutes sends three tickets to the pass at once and the third one waits for both of the others. Spacing those same three tables across ten minutes does not make anyone wait longer at the door — the host just holds for a beat — and it keeps the kitchen from eating a queue. Your host is effectively dispatching work to the kitchen. Give them the authority to pace it.

Get interruptions off the expo and the manager. Every phone call during the rush pulls someone's attention away from the pass. Takeout calls, reservation questions, a delivery driver who cannot find the side door. Routing orders and basic questions to something that does not need a human — online ordering, an answering agent — is a kitchen speed fix disguised as a tech purchase. We went into this specifically in What to Do With the Phone During Your Dinner Rush.

Shorten the pay step, not the meal. The gap between "we're done" and "we're gone" is real time and it is usually dead time. Pay-at-table terminals, a QR check, or just a server rule that the check gets offered when the last fork goes down will recover a few minutes per table and nobody feels pushed, because guests want to leave at that point too.

Rushing people is not a lever

Pre-bussing aggressively, standing at the table, clearing while one person is still eating, dropping the check before anyone asked — all of it recovers a handful of minutes and costs you the thing you were trying to protect. People notice. They notice enough to mention it in a review, and a review about feeling rushed does more damage to next month's bookings than one extra turn does for tonight.

The math also does not work. If dining time is 55 minutes and you squeeze it to 50, you gained five. If ticket time drops from 28 minutes to 18, you gained ten, and the guest's experience got better instead of worse. Your biggest available win and your guest's interest point in the same direction. That is rare. Take it.

There is one honest exception: very long post-meal lingering on a night with a wait at the door. Handle it with hospitality, not pressure. Offer to move the party to the bar for another round. You free the table and keep the sale.

Re-time it after you change something

The reason to write the numbers down is so you can tell whether the fix worked. Change one thing — move a dish off the grill, raise a prep par, hold tickets in the host stand for a few minutes — and time twenty more tables.

Most owners skip this and end up arguing about whether Saturday felt better. Timed tickets end that argument in a week. And once you know your real ticket time by station, you also know how many covers you can actually serve, which is the number you need before you buy another ad or add another shift.

If you want the ordering and phone side handled so your pass stays clear during the rush, that is most of what we build for restaurants. But start with the notepad. The notepad is free, and it will tell you whether you need anything else at all.