Most people with food allergies know to tell the restaurant. The harder part is knowing which questions reveal whether the kitchen can actually be trusted with that information.

"Does this contain sesame?" is a reasonable starting point. It is also the question that is easiest to answer confidently without really knowing. A well-meaning server who checks the menu and sees no sesame in the listed ingredients can answer "no" in good faith, without knowing that the dish is made in a shared fryer where sesame is present.

The questions below are the ones that get past the surface and into the system.

"Is [allergen] in this dish, or just handled in the same kitchen?"

This question distinguishes between two different risk categories that the answer "yes, we use nuts" does not separate.

A kitchen that uses nuts as an ingredient in several dishes is a different risk from a kitchen where nuts are present but only in one or two dishes as a topping. The former involves risk of cross-contamination risk. The latter may be manageable, depending on the specific dishes and procedures.

The question also signals to the staff member that you understand the difference. A kitchen that handles allergens well will appreciate the specificity. One that does not will sometimes reveal that through the quality of the response.

"Do you use shared or dedicated fryers?"

This is one of the most reliable diagnostic questions in any kitchen context.

A shared fryer used for battered fish (wheat, egg), chips (no declared allergen), and onion rings (wheat, egg) means that anything coming out of that fryer carries residual risk from everything else that went in. For any sever allergy, this is a question worth asking before ordering anything fried.

A kitchen that knows the answer – either way – is a kitchen that has mapped its own processes. A kitchen that is uncertain has not.

"Can you check with the chef?"

This question is less about the answer and more about what the response reveals.

A server who says "of course, give me a moment" and goes to check is operating in a kitchen where checking is the normal thing to do. The chef is a resource to be consulted.

A server who answers immediately and confidently, on a specific question about ingredients or preparation without checking is likely giving you their best understanding of the dish. That may be accurate. But it is their interpretation of the menu, not a kitchen confirmation. The two are not the same thing.

A server who seems put out by the suggestion, or who says "I'm sure it's fine," is telling you something about how allergen questions are received in that kitchen. That is worth noting.

"Is this made fresh or from a pre-made sauce or mix?"

Pre-made sauces, marinades, spice blends, stocks, and bases are the most common sources of hidden allergens.

Milk powder in a sauce that is not described as creamy. Wheat in a seasoning mix. Soy in a stock that would not obviously contain it. These are not unusual – they are standard in many commercial kitchens, and they do not always appear on the menu description.

A dish assembled fresh in the kitchen, from ingredients the chef can name, gives you much more visibility than one that uses a pre-made component from a catering supplier. The latter may be perfectly fine, but it requires a different level of verification.

"What specifically is the cross-contamination risk?"

If a menu says "may contain" or a server says "there is a cross-contamination risk", this question moves it from a vague warning to a piece of usable information.

These terms are often used interchangeably, but they can mean two different things. Sometimes the warning refers to a precautionary risk in the supply chain: an ingredient sourced from a facility that also handles the allergen, before it ever reached this kitchen. Other times it refers to a specific, identifiable risk in how this kitchen prepares the dish: a shared piece of equipment, the same prep surfaces, the same utensils used across different dishes. The level of risk these represent is not the same.

The answer tells you what the actual risk is and where it comes from. That lets you decide whether the risk is one you are comfortable with given your specific allergy and your specific reaction threshold.

A vague "there might be a cross-contamination risk" is not actionable. A specific "we prepare this dish on the same surface as dishes containing gluten" is.

What confident answers sound like

A staff member who knows the allergen information will give a specific answers without hesitation.

"That dish contains dairy in the sauce. The base itself doesn't, but we finish it with butter. If you need dairy-free, the lamb is made completely separately and there's no dairy anywhere in the dish."

That answer tells you the allergen, where it is in the dish, that the person understands what dairy means in a kitchen context, and what the alternative is.

A vague answer like "I believe it should be fine," "most of our dishes are fine for most allergies" signals uncertainty. The person may be doing their best. But you are now working with their best guess, not confirmed information.

When to order something simpler

There will be meals where the kitchen cannot give you full confidence about a specific dish. The sauce has multiple components they cannot fully verify. The cross-contamination question does not have a clear answer. The server keeps needing to check and keeps coming back with slightly different information.

In those situations, simplifying the order is a reasonable and practical response. The easiest thing to make safe in most kitchens is a protein (a steak, a piece of fish) with no marinade, no sauce, cooked separately, with some vegetables on the side.

That might not be the thing you wanted to order. But it is not a failure. It is a calibrated decision about the information available to you.

It is worth reframing what "a good meal out" looks like when you have allergies. It is not the same as a meal out for someone who can order anything on the menu. Sometimes the safe choice is simpler than you would like. A plain steak with vegetables, well-cooked, at a table with people you like, is a good meal. Adjusting expectations is not settling, it is making the best of what is actually available and still enjoying the experience.

When to trust, when to simplify, when to leave

Most restaurants, when asked the right questions, will give you enough information to make a reasonable decision. The answer may be "this dish is straightforward and completely safe," or "you should probably avoid this one but there are good options over here," or "honestly, our kitchen handles a lot of your allergen throughout service and we can't give you a full guarantee."

All of those are useful answers. A kitchen that tells you honestly it cannot safely accommodate your allergy is doing you a service, not a disservice.

The red flag to take seriously is a kitchen that cannot answer specific questions, that answers confidently without checking, or that seems to treat allergen questions as an burden. That combination (confidence plus vagueness plus resistance) is a signal that the information may not be reliable, and the risk is not fully understood.

In that situation, leaving is a reasonable option that keeps you safe.