The Complete UK Wedding RSVP Guide (2026)

By Andrew Heppinstall Updated 22 June 2026 12 min read

Wedding RSVPs in the UK in 2026 sit somewhere between tradition and chaos: paper cards, group chats, wedding websites, voice notes from a relative who never reads email. This guide covers the lot - timing, methods, multi-event days, multilingual families, dietary safety, chasing non-responders, and how to pick the right approach for your wedding.

What is an RSVP and why does it matter?

RSVP is an abbreviation of the French répondez s'il vous plaît - literally, "please reply". On a wedding invitation, it's a request that the guest tell you whether or not they intend to come. That's the polite version. The blunt version is that without RSVPs, you cannot get married well.

Caterers price per head, usually with a confirmed-numbers deadline ten to fourteen days before the wedding. Venues set minimum spends, draw seating plans and decide whether they need to open a second function room. Florists buy stems by the table count. The DJ needs to know if the evening crowd is forty people or one hundred and forty. Every one of these decisions cascades from a single piece of data: who, exactly, is coming, and to which part of the day.

The financial consequences of bad RSVP data are not trivial. A typical UK wedding breakfast costs between £75 and £140 per head. Over-catering by ten guests is roughly the price of a long weekend in Lisbon. Under-catering, of course, is worse - guests with no plate is the kind of memory people keep. So RSVP collection isn't admin for its own sake. It's the difference between a wedding that runs and one that wobbles.

The other reason RSVPs matter, less talked about, is that they're an early signal of how stressful your run-in is going to be. Couples who collect cleanly and quickly tend to arrive at the wedding rested. Couples who are still texting cousins at 11pm the week before tend not to. If you take nothing else from this guide, take that.

When to send wedding RSVPs in the UK

UK timing is fairly settled, and most guests will be expecting roughly this rhythm:

If you're getting married on a bank-holiday Saturday in May or August - the busiest UK wedding dates - move save-the-dates forward by another month. Guests are juggling three or four weddings a year and they will block out the dates that arrived first.

One small thing that helps: pick an RSVP deadline that's a memorable date, not "the third Tuesday in August". A guest is more likely to act on "RSVP by Friday 7 August" than on "by 23/08". Pinning it to a weekday creates a soft urgency.

How many guests will actually reply?

Across UK weddings we've looked at, the pattern is depressingly consistent: roughly 80% of invited guests reply on or near the deadline, and the remaining 20% need to be chased. That last fifth is where most of the admin pain lives. For a 100-guest wedding, that's 20 individual conversations with people who are not ignoring you on purpose - they're just busy, or they lost the card, or they forgot.

A few factors push the on-time rate up or down:

• Method matters. Paper reply cards posted with a stamp tend to land around 70%. A well-designed online form sits closer to 85%. WhatsApp-based replies, where the guest can answer in two thumb-taps without leaving the app, can reach 90%+ - but only if the message looks personal rather than spammy.
• Clarity matters. If the invitation asks more than two questions, response rates drop. "Yes/no" gets answered. "Yes/no, plus dietary, plus song request, plus accommodation" gets put down for later.
• Demographic skew matters. Older relatives reply faster on average than guests in their twenties. Guests with children reply slower than guests without. Guests travelling internationally are slowest of all.
• The deadline itself matters. A clear, specific date with a one-line consequence ("we need to confirm final numbers with the venue by then") performs noticeably better than a vague "please RSVP soon".

For a detailed breakdown by region, age band and event type, see our UK wedding RSVP statistics 2026 page. The short version: expect to chase about one in five, and budget time for it.

Methods of collecting wedding RSVPs

There is no single right method. The best choice depends on your guest list, your timeline, and how much admin you and your partner are realistically willing to absorb. Here's an honest look at the main options.

Paper RSVP cards

The traditional approach: a printed card with two tick boxes and a return envelope, ideally with a stamp already on it. Beautiful and tactile, and a real keepsake for older relatives who will photograph yours next to the invitation and put both in a drawer. The downsides are real, though - cards get lost in the post, replies trickle in over weeks, and you spend evenings transcribing them into a spreadsheet. Pre-stamped return envelopes also add £0.85-£1.40 per guest to your stationery cost, which adds up at 120+ invites.

Online forms (Typeform, Google Forms, Jotform)

Fast to set up, free or near-free, and easy for guests who are comfortable with web forms. The catch is that you have to drive guests to the form yourself - usually a link printed on the invitation or a QR code. Older guests sometimes won't engage with either. You'll still need a parallel method (a phone number to call) for those guests, which means you're now running two systems.

Wedding websites (Joy, Zola, The Knot, Hitched)

An all-in-one option with an RSVP module bundled into a website that also hosts your story, registry and travel info. Nice for design-conscious couples who want a polished page guests can browse. The RSVP completion rate is typically lower than dedicated tools because guests have to remember the URL, find the page and log in - more friction than a tap on a message. Worth a careful look at our comparison with Joy if you're weighing this approach.

Email

Cheap and direct. Works for tech-comfortable guests and falls apart for everyone else. You'll spend a lot of time copying replies out of your inbox into a tracker, and "reply all" mishaps are not uncommon. Best used as a backup channel rather than the primary one.

Phone

Often the fallback for the last five guests who haven't responded to anything else. Lovely for the conversation - you actually catch up with your great aunt - but slow at scale and dependent on you remembering to log everything afterwards.

WhatsApp and SMS group messaging

Many UK couples now do a hybrid: posted invitation for ceremony, and a WhatsApp message a week later to nudge people toward the actual reply mechanism. WhatsApp has the highest open rate of any channel by a considerable margin. But manually messaging 120 people one by one is its own kind of hell, and group chats turn into chaos within hours. Several tools - including the one we'll get to below - automate the one-to-one messaging while keeping each conversation private. See our comparison with Save the Date for a closer look at WhatsApp-based services.

Conversational AI

The newer option, and the one this site is built around. A guest receives a personal WhatsApp message, replies in plain language ("yes I'm coming, vegetarian please, +1 is Maya"), and the AI extracts the structured data and writes it to your dashboard. It also handles follow-ups, multilingual replies, dietary capture and the awkward "have you booked the hotel yet?" prompts. The benefit is roughly zero admin once it's set up; the cost is a subscription fee, typically £40-£90 for the whole wedding. Our walkthrough shows exactly what guests see.

What information should you capture from each guest?

The temptation is to ask for everything in one go. Resist it. Long forms drop response rates. Better to ask the essentials at RSVP time and follow up later for the nice-to-haves.

Essential at RSVP:

• Confirmed name spelling (it matters for place cards)
• Yes/no for each part of the day they're invited to (ceremony, breakfast, evening)
• Plus-one - yes/no, and the plus-one's full name if confirmed
• Dietary requirements (vegetarian, vegan, halal, kosher, gluten-free, dairy-free)
• Allergies - captured separately from preferences, because they're medical, not stylistic

Helpful, but can be a second-pass:

• Song requests for the DJ or band
• Whether they need help booking a hotel
• Whether they have access requirements (step-free, BSL, hearing loop)
• Whether they're bringing children, and ages
• Questions about dress code, parking, kids being welcome

Putting allergies and dietary preferences in the same field is the most common mistake we see. They look similar but they aren't. A vegan guest who eats fish for the day is a slightly disappointing meal. A coeliac guest who's served the wrong canapé is a hospital trip. Capture them separately and pass them to your caterer separately.

How to chase guests who haven't replied

First, give them a fortnight. Up to two weeks past your deadline is normal - life happens, post sits unopened, calendars get full. Don't fire off a stressed message the day after the deadline.

Then, escalate gently:

1. A polite written nudge first. A short, friendly message - "Hi Sam, just checking you got our invitation - no pressure, but we'd love to know if you can make it so we can finalise numbers with the venue. Either way, just hit reply." Keep it specific and short. Avoid guilt.
2. A second nudge a week later, if needed. Mention that you need to lock in final numbers with the caterer. People respond to concrete deadlines from third parties more than to vague pressure from you.
3. Then phone. If the guest hasn't replied to two written nudges, calling is faster and kinder than a third message. Often they'd assumed they'd already responded.
4. Set a hard cutoff. Decide a "no answer means no" date - usually three days before you submit final numbers - and treat silence as a decline from that date. It's not rude; it's necessary.

Handling multi-event weddings

Most UK weddings are at least three events stacked into one day: ceremony, wedding breakfast, evening reception. Plenty of couples invite different guests to different parts - 80 to the ceremony and breakfast, plus another 60 joining for the evening. That's three different invite lists, three different RSVP questions, and three different head counts your caterer needs.

The single most useful change you can make is to ask a yes/no per sub-event, not a single "are you coming?" question. A guest invited to all three parts might only manage the ceremony. A guest invited to the evening might bring a partner who can do the breakfast but not the evening. Treat each event as its own attendance question and your data stays clean.

It gets more involved at South Asian weddings, where a wedding is often a three-to-five day calendar of distinct events: mehndi, sangeet, civil ceremony, religious ceremony, reception. Each event has its own guest list (often overlapping), its own dress code, its own venue and its own caterer. The "yes/no per event" pattern stretches to fit but the admin load multiplies. We've written specifically about this challenge on our South Asian weddings page.

Jewish weddings frequently split between the bedeken or ketubah signing (close family and witnesses only), the ceremony itself and the reception with dancing. Nigerian weddings often split between a traditional engagement ceremony (sometimes weeks before) and the white wedding. African church weddings can include separate prayer services. The pattern is the same: track each event as a separate attendance question.

Whatever the structure, the rule is the same: one guest, multiple yes/nos. A flat "coming / not coming" field cannot represent the way real weddings actually work.

Managing multilingual guest lists

A growing number of UK weddings have guests across two, three or four languages. A British-Polish wedding might have grandparents who only read Polish, while the bride's siblings reply happily in English. A British-Pakistani wedding might need Urdu for one set of aunts, English for everyone under 50, and Punjabi voice notes for the village relatives back home.

Three approaches work:

1. Bilingual paper invitations - English on one side, the second language on the other. Beautiful but expensive, and you still need someone to receive non-English replies and translate them.
2. Translated online forms - duplicate the form in each language and send the right link to each guest. Works, but adds maintenance: a change to the English form has to be replicated three times.
3. Conversational tools that detect the guest's language and reply in it. This is the strongest option for genuinely cross-language guest lists, because the guest just types in whatever language is most natural and the system handles the rest. Our multilingual weddings page goes into how this plays out in practice.

Whichever route you take, do not rely on younger relatives to translate replies for you. It's an enormous favour to ask, and it gets old very quickly when you're asking five times a week.

Dietary requirements and allergies

UK food allergen law - specifically the Food Information Regulations 2014, sometimes referred to in the context of "Natasha's Law" for pre-packed food - puts a real obligation on caterers to know what's in the food they serve and to communicate the fourteen named allergens accurately. That obligation is theirs, not yours. But you are the link in the chain that passes the data to them. Get it wrong and you're inviting either a wasted plate or a hospital visit.

Capture the following separately:

• Dietary preferences - vegetarian, vegan, pescatarian, halal, kosher, no pork, no beef, no shellfish
• Allergies - the fourteen UK regulated allergens (celery, cereals containing gluten, crustaceans, eggs, fish, lupin, milk, molluscs, mustard, peanuts, sesame, soybeans, sulphites, tree nuts) plus any others the guest mentions
• Severity - "I prefer to avoid" vs "I will need an EpiPen if I eat this". The kitchen needs to know.

Pass these to your caterer in a single clean spreadsheet, ideally two weeks before the wedding, with each guest's name, table number (if known), allergies in one column and dietary preferences in another. Don't merge them. Don't summarise them. Your caterer would rather have one row per guest with empty cells than a sentence describing the table.

The caterer handoff

Your caterer needs three things from you, on a clear schedule:

• Final confirmed numbers for the wedding breakfast - usually 10-14 days before the wedding, per your contract.
• Per-guest dietary and allergy data - same deadline.
• Table plan with names - 5-7 days before, so place cards can be printed and plates can be flagged correctly.

Most professional caterers will accept this as an Excel file, a CSV or even a tidy email. What they cannot work from is "I'll send it over later" - any time you push back the data, you push back the kitchen's prep, and a stressed kitchen is the start of every catering problem you've ever read about.

Talk to your caterer early - ideally when you book - about exactly what format they want and when. Some have an online portal. Some want a phone call. Knowing their preferences upfront removes a friction point at the worst possible moment.

Common RSVP mistakes UK couples make

1. Setting the deadline too close to the wedding. Three weeks is the minimum; four is comfortable. Two weeks gives you no slack to chase.
2. Combining allergies and preferences in one field. You will regret this when the caterer asks "is the dairy one a lactose intolerance or a milk allergy?" and you have to ring four guests back.
3. Asking too many questions on the invitation card itself. Anything beyond yes/no/dietary lowers response rates. Capture the rest in a follow-up.
4. Not specifying who is invited. Address the invitation to specific people by name. "The Smith Family" is ambiguous - does it include the adult children? Be explicit.
5. Forgetting that plus-ones need their own dietary capture. If you allow plus-ones, capture their name and requirements too. Otherwise the kitchen has half a table they know nothing about.
6. Putting an RSVP-by date that isn't a specific weekday. "By the end of August" is invitation to ignore. "By Friday 28 August" is concrete.
7. Relying on one channel for everyone. A digital-only RSVP loses your less tech-comfortable relatives. A paper-only RSVP loses your group of friends who reply to nothing slower than WhatsApp.
8. Not tracking the data centrally. Replies arriving across three inboxes, two phones, the post and a kitchen drawer is how guests get missed. One spreadsheet (or one tool) for everything.
9. Forgetting evening-only guests in the seating plan. They're not at the breakfast but they still need a table reference for the evening drinks station.
10. Not setting a "silence equals decline" date. If you don't define this, you'll catered for guests who aren't coming.

A timeline for RSVPs

A week-by-week working calendar from about eight months out:

When to consider a managed RSVP service

Managed services - whether that's a dedicated tool like AisleReply, a paid module on your wedding website, or hiring a wedding planner to handle it - aren't right for every wedding. A 40-person ceremony at a registry office followed by lunch in the garden doesn't need anything more than a group chat. But there are situations where a managed service genuinely earns its keep:

• Large guest counts. Anything past about 80 guests starts to bend the "we'll just do a spreadsheet" approach. Past 150, manual tracking is a full second job.
• Multilingual guest lists. If you're translating replies from three languages, automation pays for itself within a week.
• Multi-event weddings. Tracking five events x 200 guests = 1,000 individual yes/nos. Spreadsheets handle this badly.
• One stressed parent. Often the mother of the bride or groom is doing this admin on top of a full-time job. A managed service is, in this case, a gift to that person.
• A short engagement. Six months or less means everything has to move quickly, with no slack for slow RSVPs.
• Working with a planner. Most professional planners now expect digital RSVP data they can pull into their seating tools - see our wedding planners page for how this typically works.

If none of those apply, paper plus a tracker spreadsheet may be all you need. If two or more apply, look seriously at a managed option. Our frequently asked questions page covers the most common queries we hear from couples weighing this up.

Written by Andrew Heppinstall, founder of AisleReply. AisleReply is operated by Validus Media Ltd, registered in England and Wales, company number 08013355. Last updated 22 June 2026.