Latest / Restaurant Business with Fexingo: Food Service, Hospitality, and Independent Operators / Dinner Service Timing Is a Profit Game
Transcript
- Lucas: So we talk a lot on this show about menu prices, about labor costs, about real estate. But there's this one metric that sits underneath all of it that I think operators don't talk about enough, because it's invisible to the guest but it drives the entire economics of a dinner service. Luna: What's the metric? Lucas: Table turns. Specifically, how long it takes a table to go from seated to paid and out the door. That time is the single biggest lever a restaurant has over its revenue per seat. And I'm not talking about fast food — I mean for a full-service dinner house. Luna: Okay, so the faster the turn, the more covers you can serve on a Saturday night. But there's obviously a ceiling — you don't want to rush people and kill the experience. Lucas: Exactly. So the game is: how do you optimize the timing without making the guest feel like you're turning a table? And the numbers here are pretty stark. Let's take a typical independent restaurant with 40 seats, open for dinner service from 5 p.m. to 10 p.m. — that's five hours of service. If your average table turn is two hours, you get two and a half turns per seat per night. Forty seats times two point five equals a hundred covers. If your average check is $65, that's $6,500 in revenue for that dinner service. Luna: Right. And if you can shave that to 90 minutes — same seats, same hours — you go to three point three turns. That's 132 covers. At $65 average check, that's $8,580. So an extra $2,080 per night, just from timing. Lucas: That's the math. And that extra $2,000 a night — five nights a week, 50 weeks a year — that's half a million dollars in additional revenue, from the same rent, same kitchen, same staff base. The incremental cost is mostly just food cost and maybe a little extra labor if you need an extra server. But the rent doesn't change. Luna: So the question is: how do you actually move that needle? What makes a table take two hours versus 90 minutes? Lucas: There are really three buckets. One: the kitchen — how fast can you fire the courses. Two: the service sequence — how quickly the server takes the order, delivers the food, clears plates, presents the check. Three: the guest — some people just want to linger. The first two you can control, the third you can influence. Luna: And that's where data comes in. I know some restaurants now use their POS and reservation systems to track actual table times per server, per daypart, per section. Lucas: Absolutely. A place like Darden — they own Olive Garden, LongHorn Steakhouse — they've been doing this for years. But independent operators can do it too with modern POS systems. You can see: 'Server Lisa averages 22 minutes from appetizer to entree, but Server Mike averages 29 minutes.' That's a seven-minute gap per table. Over a five-table section and two turns, that's 70 minutes of lost table time per night. Luna: So you can coach servers to be more efficient without being rude. That's a huge lever. Lucas: And there's also the kitchen timing. Some chefs — especially if they came from fine dining — want to plate everything to perfection, but if the ticket times are consistently 18 minutes for an entree and the restaurant next door is doing it in 12, you're losing a table turn right there. The guest doesn't know, but the P&L does. Luna: There's a famous example from the early days of Shake Shack. Danny Meyer's team realized that if they could get the burger out in under four minutes, they could push through the lunch rush much faster. But that's quick service. For full-service, what's the benchmark? Lucas: For casual dining, industry data suggests a target of 45 to 55 minutes total table time. For midscale, 60 to 75 minutes. For fine dining, 90 to 120 minutes. But here's the thing — fine dining actually makes more money per table, so they can afford longer turns because the average check is higher. A $200 check at two hours is actually better revenue per hour than a $65 check at 90 minutes. So the math flips. Luna: Right, so the optimization depends on your concept. For a high-volume, lower-check restaurant, speed is everything. For a tasting-menu place, you want people to stay because they're spending more per minute. Lucas: Exactly. And that's why some restaurants are moving to fixed-price, timed menus. They say, 'You have the table for 90 minutes. Here's the three-course menu for $75.' It solves the linger problem. The guests know the deal, and you can schedule a second seating with confidence. Luna: I've seen that work well at places that do early-bird specials or pre-theatre menus. But there's a risk of feeling rushed, especially if the food is slow. Lucas: That's the tension. You can't just yell 'faster, faster' without affecting the experience. But there are subtle design choices. For example, if you clear the appetizer plate and bring the entree within two minutes, the guest perceives that as attentive, not rushed. If it takes eight minutes, they start wondering where their food is. So the window is actually quite narrow. Luna: And the check delivery is a huge one. I've been in restaurants where I'm ready to leave but I sit for 10 minutes waiting for the check. That's dead table time. Lucas: That's probably the single easiest fix. Train servers to drop the check as soon as the guest finishes the last bite, or even before. Some POS systems let you pre-print the check so it's ready. If you save five minutes on check delivery per table, and you have three turns on 20 tables, that's five hours of recovered table time per night. Luna: And yet so many servers wait until the guest asks. It's a habit that's hard to break. Lucas: It is. And it ties into the tip — some servers worry that rushing the check means a lower tip. But actually, if you're efficient, you can turn the table and get another party, and the overall tip per hour goes up. The server who does three turns at $100 average check versus two turns at $120 — the three-turn server makes more in tips even if the tip percentage is the same. And the house gets more revenue. Luna: So it's an alignment issue. The server's incentive is per-table tip, but the restaurant's incentive is per-hour revenue. If you can align them — say by tipping on total sales or by offering a bonus for faster table turns — you can change behavior. Lucas: Some places are experimenting with tip pooling or service charges that get distributed based on covers served. It's a shift, but it's happening. And the data is there to back it up. Luna: I want to bring up one more angle: the reservation software itself. Some platforms now let you set table durations. OpenTable, for instance, lets you set a default dining time — 90 minutes for dinner, 60 for lunch. And they'll block the table from being bookable again until that time has passed. But you can also override it if you know a table is turning faster. Lucas: That's a powerful tool, but it only works if you're disciplined. If you set a 90-minute default but your actual average is two hours, you'll overbook and create a wait that frustrates everyone. So you have to know your actual data. Luna: And that data can vary by day of week, by season, even by which server is on. So you need to track it. Lucas: You know, it's interesting — we're talking about this as a profit lever, but it's really about respect for the guest's time, too. If you can get someone in and out in 75 minutes with a great experience, they'll come back. If you make them wait 20 minutes for the check, they'll remember that. Luna: And that's the sweet spot: optimizing for both revenue and guest satisfaction. They're not mutually exclusive. Lucas: If these conversations have moved your work forward in any small way — maybe you've looked at your own table times differently after an episode — we want you to know that this show is completely ad-free by design. Luna: Yeah, there are no sponsors, no ad breaks. That's a choice we made from the start, and we like it that way. Lucas: So if you'd like to support that, and help us keep doing deep dives like this one, the simplest way is to buy us a coffee. The link is buy me a coffee dot com slash fexingo. Luna: It's genuinely just that — a small gesture if you find value here. No pressure, no perks, no rewards. Just knowing that listeners find it useful is enough. Lucas: Now, back to table turns. One thing I didn't mention is the role of music and lighting in pacing. There's actually research showing that faster-tempo music makes people eat faster, and brighter lighting makes them leave sooner. Luna: Really? So you can design the ambiance to influence turn time without the guest even realizing it? Lucas: Exactly. A study from the Journal of Consumer Research found that diners in a restaurant with upbeat music spent an average of 45 minutes at the table, versus 56 minutes with slow music. That's 11 minutes per table. And the check size didn't differ significantly. So you effectively get an extra turn over the course of the night just from the playlist. Luna: And lighting — I've heard that dimmer lighting encourages people to linger, which is fine if you're a wine bar selling $20 glasses. But if you're a family restaurant, you might want brighter lights. Lucas: Right. So the same physical space can be tuned for different dayparts. Lunch — brighter lights, faster music, maybe even a more limited menu to speed decisions. Dinner — dimmer, slower, to encourage higher spend per head. Some chains are really good at this. I'm thinking of a concept like True Food Kitchen — they have different music playlists programmed for each time of day. Luna: And that's all relatively cheap to implement. It's not a kitchen remodel. It's a Spotify playlist and some dimmer switches. Lucas: Cheap and reversible. If it doesn't work, you change it back. But the data will tell you quickly. You can run an A-B test: two weeks with fast music, two weeks with slow, and compare covers per night and average check. Luna: That's the beauty of modern restaurant tech — you can actually measure these things now. Ten years ago, you'd just have a gut feeling. Now you can see the numbers. Lucas: And the numbers don't lie. If you're doing 100 covers a night and you can get to 110 just by changing the music tempo, that's a 10 percent revenue increase with zero cost. That's a no-brainer. Luna: So let's say I'm an operator listening to this. What's the one thing I should do tomorrow? Lucas: Look at your POS data for the last month. Pull the average table time for each server, each daypart. Find the fastest server and the slowest. Shadow them and see what the difference is. Usually it's little things — how quickly they bring the check, how they clear plates, whether they upsell dessert before the entree arrives. Then share those best practices with the team. That alone can buy you 10 to 15 minutes per table. Luna: And that 10 to 15 minutes, over a year, is real money. I like that it's actionable. Lucas: It's the kind of thing that doesn't require a big consultant or a new system. It's just paying attention to the clock. And in this business, minutes are money.