Google Forms RSVP: fine for answers, not guest lists
A form is a genuinely good way to collect answers, and it costs nothing. The trouble is that a wedding RSVP is not really a form problem - it is a guest list problem, and the form is only the last step of it.
This page is about the work you end up doing around the form, and what changes when the invitation, the list and the reply are one thing.
What a form does well
We are not going to pretend otherwise, because plenty of couples get all the way to the wedding this way.
It is free, and it is now
You can have a working RSVP form in ten minutes without paying anyone or learning anything new.
It collects clean answers
Ask the questions you want, get them back in a tidy column each. As a data-collection tool it is genuinely good.
Everyone can open it
No app, no account, works on any phone. That part is exactly right, and it is the part we copied.
It is the right tool for a small list
Twenty people and one event? Send the form. Honestly. The rest of this page is about what happens at a hundred and fifty guests across three events.
The workflow you end up assembling
- Build the formQuestions for attendance, guest count, meal choice, and which of your events they are coming to.
- Keep a list somewhere elseThe form does not know who you invited, so the guest list lives in a separate sheet you maintain by hand.
- Send the link by handOne link, sent to everyone. So you paste it into messages one at a time, or into a group chat and hope.
- Match the replies backResponses arrive as rows typed by guests. You match 'Amara' to 'Amara & Nuwan Perera' on your list, and chase the fourteen people you cannot account for.
The DIY stack against one invitation
Same wedding, same guests, same questions. The difference is how many places the answer has to travel through before it is a number you can give the caterer.
| Form plus spreadsheet plus chat | Link Invitation | |
|---|---|---|
| The invitation itself | A form. You send the design separately, as an image or a printed card | The invitation and the reply are the same page |
| Who you invited | A spreadsheet you maintain by hand, separate from the responses | One guest list, with the replies on the guests' own rows |
| The link guests get | One link, the same for everybody | A personal link per guest, addressed to them |
| Who has seen it | Unknown. A message delivered is not an invitation opened | Opened or not opened, per guest and per event |
| Several events | A question in the form, then filtering the sheet to count each one | Guests assigned per event, counted per event |
| Matching replies to people | By hand, from whatever the guest typed into the name box | Already matched - the link identifies the guest |
| Duplicate or joke entries | Anyone with the link can submit, repeatedly | Public sign-ups arrive pending until you approve them |
| Cost | Free, plus your evenings | One payment, unlimited guests |
This compares the do-it-yourself workflow couples describe, not a feature audit of any Google product. If you think we have described it unfairly, tell us and we will correct it.
If your list is short, your wedding is one event, and you already have the invitation handled - use the form. It is free and it works.
See what replies look like when they arrive attached to a guest on the live RSVP dashboard, or read the rest of the honest comparisons.
Keep the answers. Lose the spreadsheet.
One invitation, one guest list, one place the replies land. Build it free and see it before you pay.
Start your invitationFree to build and preview. Unlimited guests on both plans.