Event Registration Form with Google Forms (Template + Tips)

Updated July 2026 · 7 min read

You don't need a ticketing platform to register people for a meetup, fundraiser, workshop or company offsite. Google Forms is free, everyone can open it, and every registration lands in a spreadsheet you can sort at the door. What it won't do is take payments or cap attendance automatically — so the trick is a well-built question set and a couple of settings that do the heavy lifting. Here's the full template.

Step 1: Create the form and front-load the details

Start a blank form at forms.google.com (or in FormMaker on your phone). Title it with the actual event name — "Riverside 5K Volunteer Appreciation Dinner" — and use the description for everything a registrant needs before committing:

• Date and time, including doors-open time
• Venue name and full address
• Cost, if any, and how to pay ("$15 at the door, cash or Venmo")
• Registration deadline
• A contact for questions

Half the "quick question" emails you'd otherwise get are answered right here.

Step 2: The question template

Copy this set and trim what you don't need — every question you cut raises your completion rate, especially on phones.

1. Full name — Short answer, required.
2. Email address — turn on Collect email addresses in Settings instead of asking; it's typo-proof and one less field.
3. Phone number — Short answer, optional. Only ask if you'd genuinely text people about day-of changes.
4. Ticket type — Multiple choice, required:
   • General admission — $20
   • Student / senior — $12
   • Member — free
   • Table of 8 — $140 (I'll list guest names below)
5. Which sessions will you attend? — Checkboxes (skip for single-track events):
   • 9:30 AM — Keynote
   • 11:00 AM — Workshop A: Grant writing basics
   • 11:00 AM — Workshop B: Volunteer recruiting
   • 1:00 PM — Roundtable lunch
6. Dietary needs — Checkboxes: None / Vegetarian / Vegan / Gluten-free / Nut allergy / Other (with an "Other" text field). Only ask if food is served — an unused dietary question signals a copied template.
7. Guest names — Paragraph, optional, for group tickets.
8. Consent — Checkboxes, required: "I agree to the event photo policy and code of conduct (link in the description)." A required checkbox is the cleanest consent pattern Forms offers.
9. Anything else we should know? — Paragraph, optional (accessibility requests live here).

If you take payment, say exactly how in the ticket-type options or confirmation message — Forms itself can't process cards, so pair it with a payment link or collect at the door.

Step 3: Settings that make it a registration form

• Collect email addresses (Settings → Responses) — you get a verified address with zero typing.
• Limit to 1 response — prevents duplicate registrations; requires respondents to sign in to Google. If your audience includes people without Google accounts, leave it off and dedupe in the Sheet instead.
• Allow response editing — lets attendees fix their own session picks instead of emailing you.
• Confirmation message — this is your ticket stub. Replace the default with: "You're registered for the Appreciation Dinner — Sat, Nov 14, 6:30 PM, Riverside Community Hall, 400 Elm St. Doors at 6. Parking behind the building. Questions: [email protected]." People screenshot this; make it worth screenshotting.
• Response receipts — turn on "Send responders a copy of their response" so they get the confirmation by email too.

One honest caveat: Google Forms cannot cap total registrations automatically. Watch the count in the Responses tab and toggle Accepting responses off at capacity — our guide on closing a form and limiting responses covers every option.

Step 4: Share it — and put a QR code at the door

Click Send, grab the shortened forms.gle link, and distribute it everywhere your audience already is: the newsletter, the community Facebook group, the Slack channel, the church bulletin.

Then make a QR code — see our QR guide — and use it twice:

• Before the event on posters and flyers.
• At the door for walk-ups. A "Not registered? Scan here" sign turns walk-ins into rows in your spreadsheet within seconds, so your attendee list stays complete without a clipboard.

FormMaker generates the share link and QR code for any of your forms directly from your phone, which is handy when you're already at the venue taping up signs.

Step 5: Export the attendee list to Google Sheets

In the Responses tab, click the green Sheets icon to create a linked spreadsheet. Each registration is a timestamped row. Before event day:

• Sort by last name (add a helper column with =INDEX(SPLIT(B2," "),1,COLUMNS(SPLIT(B2," "))) or just sort the name column) so door check-in is fast.
• Count dietary needs with =COUNTIF() to give the caterer real numbers.
• Tally sessions so you know which room needs more chairs.
• Share view-only with co-organizers; share edit access only with whoever runs the door.
• Need a file for a badge printer? File → Download → CSV.

Step 6: Check-in from your phone

No scanners needed. The night before, add a "Checked in" column to the Sheet. At the door:

1. Open the linked Sheet in the Google Sheets app on your phone (or a tablet at the welcome table).
2. As each guest arrives, use search (the magnifier icon) to find their name and type an x in the Checked in column.
3. Walk-ups scan the QR code, register, and appear at the bottom of the Sheet — mark them checked in on the spot.
4. Afterward, =COUNTA() on the check-in column gives your true attendance versus registrations — the no-show rate that makes next year's planning smarter.

If you built and manage the form in FormMaker, you can also watch responses arrive in the app while a co-organizer runs the Sheet.

FAQ

Related guides

• Sign-up sheet with Google Forms
• Google Forms RSVP template
• How to close a Google Form and limit responses