RSVP Form with Google Forms: Template + Step-by-Step

Updated July 2026 · 7 min read

Google Forms is free, works on every device your guests own, and puts all the replies in one place — which makes it a genuinely good RSVP tool for weddings, birthdays, team dinners, and community events. This guide gives you the exact question set to copy, the two settings that matter, and how to get the form in front of guests and track who's coming.

The RSVP template: 5 questions to add

Start a blank form at forms.google.com (or in FormMaker if you're on your phone), title it with the event name and date — e.g. "Sara & Tom's Wedding — RSVP by May 1" — and add these questions:

1. Full name

• Type: Short answer
• Required: Yes

Ask for the full name even if you're collecting emails — you'll be matching this list against invitations, not email addresses.

2. Will you attend?

• Type: Multiple choice
• Options: "Joyfully accept" / "Regretfully decline" (or a plain Yes / No)
• Required: Yes

Keep it to two options. A "Maybe" option feels polite but leaves you with a guest count you can't plan around.

3. Number of guests (including you)

• Type: Dropdown
• Options: 1, 2, 3, 4 — only as high as your invitations actually allow

A dropdown with a capped list quietly enforces your plus-one policy; a short-answer number field invites "5, if that's okay?"

4. Dietary restrictions

• Type: Checkboxes
• Options: None, Vegetarian, Vegan, Gluten-free, Nut allergy, Other (with a text field)

Checkboxes let a guest pick more than one — vegetarian and gluten-free is common. Add the built-in "Other" option to catch anything you didn't list.

5. Message for the host (optional)

• Type: Paragraph
• Required: No

Guests use this for song requests, arrival times, and well-wishes. Leave it optional so nobody stalls on the last question.

Two settings that make it work

Open the form's Settings and turn on:

1. Limit to 1 response. Stops double submissions when a guest can't remember whether they already replied. Note: this requires respondents to sign in to a Google account.
2. Collect email addresses. Ties every response to an email, so you can follow up with guests individually — directions, schedule changes, "you never told us your entrée."

If some guests may not have Google accounts, weigh the trade-off: requiring sign-in enables the one-response limit, but skipping it makes the form frictionless for everyone. For most events, keeping the name question required and skipping the sign-in requirement is a reasonable fallback.

Share it: link or QR code

• Link. Tap Send, choose the link icon, and check Shorten URL. Paste it into your invitation email, group chat, or event page.
• QR code. For printed invitations or posters, generate a QR code that opens the form when scanned. Guests point their camera at it and land straight on the RSVP. See our full guide: how to make a QR code for a Google Form.

FormMaker can share the form link or a QR code directly from your phone's share sheet right after you create the form.

Track who has responded

• Responses tab. The Summary view gives you an instant headcount — the pie chart on the attending question is your yes/no split, and the guest-count answers let you total attendees.
• Linked Google Sheet. In the Responses tab, tap the Sheets icon to create a linked spreadsheet. Each RSVP becomes a row with a timestamp, which makes it easy to sort by name, filter to "yes" replies, and check names off against your invitation list.
• Email notifications. In the Responses tab menu, enable Get email notifications for new responses if you want a ping when each reply arrives.
• Chasing stragglers. Because Google Forms only records people who responded, keep your master invite list in the linked sheet (add a column beside the responses) and compare as the deadline approaches.

When your RSVP deadline passes, close the form so late replies don't sneak into your final count — here's how to close a Google Form.

FAQ

Related guides

• How to make a QR code for a Google Form
• Google Forms on mobile: the complete guide
• Google Forms logic: skip questions & branching explained