Work backwards from the supplier dates
Start with a list of everything that needs a number and the date each one needs it. The caterer’s final headcount is usually the earliest and the firmest. The seating plan, printed place cards, name badges, transport bookings, hotel room blocks and the venue’s fire capacity confirmation each have their own date. Write them down; the earliest is your hard date.
The RSVP deadline sits before that hard date by the time it takes to follow up: enough for one reminder, a few days for answers, and a short round of personal calls to the guests who matter most. For most events that gap is about a week. The deadline you print is therefore not the last possible day — it is the day that leaves you room.
- List every decision that depends on numbers, with its supplier date.
- Take the earliest date as the hard date.
- Subtract the follow-up window: reminder, waiting time, personal calls.
- Print that as the RSVP deadline, with the weekday.
- Send the invitation early enough that guests have time to answer before it.
RSVP deadlines by event type
Event types differ in how far ahead guests plan and how early suppliers commit, so the same rule produces different dates. These are common conventions rather than fixed rules; your own suppliers’ dates always win.
- Wedding: invitations several weeks to a couple of months ahead; RSVP deadline about three to four weeks before the day, because seating, menus and transfers all follow it.
- Gala or seated dinner: deadline two to three weeks before, ahead of the table plan and the kitchen’s order.
- Conference: registration closes when sessions, badges and catering lock — often one to two weeks before, with a separate earlier date for session choices.
- Corporate reception or launch: one to two weeks before; standing events tolerate late changes better than seated ones.
- Birthday or private party: about a week before, or a few days for a casual gathering.
- Children’s party: a few days to a week before, so food and allergies can be planned; parents answer late, so follow up early.
Following up with guests who have not replied
Silence is rarely a refusal. Usually the invitation was opened at a bad moment and forgotten, landed in a folder nobody reads, or went to an address the guest no longer uses. Before you chase anyone, check whether the invitation actually arrived; an address that bounced needs a correction, not a reminder.
Follow up with the silence only. A reminder sent to the whole list annoys the people who already answered and teaches everyone that your messages can be ignored. Keep it short, friendly and useful: the event, the deadline, the one link or number to reply with, and nothing that sounds like a reproach.
- Friendly: “Just a reminder — we would love to know by Friday 12 May whether you can join us.”
- Practical: “We are confirming numbers with the venue on Monday. Could you let us know by Friday?”
- Business: “Your place at the dinner is still held. Please confirm or decline by 12 May using your link.”
When a reminder is not enough
After one written reminder, the remaining silence is best handled person to person. A short call or a direct message from someone the guest knows — the host, the account manager, the colleague who suggested the invitation — gets an answer when a third email will not. Keep these calls for the guests whose presence matters to the event or to the numbers: the VIPs, the speakers, the families with several seats.
Decide in advance what silence means when the deadline passes. For a seated event, the usual choice is to plan as if a silent guest is not coming, and to say so in the reminder. For a standing event, you might count a share of the silent ones based on your own past events. Either way, decide once and use the same rule for everybody.
Late yeses, cancellations and substitutes
The deadline does not stop people changing their minds. A late yes is good news if there is still room and the kitchen can absorb it; say yes warmly when you can and say plainly when you cannot. A cancellation after the deadline is more useful than a no-show, so make cancelling easy — the same link, a reply to the invitation, a named contact — and thank people for it.
Corporate events bring substitutes: the invited director sends a colleague instead. Decide whether places are transferable before invitations go out, and if they are, collect the substitute’s name and questions as a proper reply rather than a note in someone’s inbox. Otherwise the door will meet a stranger with somebody else’s code.
- Set a change cut-off for meals and seating, usually the caterer’s date.
- After it, accept cancellations but warn that meal changes may not be possible.
- Keep the reply history so you know who changed and when.
- Treat a substitute as a new guest record, linked to the original invitation.
Final numbers for the caterer
The final count is the confirmed yeses, plus their named companions, broken down the way the kitchen and the floor need it: meal choices, allergies and intolerances with their severity, children’s portions, and any seating constraints. Give the caterer counts, not a list of names, unless they need names for place cards or allergy labels.
Then decide the margin. Some confirmed guests will not arrive, and a few unexpected ones will; the size of that gap differs between events and audiences, so base it on your own previous events rather than a rule of thumb. If you have measured how many yes replies came through the door last time, you have the best number available.
After the event: learn your own gap
The deadline and the follow-up are only judged on the night: how many confirmed guests came, how many arrived without replying, how many cancelled after the cut-off. If replies and check-ins are recorded against the same names, the comparison is a list rather than a guess, and the next event’s deadline and margin can be set from evidence.
In Winglark, reminders go only to guests who have not answered, every invitation’s delivery is traced so a bounced address is fixed rather than reminded, and the report compares replies with the door, by name.