The list your caterer will ask for: menus, allergies and plus-ones without chaos

There is a moment, about two months before the wedding, when every couple discovers the same black hole: the RSVPs. A cousin confirmed by WhatsApp, a friend over Instagram, the great-aunt told your mother "of course she's coming" — and the caterer wants a headcount, the menus and the allergies in a table. This guide is about never reaching that moment.

Why WhatsApp does not work (even though it seems to)

WhatsApp collects replies, but not data. "We'll be there!" does not say how many they are, what they eat, or whether the kid is coming. Multiply that by 120 guests and you have a second job: chasing, re-asking and copying everything by hand into a spreadsheet that goes stale every day. (For timelines and polite chasing templates you already have our RSVP guide; this one is about the next step: the list.) The solution is not more discipline — it is a form that asks just enough, once, and keeps it in order.

What to ask (and what not to)

Just enough usually means this:

• Are you coming? — yes or no, no "we'll see".
• How many of you? — plus-ones with names, or the ghost "+1"s will haunt your seating chart.
• Menu and allergies — as closed options (meat / fish / vegetarian) plus one allergies field. The caterer does not want prose; the caterer wants numbers.
• Will you use the bus? — if there is one, this answer saves you an empty bus or two overcrowded ones.
• One song — optional, but it fills the dance floor from minute one.

And what not to ask? Everything else. Every extra field lowers your response rate: a two-minute form gets filled on the sofa; a ten-minute one gets left "for later" — and "later" means you will be chasing.

The deadline (and the margin trick)

Set the deadline 3-4 weeks before the wedding, even if the caterer needs the numbers at 2: that margin is your cushion for chasing stragglers calmly. And announce the date on the invitation itself ("please RSVP by 15 May") — a deadline nobody announced does not exist.

Delivery day: the clean list

The end goal is answering the caterer in one click: so many adults, so many children, so many vegetarians, these allergies. If the RSVPs came in through a structured form, that list already exists — you just export it. If they came in through WhatsApp… you know how that ends.

On a Weddara wedding website the RSVP works exactly like that: guests confirm from their phone's browser, nothing to install; menus, allergies and plus-ones arrive as ordered data; and you see everything in one list you can hand to the caterer as is. On Premium, the seating planner uses those same answers to build the floor plan — with the diets already counted per table.

In short

RSVPs are the one wedding task that can be fully automated — and the one that buys the most peace of mind once it is. Short form, closed options, an announced deadline, and a list that exports itself. Build your website with RSVP in 10 minutes and let confirming be your guests' job, not yours.