Wedding RSVP online: replies, menu choices and guest questions

Replies are not a feature. They are a process with a deadline attached to somebody else's contract, which is why the tool matters less here than the order you do things in.

The difference only shows in the week before the deadline. That is when the replies arrive that no form anticipated: a plus-one with no name, a child who is coming after all, a nut allergy mentioned in a message to your mother. Couples who have thought those cases through add them in two minutes; the rest end up running three lists side by side and hand the caterer a number nobody can check.

The route in — paper, QR code, email — is a separate subject with a guide of its own. This one starts at the moment an answer comes back and ends at the number you hand the kitchen.

A reply that only says yes is not much use. Everything the kitchen, the seating plan and the shuttle need is attached to it, and if it is not collected in that same moment it gets collected later, one guest at a time.

So the form is a balance rather than a length. Too long and people stop halfway; too short and you spend March on the telephone.

Every question costs willingness to answer, so every question needs a consequence: the menu choice drives the order, the allergy drives the kitchen, the plus-one drives a chair. Anything nobody needs after the day does not belong in the form.

Two answers are routinely merged and belong apart: "I do not eat meat" is a preference, "nuts cause a reaction" is a medical note. The kitchen treats them differently, and both sit against a name rather than a table number. The same goes for plus-ones and children: a plus-one without a first name becomes a place card nobody can match, and children belong in the list with their age, because the children's menu, the high chair and the childcare depend on it. Ask for both separately instead of as one "number of people" field.

Almost everything a pricing page says about replies is about the form. Almost everything that goes wrong with replies is about the edges of the form: the sixty-first invitation, the answer that arrives twice, the export that will not open.

Those are worth checking before you commit, because they all surface in the same fortnight, and it is the fortnight with the least room in it.

For RSVP, two limits matter more than the design catalogue: how many invitations the package holds and what happens when you go past them. A cap that only surfaces at guest sixty-one hits you in the week you have the least time. Check beforehand how many invitations are included and whether a re-sent invitation counts as a new one.

The second point is the way out. Replies you cannot export belong to the tool rather than to you, and that spreadsheet is exactly what the caterer needs. Establish before you decide whether export is included and whether it carries menu choices and allergies. A guest list that collects everything in one place only helps if it also lets go of it again.

The gap between invitations sent and answers received is rarely a technical failure. It is the part of the guest list the form was never going to reach.

Two groups make it up and they need different handling: people who could reply online and will not, and people who cannot.

Assume from the start that some guests will not reply digitally. Older relatives, guests without a data plan and everyone who files the letter in a drawer need a second route: a phone number on the card, and the option for you to enter the answer yourselves. What matters is that it lands in the same list as the digital replies — two piles counted separately never agree.

Guests travelling from abroad need an earlier deadline. Flights, leave from work and, for some, a consular appointment carry their own lead time, and an invitation letter cannot be produced at short notice. Send that group the date well ahead of the full invitation and ask straight away who needs one for the authorities. How the QR code and the reply route fit together is covered in the digital invitation with a QR code.

Replies gather more about your guests than any other part of a wedding page: a meal choice, an allergy, sometimes a mobile number, all sitting against a name.

None of that is a problem in itself. It becomes one through copies — the family chat, the spreadsheet emailed to the caterer, the printout left on the venue's desk.

In practice that is three decisions. Who in the family may see the list? Allergies and addresses are not a group-chat topic, even when both families contribute names. What does the caterer receive? Numbers, menu choices and allergies — not phone numbers and not postal addresses. And what happens afterwards? Agree in advance when contact details get deleted; once the thank-you cards are out, most fields have no reason to exist.

Separated parents are the most common friction point. Both sides want to invite, both want to see who has accepted, and neither should receive the other's address list. The clean answer is one list with clear ownership rather than two: you maintain it, both households supply names, and what they get back is a number rather than a file.

The deadline is the one date in wedding planning you can calculate instead of choosing.

You do not have to guess the deadline; it is in your contracts. Find the date on which the kitchen needs final numbers, subtract a few days for the seating plan, then another two to three weeks for chasing. What is left is the RSVP date that belongs on the card — not the round number that simply reads well.

Chasing needs an order you set once and then work through:

• An automatic reminder to everyone still outstanding, with the deadline and the link.
• Then a personal message, written by whoever invited that guest.
• Finally a phone call — anyone silent by then will not answer a third email, and you enter the reply yourselves.

A cancellation three days out is not a disaster, it is a procedure: change the status, report the number to the kitchen, pull the place card, close the gap at the table. Couples holding two celebrations — a small registry ceremony and a larger party later — mark that against each guest, or the small number ends up in the large order. The seating plan is part of the package, and it reads the replies directly instead of copying them out of a second spreadsheet.

Getting Married is built for that order: your own questions set before the first invitation, a deadline you choose, reminders for whoever is still outstanding, and an export the kitchen can work from.