Restaurant Table Turnover: Why Full Seats Doesn't Mean Full Revenue
A 40-seat restaurant has 2 seatings per night (lunch and dinner). Capacity: 40 × 2 = 80 covers per day. If average check is $35, max revenue is 80 × $35 = $2,800/day. But if one table takes 2.5 hours (lingering after eating), you can't turn it over. One slow table costs 1.5-2 covers. Daily revenue drops to $2,450. Over a year, that's $127K in lost revenue.
- The Table Turnover Economics
- Why Table Timing Matters
- AskBiz: Table Timing & Turnover Tracking
- Seasonal & Day-of-Week Trends
- Real Example: Casual Dining Chain
The Table Turnover Economics#
A fine dining restaurant targets 1.5 covers per table per night. A casual restaurant targets 2-2.5 covers (faster dining). A fast-casual targets 3-4 covers (minimal lingering). If a table takes 90 minutes (appetizer, entree, dessert, coffee) and you have 2 seatings (180 minutes), you get 2 covers. If it takes 120 minutes, you get 1.5 covers = 25% revenue loss. Now, fine dining intentionally targets 1.5 covers (premium experience, high check average). But casual dining doesn't. If a casual restaurant averages 2.2 covers (instead of 2.5), that's 12% revenue loss. Most casual restaurants don't track this metric. They don't know their turnover rate.
Why Table Timing Matters#
Every second a customer sits is either: (1) Happy (lingering after a great meal = good experience, maybe they'll return). (2) Unhappy (waiting for food = bad experience). (3) Wasting your economics (dessert menu sitting on the table for 20 minutes = they're not going to order). Ideal flow: greet → seat → order (5 min) → food arrives (15-20 min) → eat (30 min) → offer dessert (5 min) → pay (5 min) = 60-75 min total. Longer, and you're either providing premium service (worth it for fine dining) or running slow (fix the problem).
AskBiz: Table Timing & Turnover Tracking#
AskBiz POS logs: (1) Seat time (when table is seated). (2) Order time (when order is placed). (3) Serve time (when food arrives). (4) Pay time (when check is closed). From these, AskBiz calculates: (1) Order lag (5 min from seat to order—good). (2) Cooking time (12 min for appetizer, 18 min for entree—is kitchen backing up?). (3) Eating time (30 min—customer satisfied or rushing?). (4) Time-to-close (5 min from pay to table cleared—good). (5) Total seat time (90 min for 2-course, 75 min for 1-course). (6) Covers per table per night (calculated from seat times and seatings). AskBiz shows: "Tuesday night: avg table time 94 min (target 85 min). Covers per table: 1.9 (target 2.3). Issue: Order lag is 12 min (target 5 min). Ask host to seat slower or tell servers to take order faster."
Seasonal & Day-of-Week Trends#
Table timing varies by: (1) Day of week (weekends are busier, people linger more). (2) Time of night (early seatings eat faster; late seatings linger). (3) Season (slower in off-season, people are in no rush). AskBiz tracks by day/time: "Friday nights: table time 105 min (people celebrating, lingering). Wednesday afternoons: 68 min (businesspeople in a rush). Adjust staffing and menu accordingly."
Real Example: Casual Dining Chain#
A 10-location casual restaurant chain was averaging 1.8 covers per table per night (target: 2.3). That's 22% below target. After tracking table timing with AskBiz, they found: (1) Order lag was 10 min (servers were slow). (2) Cooking time was 25 min for 15-min dishes (kitchen backing up). (3) Dessert upsell dropped from 40% to 15% over the year (wasn't offered properly). Fixes: (a) Train servers on faster order-taking (use tablets). (b) Optimize kitchen workflow (reduce 15-min dishes, swap for faster items). (c) Retrain on dessert upselling. (d) Monitor speed with AskBiz weekly. Result: Covers per table increased from 1.8 to 2.2 (22% improvement). With avg check $28, that's an extra $2.2 covers × $28 × 10 locations × 300 days/year = $1.8M in additional annual revenue. All from understanding and optimizing table turnover.
Setting Up Table Timing Tracking Without Slowing Down Service#
The concern most restaurant owners raise first is that timing every stage of service will add friction for servers already stretched during a rush. In practice, AskBiz captures most timestamps automatically from natural POS actions already happening — a table is marked seated when the host assigns it, order time is logged the moment the order is sent to the kitchen, and pay time is logged when the check closes, all actions staff perform anyway. The only added step is marking "food delivered" when a dish reaches the table, which takes a single tap and is worth the small friction because it's the one data point that distinguishes a slow kitchen from a slow server. Restaurants that roll this out successfully train on it during a slow shift first, not a Friday night rush, and frame it to staff as a tool that protects them — a server whose section runs slow because the kitchen is backed up wants that documented just as much as management does.
Common Mistakes When Optimizing for Table Turnover#
The first mistake is optimizing turnover uniformly across all tables and times, ignoring that a Friday 7pm turn should look different from a Tuesday 2pm turn — pushing faster turns during a slow Tuesday lunch when the dining room is half empty just rushes customers for no operational benefit. The second mistake is treating every minute of table time as waste — an extra 10 minutes at the end of a meal where the table lingers over coffee after paying is not lost revenue if the dining room isn't at capacity waiting for that table; the metric only matters when there's actual demand for the seat. The third mistake is fixing table speed by rushing service rather than fixing the actual bottleneck — if cooking time is the constraint, training servers to take orders faster just shifts the wait from the table to the kitchen pass, with no net improvement in covers per table and a service experience that feels rushed for no gain.
People also ask
What's a good covers-per-table metric?
Fine dining: 1.2-1.5. Upscale casual: 1.5-2. Casual: 2-2.5. Fast-casual: 3-4. Fast food: 4-6. Benchmark against your concept.
What if customers want to linger?
That's fine for ambiance (especially fine dining). But if casual restaurant has 2-hour sitters, there's a problem (maybe bad service, slow kitchen, unclear when to pay). Investigate.
Can I speed up table turnover without losing customers?
Yes. Optimize: (1) Order speed (train servers, use tech). (2) Kitchen speed (streamline menu, better workflow). (3) Payment speed (offer mobile pay). Don't rush customers—optimize processes.
How do I track covers if I have a bar?
AskBiz can track separately: dining tables vs. bar stools. Bar typically has 1 cover per shift. Dining tables 2-3. Different targets.
Our team combines expertise in data analytics, SME strategy, and AI tools to produce practical guides that help founders and operators make better business decisions.
Unlock $500K-$2M Annual Revenue From Table Optimization
AskBiz tracks table timing, calculates covers per table, identifies bottlenecks. Increase turnover by 10-15% without cutting experience. Try free for 14 days.
Connects to Shopify, Xero, Amazon, QuickBooks, Stripe & more in minutes