Event Planning

How to ask guests about dietary needs before a party

Ask guests about food needs in a private reply, before you finalize the meal. Say who will receive the information and check it with the person preparing the food. A request or menu label does not prove a dish is suitable, so leave unverified details open.

Updated 2026-10-29

Convite Editorial Team4 min read
Generated image: dishes prepared for a gathering. Their ingredients cannot be inferred from the photo.
Photograph generated to illustrate this guide. Does not depict a real event.

A clear question starts a conversation; it does not make the host a specialist or certify a menu. Information may pass from a guest to the person collecting replies and then to whoever prepares or serves the food. An important detail can be lost at each step. This guide offers wording and a way to distinguish a received request from checked arrangements without asking for diagnoses, medication or medical history. These are editorial models, not a health protocol. Individual needs belong in a direct conversation with the guest and relevant professionals.

Who should you ask, and through which channel?

Offer invited people a private way to tell you what they need regarding food. Explain that the question helps with meal planning and who will review the reply. Do not infer needs from someone’s appearance, age or relationship to the group. Avoid asking anyone to explain a personal situation in a public chat to justify an alternative.

When an invitation includes other people, one person’s reply does not prove they know everyone’s needs. Ask for the information to be checked with each diner or the responsible adult where appropriate. Keep confirmed attendees separate from pending food questions. A menu reply does not settle the headcount by itself, and an RSVP does not establish that a particular dish is suitable.

What can you write without promising too much?

Original model: “We are planning food for [gathering]. If you have a dietary need we should review, please reply privately through [agreed channel] by [agreed date]. With your agreement, we will share the necessary information with [person preparing the food] and check the available arrangements with you.” Do not replace that final check with a promise that a safe option will always be available.

Agree on the reply deadline with whoever prepares the meal, based on their actual lead time and the event date. No fixed number of weeks resolves every situation. If a responsible person or service arrangement is still undecided, keep that marked as pending in your private plan. A late reply needs a check rather than automatic dismissal or an assumption that the change has already been handled.

Build a private question about food

Blog tools: no messages are sent and no data is stored; these are not app features. Use examples without private information.

Choose an option and prepare the wording. Review bracketed fields before using it.

How can you track the reply without diagnosing anyone?

Keep the information as the guest communicates it and ask for clarification when you do not understand what needs review. Do not translate a word into a medical category yourself. “Vegetarian,” “allergy,” “intolerance” and an ingredient preference do not mean the same thing. The organizer’s job is to pass on an understood request, not decide what someone can eat or demand evidence before considering a question.

Use separate stages: reply received, question passed to the preparer, arrangements awaiting confirmation and agreement reviewed with the guest. The table on this page is not a clinical risk classification. Do not combine every case under a color code that hides differences or circulate the complete needs list to people who are not involved in preparing or handling the relevant arrangements.

Track a request without classifying medical risk
Request stateAction still to check
Reply receivedClarify what is needed through the agreed private channel.
Question passed onObtain a response from the person preparing or serving the food.
Option pendingExplain that the preparation is not yet confirmed.
Arrangement reviewedReview later changes to the dish or preparation with the guest.

Why asking before preparing food matters

FARE’s “Ready to Live” public-service video raises food-allergy awareness before a gathering and also discusses emergency preparedness. It is general education, not a personalized medical plan or confirmation that a dish is suitable. This guide focuses on asking and reviewing with the guest and food preparer.

The YouTube player loads when you open the video. Watch on YouTube.

Generated image: food containers and plates. It does not demonstrate allergen or temperature controls.
Editorial illustration reused from this journal; it depicts neither this event nor a verification.

What should you check with the person preparing the food?

Ask about the actual recipe, ingredients and planned changes, and clarify how the request will be handled during preparation and service. A dish name does not describe everything in it. FDA explains that allergen cross-contact can occur between foods. Changing a menu label or removing a visible ingredient does not by itself establish that a preparation is suitable for an allergy.

If food comes from several people or providers, identify who can answer questions about each preparation. Someone bringing one dish may not be able to confirm conditions across the venue’s kitchen. Labeling rules and their requirements vary by country and service. The FDA’s US reference is not presented here as the Mexican or French regulation governing your event.

Choose the next step without skipping a check

Read the options without JavaScript
Reply received, not reviewed
Ingredients and preparation still need reviewing with the responsible person. Do not present the record as a confirmed option.
The provider needs clarification
Ask only for the needed detail privately and keep the issue pending. Do not infer it from the dish name.
The dish or preparation changed
Reopen the review with the guest and the food preparer. The earlier response neither confirms the change nor certifies safety.

These options organize decisions; they do not certify safety, rights or a handoff. Keep missing answers pending.

What if you cannot confirm an option?

Explain the uncertainty before serving and discuss the next step with the guest. Do not suggest tasting a little to find out or decide on their behalf that an amount is small. An unverified preparation should not be presented as suitable for their need. This blog does not assess individual tolerances, and its tool does not certify recipes, kitchens or menus.

If an alternative is discussed, check with the guest and venue which parts can actually be arranged. Do not promise storage, separate preparation or assistance that is unavailable. Medical decisions and individual plans remain with the guest, their family and relevant professionals. The communication task is to avoid a false confirmation and make clear who will check what is still unresolved.

Generated image: a closed blue folder and pens on a table.
Generated and reviewed editorial illustration; no private information appears in the image.

How do you keep information accurate until the meal?

Tell the responsible person if a recipe, supplier, diner count or request changes. An old note does not confirm a new version of the dish. Before the gathering, check which information is current and which questions remain open with whoever handles service. A generic sign or a seating assignment does not replace that conversation.

The generator prepares a generic question; it does not collect medical replies or send messages. The review checklist is a coordination aid, not a safety certification. It does not attribute menu planning or allergy records to Convite either. Check the app’s current QR invitation features and separately organize the food-related communication you have agreed to handle.

Before finalizing your plan

Can I ask only about allergies?

Explain that you are reviewing dietary needs and offer a private reply. Do not classify the guest’s situation yourself.

Does receiving a reply confirm the menu?

You still need to check arrangements with the food preparer and the guest.

Is there a universal one-week or three-week deadline?

This model sets no universal deadline. Agree on timing with the preparer based on the actual service and event.

Does a dish name prove it is suitable?

It does not describe every ingredient or preparation condition. Check the specific request before confirming.

What if preparation details cannot be checked?

State that it is unverified and discuss the next step with the guest. Do not label it suitable or suggest tasting to test it.

Does the generator store health information?

It does not request medical replies. It prepares a generic local question without sending or automatically storing information.

Sources and helpful reading

Practical guide from the editorial team. Examples are for guidance; adapt decisions and requirements to your event.

  1. FDA: food allergies and cross-contact: US reference; its labeling requirements are not transferred to other countries.
  2. Convite: current features: Blog aids do not certify menus or collect health replies.
Back to top ↑

From planning to invitations

Make the welcome
just as thoughtful.

Convite lets you design QR code invitations, share them via WhatsApp or email, and manage guest check-in seamlessly. Discover how it works and explore available features.