For the host who has to brief the caterer
The kitchen does not want names, it wants numbers: how many of each dish, and who cannot eat what. Here is how a meal choice and an allergy arrive inside the reply, so the counts are ready weeks before service.
"Fourteen for the chicken, nine for the fish, two no beef, one very serious allergy." That is the sentence a kitchen wants, and it is almost impossible to assemble from text messages. Every guest who replies "the veg one, please" in a group chat is one more translation you have to make before you can give a number.
Collecting meal preferences inside the RSVP fixes this, because each guest chooses from the same short list of options you set. Their answer is data the moment it lands, and the totals per dish build themselves instead of you reading forty messages at midnight.
Every extra question is one more guest who gives up. Ask the ones that change the food.
Three steps, and all of them happen on their own.
On the invitation page, each guest picks a meal and can type an allergy note in the same reply, attached to their name.
Your guest list gathers the choices into a count per dish, and the allergy notes sit beside the people they belong to.
Weeks ahead of service you give the kitchen a figure per option and a short list of restrictions, not a shoebox of messages.
There is always one. A severe allergy, a strict diet, a guest who simply cannot face the menu you chose. A good meal-preference setup does not force them into a box that is wrong; it gives a free-text note in the same reply, so you learn about the problem while there is still time to solve it, rather than at the table on the day.
Because the note is attached to their name on the guest list, you can pass one clear line to the caterer about who needs what. That is the whole point of asking during the RSVP rather than after: the preferences arrive with the headcount, not a week later when the order is already placed.
How it works
List the meal options on the event page, the same ones the caterer can actually provide, and give each a plain label.
Keep a free-text field on the reply so a guest can add a restriction, and it lands with their meal choice and name.
As guests reply, your guest list rolls the choices into a number per dish, with allergy notes gathered beside the people.
Before the order closes, hand over a count for each option and a short list of restrictions to plan around.
Questions
Yes, that is where it belongs. When you offer meal options, each guest chooses one in the same reply as their confirmation, and can add an allergy note. Nothing separate to chase later.
Leave a free-text note on the reply so they can say so. Their restriction lands on your guest list under their name, giving you time to arrange something before service rather than learning at the table.
The guest choices add up into a running count per option, which is the number the caterer wants. You read the figures off the list instead of tallying replies yourself.
No, and it does not need to. What you get is the answer each guest submits, meal and allergy attached to their name, and the totals that fall out of it.
A guest who updates their reply edits the same record, so a dish count moves with them until you hand the final number to the kitchen.
Keep it short: name the options plainly so the labels are honest, and add one line inviting an allergy note. The reply page shows the choices beside the confirmation, so guests answer without scrolling back.
Get Started
Ask each guest for a meal and a note inside the RSVP, and you hand over exact counts per dish weeks before service, instead of a pile of messages to translate.
