Gluten-Free on the Menu Means Nothing If Your Staff Can't Back It Up
Hey Team!
Saturday night, 7:45pm. A table of four sits down and one of them mentions she has celiac disease. Your server nods, points to the GF symbols on the menu, and takes the order. What your server doesn't know is that the fries she just ordered for that guest go into the same fryer as the breaded chicken tenders. And nobody on that line is going to stop and think about it because nobody told them to.
That's the story I see play out in restaurants all over the country. Operators do the right thing on paper. They audit ingredients, they update the menu, they print the little wheat symbol next to the right items. And then they send staff to the floor without ever having the actual conversations that matter.
Putting "gluten-free" on your menu without training your team to defend it isn't a marketing problem. It's a liability problem.
Let me walk you through the three places where a gluten-free claim dies at the table.
The first one is the shared fryer. This is the most common failure I see. A guest asks if the fries are gluten-free. The server checks the menu, sees no wheat ingredients listed, says yes. Done. Except the fries are cooked in oil that's had breaded items in it all day. That oil is contaminated. The fryer itself is the issue, not the potato. Your server needs to know, without looking it up, whether your operation has a dedicated fryer for GF items. If you don't, the honest answer is "our fries are made with gluten-free ingredients but we can't guarantee a gluten-free preparation because of our shared fryer." That's the right answer. Most servers have never been taught to say it.
The second conversation that kills a GF claim is pasta water. This one comes up less often but it's just as real. A guest orders a gluten-free pasta dish. Your kitchen uses dedicated GF noodles. Good. But if those noodles go into the same pot of water that just had regular pasta in it, you've cross-contaminated the dish. The proteins from wheat pasta leach into the water. At Fat Tommy's, when we added a GF pasta option, I made every single kitchen employee walk through this specific scenario during training. Not because they were careless people. Because nobody had ever told them this was how contamination actually works.
The third conversation is flour-dusted surfaces and pans. A lot of kitchens dust cutting boards, sheet pans, or sauté pans with flour as part of prep. It's so routine that nobody thinks about it. But if a GF item gets cooked on a surface that had flour on it earlier in the day, the claim falls apart. Your staff needs to know what gets dusted in your kitchen and what doesn't. They need to know which pans are safe and which aren't. This is operational knowledge. It lives in your specific kitchen, not in a general food safety manual.
Now here's the part that most operators skip. Knowing these facts isn't enough. Your staff needs to have practiced saying them. There's a real difference between a server who's read about cross-contamination once and a server who's answered a celiac guest's questions ten times in a training scenario. One of them fumbles. The other one handles it cleanly and builds trust with the guest.
This is exactly why we built quiz-based training around allergen scenarios at ShiftTrained. Not just "what are the big eight allergens" but "a guest says they have celiac disease and they want the salmon with the gluten-free sauce, what do you tell them about how that dish is prepared tonight?" That question forces a server to think operationally, not just recall a definition. When we ran staff at Black Barrel Tavern through this kind of scenario drilling before we reopened our menu with new GF items, the conversations at the table got noticeably cleaner. Servers stopped guessing. They either knew the answer or they knew how to say they needed to check.
The liability angle is something operators don't talk about enough. A menu with a gluten-free claim is a promise. If a guest with celiac disease orders something based on that promise and gets sick, you're not protected because the ingredient list was technically accurate. You're exposed because you made a claim your staff couldn't support. Courts and health departments don't separate the menu from the service. The whole experience is the product.
I've seen operators think that taking the GF labels off the menu is the safe move. And in some cases, if you genuinely can't control cross-contamination, that's honest. I respect it. But if you're going to make the claim, you have to back it up all the way to the table. That means the server knows your fryer situation. It means the line knows your pasta protocol. It means your prep team understands what flour-dusted surfaces do to a GF dish. All three, every service.
The guests who need this information aren't being difficult. They're making a health decision based on what you tell them. A server who confidently gives the wrong answer isn't just costing you a repeat customer. They're putting someone in real physical distress.
Train the scenarios. Not once during onboarding. Regularly. Before new menu items launch. Before big service periods. Make the answers second nature, because the question is going to come up at 7:45 on a Saturday night and your server is going to be the only one at that table who knows what's actually happening in your kitchen.
Have a great day! — Terry Psaltakis
Your AI Restaurant Guy
