Latest / Restaurant Business with Fexingo: Food Service, Hospitality, and Independent Operators / How Restaurant Table Turn Times Affect Revenue Per Seat
Transcript
- Lucas: You walk into a busy restaurant at 7 PM on a Saturday, and the host says it's a 45-minute wait. You look around and see four tables that are clearly done — they're just sitting there, talking, maybe scrolling their phones. Luna: Right. And every minute they sit, that's a minute the restaurant isn't making money on that seat. Lucas: Exactly. That idle time is the single biggest drag on revenue per seat that most independent operators ignore. They focus on menu prices, they focus on food cost — but the number of times you can turn a table in a night directly determines your top line. Luna: And it's not just about rushing people out. It's about designing the experience to flow naturally, so the guest feels well-served but the restaurant doesn't lose a full turn. Lucas: Right. So let's put a number on this. Say you have a 40-seat restaurant open for dinner service, 5 PM to 10 PM — that's five hours. If your average table turn is 90 minutes, you can seat each table about 3.3 times per night. If your average check is $60 per person, and you're at 80 percent occupancy, that's about $6,336 in nightly revenue. Luna: Okay, that's the baseline. Now what happens if you shave 15 minutes off that turn time? Lucas: Drop it to 75 minutes, and suddenly you can seat each table four times per night — that's 21 percent more covers. Same rent, same labor, same fixed costs. Nightly revenue jumps to about $7,680. That's an extra $1,344 per night, which over 300 operating days is over $400,000 a year. Luna: That's the difference between breaking even and a healthy profit for a lot of independents. Lucas: Precisely. And the beauty is you don't have to raise prices or cut portion sizes. You just have to move people through the meal more efficiently. Luna: So how do you actually do that without making guests feel rushed? Because I've been to places where the server brings the check before you've finished your entree, and it ruins the experience. Lucas: That's the pitfall. The goal isn't to rush; it's to eliminate dead time. Let's break it down by course. The biggest time sink is usually the period between finishing the main course and ordering dessert. That's where a good server can step in. Luna: The pre-buss move — clear the plates, ask about dessert, offer coffee, all in one smooth motion. Lucas: Exactly. And drop the check — not before they're ready, but right after they say yes or no to dessert. If they say no, you bring the check immediately. If they say yes, you bring it with the dessert so they can pay at their leisure. Luna: I've also seen restaurants use staggered bread service — don't put bread on the table until the appetizer is ordered. That way, guests aren't filling up and lingering before they've even ordered. Lucas: That's smart. And here's a counterintuitive one: slower music can actually speed up the table turn. Studies have shown that slower music makes people eat more slowly, but they also leave sooner after the meal because they're more relaxed. The key is matching tempo to the course. Luna: Right — up-tempo during the meal, then slower as they finish. That's a subtle cue. Lucas: Let's talk about a real-world example. Darden Restaurants, which operates Olive Garden and LongHorn Steakhouse, is a master of table turn data. They've engineered their service sequence to hit about 45 to 50 minutes for lunch and 60 to 70 minutes for dinner. That's fast, but they've trained guests to expect it. Luna: And they don't have check averages that high — around $18 to $20 per person at Olive Garden. So they need those turns to make the math work. Lucas: Exactly. A high-end restaurant with a $150 check average can afford a 2-hour turn. But a casual spot needs volume. The point is, every operator should know their target turn time based on their check average and occupancy cost. Luna: So what's the first step for an independent operator who wants to improve? Should they just start timing tables? Lucas: Yes, but do it discreetly. Have the host or a manager log the time each party is seated and the time they leave — just for a week. You'll likely find that the average turn is 10 to 15 minutes longer than you think, especially on weekends when people linger. Luna: And then you identify the bottlenecks. Is it the kitchen? The server? The payment process? Lucas: Exactly. One of the biggest fixes is at the payment stage. If you can process credit cards tableside with a handheld terminal, you can save three to five minutes per table versus walking to the POS and back. That alone can add a full extra turn on a busy night. Luna: And training servers to upsell dessert and coffee serves double duty — it increases check average while also signaling that the meal is winding down. Lucas: Another tactic: offer a 'tasting plate' or a small dessert as a comp if the guest is lingering past the expected turn time. It's a gracious way to encourage them to finish up, and it generates goodwill. Luna: I've also seen restaurants use a subtle signal — like dimming the lights slightly or turning up the music a notch at a certain point. Guests subconsciously pick up on it. Lucas: That's a bit manipulative, but it works. The key is to make the guest feel like they've had a complete experience, not a rushed one. If they leave feeling satisfied and not hurried, they'll come back. Luna: And that's the real metric — not just turn time, but repeat visit rate. If you push too hard, you lose the long-term revenue. Lucas: Absolutely. So let's tie it all together with a simple rule of thumb: every five minutes you shave off your average table turn, you increase your revenue per seat by about 6 to 8 percent, assuming no change in check average. That's a massive lever. Luna: And it's free. No marketing spend, no menu redesign — just better operations. Lucas: You know, that's exactly the kind of insight that makes this show worthwhile for me. And if it's moved your thinking forward even a little, I'll just say this — if today was worth a coffee to you, there's a link: buy me a coffee dot com slash fexingo. That's the smallest ask I can make, and it genuinely helps keep this ad-free. Luna: Yeah, it's a small way to say this matters. We don't have sponsors, so listener support is what keeps us going. Lucas: Alright, back to it. So let's talk about one more specific tactic: the 'check drop before dessert' method. If you bring the check when you drop the dessert, guests can pay whenever they want — and they often leave within five minutes of finishing. Luna: That's huge for the last turn of the night, when you're trying to squeeze in one more party before closing. Lucas: Right. And the data backs it up. A study by a restaurant consulting firm found that restaurants using tableside payment and pre-dessert check drop reduced average dining time by 12 minutes without affecting guest satisfaction scores. Luna: Twelve minutes — that's almost a whole extra turn per night for a busy dinner service. Lucas: Exactly. So here's my challenge to listeners: track your turn times for one week. Find your average. Then pick one tweak — pre-bussing, faster payment, staggered bread service — and see what happens. The upside is enormous. Luna: And if you're a regular listener, maybe consider that coffee. We'll be back next time with another operation deep dive. Lucas: Until then, keep turning those tables.