Deadlines that protect the caterer, questions worth asking, chasing without nagging — and why the reply card's job moved online.
Répondez s'il vous plaît — the one French phrase every wedding guest knows, and the one instruction a reliable third of them ignore. The RSVP is where a wedding's romance meets its operations: behind the pretty card sits the caterer's contract, the seating chart, and the bar order. This guide covers the whole mechanism — deadline, medium, questions, and the gentle art of extraction — because a wedding runs on its reply data, whether or not anyone calls it that.
Work backwards: the caterer's contract wants final counts about two weeks out; the seating chart wants a week of work before that; and some guests will miss any deadline printed. So: RSVP deadline three to four weeks before the wedding, plus a private buffer of several days between the printed date and the date the numbers are truly needed. The full mailing calendar around it is in the timing guide; the buffer is the part people skip and regret.
The traditional reply card — its own envelope, its own stamp, the little M___ line that a surprising number of guests do not understand ("M" begins Mr./Mrs./Ms. + your names, for the record) — is a lovely object with three operational weaknesses: it asks almost nothing, it tells you nothing about when it was sent, and it cannot remind anyone of anything. The online RSVP inverts all three: it timestamps every reply, holds dietary detail properly, sends its own reminder before the deadline, and — done well — already knows who it is talking to, so "the Hendersons" answer for exactly the two Hendersons invited and no speculative third. The register question is real but solved: a beautifully printed card carrying the link (or a small QR) keeps the paper's formality and the system's intelligence. Guest lists that skew older or traditional deserve the stamped card as an option beside it — both channels feeding one list.
Every question costs response rate, so the budget is small and should be spent well:
Questions to resist: favorite memory of the couple (sweet, unanswered, unread), advice for the newlyweds (the guest book's job), and anything the answer to which changes nothing operationally.
Expect 20–30% of any list to need a nudge; plan for it and it stops being disappointing. The sequence that works: an automatic reminder to non-responders a week before the deadline (online systems do this on their own — the single best argument for them), then, the day after the deadline, personal contact only — a warm text or call from whichever of you knows them, never a broadcast and never a public post. The wording that lands: "We're finalizing numbers with the caterer this week and would so love to have you — can I put you down?" It presumes goodwill, names the real constraint, and closes with a question that takes one word to answer.
Since half the readers of any RSVP article are guests being chased: the etiquette is short. Reply by the date, even — especially — if the answer is no. Do not write in a guest who was not named (the envelope defines the invitation). Give dietary information when asked, not on arrival. And a decline needs no essay: warmth plus regret, two sentences, send.
Collected properly, the RSVP season ends with something better than a headcount: named guests matched to households, dietary needs the kitchen can cook to, arrival days that shape the welcome dinner, and a clean substrate for the seating chart. That is the modern reframe worth adopting — the RSVP is not an etiquette ritual with a spreadsheet problem attached. It is the moment the guest list becomes real, and everything after it is built on what was asked.