Latest / Restaurant Business with Fexingo: Food Service, Hospitality, and Independent Operators / Why Dinner Rush Staffing Ratios Drive Restaurant Profit
Transcript
- Lucas: You walk into a busy restaurant at 7:30 PM on a Saturday. The dining room is packed, every table seated. But the bar is two-deep with people waiting for a spot. And you notice—the host is apologizing, saying it'll be another 25 minutes for that table the hosts just cleared. Luna: Right, because the table is clean, but the kitchen is backed up. The food isn't coming out fast enough to turn it. Lucas: Exactly. And the operator's instinct is usually, 'We need more servers' or 'We need a faster point of sale system.' But the real bottleneck is almost never front of house. It's the ratio of back of house staff to front of house staff during the peak hour. What I call the boh to foh ratio. Luna: So you're saying the number of line cooks relative to servers matters more than absolute headcount. Lucas: Exactly. And it's a metric most independent operators never track. They staff by habit—same schedule every week, same number of cooks on a Friday as a Tuesday. But the dinner rush is where the money lives or dies. A 150-seat independent Italian restaurant in Chicago—I'll call it Via Roma—ran an experiment earlier this year. They added one extra line cook to the dinner shift on Fridays and Saturdays. Just one. And within eight weeks, their weekly revenue was up 12 percent. Luna: Twelve percent from one person? That's huge. What changed? Lucas: Ticket times dropped by four minutes on average. That doesn't sound like a lot, but over a three-hour dinner rush, those four minutes per ticket let them turn an extra full cycle on six of their twelve two-tops. That's six extra covers per night at $65 per head. Roughly $390 a night in incremental revenue. Luna: And the cost of that extra cook, say $18 an hour for a six-hour shift, that's $108. So net gain of almost $300 a night. That's a 3.6x return. Lucas: You nailed it. And that's before you factor in the table turns that didn't happen because the wait time drove people away. The host stand was telling 30-minute waits that were actually 45. By the end of the night, they'd lost maybe three or four parties that just walked out. Luna: So the boh to foh ratio—what's the magic number? Lucas: There's no universal sweet spot, but Via Roma's data is telling. Before the change, they ran three line cooks and six servers—a 0.5 ratio. After, four cooks to six servers—0.67. That extra 0.17 made all the difference. For a busy Italian kitchen with a lot of made-to-order pasta and sauté work, 0.67 seemed to be the minimum for keeping ticket times under 12 minutes during peak. Luna: Which is interesting because a lot of fast-casual places run a boh to foh ratio closer to 1.0 or even higher. But a fine-dining spot might be at 0.4 because the kitchen is more complex and the front of house team is larger for service. Lucas: Right, and that's the nuance. The ratio needs to be calibrated to the menu complexity and the dining room layout. But the point is: most operators don't even know their current ratio during rush. They know total labor cost as a percentage of sales, but that's an average across the whole day. It smooths over the peak-hour bottleneck. Luna: Let's talk about why that bottleneck happens. Is it just that the kitchen can't plate fast enough? Lucas: It's more specific. The bottleneck is almost always at the 'pass'—the point where the expo calls the order and the cooks fire the proteins. If you have one person on the sauté station and the ticket rail is eight deep, every new ticket adds four minutes to the previous ticket. The whole system compounds. But if you add a second sauté cook, you can split the rail—odd tickets to one, even to another—and suddenly the queue collapses. Luna: So it's about station splitting, not just adding bodies. Lucas: Exactly. Adding a cook without reorganizing the stations doesn't help. Via Roma split the sauté and grill stations. Before, one cook did both. After, one cook handled all the pasta and risotto, the other handled the proteins and apps. That's where the four-minute drop came from. Luna: And I imagine the servers felt it too. Faster food means happier guests, higher tips, less stress at the pass. Lucas: Absolutely. Server turnover dropped at Via Roma in the months after the change. They were getting burned out from apologizing for slow food. The front of house morale improved because they could actually deliver the experience they wanted to. Luna: It's funny—if these conversations have moved your work forward in some small way, whether you're a restaurant owner or just someone who loves the business side of hospitality, we keep this podcast ad-free because of listeners like you. If you've found value, you can support us at buy me a coffee dot com slash fexingo. No pressure, just a way to keep these episodes coming. Lucas: Yeah, it's a small gesture that makes a big difference for us. And we appreciate every bit of support. So back to the numbers—the interesting thing about Via Roma's experiment is that they didn't change the menu, prices, or marketing. The entire revenue lift came from operational efficiency during the two busiest shifts of the week. Luna: So what's the first step for an operator who wants to audit their own boh to foh ratio? Lucas: Step one: pull your point of sale data for the last four Fridays and Saturdays. Look at the time between when a ticket is opened and when it's marked 'ready.' Calculate the average ticket time for each 30-minute block between 6:30 PM and 9:30 PM. If you see a spike—say tickets going from 10 minutes to 16 minutes between 7:00 and 8:00—you've found your bottleneck. Luna: And then count heads. Literally walk the line at 7:30 on a Saturday and write down how many BOH and FOH are on the clock. Lucas: Right. Do that for two weeks. Then look at your ratio during the bottleneck block. If it's below 0.5 for a scratch-cooking kitchen, you're almost certainly understaffed on the line. Try adding one person on the busiest station and re-measure ticket times after two weeks. If the average drops by more than three minutes, the ROI is almost certainly positive. Luna: What about the risk? You add a cook, ticket times stay flat, and you're just burning labor. Lucas: That's why you test for two weeks. But honestly, in my experience, if ticket times don't drop, it's usually because the bottleneck is elsewhere—maybe the expo or the POS system lagging. But the test is cheap. One extra cook for six shifts is maybe $650. If you don't see improvement, you pull the shift. But more often than not, you'll see a lift. Luna: There's also a psychological factor. When the line is drowning, cooks cut corners—they under-season, they rush plating, they fire proteins too early. Quality suffers. Adding one person relieves that pressure and actually improves consistency. Lucas: Big time. Via Roma's food cost actually improved by about 1.5 percent during the experiment. Less waste from overcooked proteins, fewer remakes. That's another hidden benefit. Luna: So the boh to foh ratio isn't just a staffing metric—it's a quality and cost metric too. Lucas: Exactly. And the beauty is it's completely within the operator's control. You can't control foot traffic or food costs the same way, but you can decide how many cooks are on the line next Saturday. Luna: One thing I'd add: this ratio matters most during the two-hour peak. You might not need the extra cook for the whole shift—maybe just from 6:30 to 9:00. Some operators do a split shift or bring in a part-timer for that window. Lucas: That's a pro move. It keeps your labor percentage lower while still capturing the rush. Via Roma actually ended up hiring a part-time cook who worked Friday and Saturday from 5:30 to 10:00. They paid a premium—$22 an hour—but it was still worth it. Luna: What about restaurants with multiple kitchen stations—like a pizza oven, a grill, a fry station? Does the ratio still hold? Lucas: It does, but you need to think about it per station. A pizza place might need a dedicated pizzaiolo during rush, and if that person is also trying to run the fryer, you've got a problem. The ratio should be calculated at the station level, not just kitchen-wide. If your fry station is the bottleneck, add a fry cook. Luna: So the takeaway is: stop staffing by habit. Look at your ticket times, find the bottleneck, and adjust your boh to foh ratio for the peak window. Lucas: Exactly. And do it this week. Because every Saturday night you run understaffed is money you're leaving on the table—or rather, tables you're leaving unturned. Luna: It's a small change with a big ripple effect. And honestly, it makes the shift better for everyone—the cooks, the servers, and the guests. Lucas: Yeah. And that's the kind of win that keeps you in this business for the long haul.