Managing wedding guests without losing your sanity

The list that keeps growing

Nathalie and Julien had planned for 90 guests at their wedding. Six weeks before the big day, they were at 118. Between the "we really can't not invite my cousin and her husband, that would be awkward" moments and Julien's colleagues who invited themselves by casually asking "so, when's the wedding?", the list grew by 30% before they even realised it. This isn't an isolated story: it's almost a rule. Plan from the start for a 10 to 15% margin between the "dream" list and the "real" list, and budget for it accordingly rather than discovering the gap in a full-blown panic two months out.

A wedding guest list is never just an Excel sheet with names and checkboxes. It's a miniature diplomatic forum, a logistics exercise and a psychological endurance test, often all at once. Here's how to get through it without losing your sanity or your relationship.

The replies that never arrive

The RSVP card is a beautiful invention on paper and a nightmare in reality. Out of a list of 100 people, expect a third to reply within ten days, a third within the month, and the last third to never reply spontaneously at all. That's a statistical fact, not a judgement on your friends.

"We sent the invitations in March for a September wedding. By the end of May, we had 40 replies out of 130. We panicked, thinking nobody wanted to come. Turns out people were just waiting to see if they'd be free six months ahead."

The solution isn't to politely wait for the magic to happen. It's to set a clear reply deadline (usually 6 to 8 weeks before the wedding) and to plan, right from the moment invitations go out, two follow-ups: a gentle mid-point nudge ("hey, we're working on the seating plan, let us know soon if you're coming!") and a firm reminder one week before the deadline. Direct messages work far better than a group email nobody feels personally addressed by. Expect to need to individually chase between 15 and 25% of guests, often the same kinds of people: distant family, teenage friends you haven't seen in ten years, and polite "maybes".

One detail that changes everything: ask for a single grouped reply for couples and families, not one per person. This avoids ending up with "Mark: yes" and "Sophie, his wife: no reply" three weeks before the event, forcing you to chase down a single missing official "yes".

Diets and allergies, without spending three months on it

This is the classic trap: trying to handle everything case by case through scattered messages, and ending up two weeks before the meal with seven Instagram messages, three texts and an email to sort through just to piece together who's allergic to what. The caterer, meanwhile, wants a clean list two weeks in advance, not a puzzle.

The right method: build the question directly into the RSVP form, with precise checkboxes rather than a free-text field ("vegetarian / vegan / gluten-free / severe allergy - please specify / no restrictions"). A free-text field like "any allergies?" produces unusable answers like "a bit of everything really", or worse, no answer at all because the person doesn't think it applies to them even though they've been allergic to nuts their whole life.

For a wedding of 120 guests, expect on average 8 to 12 specific diets (vegetarian, vegan, gluten-free) and 2 to 4 severe allergies that need to be discussed directly with the caterer, not just ticked off on a form. These last ones deserve a dedicated call or message: a nut allergy isn't negotiable the way a vegetarian preference is, and the caterer needs to know exactly which dish is affected, not just "there's an allergy somewhere in the room."

Advice from a wedding planner with fifteen years of experience: "I always give the caterer the list of diets three weeks ahead, never less. Below that, they just do a generic 'gluten-free for everyone to be safe' menu, which costs more and is usually not as good."

Accommodation and carpooling for guests coming from afar

For a typical wedding, about 30 to 40% of guests travel more than an hour to get there. For them, the wedding isn't just an evening — it's a trip that involves accommodation, often children, and sometimes a pet that needs looking after.

Three things to plan concretely:

• Block hotel rooms early. Negotiate a room block with one or two nearby hotels (often 10 to 15% off the public rate if you book 15 to 20 rooms) and give guests a deadline to book within that block, after which the rooms go back on general sale. Six months out is the right time; by three months out, half the hotels in the area are already booked if the wedding falls on a Saturday in June or September.
• Carpooling doesn't organise itself. A simple group message asking "who has room in their car?" rarely works beyond 15 people, because nobody wants to be the first to reply or the one who "only" has two spots. A shared spreadsheet or a tool that centralises who's leaving from where, at what time, and with how many spots available completely changes the dynamic: people organise themselves without waiting for someone else to take the lead.
• Plan the return trip. This is the point that trips people up most often: everyone thinks about the journey there, nobody about the one back at 2am after a few drinks. A shuttle or a pre-arranged sober carpool avoids awkward debates on the doorstep past midnight.

Kids and childcare: the question people dodge for too long

"Wedding with or without kids" is one of the most divisive decisions there is, and the worst mistake is leaving it unclear until the last minute. If you're welcoming children, say so explicitly on the invitation, don't leave people guessing. If you're not, say that just as explicitly, tactfully but unambiguously, ideally with a solution attached.

For a mid-sized wedding that welcomes children, expect them to make up roughly 10 to 15% of the total guest list. For these families, two options really do reduce the tension: either an on-site childcare setup with one or two carers for the evening (budget around 25 to 35 euros per child per evening for this service, usually very well received by parents who can finally dance), or a list of recommended local babysitters sent ahead of time to the families concerned so they can arrange it themselves.

What never works: deciding "no kids" a week before, assuming everyone will just understand. Families need at least six to eight weeks to find childcare, especially if the wedding falls on a weekend when the whole extended family is already invited and therefore unavailable to babysit.

The seating plan, that political puzzle

The seating plan is arguably the most underestimated task early on and the most time-consuming one at the end. Honestly, expect 4 to 8 hours of actual work for a wedding of 100 to 150 people, often spread over several evenings because the brain hits saturation point after 45 minutes of this kind of decision-making.

Rules that work, drawn from dozens of weddings' worth of experience:

• Never create a "the singles" table or a "people we didn't know where to put" table. It's instantly recognisable and felt as a relegation.
• Always seat at least one shared connection next to anyone who's socially isolated (the colleague who only knows the couple, the childhood friend who came alone).
• Separating families in open conflict isn't cowardice, it's organisational common sense — but don't put them at adjacent tables facing each other all evening either.
• Finalise the plan only after the RSVP deadline, never before, or you'll end up redoing it three times.

The real problem isn't seating 100 people who've all replied. It's handling the 5 to 10% of last-minute changes that arrive after the plan is "finished."

Last-minute guests and cancellations: the invisible margin

Two weeks before the wedding, it's almost guaranteed that one of two things will happen: someone cancels (flu, childcare falling through, a sudden family fallout) or someone asks to come even though they weren't on the original list. Out of 100 confirmed guests, statistically expect 3 to 5 last-minute cancellations, often within 48 to 72 hours of the event.

This is where the per-head budget becomes a nerve-wracking topic. Most caterers ask for a final headcount 5 to 10 days before the event, with a tolerance of 3 to 5% variation at no extra cost. Beyond that, every extra or missing place setting can get expensive: adding 5 place settings the day before can end up costing 20 to 30% more per head than if those same people had been counted in the original number, because the caterer has to improvise rather than plan their purchases.

The most effective workaround: deliberately keep 3 to 5 "floating place settings" in the final budget, neither announced to the caterer as final nor forgotten altogether, a buffer margin that absorbs last-minute adjustments without drama or panic-driven extra cost. And for cancellations, notify the caterer as soon as possible: a cancellation flagged five days ahead can often be refunded or deducted, one flagged the morning of the event, almost never.

The per-head budget, that number that keeps moving

The per-head budget (meal, drinks, sometimes venue hire spread across the guest count) is rarely stable between the first quote and the final bill. Couples who track their spending closely see, on average, an 8 to 15% increase between the initial budget and the actual cost per guest, mainly due to three factors: drinks consumed beyond the package, options added along the way (an extra dessert, a fancier wine because "you only get married once"), and the famous floating place settings margin mentioned above.

A useful benchmark to avoid getting caught out: always ask the caterer for an "all-inclusive" per-person price that includes service and drinks, not a price for "the dish, with everything else on top", which looks well-controlled on paper but easily blows out by 15 to 20% on the day once wine, coffee and service are added.

Centralise instead of juggling fifteen conversations

What makes managing guests exhausting is almost never one particular task — it's the scattering. Replies come in by text, WhatsApp, email and sometimes verbally over drinks ("yes yes we're coming, put us down!"). Diets are jotted on a sticky note, in a notebook, in a phone note. Carpooling gets discussed in a different WhatsApp group than the one about diets. The result: by the time you finalise the seating plan, nobody remembers who confirmed, who still hasn't replied, and who mentioned an allergy six weeks ago in a conversation now buried under other messages.

Bringing all this information together into one shared tracking tool — who's replied, who's eating what, who needs a room or a car seat — saves you from having to piece it all back together by hand the week before the wedding. This is exactly the kind of coordination that tools like OuiCanPlan simplify: one single place where guests confirm, specify their requirements and see the practical information, instead of fifteen parallel threads to keep track of. The results are real and ad-free.

What to remember before you get started

Managing wedding guests isn't a side administrative task: it's often the item that consumes the most mental energy over the six months of planning, far more than choosing the venue or the dress. The key isn't trying to control everything perfectly, but anticipating the known friction points: the follow-ups you'll need to send, the diets you'll need to collect cleanly, the families you'll need to keep apart at the tables, and the budget margin you'll need to keep for last-minute surprises. None of this needs to be improvised at the last minute under stress. It can all be planned, six months ahead, with method rather than hope.