A message such as “vegetarian please” is useful only if the organiser can connect it to a person, an event, and a selected dish. MealReply asks every guest for a structured dietary status and an optional note at the same time as their meal choice.
Separate general preference from dietary need
The meal option records what the guest wants to eat. The dietary status records whether the organiser needs to pay attention to a restriction. Keeping those fields separate avoids turning every preference into an unclear free-text note.
Describe dishes before sharing
Mention the main ingredients or style when the dish name is ambiguous. Do not claim a meal is allergen-free unless the provider has confirmed it. Guests should have enough context to choose, not a substitute for professional allergen guidance.
Ask for concise, actionable notes
A useful note names the relevant ingredient or constraint, for example “severe peanut allergy” or “no dairy.” The private receipt lets the guest correct the choice or note while responses remain open.
Close responses before placing the order
Tell guests when choices close, review unanswered invitations in the original channel, and lock the list before sending quantities to the caterer. Reopen only when you deliberately want to accept changes.
Confirm serious requirements directly
Use the organiser list to identify people who need a direct follow-up. Confirm severe allergies with both the guest and provider; a web form is a coordination aid, not a food-safety guarantee.