Using Google Forms for event registration and where it starts to break down

A Google form will run event registration for free, and for a single session with a fixed room and one organiser it does the job well. The setup takes about fifteen minutes: a handful of questions, email collection switched on, a response limit set to the number of seats, and receipts sent to every registrant. Where it starts to break down is not the form itself. It is the seat count under a rush of sign ups, the confirmation email, cancellations and waitlists, and the list that ends up at the door. This guide covers the setup first, using the setting names as they appear in Google Forms, then each of those four break points, with the limits Google documents as of October 8, 2026.

Setting up a registration form, step by step

The menus below follow the current Google Forms layout and the Google Docs Editors Help pages.

1. Create the form and decide the questions. Keep it to what the organiser will actually use: full name, email, which session if there is more than one, how many people the registration covers, and anything that affects catering or access. Every extra required question costs completions on a phone.
2. Collect email addresses. Open Settings at the top of the form, expand Responses, and under Collect email addresses choose either Verified or Responder input. Verified records the address of the Google account the person is signed in with. Responder input lets anyone type an address, which suits a public event where many registrants will not want to sign in.
3. Turn on receipts. In the same Responses section, set Send responders a copy of their response to Always. This option only appears once email collection is on.
4. Cap the registrations. Under Accepting responses, choose Set close date or response limit. Pick After a number of responses and enter the seat count, or On a date to close registration at a deadline. Edit the closed message so late arrivals see something useful, such as where to join a waitlist.
5. Validate the fields that cause trouble later. Response validation on a short answer question can enforce an email format, a number range or a pattern. A party size question limited to 1 through 4 prevents a registration for forty.
6. Link a spreadsheet. On the Responses tab, link the form to Google Sheets. This sheet becomes the working list for everything after the form closes.
7. Turn on owner notifications. On the Responses tab, open More and choose Get email notifications for new responses, so the organiser sees sign ups arrive.

That is a complete, working registration system for a small event. Several of the ranking guides stop here, and for an internal session with thirty seats they are right to.

The settings that matter, and the catch in each

Each of the settings above has a documented limit that only shows up under event conditions.

None of these are faults. They are what a general form tool is designed to do. The rest of this guide is about what happens when an event needs more than that.

Where the seat count goes wrong

The response limit is the setting most organisers rely on, and Google's own help page carries the exception in plain words: if multiple people respond at the exact same time, the form accepts responses regardless of the response limit.

For a survey, this barely matters. For registration it is the normal case. Sign ups do not trickle in evenly. They arrive in a burst in the first minutes after an announcement goes out to a mailing list or a social post, which is precisely when simultaneous submissions happen. A form set to close at 60 can finish at 63, and the three extra registrants already have a receipt that looks like a confirmation.

There are two quieter versions of the same problem.

The limit counts submissions, not people. If the form asks how many people a registration covers, the limit still counts each submission as one. Sixty submissions with an average party of 1.5 is ninety people in a sixty seat room. Google Forms has no setting for a response that consumes more than one seat, so a group event needs the running total kept in the sheet, usually with a sum on the party size column.

The count does not give seats back. A cancelled registration is still a submission. A form that closed at 60 stays closed after five people drop out. Reopening means raising the limit by hand, watching the count, and closing it again.

The practical fix inside Google Forms is to set the limit a few below capacity, keep a total in the linked sheet, and check the final count against the room before sending anything that says a place is confirmed.

What registrants actually receive

When Send responders a copy of their response is set to Always, each registrant gets an email containing their own answers. That is a receipt. It tells them the form received something. It does not tell them where to go, what time doors open, how to join online, or whether their place is confirmed or provisional, because none of that is in their answers.

Google's help page points to the gap itself. For more notification options and customised follow up emails, it recommends the Form notifications add-on. The same page adds a caution that matters for events: in certain circumstances, responders may not receive expected response receipts due to spam filters or other counter-abuse measures.

So the email that registrants treat as their confirmation comes from somewhere else. In practice that is one of three routes:

• A mail merge from the linked sheet. Reliable, but someone has to run it every time a batch of sign ups arrives, and remember which rows have already been sent.
• An add-on or automation tool wired to the form or sheet. Runs on its own, at the cost of another setup, another permission grant and often another subscription.
• Manual emails. Workable for twenty people. At a hundred, someone is skipped or emailed twice.

Whichever route is chosen, write the confirmation so it answers the four questions registrants actually have: is the place confirmed, when and where, what to bring or how to join, and who to contact if plans change. A registrant who knows those four things does not email to ask.

Cancellations, waitlists and the list at the door

Three jobs sit between the form closing and the event starting, and Google Forms is not involved in any of them.

Cancellations. They do not come through the form. They come back as replies to whichever address sent the confirmation, worded however the person likes. Someone has to read the message, find the right row in the sheet and mark it. Until that happens, the seat is held by someone who is not coming, and the reminder will still go to them.

Waitlists. There is no waitlist setting. Once the form closes, later visitors see the closed message. A common workaround is a second form linked from that message. Promoting someone means emailing them, adding them to the main sheet, and making sure the reminder and the door list both pick them up. Each of those is a separate manual step.

The door list. This is where the earlier gaps become visible. If producing the list means exporting the sheet, filtering out cancellations, adding promoted waitlist names and printing, it gets done the night before. Every change after that point is missing at the entrance.

A simple status column in the linked sheet, with values such as registered, confirmed, waitlisted, cancelled and attended, removes much of this pain. Filter on it for reminders and for the door list. The weakness is that the column is only as current as the last person who remembered to update it, and the sheet does not record who changed a status or when.

Volume limits, updated for September 2026

Volume is rarely the reason to leave Google Forms for events, but the limits changed recently and are worth knowing. According to the Google Docs Editors Help page checked on October 8, 2026, Forms introduced new data and response limits starting in September 2026:

To keep accepting responses past the 500,000 cap, the owner downloads and deletes existing responses. Google recommends closing the form before doing so.

The practical reading for organisers: a single event will almost never get near these numbers. The figure that does matter is reuse. A team that runs a monthly session from one form, collecting every registration since the first event, will hit the 10,000 response point sooner than expected, and the individual view disappears exactly when it is needed to look up one person. Making a fresh copy of the form for each event avoids this and keeps each event's list separate.

When to keep the form and when to move the second half

The deciding question is not about the form. It is about everything that happens after a registration arrives. Looking back at the last event answers it quickly.

One of these is easy to live with. Three or more means the spreadsheet has become the coordination system, and a spreadsheet has no memory of who changed what or who replied to whom.

At that point the form editor is not what needs replacing. The questions, the link and the response limit can all stay as they are. What changes is the place a registration lands. A form tool with response management gives each registration a status such as confirmed, waitlisted or cancelled, an owner, and a reply sent from the same screen and kept on the record. Reminders and the door list are then built by filtering on status rather than by rebuilding a sheet. The features page lists what that covers, and use cases walks through event registration and RSVP, including reminders and recording who actually came. Existing Google Forms responses can be exported as CSV and imported, so registrations already taken are not lost.

Cost tends to be the next question. One tool of this kind prices only by the number of people working the registrations, with unlimited forms and unlimited responses on every plan: free for one person, $39 a month for up to three, and $99 a month for up to ten, before tax, as listed on its pricing page on October 8, 2026. A one person event desk can therefore run its whole second half without paying anything.

What to change first

Keep the Google form for the next event and leave its questions alone. Change where registrations go after they are submitted, so each one carries a status, an owner and its reply history. A walkthrough of that screen, with no account needed, is in the Halict demo.

Q1. Can a Google form close automatically when the event is full?

Yes. In Settings, under Accepting responses, Set close date or response limit can close the form after a set number of responses. Google states that simultaneous submissions can be accepted beyond the limit, so set the cap slightly under capacity and check the final count before confirming places.

Q2. Can Google Forms send registrants a confirmation email with event details?

Not natively. Setting Send responders a copy of their response to Always sends registrants their own answers, which works as a receipt. Venue, time and joining details need a mail merge, the Form notifications add-on, or another tool. Google also notes that spam filters can stop some receipts arriving.

Q3. Do people need a Google account to register through a Google form?

Not for a basic form using Responder input for the email address. Sign in becomes necessary when the form uses verified email collection or the Limit to 1 response setting, and also for file upload questions. For a public event, avoiding sign in usually means more completed registrations.

Q4. How many registrations can one Google form hold?

Since September 2026, Google lists a limit of 500,000 responses and 1 GB of storage per form. Some views degrade much earlier: individual response view can become unavailable above 10,000 responses. Using a fresh copy of the form for each event avoids hitting those thresholds.

Q5. What is the simplest way to run a waitlist with Google Forms?

Edit the closed message to link to a second form for the waitlist. When a place frees up, email the next person, add them to the main sheet and update a status column. Filtering that column for reminders and the door list keeps promoted registrants from being missed.