For the week before, when plans move
Handling RSVP Changes without Starting from Scratch
A yes that turns into a no, a partner added late, a date that moved twice: changes belong on one live list, not in ten chats you have to remember.
For the week before, when plans move
A yes that turns into a no, a partner added late, a date that moved twice: changes belong on one live list, not in ten chats you have to remember.
Someone who said no and now wants to come, a partner added at the last minute, a date that moved twice: changes are normal, and the mess only happens when each one arrives as a separate message you have to remember and re-count. A page with a live list makes a change an edit instead of a crisis.
Two things move when plans shift: what guests send and what you fix. Both are handled by the same address, so nobody is reading an outdated version of the day.
A guest who changes their mind reopens the page and replies again; the new answer replaces the old one on your list, which shows their current state, not a pile of contradictions. If they want to add a plus-one, it lands inside whatever limit you set, so a late extra is a real seat with a name rather than an anonymous stranger.
When you move the date, the venue or the order of the day, you change it on the page and the same link carries the correction. There is no new address to send and no thread to rewrite; the next person who opens it reads the fixed plan. Draft changes stay invisible to guests until you publish them, so you are never showing a half-updated time.
You decide how many extra places a guest may name. Inside it, changes arrive counted; outside it, they do not, so the headcount never runs away from you.
Shown on the page, it gives guests a reason to settle their plans and gives you a moment to finalise numbers before you commit to the caterer.
It reflects the current answer for every name, so a flip from no to yes shows as yes the moment it happens, not in a chat you have to scroll.
A page softens the awkwardness of a change of mind, but a cut-off date keeps it fair to everyone:
How it works
Tell the person who changed their mind to reopen the link and answer once more. Their new yes or no overwrites the old one on the list.
Set the rule up front so a late companion arrives as a named seat you allowed, instead of an untracked extra you discover on the day.
When a detail moves, fix it on the page and publish. Every guest with the same link reads the corrected version from then on.
Open the live count just before you finalise numbers, because the changes that came in over the week are already totalled there.
Questions
Yes. They reopen the invitation and answer again, and the newest reply is the one that counts on your list. You are not left holding a yes that has quietly turned into a no.
No. Edit the page and publish; the link stays the same and everyone who opens it later reads the new date. Only people who already visited need a heads-up, and you can remind the non-responders from your list.
They name the extra person inside your set limit and it appears on the list with a real name attached. Beyond the limit it simply will not add, so the count stays yours to trust.
It shows each guest's current state, which is what you need to plan from. A change of mind updates the row rather than leaving two answers fighting over the same seat.
Get Started
Guests update their reply, you edit the page, and the same link stays truthful through every flip. Start free and upgrade as your guest list grows.