Restaurant table turnover calculator (India)
Track daily covers by meal period and auto-calculate table turnover rate, revenue per cover and revenue per table. Select your restaurant format — QSR, casual dining, fine dining, cafe, bar-led or cloud kitchen — and get benchmark ranges for each metric. Navigate between days, review a rolling 7-day trend, and export CSV for your daily ops report. Saves in browser. No signup.
What is table turnover rate and why it matters
Table turnover rate is the number of times a table is occupied and vacated during a service period. A restaurant with 20 tables and 60 covers at lunch has a table turn of 60 ÷ 20 = 3×. It is one of the most direct measures of floor efficiency — alongside revenue per available seat hour (RevPASH), which combines turn rate with average spend.
In India, the benchmarks vary sharply by format. QSR (quick service) outlets target 3.5–6 turns per day across all service periods combined. Casual dining (the most common format) targets 1.5–2.5 turns per day — a well-run casual dining outlet achieves 1.8–2.2 turns with a healthy lunch + dinner flow. Fine dining operates at 0.8–1.2 turns per day by design — the experience requires dwell time, and the revenue per cover compensates. A fine dining outlet chasing 2× turns is sacrificing the experience and will not retain the customer segment it serves.
Revenue per cover vs revenue per table
Revenue per cover (average transaction value) tells you whether guests are spending in line with your menu price points. A sudden drop in revenue per cover at dinner — without a drop in covers — often means a shift in table mix toward smaller groups or a beverage attach rate problem.
Revenue per table per day is the composite metric: it reflects both how often a table turns and how much each sitting contributes. It is the closest proxy to floor profitability per square foot. In a Mumbai or Delhi casual dining outlet, a revenue-per-table figure below ₹4,000/day on a table with 4 seats typically signals either poor occupancy or a low average ticket — both require different interventions.
How to improve table turnover without hurting the experience
The most effective interventions are operational, not pressure-based. A bill dropped promptly after the main course is cleared — rather than left on request — reduces post-meal dwell time by 8–12 minutes without any perceptible rush. Keeping dessert menus and the billing process concurrent (asking about dessert at the same time as bringing the bill request card) further compresses the exit cycle.
Table management: a waitlist system (even a paper one) eliminates the gap between one party leaving and the next being seated. The average gap in Indian casual dining without a waitlist is 6–10 minutes; with active waitlist management it drops to under 2 minutes. Over a 3-hour lunch service with 20 tables, that is the difference between 1.6× and 2.0× turns.
Where this fits
- Daily sales report (DSR) — the revenue figures you enter here for each period feed directly into the DSR; use the DSR for the channel-wise and tender-wise breakup of the same revenue
- Cash variance calculator — after closing the day, compare the revenue per shift from this tool against the cash + card + UPI tender collected to flag any variance
- Prime cost calculator — with total daily revenue known, feed it into the prime cost tool to see whether COGS + labour stays within the target band
- Monthly P&L statement — 30 days of revenue per cover data aggregated gives you the monthly revenue line; the trend also highlights which weeks or periods dragged down the average
- P1 — Daily cash close pillar — all articles on end-of-day reconciliation, shift handover, and daily KPI tracking for Indian restaurant operators