✍️ Article

From RSVP to Seating Plan: Handling Last-Minute Wedding Guest Changes

The week before a wedding can contain several incompatible lists: invitations sent, replies received, numbers promised to catering and names placed at tables. They often diverge because each list represents a different question.

A reliable process connects them without pretending they are interchangeable. Use the Wedding RSVP Follow-Up Studio for guest responses and the Wedding Planning Lab for seating assignments.

Decide what each number actually means

There are at least four different counts: invited, accepted, attending as of your last confirmation, and seated in the current room plan. A person may be accepted but not seated yet, or seated provisionally before a final reply. That mismatch should be visible, not silently corrected.

A sample change register might read:

Situation RSVP record Seating decision
Guest has not answered Awaiting reply Leave provisional / unassigned
Plus-one confirmed Update actual accepted count Add one separate seating place
Guest cannot attend Record response source and date Remove assignment and review meal count
Dietary update received Check catering’s submission procedure Avoid broadcasting sensitive details

The venue or caterer may have its own final-headcount deadline. Confirm it directly; do not generate it from a generic checklist.

Handle the cutoff as a process

Before the stated supplier cutoff, reconcile the latest guest responses with the expected seating count. Identify each unresolved entry and assign a person to contact the guest. After the cutoff, submit amendments in the way your supplier permits, and keep a record of the reply.

Do not assume a late guest can be added just because your draft board shows an empty seat. Capacity, meals, access and venue approval are separate questions.

Keep a small, versioned seating history

In the Lab, reassign people using drag-and-drop or the per-guest menu. Save a JSON backup before major changes if you need a recoverable prior version. A backup is a point-in-time local file; it is not an audit record of a supplier’s acceptance.

Use the Event Guest Seating Planner for notes about table capacity and the status of unresolved placements. Be careful about storing information that guests would not want widely disclosed.

Tell the right people exactly what changed

A last-minute handoff should be a delta, not another 20-page plan. For example: “Table B loses one person; Table C gains one; total confirmed guest count unchanged. Please acknowledge the revision to version 3.” Only send such a statement when the figures are actually verified.

The catering team may need the final count, while an usher needs table names and guest assignments. They do not necessarily need each other’s information.

Final review before doors open

Check the number of accepted guests, names waiting for a seat, per-table totals, supplier confirmation of final headcount and the owner for live adjustments. If something is unknown, write it as unknown and point to the next person who can resolve it.

Try the workflow: Keep RSVP responses in the follow-up studio and test seating changes with the free Lab.