Allergen Cross-Contact: The Question Every Server Fails
Hey Team!
Friday night. You're slammed. A four-top sits down and one of them mentions she has a tree nut allergy. The server nods, says of course, asks a couple quick questions about what she wants to order. She orders the chicken with pesto. Server says, "You're fine, pesto is just basil and cheese." Ticket goes in. Food comes out. Guest takes three bites and reaches for her EpiPen.
Pine nuts are a tree nut. They're in almost every traditional pesto. And your server didn't know that because nobody ever sat down with them and actually walked through what's inside each component on your menu.
That's not a training failure. That's a system failure. There's a difference, and it matters.
Here's what I've seen play out in 30 years of running restaurants. Servers aren't lazy. They're not trying to hurt anyone. They confidently answer allergen questions because they genuinely believe they know the answer. That confidence is the dangerous part. A server who says "I don't know, let me check" is protecting your guest. A server who says "oh, that's fine" with a smile, based on a half-remembered pre-shift from six weeks ago, is the one who puts someone in the ER.
The hidden allergens are the real problem. Not the obvious ones. Nobody's forgetting that the shrimp dish has shrimp. The ones that catch people are the ones buried in components. The egg in the aioli. The anchovies in the Caesar dressing. The walnuts in that pasta sauce we added to the menu at Black Barrel Tavern last spring, which weren't on anybody's radar because they came in through a sauce modification and never got formally communicated to the floor.
We caught that walnut situation before it became a problem, but only because I personally walked every server through the updated menu that week. That's not scalable. That's not a system. That's me running around putting out fires.
Think about all the places these things hide. Fish sauce in a Thai-inspired glaze. Sesame in a vinaigrette that looks like it's just oil and acid. Milk solids in what your line cook is calling "just butter." Malt vinegar on the fries. Wheat in soy sauce. Soy in the marinade that came from a pre-made base your kitchen bought from a distributor. Your servers don't read spec sheets. They don't go into the walk-in and check labels. They answer based on what they were told, which was based on what someone else was told, which may or may not have been based on the actual recipe.
Now let me tell you about the confidence gap, because this is the thing that keeps me up at night. If you ask a server "does our Caesar have anchovies," a lot of them will say yes because they know that one. It's famous. But if you ask them "does the Caesar dressing we use have anchovy paste, and how is that different from a guest who says they have a fish allergy versus a shellfish allergy," you'll get a very different answer. Or no answer at all. The knowledge is shallow. It doesn't hold up under the actual questions a scared guest asks at the table.
The solution isn't a longer pre-shift. Pre-shifts are chaotic and the information doesn't stick. I've written about this before. What actually works is repetition, specificity, and testing that reflects real situations, not multiple choice trivia.
When we built ShiftTrained, one of the things I cared most about was the allergen layer in the quiz questions that get generated from your menu. Because the AI doesn't just read "pesto" and move on. It reads the ingredients, it knows that pesto contains pine nuts, and it generates a question that specifically tests whether your server understands that a guest with a tree nut allergy cannot have the pesto. It generates the follow-up. It catches the aioli. It flags the Caesar. It surfaces the walnut sauce because that's in your menu document. Not because I wrote a question about it manually, which nobody has time to do, but because the system reads what you actually serve and builds questions around the real risk.
The old way of handling this was to print an allergen matrix on a laminated card and hope staff actually studied it. Nobody studied it. It lived next to the POS and got coffee stains on it. The new way is mobile-native questions that staff can take on their own phones, that get specific enough to actually change what they say at the table.
At Fat Tommy's we've seen staff voluntarily retake the allergen-focused quizzes. Not because we made them. Because they got a question wrong the first time and it bothered them. That's the behavior change you're actually looking for. That's what makes a guest safe.
The confident wrong answer is the one that sends someone to the hospital. The uncertain correct answer, the one where your server says "hold on, I want to double-check that for you," is the one that saves you from a lawsuit, a health department visit, and the kind of story that ends up on local news.
Know your ingredients. Test your staff on the real ones. The hidden ones. The ones nobody thinks to ask about until it's too late.
Have a great day! — Terry
Your AI Restaurant Guy
