Wedding RSVP Wording: Examples & What to Ask Your Guests

Couples agonise over invitation wording and dash off the RSVP in a minute — backwards, operationally. The invitation is read once; the RSVP determines your headcount, your catering bill, your seating chart and how many chasing messages you send in month eleven. Good wording pays for itself forty times over.

RSVP card basics (and what "M____" means)

A traditional reply card carries four elements:

• The name line. That mysterious "M____" prompts guests to write "Mr and Mrs Okafor" — the M starts their title. It reads as elegant to traditionalists and as a typo to everyone else; a plain "Name(s):" line loses nothing.
• Accept / decline — "joyfully accepts / regretfully declines".
• The deadline — "kindly reply by 20 July".
• Anything you must know per guest — meal choice, dietary needs.

What to ask beyond yes or no

Every question you ask at RSVP time is a question you don't chase later. The high-value list:

• Names of everyone replying — so "The Patels ×4" never haunts your seating chart.
• Meal choice and dietary requirements — per person, not per household.
• Which events they'll attend — welcome dinner, excursion, brunch — if you're hosting a destination weekend.
• Travel details — flight number and hotel, for destination weddings; it's the difference between a guess and an arrivals plan.
• A song request — optional, delightful, and the best icebreaker question ever printed.

“Ask everything at the moment of yes. Enthusiasm answers questions that reminders never will.

Wording examples

Formal

"The favour of a reply is requested by the twentieth of July. M____ · ____ joyfully accepts · ____ regretfully declines · Entrée: beef / fish / garden. Please note any dietary requirements."

Casual

"Can you make it? Reply by 20 July. Names: ____ · Wouldn't miss it / Celebrating from afar · Dinner: beef / fish / veggie · Anything you can't eat? · One song that gets you dancing: ____"

Destination

"We can't wait — but first, logistics! Please reply by 20 July. Names: ____ · Joining us in Ravello? Yes / Sadly not · Which events: welcome drinks / wedding / boat day / brunch · Dietary notes: ____ · Flight number & hotel (if booked): ____"

Adults-only

"We've reserved ____ seats in your honour. We love your little ones, but this will be a grown-ups' evening. Accepts / declines by 20 July."

Plus-ones, handled kindly

"____ and guest — we'd love to meet them! Guest's name for the place card: ____." (And when there's no plus-one, name every invited guest and add nothing — the absence is the answer.)

Online RSVP wording

Online RSVPs have quietly become the default for destination weddings — replies land in seconds from any country, nothing sits in the post, and details arrive structured instead of scrawled. The wording shifts from card-speak to interface-speak: short labels, one question per line, and a warm confirmation ("You're on the list — we can't wait").

The detail that changes everything: personalised links. When each household's link already knows who they are, guests never type names, families reply together in one pass, and you never de-duplicate "J. Smith" against "Jamie Smith" again.

Setting (and holding) the deadline

Give the deadline a reason and it holds itself: "please reply by 20 July so we can confirm the caterer". For destination weddings that's two to three months out — the full timeline walks through why. Print the date on every RSVP surface, and resist extending it publicly; extend privately for the few who genuinely need it.

Chasing non-responders politely

Scripts that keep friendships intact:

• Four weeks out (light): "We're finalising numbers for Ravello — pop your RSVP through when you have a sec! Link below."
• One week out (direct, warm): "Last call for RSVPs this Friday — we'd love to know either way so we can plan properly."
• After the deadline (personal): "No RSVP from you yet — everything okay? We'd love you there; just need to give the caterer numbers Monday."

And the golden rule: reminders go only to people who haven't replied. Guests who answered in week one should never see a "final call".

Tracking responses without a spreadsheet

However replies arrive, you need one live view: who's confirmed, who's declined, who's silent, plus meals, dietaries and travel details per person. A spreadsheet can hold it — the grind is data entry and keeping it truthful as replies trickle in over months. Purpose-built RSVP tools update the list the moment a guest replies and show the gaps at a glance; evraft adds the destination layer on top, pairing each reply with flights, hotels and arrival times.