When a guest changes a wedding RSVP after the deadline, confirm exactly who and which events are affected, check what your venue and caterer can still accommodate, and update one master guest record. Then notify everyone using that information. A submitted online change is a request to reconcile your plans, especially when it adds a person or changes a meal.
The difficult part is rarely typing a different answer into a spreadsheet. It is making sure the seating chart, dinner count, transportation list, and guest all reflect the same decision. This guide covers changes to an existing response, rather than chasing someone who has never replied.
Cover: AI-assisted editorial layout based on a real LunaInvites product photograph. Styling props shown are not included in the invitation set.
First, identify what actually changed
A message saying “Our plans changed” leaves several questions open. Does one person in the household need to cancel, or everyone? Is the guest missing the ceremony but attending dinner? Has an originally invited companion changed, or is someone asking to bring an additional person?
Reply privately and ask only for details needed to plan. A guest dealing with an emergency does not need to give you a personal explanation. You do need names, affected events, and a clear attendance decision. Keep a request awaiting approval separate from a confirmed update.
| Change received | Check before confirming | Records to review |
|---|---|---|
| Accepted, now cannot attend | Which named people and events? | Attendance, meals, seating, transport |
| Declined, now wants to attend | Capacity, catering, and whether a seat remains available | Pending request, then confirmed attendance if possible |
| Meal selection changed | Whether the caterer can make the substitution | Meal total and the individual guest's place setting |
| Only part of the celebration | Exactly which invited events they will attend | Separate ceremony, reception, and additional-event lists |
| Different or additional companion | The original invitation and whether you approve the change | Named guest record, seating, meals |
Understand the three deadlines that matter
Your printed RSVP date, the website's form-closing date, and the vendors' final-change dates may be different. Before answering a late request, look at all three. The invitation deadline tells guests when you need their answer; it does not tell you what a caterer can change this afternoon.
Check the agreements and current instructions you received from each vendor. Ask a precise question: “Can we remove one chicken meal and add one vegetarian meal for the same guest, and when do you need that confirmed?” Avoid assuming that a cancellation reduces the bill, or that an empty chair automatically makes room for a different guest. Minimums, preparation, staffing, and venue limits can affect the answer.
For example, your invitation might request replies by May 1, while a vendor needs a final list on May 8. A May 3 change and a May 10 change could therefore need different handling. These dates are an illustration, not a recommended universal timeline.
Use one change log, even if replies arrive everywhere
Choose one person to maintain the master list. Your partner, parent, or planner can forward messages to that person rather than each editing a separate copy. If you share editing access, agree which record is authoritative and how pending requests are marked.
A useful change log needs these fields:
- Guest name and household identifier
- Date and channel of the new message
- Previous confirmed response
- Requested change, including the affected event
- Status: pending, confirmed, or unable to accommodate
- Vendor or planner acknowledgment still needed
- Date the final answer was sent to the guest
Write “Alex Rivera, reception: yes to no” rather than “Riveras canceled” if Alex's partner is still coming. Count individual people as well as households. Preserve a short change history so you can explain why yesterday's export differs from today's list without searching through every text thread.
If the issue is an unidentified or repeated submission rather than a changed plan, use our guide to RSVPs with missing names and duplicate replies first. Do not merge two records merely because their surnames match.
Know what your online RSVP form does
Check the behavior of your particular website before telling guests to submit again. The Knot's guest instructions explain that guests can update a response while online RSVP remains open. Its guidance also recommends a personal message for changes close to the wedding, when final arrangements may already be underway.
WedSites' RSVP change guidance describes a setup in which a new submission replaces the earlier response. It recommends saving a guest-list export when finalizing arrangements and controlling whether later edits remain available. That behavior should not be assumed for every platform.
For your own form, test with a record you control: can an existing guest edit, does the new response replace the old one, and who receives an alert? Remove test data from planning counts. If the form is closed, provide a direct contact route instead of sending guests to an unavailable button. Our phone and text RSVP guide can help you make that route clear.
Four messages you can adapt
The following examples are original templates. Replace the names, dates, and arrangements with your own, and send them privately.
1. Accepting a cancellation
“Thanks for letting us know, Morgan. We understand and will miss you. I've updated your reception attendance to not attending. Just to confirm, is Jamie still joining us for the ceremony and dinner?”
This acknowledges the guest without asking for an explanation or making assumptions about the rest of the household.
2. Holding a declined-to-accepted request while checking
“Thanks for reaching out, Taylor. We'd love to see you, but our final arrangements have been submitted. I'll check with our venue and caterer and get back to you by Thursday evening. Please wait for my confirmation before changing your plans around the reception.”
Only promise a reply time you can meet. If attendance cannot be accommodated, say so clearly and kindly: “I've checked, and unfortunately we can't add another guest to the reception at this stage.”
3. Confirming a meal change after approval
“Hi Jordan, the caterer has confirmed your change from chicken to the vegetarian selection. Your reception attendance remains confirmed, and I've updated our seating and meal list. Thanks for contacting us directly.”
If the change concerns a dietary need, share the necessary information with the caterer through an appropriate private channel. Do not promise that a meal is suitable until the caterer has confirmed what it can provide. See our dietary-requirements RSVP guide for wording that separates meal preference from a practical requirement.
4. Redirecting changes after the form closes
“Online RSVP is now closed. If your confirmed plans change, please text Avery at the contact number provided with your invitation. Include your full name and the event affected. We'll reply directly to confirm what we can update.”
Place this note on the RSVP page or send it to affected guests. You generally do not need to replace the original invitation because one household's response changes.
Send one clear update to everyone who needs it
After you confirm the change, work outward from the master list. Review the caterer's meal count, the seating plan, any name or meal indicators already prepared, and transport reservations if relevant. For a multi-event celebration, check each invited event separately.
Send a concise change summary rather than an unmarked replacement spreadsheet: “Version 3, May 6: Alex Rivera removed from reception dinner; Jamie Rivera remains attending; total reception guests now 84.” Ask the recipient to acknowledge the update when it affects a deadline or service. A message sent is not the same as a change accepted.
Mark old exports as superseded and give the final version a date and time. On the wedding day, your designated contact should have the current version and a short list of unresolved items. This prevents a helpful relative from handing the venue an outdated printout.
What belongs on the invitation before any changes happen?
Keep the initial response instructions simple: a deadline, the response method, and a way to reach the host if plans change. Avoid printing a long change policy on the main card. A website or details message can hold the practical explanation.
The cover features LunaInvites' black-envelope clear acrylic invitation with a gold border. The listed set includes one clear acrylic invitation card and one black envelope. The wood slice, greenery, ribbon spool, pen, and decorative leaves in the styled photograph are props. You can browse the invitation collection while planning a clear response route for your guests.
For this physical invitation order, the digital proof is the design-approval stage. Confirm names, dates, response details, and contact information before approving production. Under the current shipping policy, US shipping is free, with estimated total delivery of approximately 7–8 days after final design proof approval, including 2 days of production. This is an estimate, not a guaranteed arrival date.
Your final check: close the communication loop
Before calling an RSVP change resolved, ask four questions: Is the guest's final answer clear? Does the master record match it? Have the people delivering the event acknowledged the necessary updates? Has the guest received your final confirmation? When all four answers are yes, the change is handled rather than merely recorded.
Sources and store details checked October 15, 2026. Website functions and vendor deadlines can vary; verify your own setup and arrangements.