Wedding RSVP Form Template
A wedding RSVP with the courtesy of good stationery — acceptance in invitation language, entrée selection, a song request, and a graceful path for regrets.
Together with our families, we would be honored to have your reply. It takes a moment — and it helps us plan a day worthy of the people we love.
The mail-back RSVP card is a lovely tradition with a terrible completion rate. Cards get lost in drawers, stamps never get bought, and six weeks out the couple is texting a third of the guest list one by one — the least romantic task in wedding planning. A digital wedding RSVP keeps the register of good stationery while fixing the logistics: replies arrive instantly, counts tally themselves, and nobody's grandmother has to find a mailbox.
Why these fields. The invitation-name field leads, and its phrasing — exactly as it appears on your invitation — is doing quiet guest-list enforcement: named invitations are how couples control plus-ones, and this field keeps replies matched to the list you actually invited. The acceptance question speaks stationery ("joyfully accepts / regretfully declines") because tone is content at a wedding; a form that sounds like a survey cheapens the invitation it follows. Acceptance reveals three questions through logic: the entrée selection your caterer bills by, an allergy field scoped to the whole party, and a dance-floor song request — equal parts reception playlist and a signal that the couple reads every reply. Decliners are routed past all of it to an ending written with genuine warmth, because a decline handled gracefully is remembered as kindly as an acceptance. The message field stays open to both paths; some of the best wedding-card lines arrive from people who cannot come.
What we left out. Registry links — they live on the wedding website, not inside a reply. Mailing addresses, which the wedding guest address collection template gathers months earlier, before invitations print. And plus-one negotiation fields: the named-invitation frame answers that question before it gets asked.
Who uses this. Couples running RSVPs from their wedding website or a QR code on the invitation insert, wedding planners managing several client weddings from one account, and small venues that offer RSVP handling as part of their package.
Make it yours. Swap the entrées for your actual menu and rename the options in the editor. Turn on password protection in Settings and print the password on the invitation so the reply page stays invitee-only. Set the close date to your RSVP deadline — the form enforces it so you do not have to — and match the theme to your stationery with a serif font and your wedding colors. When the caterer calls, the Summary view already has entrée counts, and the CSV export is your seating-chart starting sheet.
Grace for the no. Half of wedding RSVP design is the decline path, and most forms treat it as an afterthought. Here it is two questions, one heartfelt ending, and an open message box — short enough to be painless, warm enough that the friendship is intact when the photos go out.
Frequently asked questions
Can we still include paper RSVP cards?
Many couples run both — print this link (or its QR code) on the invitation insert and let guests choose. Digital replies land instantly; paper ones you type in from the card.
How do we keep the form to invited guests only?
Turn on password protection in Settings and print the password on the invitation. Only guests holding the invite can open the RSVP page.
How does the caterer get the entrée counts?
The Summary view tallies each entrée automatically as replies arrive, and the CSV export includes a column per question — send the caterer either.
What happens after our RSVP deadline passes?
Set the close date in Settings and the form closes itself with a message you write — for example, a note to text the couple directly for late changes.