How to Train Staff on Daily Specials Before the Doors Open

It isn't.

Here's what I actually believed for too long: if I stood in front of my staff at 4pm, described the special clearly, maybe even had them taste it, they'd remember it at 7:45. That's the model. Chef introduces it, floor manager reinforces it, servers nod, everyone goes to work. It's also basically useless by the time the rush hits.

The problem isn't attention. Your servers are paying attention at 4pm. The problem is time. Three hours of ticket flow, table turns, side work, a 86 on the halibut, a table in the weeds, someone's card getting declined, and whatever happened in section 3 before they even got to the floor. By mid-service, the details of the special are gone. Not because your staff is bad. Because that's how memory works under stress.

I ran into this exact wall at Black Barrel Tavern. We were rotating specials hard, trying to keep the menu interesting, doing real composed dishes with actual technique behind them. And the servers could describe the vibe of a special but not the thing itself. Not the preparation. Not the components. Not why it was worth ordering. A guest would ask and they'd get the summary version, which is basically nothing. You don't upsell a $34 dish with "it's really good tonight."

The verbal pre-shift rundown is a buggy-whip. It worked when your staff had two hours of slow service ahead of them and the special was grilled salmon with lemon butter. It doesn't work when the special is a walnut-crusted duck breast over farro with a fig reduction and your doors open in 45 minutes and half the floor hasn't heard the full rundown because they clocked in late.

Now let me tell you what actually works.

Push it to their phones before they hit the floor. Not a PDF. Not a text in a group chat. A short quiz, five or six questions, built around the specific special that night. What's in it. How it's cooked. What to say when someone asks why it's worth the price. What the allergens are. What it pairs with. Two minutes on their phone at clock-in, and now it's not just something they heard once. They've actively recalled it. That's the difference between information that sticks and information that evaporates.

At Fat Tommy's we started building quiz sets for specials the same day chef finalizes them. Takes a few minutes. By the time the first server clocks in, the questions are waiting. They answer them, they get immediate feedback on what they got wrong, and they walk onto the floor knowing the dish. Not a rough sketch of it. The actual dish.

The other thing this fixes is consistency. When you do a verbal rundown, every server gets a slightly different version depending on where they were standing, whether the kitchen was loud, whether they asked a follow-up question. One server learns the walnut crust is house-made and toasted to order. Another one doesn't know that. Now you've got ten different descriptions of the same plate going out to tables, which means some tables get a real sell and some tables get "yeah it's really good." The quiz standardizes the message. Every server leaves knowing the same thing.

I've heard operators push back on this with two objections. The first is "my staff won't do it." And I get it. Nobody wants to add friction to clock-in. But what I've seen at both of my restaurants is that when the quiz is short and actually about their job that night, staff do it. They don't want to get caught flat-footed at a table either. They have their own pride about this. Give them a tool that takes two minutes and helps them not look dumb in front of a guest, and most of them will use it.

The second objection is "it takes too long to build the quiz." That one I have less patience for, because the platform I built, ShiftTrained, generates quiz questions from a menu upload in minutes. You're not writing questions by hand. The work is mostly done for you. The special changes tonight? Update it and push. That's the operation now.

There's also a compliance angle worth naming. Specials often carry the most allergen risk. A special with walnuts, a sauce with hidden shellfish, a prep that shares a surface with something your guest can't eat. The verbal rundown is a single point of failure on information that can send someone to the hospital. A quiz with allergen flagging built in means every server has confirmed they know what's in the dish before they recommend it to a table. That matters more than the upsell.

The bigger shift here is understanding what pre-shift training is actually for. It's not a ritual. It's not about showing your team you care. It's about making sure that at 7:45 on a Saturday night, when a guest at table 12 asks what's in the special, your server doesn't say "it's like... a mushroom thing." They say "it's a walnut-crusted duck breast over farro with a fig reduction, pairs really well with the Syrah, and the whole dish is gluten-free if that matters to you."

That's the version that sells the dish. That's the version that makes the guest feel like they're in good hands. That's the version you can actually count on.

Have a great day! — Terry Psaltakis
Your AI Restaurant Guy