What to actually ask a guest with dietary restrictions

A friend once told me, three days before a dinner, that she was "kind of vegetarian." I made a mushroom thing. She ate around the mushrooms. Turns out she meant she was trying to eat less red meat and was, in fact, allergic to mushrooms. This is what happens when you ask a vague question and get a vague answer, and then serve someone a plate of the exact thing they cannot eat.

The problem is almost never that people won't tell you. It's that we ask them a question so open-ended — "any dietary restrictions?" — that they don't know which of their several small food situations qualifies. Vegetarian? Sometimes. Gluten? Only when it's bothering her. Shellfish? Deadly. All of those get filed by the guest under "restrictions," but only one of them is going to send anyone to the hospital. Your job as the host is to pull that information apart.

The two questions to ask, and when to ask them

Ask when you invite. Not the day before. Not when they walk in the door and you're already committed to a lamb shoulder. The moment you say "come for dinner on the 14th," you also ask:

1. "Is there anything you can't eat, or really don't want to eat?"
2. "Anything I should keep out of the kitchen entirely?"

Those are doing different jobs. The first one gives them a wide net to catch preferences, mild intolerances, the thing their doctor told them to cut back on, and the food they simply hate. The second one is asking about danger — the peanut, the sesame, the shellfish where even the pan matters. Most people, given both questions, will sort themselves into the right bucket. "I don't really do pork, but I'm not weird about it" goes in bucket one. "My partner has a tree nut allergy, so no walnuts, no almonds, and please check the pesto" goes in bucket two.

The reason to split it is that guests routinely under-report the serious stuff because they've spent their whole lives being told they're being difficult. If you only ask one question, they'll tell you the socially acceptable version. Two questions gives them permission to be specific.

Here's the actual text of a message I send. Steal it.

Hey — so glad you're coming on the 14th. Before I plan the food: is there anything you can't eat or really don't want to eat? And separately, anything with a real allergy attached to it that I should keep out of the kitchen entirely? No detail is too much detail, I promise it makes my life easier not harder.

That last line is the part that matters. Most people will minimize. Telling them upfront that specificity helps you removes the social tax on giving you a real answer.

The follow-up nobody asks

Once they answer, there is one more question, and this is the one that separates a fine dinner from a good one:

"Is there something you actually love that I could work in?"

People with dietary restrictions spend a lot of meals eating the sad plain version of everyone else's food. The steamed vegetable next to the roast. The fruit plate for dessert while everyone else has cake. If your friend is celiac, she has eaten a lot of grilled chicken breasts in her life. Ask her what she misses, or what she'd choose if someone actually cooked for her. You'll get an answer like "honestly, a really good risotto" or "my mom used to make this lentil thing." Now you have a direction. You are not cooking around her restriction; you are cooking toward something she'll be glad to eat.

This is the detail the internet skips. Every hosting article tells you to accommodate. Almost none of them tell you to ask the guest what they'd genuinely enjoy, which is the entire point of having someone over.

Building a menu that quietly works

The trick is not to make a separate dish for the person with the restriction. That's the move that announces itself — the little ramekin of tofu next to everyone else's brisket. It makes the guest feel like a problem you solved.

Instead, work backward from the strictest constraint. If one person is gluten-free and one is vegetarian and one hates cilantro, your menu should be gluten-free and vegetarian and cilantro-free by default, and then you add things for the omnivores as extras, not the other way around. A roast chicken alongside a genuinely good vegetable-forward main is a menu where the vegetarian is not being accommodated — she's just eating dinner.

A rough heuristic: about 70% of your table should be things everyone can eat. The remaining 30% is where you put the optional add-ons — the cheese board, the crusty bread, the anchovy situation. This way, no single dish is the "safe" one, which is what makes people feel othered.

A few concrete equipment things that help:

• A separate cutting board (a cheap plastic one, six or seven dollars) for anything you're prepping that a guest is allergic to. Cross-contamination is a real thing and washing between tasks is not always enough, especially with nuts and shellfish.
• Masking tape and a marker to label serving dishes at the table — "contains dairy," "has walnuts on top." Guests can self-serve without interrogating you mid-conversation.
• A printed or texted menu sent the morning of. This gives anyone with a restriction one last chance to say "oh, actually, I forgot about" without having to do it in front of the table.

The labeling is the piece people skip. You know what's in your food. Your guests don't. A guest with a restriction will spend the entire meal quietly trying to figure out whether the sauce has butter in it. Save them the mental math.

You will still, at some point, forget something. Someone will mention a shellfish allergy and you'll put fish sauce in the dressing without thinking. It happens. Ask, apologize briefly, offer them the salad without dressing, move on. Being a good host is not being a perfect host — it's being someone who took the question seriously in the first place.

This weekend, before you plan anything else: send the message. Two questions, one follow-up, to one person you've been meaning to have over. That's the whole starter version.