Choice eliminator for Google Forms: the five add-ons compared
A choice eliminator is an add-on that gives each answer in a Google Form a capacity and removes the answer from the live form once that capacity is reached. It turns a plain multiple-choice question into a sign-up sheet with slots. Five add-ons dominate the search results for this, and they look alike on the surface. I installed each of them in July 2026, read their consent screens and their reviews, and the differences are in three places: how a booking is decided, what the add-on can access, and what happens to the person who arrives when a slot is full.
I make one of the five (Form Slots), so take the ranking with that in mind. The facts below are checkable on each listing.
The five, at a glance
| Add-on | Installs and rating (July 2026) | How a booking is decided | Waitlist | What it asks to access | Free tier |
|---|---|---|---|---|---|
| CAPY: Choice Eliminator, Form Limiter, AI (AddonForge) | 1M+, 4.88 | Trigger after submit | No | All your Google Sheets (edit and delete), forms it is installed in, run while you are away | Yes |
| Form Limiter (Skyfield) | 1M+, 4.91 | Trigger after submit | No | Files it creates, forms it is installed in, send email as you | Yes |
| Form Choice Limiter (Everest Web Deals) | 1M+, 4.86 | Trigger after submit | No | All forms in your Drive, send email as you | Yes |
| Choice Eliminator 3 (2HAC Studio; also 4 and 5) | ~4.6 | Trigger after submit | No | All your Google Sheets (edit and delete), all forms in your Drive | Yes |
| Form Slots | New, no public count yet | Server-side, one decision at a time per form, before confirming | Yes, automatic promotion and emails | Only the form it is installed in; creates a Sheet only on reset | Yes, one live form with every feature |
Not in the table: Choice Eliminator Lite, the add-on with the biggest install count (2.89M+). It could not be installed when I tested it and sits around 3 stars, so I would not start there today. If you are looking for the Choice Eliminator 2 you used years ago, this page explains what replaced it.
How a booking is decided, and why it matters
Four of the five work the same way under the hood. Google Forms saves the response, then fires an "on form submit" trigger, then the add-on counts and, if an option is full, edits the form to hide it. The gap between "saved" and "hidden" is a few seconds on a good day. For a parent-teacher slot sheet that fills over a week, nobody notices. For a workshop with twelve seats that 40 people open at 9:00, the gap is where the overbooking happens: the last seat gets taken by two or three people who all saw it available. Reviews across these add-ons mention "a few over the limit", and the Lite developer describes the tool as meant for light use.
Form Slots moves the decision to its own server. Each response is checked against the remaining capacity in a transaction, one at a time per form, and only then confirmed. Two submissions in the same second cannot both get seat twelve; the second one is waitlisted. The form, link and QR code stay the ones Google gave you, which is also what separates it from hosted-copy tools that move respondents to a different URL.
What each add-on asks to access
This is the part most people click through without reading. The consent screens I saw:
- CAPY and the Choice Eliminator 3 family ask to see, edit, create and delete all your Google Sheets. CE3 also asks for all forms in your Drive.
- Everest asks for all forms in your Drive and to send email as you.
- Skyfield is the cleanest of the trigger-based group: only files it creates, only forms it is installed in, plus send email as you.
- All four ask to run while you are not present, because the trigger needs your account to execute.
- Form Slots asks only for the form it is installed in (read questions and responses, update options, open and close it). It creates one Google Sheet when you reset a round, and never sends email as you; booking emails come from its own address.
In a school or an organization with an admin who reviews add-ons, this list decides whether you get to use the tool at all.
The person who arrives when a slot is full
None of the trigger-based four has a waitlist. The option is gone, the person picks something else or leaves, and if someone cancels later you handle it by hand. Everest and Skyfield can email you about events (Everest on every click of a closed option, which its users complain about), but nothing goes to the respondent.
Form Slots queues extra sign-ups in arrival order. When a seat opens, because a response was deleted, the limit was raised, or a person changed their answer, the first in line is confirmed automatically and gets an email. Confirmed people get a confirmation too. This needs the form's "Collect email addresses" setting on. Without it, limits still work and there is simply no queue. There is a full walkthrough in how to add a waitlist to Google Forms.
Smaller things that bite in practice
- Section routing. If the limited question uses "Go to section based on answer", removing an option can break the routing. Skyfield pauses elimination on such questions and Everest's FAQ warns about it. Form Slots rewrites the options while preserving the routing, so hidden options do not break the flow.
- Editing option text. On Everest, changing an option's wording resets its count, and two options with identical text can overbook. Keep option texts unique on any tool.
- Trigger limits. Apps Script allows 20 triggers per account. With a limit and a schedule on each form, that is about ten forms before a trigger-based add-on stops working. There is no such ceiling on a server-side tool.
- Copied forms. Duplicating a form does not copy its triggers, so a copied form silently has no limit until you re-enable the add-on. Form Slots recreates its watch when you connect the copy.
- Reset. Everest's and Skyfield's reset clear responses. Form Slots backs every response up to a new Google Sheet first, then clears.
Which one I would pick
For a slow form with a handful of slots and an admin who already approved CAPY or Skyfield, keep what you have; both are mature and well rated, and Skyfield's permissions are reasonable. For anything competitive, where the first minutes decide who gets in, use a tool that decides before confirming, and use the waitlist so the people you turn away still get a chance. That is the case Form Slots was built for. The free plan covers one live form with every feature, so the cost of trying it on your next sign-up is zero.
If you already have a choice eliminator and it is letting extra people through, the troubleshooting guide lists the five usual causes. For the full picture of total caps and close dates, see how to limit responses in Google Forms.
Questions people ask
What is a choice eliminator for Google Forms?
An add-on that gives each answer of a multiple-choice, dropdown or checkbox question a limit and removes the answer from the live form when the limit is reached. It is how people turn a Google Form into a sign-up sheet with capped slots.
Is there a free choice eliminator?
Yes. CAPY, Skyfield Form Limiter, Everest Form Choice Limiter and the Choice Eliminator 3/4/5 family all have free tiers, with limits on forms or features. Form Slots is free for one live form at a time with every feature included.
What happened to Choice Eliminator 2?
The original add-on is no longer the one most people land on. Choice Eliminator Lite could not be installed when I tested it in July 2026 and is rated around 3 stars, and several lookalikes (Choice Eliminator 3, 4 and 5) now carry the name.
Why do choice eliminators sometimes overbook?
They run on a Google Forms trigger that fires after a response is stored. If several people submit the same option within a few seconds, all of them get through before the option is removed. Only a server-side check before confirmation avoids it.
Does a choice eliminator work with Go to section based on answer?
Not always. Removing an option can break section routing, and both Skyfield and Everest say so in their documentation. Form Slots keeps the routing intact while an option is hidden.