A guest sends a quick message: their partner can now attend. You reply warmly, but the caterer receives the old count and the check-in team has only one name. The RSVP changed; the event plan did not.
Update the authoritative list first
Record the change in the list used to coordinate the event, with the date and person making it. Confirm what changed: attendance, guest count, named attendee or only arrival time. Do not infer that an unnamed additional guest has the same dietary or access requirements as the original attendee.
Check whether the event can accommodate the request under its capacity, booking and supplier arrangements before promising it. If a deadline has passed, explain what is still possible rather than quietly hoping another team will absorb the difference.
Follow the change through its dependencies
- Catering count and relevant dietary communication.
- Seating or group allocation.
- Named entry, badges or tickets.
- Transport and agreed access arrangements.
Not every change affects every item. A guest leaving early may alter transport without changing the meal count. Identify the actual consequences and send each supplier only the information needed for their role.
Confirm receipt where action is required
A message sent is not the same as a revised order accepted. Ask the responsible supplier or team member to confirm changes that affect numbers, cost or service. Keep the confirmation with the event record.
For the guest, provide a short reply that states what has been accepted and anything they still need to supply. Avoid asking them to repeat the entire booking because one field changed.
Before issuing the final operational lists, mark the version and time, and explain how later changes will be handled. A printed sheet can remain useful if everyone knows where updates are recorded.
The aim is not to make a friendly RSVP exchange bureaucratic. It is to ensure that the welcome promised in a message becomes the right place, meal and entry arrangement when the guest arrives.