Guest List and RSVPs: A Practical System That Holds
The list drives almost every other decision
Before touring venues, tasting menus or booking anything, you need a rough headcount. That number determines the size of the space, the catering budget, how many tables you need, the dance floor, whether shuttles make sense. Choosing a venue first and squeezing the list to fit it later usually ends in painful cuts with family involved.
A method that works: each partner writes their own list separately, without consulting, without filtering. Then you merge both, strip duplicates and count. That first number is almost always alarming. That's fine, and it's useful data: it tells you how much you have to cut and where from.
If parents want to add guests, ask for their lists in writing with a hard cap stated upfront. Saying "Mom, you have fifteen seats" at the start avoids the far worse conversation of "Mom, we need to remove twelve names" three months later.
The three-tier system
Split the list into three groups. Tier A is anyone whose absence would change the day for you: immediate family, closest friends, wedding party. Tier B is people you genuinely want there but could live without: cousins you rarely see, coworkers who are actual friends, friends from earlier chapters. Tier C is the grey zone: acquaintances, social obligations, people you added because they invited you to theirs.
This ordering does two jobs. First, it lets you cut with a criterion instead of on gut feeling and guilt. Second, it fills gaps: as declines come in from tiers A and B, you can move down into C without having promised anyone anything.
If you plan to invite in waves, leave three to four weeks between the first and second batch. Any tighter and it shows, and anyone who receives an invitation two weeks out knows exactly what happened.
A useful filter for tier C: have you had an actual conversation with this person in the last year that wasn't a birthday message or a group chat? If not, that isn't a wedding list, it's a contacts list.
Timelines that actually hold
Once the date is set and the venue is booked, save the dates go out eight to ten months ahead. Their only job is to block the day in people's calendars. No schedule, no dress code, no logistics. For a destination wedding or a long holiday weekend, push it to twelve months so guests can buy flights and request time off.
The full invitation, with all the information, goes out three to four months ahead, or five to six for destination weddings. It carries the RSVP deadline, and here's the part people get wrong: set that deadline six to eight weeks before the wedding, not four. You need buffer to chase stragglers, finalize seating and hand numbers to the caterer.
Your caterer will typically ask for the final count seven to fifteen days out, depending on the contract. Read that clause carefully: many set a guaranteed minimum and only allow upward adjustments after a certain date. Knowing that exact day is what tells you when your list truly has to be closed.
Leave a full week between your RSVP deadline and the day you start the seating chart. Building a chart around unconfirmed names means building it twice.
What to collect and how to store it
The common mistake is organizing the list by person when the real unit is the invitation: a household, a couple, a family. One record per invitation prevents duplicate messages and headcounts that never reconcile.
Each record needs a primary contact name, a channel (phone with country code, or email), seats offered, seats confirmed, the names of every attendee spelled the way they'll appear on place cards, dietary restrictions, whether they're attending the ceremony, the reception or both, and which side or group they belong to. Add a notes column for everything that fits nowhere else: the aunt who can't do stairs, the friend landing on the late flight.
On dietary needs, never ask a bare "any allergies?" Offer concrete options: vegetarian, vegan, gluten-free, dairy-free, nut allergy, severe allergy, other. That gives your caterer usable categories instead of free-form paragraphs someone has to interpret.
If you're arranging shuttles or hotel blocks, ask in the same form: whether they'll use the bus and from which stop, whether they need a hotel recommendation. Every question you skip now becomes a text thread during wedding week. A digital invitation that captures all of it in one flow, like the ones on Nozzia, saves you from copying answers by hand out of four different places.
Plus-ones, kids and other awkward conversations
Decide seats per invitation before you send anything, and don't renegotiate case by case. Common criteria: a plus-one for anyone living with a partner, married or not; a plus-one for anyone who'd otherwise attend alone knowing nobody; and no open plus-ones beyond that. Pick your rule, write it down, apply it identically to both families.
The cleanest way to communicate it is to leave no room for interpretation: address the invitation to the invited people by name, and have the form offer exactly those seats. If someone asks whether they can bring a date, the answer is that the guest count is closed. It's a short sentence, it's true, and it doesn't insult anyone.
On children, any decision is fine as long as it's consistent. If the wedding is adults-only, say so in the invitation in one neutral line, and tell anyone with a baby personally and early so they can arrange care. If kids are welcome, ask for ages: a children's menu is useless for an eight-month-old, and knowing how many guests are between three and ten tells you whether a sitter or an activity table is worth booking.
Chasing the people who don't reply
Assume a chunk of your list won't respond to the first ask. It isn't indifference, it's that they opened the message on the train and forgot. Follow-up isn't a failure of your system; it's part of it.
A reasonable schedule: first reminder two weeks before the deadline, friendly and general, sent only to non-responders. Second reminder three or four days out, individual this time, through the channel that person actually uses. After the deadline, phone calls. Skip passive nudges in the family group chat; thirty seconds on the phone resolves what five messages won't.
Divide the labor. Each partner chases their own side of the family, and parents chase the guests they added. It's faster, and nobody has to field an RSVP request from a stranger.
For anyone still silent after a call, apply a written rule: no confirmation, no seat. State it clearly in the second reminder and then follow through. It's fairer than holding empty chairs you're paying for anyway.
Keep everything after the wedding. The list with addresses, contact channels and who actually attended is exactly what you'll need for thank-you notes, for sending out the photo gallery link, and for knowing who still deserves a phone call.
- lista de invitados
- RSVP
- organización de boda
- invitaciones digitales
- planificación