Why is restaurant service slow? A 9-point diagnosis from seat to check

Slow service is rarely slow everywhere. It is usually one or two gaps: waiting for someone to take the order, orders reaching the kitchen late, a pass where plates sit, or the long wait for the check and then the card machine. The fix starts with a stopwatch, not a staff meeting. Time nine points from seating to payment on a few busy nights, find the longest gap, and fix that one first. This post gives the nine points, the usual cause and fix for each, a timing sheet and a worked diagnosis.

Why are restaurants so slow right now?

Short answer: staffing is part of it, but most slow nights come down to a few gaps that can be measured.

Staffing has eased since 2021 but hasn’t recovered everywhere. About a third of operators (32%) said they “don’t have enough employees to support existing customer demand”, per National Restaurant Association research reported by FE&S (FE&S, 28 Apr 2026). And accommodation and food services had a quits rate of 4.2% a month in 2025, about twice the 2.2% across all private industry (BLS JOLTS, Table 22). A team that keeps losing and training people is slower than one that doesn’t.

But a full team can still be slow, and a short team can be quick, depending on where the minutes go. Guests are clear about which minutes they mind. Asked where technology should help most at full-service restaurants, diners picked making paying easier and faster (30%) and making ordering easier and faster (28%) (NRA, 2024). Not the food. The waits around it.

Where does the time go in a table-service meal?

Short answer: in nine handovers, from the moment a party sits to the moment it has paid.

1. Seated to greeted. Someone acknowledges the table.
2. Greeted to order taken. Guests decide, and someone takes the order.
3. Order taken to ticket in the kitchen. The order reaches the people who cook it.
4. Ticket to dish at the pass. The kitchen’s own time.
5. Pass to table. Someone carries it.
6. Mid-meal requests. A second drink, more bread, a missing fork.
7. Finished to cleared. Plates go, and dessert or coffee is offered.
8. Check requested to check at the table.
9. Check at the table to paid. Often a second wait, for the card machine.

Points 4 and the eating itself belong to the meal. Most of the others are waits for a person, and those are where slow service usually hides. Our post on how long guests should wait to order looks at point 2 in depth.

What causes each delay, and how do you fix it?

Short answer: each point has a usual suspect. This table is the diagnosis sheet.

If you only fix one thing, fix the waits in rows 2, 8 and 9. They are the ones guests did not choose, and they add nothing to the meal.

How do you time your own service?

Short answer: one person, one clipboard, eight tables, two busy nights.

Ask a manager or a trusted server to follow eight tables from seating to payment, writing the clock time at each point. Use the same sheet both nights:

Then work out each gap in minutes, average it across the tables, and circle the longest controllable gap. Don’t time the eating; that belongs to the guests. A few practical points:

• Pick ordinary busy nights, not the night a party of 30 walked in.
• Mid-meal requests (point 6) are counted separately: note each one and how long it took to be answered.
• Tell the team what you’re doing and why. You’re timing the system, not the people.

A worked diagnosis at Casa Olivo

Short answer: in this example, guests spend 25 minutes waiting for a person at three points, more than the kitchen takes to cook.

Casa Olivo is a fictional restaurant (an example, not a customer). The times are invented to show how to read the sheet, not measurements.

Average over eight tables on a Friday:

The kitchen’s 18 minutes is the single longest gap, but the chef says it’s normal for the menu, and dishes don’t sit at the pass. The floor is the story: 11 minutes to get an order taken, then 8 and 6 minutes to pay. That’s 25 minutes of waiting for a person at points 2, 8 and 9. The owner’s three changes for next Friday:

1. Let guests order from their phones when they’re ready (point 2).
2. Let guests ask for the check from the table, and bring the card machine with it (points 8 and 9).
3. Put a busser on from 7:30 to 9:00 (point 7).

Then time the same eight tables again.

Is it the kitchen or the floor?

Short answer: compare when tickets reach the kitchen with when dishes reach the pass.

If tickets arrive late and the kitchen turns them around quickly, the floor is slowing things down: orders are being taken late or entered late. If tickets arrive promptly and sit, it’s the kitchen. If plates wait at the pass, nobody is running. Fix the right one: a new cook won’t help a floor problem, and a new ordering tool won’t help a kitchen that’s overloaded. When everything arrives at the kitchen at once, read the rush-hour playbook for how to pace it.

What does faster service do to table turns?

Short answer: shorter waits mean shorter meals without anyone eating faster.

In a peer-reviewed study of a 66-restaurant US casual chain, tabletop ordering devices raised sales per check by about 1% and cut meal duration by about 10% (Tan and Netessine, reported by Restaurant Technology News, 2019). A Cornell report on one chain found guests who paid on a tabletop device turned their table in 45 minutes 21 seconds, against 53 minutes 45 seconds for those who didn’t (Susskind and Curry, Cornell, 2016, p. 7). That second result is observational, since guests chose whether to use the device, and a co-author worked for the device vendor.

Faster turns matter most when guests are waiting for tables. On a quiet night, the gain is a calmer team rather than more covers. How to increase table turnover without rushing guests works through the numbers.

Where does WaiterPilot help, and where doesn’t it?

Short answer: it shortens the waits for a person at points 2, 3, 6, 8 and 9. It does nothing for the kitchen, and payment still happens with staff.

On the staff board, waiting orders and calls change colour at 1, 5 and 10 minutes, so delays show during service. Afterwards, the owner page reports time to staff confirm, kitchen time and time to answer calls, which are three of the nine points timed for you. One more honest limit: WaiterPilot has no POS connection, so if you use a till, someone rings the orders into it.

What to do next

1. Print the timing sheet and follow eight tables on your next two busy nights.
2. Circle the longest gap you control, and pick one change for it.
3. Time the same tables the following week.

To see the guest side of ordering from the table, read QR table ordering or try a sample order. For points 6, 8 and 9 in detail, see waiter call and bill. And if you’re weighing a tool for points 2, 8 and 9, compare the options side by side, with prices as published.