Training Staff at a Hotel Restaurant: Three Meal Periods, One Knowledge Base

I've consulted on a handful of hotel F&B programs over the years, and the mistake I see every single time is training by meal period in isolation. The breakfast crew learns the breakfast menu. The dinner team learns the dinner menu. And then the hotel does what hotels always do — cross-utilizes staff — and suddenly your breakfast server is on a dinner shift and has no idea what's in the branzino or whether the short rib contains gluten. Nobody wins. The guest definitely doesn't.

The better frame is this: one knowledge base, layered by context.

Here's what I mean. Start with the foundation. Every single person on your F&B staff, regardless of which shift they're being hired for, needs to know the core menu architecture. What proteins you're running. How the kitchen is organized. Which dishes carry the nine major allergens. What your sourcing story is, if you have one worth telling. This is the stuff that doesn't change whether it's 7am or 11pm. Build that layer first, train everyone on it, and quiz them on it before they ever set foot on the floor in any capacity.

At Fat Tommy's and Black Barrel Tavern, we do something similar. Before anyone learns the nuances of a specific shift, they learn the menu cold. Not "here are the proteins." I mean, here's what's in every dish, where it comes from, what it tastes like, and what can hurt a guest with a nut allergy. That foundation is non-negotiable regardless of whether someone is working a lunch rush or a late Saturday night.

Once you've got that foundation layer, then you build out the context layers on top of it. Breakfast has its own rhythm. Guests are time-constrained. They're often checking email while they order. Your staff needs to know the breakfast menu deeply, yes, but they also need to understand the pace of that service. What does a quick turn look like? What are the questions a solo business traveler asks versus a family of four? How do you handle a buffet vs. full table service if your property runs both?

Lunch is another context. It's often a hybrid audience. You've got hotel guests, local business people, and whoever wandered in from the street. The menu probably overlaps with breakfast on some items and previews dinner on others. Your training here should call out those overlaps explicitly. If the avocado toast is on both the breakfast and lunch menus, say so. If the salmon at lunch is the same salmon that appears in the dinner entrée but prepared differently, train on that distinction specifically. Don't assume staff will make those connections on their own.

Dinner is where the knowledge base gets tested most. Guests are slower, more engaged, and more likely to ask detailed questions. "Is this house-made?" "Can you do the duck medium instead of medium-rare?" "What does the sommelier recommend with the lamb?" Your training for dinner has to be deeper in the storytelling layer. Not just what's in the dish, but why it's on the menu, how it's meant to be eaten, what pairs with it. That's not fluff. That's the difference between a $38 entrée that feels worth it and one that doesn't.

Room service is its own universe and it barely gets trained as its own thing. I've seen hotels hand their room service staff a laminated copy of the menu and call it done. Room service is a blind service. You can't read the guest's body language. You can't upsell face to face. The order comes in over a phone or an app, the food goes on a tray, and one person carries it to a door. Your training for room service should be almost entirely focused on accuracy and allergen confirmation. What's your protocol when the guest says they have a shellfish allergy but they ordered a dish with shellfish listed right there in the description? Do your room service staff know how to have that conversation? Train for it specifically.

Banquets are the final layer, and honestly the most neglected. Banquet staff often aren't considered "restaurant staff" in the traditional sense, but they're serving your food and representing your property. At minimum they need to know what they're serving well enough to answer a basic question from a guest at the buffet line. Build a short banquet-specific module. Keep it tight. Focus on the menu being served that day, allergen flags, and what to do when someone has a dietary restriction that wasn't communicated in advance.

The throughline in all of this is that you're not training five different jobs. You're training one knowledge base and five contexts. When your staff understands the food deeply from the start, the context layers are just behavior guides layered on top of a solid foundation. That approach means when you cross-utilize someone from breakfast to cover a dinner shift, they're not starting from zero. They know the food. They just need the context refreshed.

That's a trainable problem. And it's a solvable one.

Have a great day! — Terry
Your AI Restaurant Guy