Google Forms with Choice Eliminator: Setup, Limits and a Better Alternative

You open 20 seats for a Saturday workshop, share a Google Form, and go to lunch. By the time you are back, 27 people have "booked" a seat, three of them in a session that was already full, and your inbox is filling up with apologies you now have to write. The form did exactly what it was built to do: collect answers. It was never built to count them.

That gap is why "choice eliminator" is one of the most searched Google Forms add-ons. This guide shows how to add one in two minutes, where add-ons start to fail once real volume arrives, and how to build a Google Forms alternative with a built-in choice eliminator in Clappia that also handles quantities, approvals and offline teams.

Does Google Forms have a choice eliminator?

No. Google Forms has no native choice eliminator. Options in multiple choice, dropdown and checkbox questions stay visible and selectable for every respondent, no matter how many times they have already been picked. The only built-in limit is closing the whole form or limiting each Google account to one response, which does nothing for per-option capacity.

To remove an option once it is full, you need a third-party add-on from the Google Workspace Marketplace, such as "Choice Eliminator" or "Form Choice Limiter". These add-ons watch new responses and edit your form's options after each submission.

How to add Choice Eliminator to Google Forms

You can set this up directly from your form editor in under two minutes:

1. Open your form in Google Forms and make sure the question you want to limit is a multiple choice, dropdown or checkbox question.
2. Click the three vertical dots in the top-right corner and select Get add-ons.
3. Search for "Choice Eliminator" or "Form Choice Limiter", click Install and grant the permissions it requests.
4. Open the add-on from the puzzle piece icon at the top of the form and click Configure.
5. Select the question and set a limit for each option, for example 1 for an appointment slot or 25 for a workshop session. Choose whether full options are hidden or shown as unavailable.
6. Submit a test response from a separate account and confirm the option count drops before you share the form.

For a class sign-up sheet or a small team lunch order, this is often all you need.

Why Choice Eliminator add-ons fail for high-volume forms

Add-ons work by running a Google Apps Script after each submission. The script reads the responses, counts each option, and rewrites the question. That design creates predictable limits:

• A delay between submit and update. The add-on runs on an installable form-submit trigger, so the option is only removed a few seconds after the response lands. Two people who open the form at the same moment both see the last seat, and both can submit.
• Script quotas. Apps Script has daily quotas on trigger runtime and executions. A busy registration day can hit them, and when a trigger fails silently, your options stop disappearing.
• Binary availability only. An option is either open or gone. You cannot sell 3 of 10 T-shirts in one response and show 7 left to the next person.
• Add-on overload. Confirmation emails, PDFs and approvals each need another add-on, and stacked add-ons editing the same form are a common source of conflicts.
• No relational data. Google Forms cannot look up a previous submission or a stock list to change what the current respondent sees without custom scripting.
• No offline filling. Google Forms needs a live connection, which rules it out for field teams booking or issuing items on site.

Practitioner tip: when a sign-up has real consequences (paid seats, clinic slots, limited stock), stop thinking of it as a form and start thinking of it as a small database. The question is not "which option was clicked?" but "how many are left right now?". Tools that store the count in a table and check it at submit time are the ones that stop double bookings.

How to build a choice eliminator in Clappia

Clappia is a no-code app platform, so every form is backed by its own database and can read from other apps. Instead of a script that edits the form after the fact, you keep a master list of options with their remaining capacity and check it at the moment of submission. You can even create a Clappia app from your existing Google Form and then add the logic below.

Pull live options from a master app

Create a small master app, for example "Sessions" or "Stock", with a record per option and a Seats left or Remaining number. In the booking form, the Get Data from Other App block shows those records as a searchable dropdown and pulls the remaining count into the form. A status filter lets you show only records marked "Open", so full options drop out of the list.

Block the submission when an option is full

Add a Validation block with an Error level and a formula such as @seats_left < 1 or @remaining < @quantity. When the condition is true, the user sees a red message like "This session is full" and the form cannot be submitted. Unlike an add-on, the check happens before the response is accepted, not seconds after.

Deduct capacity automatically with workflows

On submit, an Edit Submission workflow node finds the matching master record and sets its count with a formula like {seats_left} - 1 or {remaining} - {quantity}. Add an IF (condition) node that checks whether the new count is 0 and, on that path, sets the record's status to "Full". This is the same pattern teams use for stock tracking apps.

Confirm, approve and report

An Email node sends the booking confirmation, an approval workflow can hold high-value requests for a manager, and every booking lands in one table with dashboards. If you already schedule events in Google, you can also link form bookings to Google Calendar.

Use Case 1: Workshop slot booking that never double-books

Scenario: A training team runs 6 workshop sessions a week with 20 seats each. With a Google Form and an add-on, popular sessions regularly ended with 21 or 22 confirmed attendees because several people submitted within the same few seconds.

How Clappia solves it: the team builds a "Sessions" master app with Date, Time, Trainer, Capacity, Seats left and Status. The booking form uses a Get Data from Other App block filtered to Status = Open, so attendees only see sessions with seats. The pulled Seats left field feeds a Validation block set to Error, so a session that fills up while someone is still typing blocks their submit with a clear message instead of creating an extra booking. On submit, the workflow runs node by node:

1. Edit Submission reduces Seats left by 1 on the chosen session.
2. IF node checks whether Seats left is now 0; if so, a second Edit Submission sets Status to Full.
3. Email node sends the attendee a confirmation with the session details.

Trainers open the app on their phones to see the live roster, and the operations lead tracks fill rates on a dashboard instead of a spreadsheet.

Use Case 2: Limited-stock orders with quantity deduction

Scenario: A company sells branded merchandise to employees: 10 medium T-shirts, 8 large, 20 caps. A choice eliminator can only hide "Large" when it is gone. It cannot stop someone ordering 5 when 2 are left.

How Clappia solves it: a "Merchandise Stock" app holds Item, Size, Opening stock and Remaining. The order form pulls the item, shows Remaining, and asks for a Quantity. A Validation block with @remaining < @quantity blocks any order larger than the stock left. When an order is submitted, an Edit Submission node subtracts the quantity, so the next person who opens the form sees 7 T-shirts, not 10. Orders above a set value can route to an approval step, and a payment field can collect money in the same form. For a fuller setup with reorder alerts, see how to build a smart inventory system with auto-alerts.

Store staff can also record issues from a shop floor with weak signal, since Clappia apps work offline and sync submissions when the device reconnects. For first-come bookings where every second matters, keep the booking step online so the count is always current.

Google Forms Choice Eliminator vs Clappia: full comparison

Here is how a Google Form with a choice-limiting add-on compares with a Clappia app on the features that decide whether a limited sign-up works.

Which option is right for your form?

A choice eliminator add-on is not wrong, it is just built for small, low-stakes lists. Use this quick guide to decide.

If you are moving an existing process over, you can import your old Google Form responses into the new app so your history stays in one place, and add auto-calculations for totals and fees.

Key takeaways

• Google Forms has no native choice eliminator; per-option limits need a Workspace Marketplace add-on.
• Add-ons update options a few seconds after each submission, so simultaneous responses can still double-book.
• Add-ons only hide or show an option; they cannot deduct quantities like 3 of 10 items.
• Clappia checks remaining capacity at submit time with a Validation block and updates it with an Edit Submission workflow.
• Clappia adds approvals, confirmations, dashboards and offline data capture in the same app, with unlimited apps on its free plan.

Final thoughts

For a quick classroom sign-up, a free Choice Eliminator add-on does the job. Once a booking has money, capacity or stock behind it, you need a form that counts before it accepts, and that is where a database-backed app wins. In Clappia you can build the master list, the booking form and the workflow in an afternoon, without code, and test it with your team before rolling it out. Start building for free and turn your next limited sign-up into an app that cannot overbook.

Frequently asked questions

Does Google Forms have a built-in choice eliminator?

No. Google Forms keeps every option selectable no matter how many times it has been chosen. You need a third-party add-on such as Choice Eliminator or Form Choice Limiter, or a platform like Clappia that checks remaining capacity natively.

How do I remove an option in Google Forms once it is selected?

Install a choice-limiting add-on from the Google Workspace Marketplace, open it from the puzzle piece icon, choose the question, and set the limit for each option to 1. The add-on removes the option after it receives that many responses.

Why is my Choice Eliminator not working?

Common causes are a trigger that stopped after an error or quota limit, the question text being edited after setup, two add-ons editing the same question, or respondents submitting at the same time before the update ran. Reconfiguring the add-on usually resets the trigger.

Can Google Forms limit responses by quantity?

Not natively. Add-ons can limit how many times an option is chosen, but not subtract a quantity such as 3 out of 10 items. Clappia can, by pulling the remaining stock into the form, validating the requested quantity and deducting it with a workflow.

What is the best free alternative to Google Forms Choice Eliminator?

Clappia is a strong free option for high-volume or high-stakes bookings. Its free plan includes unlimited apps, and it combines live option lookups, submission-blocking validations, automatic capacity updates, approvals and offline mobile apps without add-ons.