Restaurant Table Turnover: Why Full Seats Doesn't Mean Full Revenue

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.

• 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.