Sort the change before you announce it
Before writing a single message, decide what kind of change you are dealing with. Most fall into one of five kinds: a guest added, a guest removed, a guest replaced by someone else, a detail of the event changed (time, venue, dress code, programme), or the event cancelled or postponed. They look similar on a busy afternoon, but each one has a different audience and a different message.
The question to ask every time is: who does this change actually affect? A new time affects everyone who is coming, and perhaps those who have not answered yet; it does not affect people who already declined. A new parking entrance affects only the guests who said they would drive. A late addition affects one person — the new guest — and the door. Write the audience down before the words.
- Guest added: the new guest, and the door list.
- Guest removed or uninvited: that guest only, personally, and the door list.
- Guest replaced: the original guest, the replacement, and the door list.
- Detail changed: those who accepted, those who have not answered, and staff; not those who declined.
- Cancelled or postponed: everyone invited, including those who declined, because they deserve to know.
Adding guests after the invitations have gone out
A late guest should receive the same invitation as everybody else, not a forwarded copy or a hurried text. If the first wave received a personal link with their own reply, the late guest needs their own link too — otherwise their answer cannot be counted and their name will not be on the door list. Avoid the shortcut of asking an existing guest to forward their invitation: it gives the new guest the wrong person’s link and leaves the original guest’s record confused.
Late additions often come with a shorter reply window. Say so politely in the invitation — the date by which you need an answer — and if the catering numbers are already fixed, check with the caterer before you send, not after. A late guest who replies yes to an event that has no seat left is a harder conversation than a late invitation that was never sent.
Keep a note of why and when each late guest was added. It is the line that explains, weeks later, why the final list is longer than the one approved.
Moving the time or the venue
A change of time or place is the change that most often goes wrong, because it is sent too widely or not widely enough. Send it to everyone who accepted and everyone who has not yet answered. Leave out those who declined, unless the change is big enough that it might change their answer — moving a weekday evening to a Saturday, for instance — in which case tell them too and invite them to reply again.
Make the message about the change, and only the change. The subject line should say what moved: “New start time: 19:30”, not “Update”. In the first line, give the new detail and the old one side by side, so nobody has to compare two emails. Then say clearly whether the guest needs to do anything: usually nothing, sometimes reply again. If the invitation contained a calendar entry, send a new one with the change.
Then update everything that copied the old detail: the event page, the reminder you scheduled for next week, the confirmation text, the signs at the venue, the instructions for the door staff. The most common failure is a reminder written before the change that goes out after it.
Swapping one guest for another
A guest who cannot come will sometimes ask to send someone in their place. Decide in advance whether you allow it, and for which events: at a public lecture it is a kindness, at a seated dinner with a careful table plan it may not be possible, and at a confidential briefing it may not be allowed at all.
If you accept the swap, treat it as two changes: the original guest is marked as declined (with a note that they sent a replacement), and the replacement becomes a new guest with their own invitation and their own code. Do not edit the name on the original record and keep the old code alive. A code is a key; when the person changes, the key should change with them, and the old one should stop opening the door.
Uninviting a guest
It happens: a list was merged badly, a name was included by mistake, or a situation has changed. Do it personally and briefly, by a person the guest knows if possible, and never by a group message. Then make sure the guest’s code no longer admits them, and that their name is removed from any printed list. An uninvited guest who still holds a working code is a decision you have handed to the door staff without telling them.
Cancelling or postponing the event
A cancellation goes to everyone who was invited, including those who declined; a postponement too, with the new date if you have one, or a clear promise of when they will hear. Say it in the first sentence. Apologise once, plainly, and do not bury the news under explanation. If there was anything to return — a deposit, a ticket price, a gift registered for the day — say how and when it will be handled.
For a postponement, ask everyone to reply again for the new date rather than carrying the old answers forward. People who could come on the 12th may not be free on the 26th, and a list of yesterday’s yeses is the most misleading number you can give a caterer.
Keeping the door list current until the doors open
Every change above ends at the same place: the door. If the door works from a list printed on Tuesday, every change since Tuesday is invisible to the person deciding who comes in. The safest arrangement is that the door reads the live guest list itself, so that a guest added at five o’clock can be admitted at seven, a replaced guest’s old code is refused, and an uninvited guest is shown as such on the screen.
If you do print a list, print it as late as you can, mark the time on it, and have one person responsible for the changes that come after. Brief the door staff on the changes that matter tonight: who was added late, who was replaced, who must not be admitted. They should never learn about a change from the guest in front of them.
Doing it without telling everyone again
The working rule behind all of this is simple: a change reaches only the people it concerns, and the record keeps a trace of what was sent to whom. In Winglark, InvitePulse works this way — add a guest late or move the time, and only the guests it affects hear about it, never the whole list again — and GatePass reads the same guest record at the door, so a change made in the afternoon is the list the door sees in the evening.