Latest / Restaurant Business with Fexingo: Food Service, Hospitality, and Independent Operators / Why Restaurant Table Turn Time Is Your Hidden Profit Lever
Transcript
- Lucas: There's a number that most independent restaurant owners I talk to can't tell you off the top of their head — but it's probably the single biggest lever they're not pulling. It's table turn time. Not average check, not food cost percentage — the minutes between when a guest sits down and when they get up. Luna: And I bet most owners think they already know it. They're like, 'Oh, dinner takes about an hour and fifteen.' But they're not measuring it by shift, by server, by day of week. Lucas: Exactly. And the difference between guessing and measuring is real money. I was looking at a 45-seat Italian spot in Portland — let's call it Via Tavola. Independent, doing dinner only, check average around $52. They tracked their actual turn time over 90 days and found it averaged 87 minutes per table on weeknights, 93 on weekends. That's almost half an hour longer than the industry benchmark for that segment. Luna: So what did they do? Slash service? Rush people out? Lucas: No, and that's the interesting part. They didn't change the menu, didn't raise prices, didn't add a time limit. They changed three specific front of house workflows. First: bread service. They used to bring bread and oil to the table within two minutes of seating — which sounds hospitable, but it actually encouraged guests to settle in and linger before even looking at the menu. They shifted to presenting the menu first, giving a three-minute alone moment, then coming back for the drink order, and only then offering bread. Luna: So you're basically controlling the pace of the appetizer phase without making it feel rushed. Lucas: Right. Second change: check presentation. Most servers at Via Tavola were trained to drop the check after the guest finished the last bite and said they didn't want dessert. That's fine, but the problem was the payment step — the guest would sit there five, seven minutes waiting for the server to come back with the machine or the change. They started having the server bring the check presenter and the handheld terminal together in one trip. If the guest pays at the table, the transaction is done in under a minute. If they need change, the server is back within two. That alone saved four to six minutes per table. Luna: That's huge. And the third? Lucas: kitchen to server handoff timing. They noticed that servers were hanging around the pass waiting for plates — sometimes 45 seconds, sometimes two minutes — because the kitchen was plating and the expo wasn't calling the dish until it was fully ready. They switched to a 'call ahead' system: the expo calls the dish name when the protein hits the pan, not when the plate is finished. That gives the server a 90-second heads-up to do a final table check, grab sides, and be at the pass exactly when the plate lands. They cut average post-fire time by almost three minutes. Luna: So what was the net effect on turn time? Lucas: They went from 87 minutes to 78 on weeknights. Nine minutes. Doesn't sound like much — but over a three-hour dinner service, that's a difference of doing 2.3 turns per table versus 2.0. For a 45-seat restaurant, that's an extra 13 or 14 covers a night. At $52 check average, that's an extra $700 a night. Over six nights a week, that's $218,000 in additional annual revenue. With essentially no cost increase. Luna: That's not a tweak, that's a strategy shift. And I imagine the food cost percentage didn't move — all that extra revenue drops straight to the bottom line, minus maybe a little extra labor for the kitchen. Lucas: Exactly. Their total cost of goods on those extra covers was maybe 30 percent. So net profit from that change was roughly $150,000 a year. For a restaurant doing maybe $1.2 million in revenue, that's a 12.5 percent profit improvement. Compare that to the alternative: cutting food cost by two percentage points — which is brutal, it means reformulating dishes, renegotiating with suppliers — that would only net about $24,000. Luna: So table turn time is a higher-leverage move than almost any cost-side fix. But does this work at every concept? I mean, if you're a fine dining place where the experience is built on a 2.5-hour meal, you don't want to compress that. Lucas: You're right. The leverage is inversely related to check average. For a concept doing $150 a head, you're selling an experience, not a meal. But the vast majority of independent restaurants in this country — and I mean the ones doing $40 to $70 check average — those are the ones where a 10-minute reduction is pure gold. And the guests don't notice if it's done well. They don't feel rushed because you're not rushing them. You're just eliminating the dead time where nobody's at the table — waiting for bread, waiting for the check, waiting for the server to come back. Luna: There's a classic study from Cornell's hospitality school — I think it's from the early 2000s — that found the average restaurant guest spends 55 minutes eating and 30 minutes waiting. The waiting part is where the waste is. Lucas: That's exactly the framework. If you can cut the waiting by even 25 percent, you get the kind of numbers we're talking about. And the beauty is, you don't need software for this. You need a stopwatch and a willingness to change your service sequence. The Portland restaurant did this with a whiteboard and a timer. They didn't buy a fancy analytics platform. Luna: What about the resistance from servers? Some of them might feel like they're being clocked, or that the pace is being dictated from above. Lucas: That's a real cultural hurdle. The Via Tavola owner told me she brought the servers into the process. She didn't say 'we're cutting table time.' She said 'I want us to turn tables faster so we can seat more guests, which means more tip opportunities for you.' And she showed them the math: if we do 13 more covers a night at $52, and the tip pool is 20 percent, that's an extra $135 in tips per night split among the team. That's not nothing. So the servers became the ones driving the changes. Luna: So you're creating a shared incentive. That's smart. And it also means the changes are more likely to stick because the staff sees the benefit. Lucas: Exactly. And the data collection shouldn't be punitive. They just tracked average turn time by shift, shared it on a whiteboard in the back, and celebrated when the number dropped. It became a game, not a surveillance tool. Within six weeks they hit the 78-minute target. Luna: You know, speaking of things that are worth paying attention to — and not to get too meta — but this conversation today is exactly the kind of thing that, if you run a restaurant, might be worth the price of a coffee. If it moves your operation forward even a little. I'm just saying, the show stays ad-free because listeners like you support it. If today was useful, you can find us at buy me a coffee dot com slash fexingo. Lucas: Yeah, and I'll add — it's not about obligation. It's about keeping the conversation going. We don't sell ads, we don't do sponsored segments, so listener support is what keeps this independent. Same link if you want to help. Luna: Alright, back to the numbers. So you mentioned Via Tavola went from 87 to 78 minutes. Is there a point where you overshoot? Like, can you compress too much? Lucas: Absolutely. If you push below about 60 minutes for a full dinner service in a mid-market independent, you're probably compromising the experience. Guests start to feel rushed. The sweet spot for most concepts is between 70 and 85 minutes for dinner. The key is to identify where your biggest dead-time pockets are and fix those, not to race to the lowest number. Luna: So it's about optimization, not minimization. There's a difference between efficient and hurried. Lucas: Exactly. And the best operators I've seen build in intentional 'slow moments' — like a pause between courses where the server steps away and the guest can have a conversation — but they eliminate the unintentional dead time. The difference is subtle but it's everything. Luna: One more thing: Are there any technology tools that actually help with this, or is it all process? Lucas: There are some good POS integrations now that can give you real-time turn time by table. Toast has a dashboard for it. But honestly, a spreadsheet and a stopwatch for two weeks will get you 80 percent of the way there. The hard part is not the data — it's the willingness to change your service rituals. Luna: Which is exactly where most restaurants get stuck. They know the number, but they don't act. Lucas: Right. And that's the podcast conversation for today. If you're an operator, pick one shift this week. Time your turns. You might be surprised what you find. Luna: I know I'm going to start counting minutes the next time I go out to eat. Probably annoying my server. Lucas: Just don't pull out a stopwatch at the table. Use the bread basket as a clock.