Guides

First come first served sign-ups in Google Forms

To run a first come first served sign-up in Google Forms you need four things: a timestamp on every response (Forms gives you that), a cap on each option, the option closing the moment the cap is hit, and a queue for the people who arrive after. Google Forms only provides the first one out of the box. "First come" is the one rule nobody argues with, and it only stays fair if the form enforces it at the moment of submission instead of you sorting it out by email the next morning.

What "first come first served" needs, technically

What Google Forms has natively: "Limit to 1 response", "Collect email addresses" and a manual "Accepting responses" toggle. No per-option limit, no total response cap, no scheduled close. The full list of workarounds is in how to limit responses in Google Forms.

The manual way, and where it breaks

Plenty of people run it by hand. Link the responses to a Sheet, sort by timestamp, and when an option reaches its number, open the editor and delete that option. Latecomers get an apology email with the alternatives.

For a slow sign-up this is fine. A club with 30 members filling 20 seats over a week needs two checks a day, nothing more.

It fails on a busy launch. Picture a studio that releases next month's classes at 9:00 am. Forty people have the link open and hit submit between 9:00 and 9:02. By the time you refresh the Sheet, the 12-seat class has 19 rows. Now you email seven people, each of whom asks "I submitted at 9:00:41, who got in before me?", and you end up pasting timestamps into replies. Two people who submitted in the same second both believe they got the last seat. Neither is wrong. The form never said no to anyone.

The add-on way: two different mechanisms

Trigger-based limiters

Most choice limiter add-ons run on Google Apps Script triggers: Choice Eliminator 3, CAPY, Form Limiter and Form Choice Limiter all work this way. The form accepts the response, Google saves it, then the trigger fires, counts, and removes the option if it is over the limit. The gap between save and removal is where the 9:00 am problem lives. Form Limiter's own reviews report 1 or 2 responses over capacity on busy forms, and the others share the mechanism. Each also needs your account's permission to run when you are not present.

I want to be fair to them. CAPY sits at 4.88 stars with over a million installs, Form Limiter at 4.91 with the same. For a sign-up that fills over days, they do the job. The timing gap only bites when many people submit at once, which is exactly the first come first served case. I tested five of them side by side.

Server-side booking (Form Slots)

Form Slots decides each booking on its own server, one at a time per form, before the seat is counted. Two people submitting in the same second cannot both get the last seat. One is confirmed, the other goes to the waitlist in arrival order. The full option is removed from the live form, usually within a minute. When a seat opens (a deleted response, a raised limit, or the same person changing their answer), the next person in line is confirmed automatically and emailed. The emails come from notifications@mail.formslots.com, never from your account, and only about that person's own booking.

The form keeps its normal link and QR code. Form Slots does not use Apps Script triggers and only touches the form it is installed in. Free is one live form at a time with every feature. Pro is $6 a month or $49 a year for unlimited live forms (pricing). It is new, so there is no install count to point at. The mechanism is the argument.

Setup

  1. Settings, then turn on "Collect email addresses". Without it the caps still work, but there is no waitlist and no emails.
  2. Make the slot question a multiple choice, dropdown or checkbox. Grid questions are not supported.
  3. Add-ons (puzzle icon), Form Slots, Configure slots, pick the question.
  4. Type the capacity next to each option, or use "Set all slots to" when every option has the same number.
  5. Optional: a scheduled open date and time, a total limit for the whole form, and the message people see when it is closed.
  6. Save & activate. The sidebar shows booked, waiting and a FULL badge per option while the sign-up runs.

Question layouts for time slots, shifts and class seats are in the sign-up sheet guide.

Tips for a fair launch

Frequently asked questions

Can Google Forms do first come first served on its own?

Only the timestamp part. It cannot cap an option or close it, so you either police the Sheet by hand or use an add-on.

How do I limit sign-ups per option?

With a choice limiter add-on. In Form Slots you type a capacity next to each option. When the option is full it is removed from the live form, usually within a minute.

What happens when two people submit for the last spot at once?

With trigger-based add-ons both responses can be saved before the check runs. Form Slots decides one booking at a time per form, so one person is confirmed and the other waits in line.

Do latecomers get a spot if someone drops out?

Yes, with email collection on. When you delete a response or raise a limit, the next person in arrival order is confirmed automatically and emailed. Details in the waitlist guide.

Questions people ask

Can Google Forms do first come first served on its own?

Only partly. It records a timestamp on every response, which gives you the order of arrival, but it has no per-option limit and no way to close an option when it is full. You either police it by hand in the Sheet or add an add-on.

How do I limit sign-ups per option in Google Forms?

Install a choice limiter add-on. Form Slots lets you type a capacity next to each option of a multiple-choice, dropdown or checkbox question. When the option is full it is removed from the live form, usually within a minute.

What happens when two people submit for the last spot at the same time?

With trigger-based add-ons both responses can be saved before the check runs, so both get in. Form Slots decides bookings on its own server one at a time per form, so one person is confirmed and the other goes to the waitlist.

Do latecomers get a spot if someone drops out?

With Form Slots and Collect email addresses turned on, latecomers wait in arrival order. When a response is deleted or a limit is raised, the next person in line is confirmed automatically and emailed.

How do I make the launch fair?

Set a scheduled open time so everyone starts together, state the rule in the form description, keep email collection on so the waitlist works, and use the form QR code at the door for in-person sign-ups.