A clear yes or no
Guests confirm whether their invitation group can attend. A decline can notify the organiser without asking the guest to complete irrelevant menu fields.
Wedding RSVPs and menu choices
Wedding replies, ready to use.
A wedding RSVP and menu-choice page lets each invited group confirm attendance and keep every person’s food details in the same private reply.
Guests open a private link in their usual browser, without creating an account or downloading an app. Each invitation can cover the people replying together, including the adult or child menu intended for each person.
The reply flow is working with fictional details in the public demo. Its full live-service rehearsal still has to be completed.
One invitation group
The practical questions stay connected.
A couple should not have to work out which meal belongs to which name after the reply arrives. The form asks for the detail at the point when the guest already has it in front of them.
Every guest named
The reply records each person in the group, rather than leaving a single contact name to stand in for everyone attending.
The right menu
Adult and child choices can be kept separate. Each required course is selected against the guest who will receive it.
Dietary detail beside the choice
Allergies, intolerances and other requirements share one note beside the relevant guest. The couple reviews that wording before the agreed venue handover rather than treating the form as medical screening.
A fictional invitation
Three people, three meal choices, one reply.
An illustrative example, not a customer record. Alex, Morgan and their child Rowan are invited together and confirm that the group will attend.
Alex · adult menu
Alex chooses the vegetable tart and roast chicken. Their choices stay beside Alex’s name.
Morgan · adult menu
Morgan chooses the soup and mushroom main, with a note asking the couple to confirm a dairy-free option with the caterer.
Rowan · child menu
Rowan’s child-menu choice is recorded separately. The couple can review all three people and prepare the agreed venue export.
Actual courses and available dishes come from your approved menu. Dietary notes need a human check with the venue; the form does not confirm that a meal is safe.
From guest to organiser
A reply has somewhere useful to go.
The service is managed around the working product. Lewis prepares the journey with the approved wording and menus, then rehearses it before any live invitation is shared.
- The couple approves the setup
Invitation groups, guest wording, courses and available dishes are checked before the reply links are sent.
- The guest completes one private flow
They answer for the people on their invitation, then review the names, meals and dietary notes before submitting.
- The answer and confirmation stay linked
The product saves the reply with its confirmation record so an email issue does not require the guest to enter everything again.
- The couple prepares the venue handover
Attendance, table assignment, course choices and dietary notes can be combined in the agreed CSV export when the plan is ready.
Private by design
Guest details are there to run the wedding.
Wedding replies can include information that needs care. The public marketing pages cannot access wedding records, and the guest route only opens with its private invitation code.
No guest marketing list
Guest information is used to provide the booked wedding service. It is not sold or used to market Yours, Dearest to the guest.
Read the working privacy noticeA defined close
The wedding receives a deletion schedule. The current working default is 90 days after the event, with an agreed export first where that is part of the scope.
Questions worth answering
Wedding RSVP and menu questions, answered.
The reply is designed to give the couple usable information without asking guests to install anything or separate meals from names.
What does the wedding RSVP page collect?
It collects attendance, each guest’s full name, the relevant adult or child menu choice and dietary notes in one private reply record.
Do guests need an app or an account?
No. Guests open their private invitation link in an ordinary browser and reply for the people included in that invitation group.
Can adult and child menus be handled separately?
Yes. The approved menu shown for each guest can reflect whether that person needs the adult or child choices, and the selection stays attached to their name.
What happens to the replies after the wedding?
The couple receives the agreed exports, and the operating plan then places guest records into a 90-day deletion schedule after the wedding. Guest information is not used as a marketing list.
Planning a 2027 wedding?
Start with the wedding you are actually planning.
Share the date, venue and the parts of the guest journey that are becoming awkward. Lewis will reply personally and confirm whether a founding setup is a sensible fit.
Check your wedding dateFounding cohort limited to three 2027 weddings. £395 including personal setup and one remote rehearsal.