Table Turnover

Table turnover rate is calculated with a simple formula:

For example: if a 20-table restaurant serves 70 guests during a dinner service, the turnover rate is 3.5.

You can also measure average table time — the minutes from seating to reset — which is the operational inverse. If a service window is 4 hours and your average table time is 80 minutes, your theoretical maximum turnover per table is 3.

What counts as a good rate? It depends entirely on your concept:

• Quick-service or fast-casual: 5–8+ turns are expected
• Casual dining: 2–3 turns per service is typical
• Fine dining: 1–1.5 turns is often intentional — the experience is the product

Compare yourself to your own past performance, not an industry benchmark that may not match your format.

A restaurant's revenue ceiling is set by two things: average spend per cover and how many covers it can serve. Physical capacity is fixed, so table turnover is the primary variable a full-service restaurant can optimise.

Consider the math: adding one extra turn per night on 10 tables, at an average spend of 400 SEK per cover and 2 guests per table, adds 8 000 SEK in a single evening — without hiring extra staff or expanding the floor.

Where time actually gets lost:

• Guests waiting too long for menus or a first greeting
• Gaps between courses caused by kitchen bottlenecks or poor pacing communication
• Bill delivery delays — many operators find this is the single biggest controllable drag
• Tables sitting reset but unassigned because the host stand is overwhelmed

Tracking turnover by day part (lunch vs. dinner), by section, or even by server helps you isolate where the slowdown is actually happening — rather than guessing.

Important caveat: turnover rate is a throughput metric, not a satisfaction metric. A table that felt rushed will not return. The goal is eliminating waste from the guest experience, not compressing the experience itself.

The best operators raise turnover by removing friction, not by applying pressure. Practical levers:

Pre-service and seating

• Use a reservation system that staggers arrival times to avoid simultaneous seating waves that overwhelm the kitchen
• Greet tables within 60–90 seconds — guests who feel acknowledged are less anxious and decide faster
• Have menus on the table before guests sit if your layout allows it

During the meal

• Train servers to read table pace and communicate it to the kitchen — a couple on a date needs different pacing than a table of colleagues on a lunch break
• Reduce course gaps by standardising kitchen ticket timing, not by skipping steps
• Offer the bill proactively once dessert plates are cleared; many guests are ready but waiting for permission

Payments

• Pay-at-table or QR-code payment options consistently cut bill-close time. Many restaurants find this alone recovers 10–15 minutes per table at peak service
• Pre-authorise cards for reservations to reduce no-shows, which protects your usable covers

Scheduling and staffing

• Match server section sizes to realistic turn expectations — an understaffed section degrades pacing regardless of kitchen speed
• Review your slowest-turn tables weekly; often a single procedural fix (a closer printer, a clearer section boundary) resolves a persistent drag

Restora's operational dashboards can surface table-time data by shift and section, making it easier to act on trends rather than gut feel.