Training Staff at a Brunch Restaurant: Cocktails, Eggs a Dozen Ways, and a 45-Minute Wait Outside
Hey Team!
Brunch is not a casual meal. I know it looks like one from the outside. Guests show up in sunglasses, order a Bloody Mary at 10:15am, and nobody's in a hurry. But the moment you're 40 covers deep with a 45-minute wait on the sidewalk and three different cooks each plating eggs Benedict their own slightly different way, you realize fast that brunch is one of the most technically demanding services you run all week.
And most operators train for it like it's a lite version of dinner. It's not. It's its own thing, and the knowledge gaps show up in real time, in front of guests who have nowhere to be and all the time in the world to notice.
Let me tell you what your staff actually needs to know cold before Saturday morning hits.
The egg thing is where I see operators get lazy first. Brunch menus often have eggs prepared four, five, six different ways, and each preparation has a vocabulary guests will use against you. "Over easy" means different things to different cooks. Poached eggs have doneness windows. Soft scrambled is not the same as scrambled. Your servers need to know exactly how your kitchen executes each preparation, not the textbook definition, because when a guest says "I like my yolk runny" and sends back a plate, it's almost always because the server didn't set the right expectation at the table. That's a training problem.
Beyond doneness, your staff needs to know the ingredients inside each egg dish cold. Not because guests are curious. Because brunch attracts a high volume of dietary modifications. Gluten-free, dairy-free, vegetarian, nut allergies. Guests ordering Eggs Florentine don't always know the hollandaise has butter. Guests ordering a frittata don't always read that it has smoked sausage in it. Your servers should be able to answer those questions without walking back to the kitchen three times. If they can't, you're slowing down a floor that's already moving too slow because of slow table turns.
Now let's talk about the bar side, because this is where brunch training falls apart completely at most places. Brunch cocktails are a different animal than your dinner cocktail list. The Bloody Mary program alone can be an entire training module. What's in your mix? What's the garnish? Is it house-made? What's the vodka? Can you make it with tequila? What's the spice level and how do you describe it honestly? Same questions apply to your Aperol Spritz, your Mimosa carafe program, your Espresso Martini if you're running one.
And here's the part a lot of operators miss completely. Day-drinking guests move differently than dinner guests. They're often pacing themselves across a long table visit. They want recommendations. They'll ask "what's good?" about a cocktail at 11am when your server might not have ever tasted any of them. If your staff can't speak to the drinks with real specificity, you lose upsell after upsell across every single table. That's not a small thing. Brunch beverage attach rates are a real number on your P&L.
The wait list situation creates its own training problem too, one that doesn't get talked about enough. When guests have been standing outside for 40 minutes, they sit down with a certain energy. They're hungry, they may have already had a drink at the bar next door, and they want to feel like the wait was worth it. Your servers' opening 90 seconds at that table determine whether you're going to have a great experience or a complaint. Staff need to know how to open a table confidently, acknowledge the wait without over-apologizing for it, and move toward a drink order fast. That's not instinct. That's a trained behavior.
There's also the upsell structure specific to brunch that your staff needs to understand. Bottomless options, if you run them, have specific rules about timing and re-pours. Add-ons like avocado, extra protein, or a side of fries need to be offered naturally, not read off a script. Coffee and juice programs often have premium upgrades. None of this happens consistently if you haven't walked your staff through it explicitly before service.
The other thing that kills brunch is incomplete knowledge on the specials. Brunch menus often have rotating or seasonal items, weekend-only features, or LTOs that change faster than your printed menu can keep up with. If your server doesn't know that the shakshuka has a 12-minute fire time, or that the seasonal Benedict has a component that's 86'd by 11:30 every single Saturday without fail, you're setting them up to disappoint guests they've already sold on the dish.
I built the platform I built because I ran this exact problem for years. Pre-shift meetings before a Saturday brunch are 10 minutes long if you're lucky, nobody's fully awake, and half the staff is still doing sidework while you're talking. The knowledge that needs to stick doesn't stick in that room. It sticks when staff can quiz themselves on it Thursday night from their couch, when they're not stressed and not distracted, and when they've already gotten the prep work done before the floor fills up.
Brunch is good revenue. It's loyal guests. It's high beverage potential. But it requires a staff that knows the food, knows the bar program, and knows how to manage the table experience when guests have been waiting and the kitchen is in the weeds. Treating brunch training like an afterthought because the vibe is casual is the mistake. The guests are casual. The preparation can't be.
Have a great day! — Terry Psaltakis
Your AI Restaurant Guy
For more on putting this into practice, see how ShiftTrained approaches server training.
