Handling last-minute seating changes safely

Updated:

Mixed weddingDance floorEntranceBar123456789
Mixed wedding

Something almost always changes in the last week before an event. A few habits keep your seating chart reliable anyway.

Back up before you change

Download the project file before larger changes. Name it with the date, for example “wedding-2027-06-05.seatingplan.json”. That way you can always go back.

Cancellation: delete the guest or free the seat

If someone cancels, set their RSVP to “Declined” – that way you still know later who was invited. If they already had a table, “Free up seats” releases it. You can also delete the guest or just remove them from their table. The free seat shows up immediately in the table overview, and a published seat finder no longer lists the guest.

Late addition: add and seat

Add new guests at the top of the guest list. “Seat one by one” then shows every guest without a seat in turn, together with the tables that still have room.

A table is removed or gets smaller

If you reduce a table’s seats or delete it, the planner asks first when guests would lose their seat. Those guests become “not seated yet” – nobody disappears quietly. Each of these changes can be reverted with Undo.

Moving tables

When you move or rotate a table, its guests stay with it. A duplicated table, on the other hand, starts empty so nobody is seated twice.

Compare two arrangements

If you are unsure, create a variant. Variants share the guest list but have their own tables and seating.

The checklist in Review & print shows whether every guest has a seat. Then print the floor plan, guest list and poster again – all outputs come from the same data and match each other.

Try it in the planner