Why Google Sheets Dropdowns Won’t Allow Multiple Selections on Mobile

A laptop test is not enough to establish that a team sheet will work on phones. As checked on October 28, 2026, Google documents that mobile users cannot select multiple dropdown options, even with multiple selections enabled. Rebuilding a working desktop dropdown will not remove that restriction.

The useful next step is to identify the edit a teammate needs to make. Updating assignments throughout a shift calls for a different arrangement from submitting a request once. The examples below are suggested layouts, not reports of a live deployment or device test.

A working list is not a working multi-select control

One Android user described exactly this problem: they created a sheet on a laptop, enabled multiple choices, and could use it there, but could not make the same selection on mobile. When the list opens normally, it is reasonable to assume there must be another gesture to select the second item.

List editing also differs between the apps. Android supports creating and changing lists through More → Data validation. Google's iPhone and iPad instructions say to create and edit lists on a computer, then select an option on the device. Having a menu for changing the list does not establish support for choosing several entries.

As a temporary arrangement, a desktop colleague can make the multi-item edits. Send that person the complete requested selection. Recording just one item on the phone and expecting someone to infer the rest creates an ambiguous record: it looks like a genuine one-item request. If that relay becomes part of every shift, changing the input layout is likely more useful than continuing to forward corrections.

Check the desktop setup before changing the layout

If multiple selections fail on a computer too, open the affected cell's Data validation rule. Under Advanced options, set the display style to Chip, then enable Allow multiple selections and remove leading or trailing spaces from the options. These are the conditions in Google's desktop instructions. The invalid-data warning setting controls acceptance of unlisted values; it is not a switch for mobile multi-select.

Use a spare test cell to select two distinct entries, then remove only one. Leave the cell and return to it to check the remaining choice. If the first few rows work but later rows do not, inspect the rules on both a working and a failing cell. Include the next row where someone will enter a new task, rather than checking only records that already exist.

A successful desktop check gives you a useful starting point for redesign: the original choices are known, and you can compare them with the replacement layout. It does not prove that every colleague can perform the same edit on their device. Decide which edits must happen away from a computer before rebuilding the entire sheet.

Use separate checkboxes for a shared record

Suppose each row represents a staff member and the choices are Training, Photography, and Operations. Someone may handle two of those duties and later drop one. Three checkbox columns let the person change each assignment independently. This is a proposed layout for a short, stable list of duties:

On a computer, select the new input cells and choose Insert → Checkbox. Start in new columns beside the old selection so you can compare entries before removing anything. Google also supports custom checked and unchecked values and using checkboxes with functions and filters. Custom values are optional; they are not necessary to establish the input workflow.

iPhone and iPad users can check and uncheck boxes created on a computer. On Android, boxes can also be added by selecting cells and choosing More → Data validation → Checkbox, according to the Android instructions. Preparing the columns centrally keeps teammates focused on editing their own entries.

The confirmation column solves a separate operational problem. Three unchecked boxes could mean “I am taking none of these duties” or “I have not filled this in yet.” If assignments depend on that distinction, collect confirmation separately. Otherwise, the coordinator may chase a person who has already answered or overlook someone who has not.

This layout becomes unwieldy when the list grows to dozens of choices. It creates more horizontal scrolling and another column whenever a duty is added. One assignment per row is another possible design: record the person and a single duty, then add a second row for a second duty. That avoids a very wide sheet, but reports must distinguish assignment counts from people counts.

A current status such as “In progress” or “Complete” usually represents one state. Keeping that field single-select avoids contradictory entries. Reserve checkbox columns for duties or options that can actually coexist.

Collect new requests through a form

A request for equipment or availability is a different job. Each person can submit a set of answers without finding a row in a shared grid. The coordinator then reviews the collected requests. This suits a new submission that needs to be captured as a whole, rather than a record teammates revise repeatedly during the day.

Open Google Forms and choose Blank form, as described in Google's setup instructions. For an equipment request, a practical example would ask for the person's name, the relevant event, and the equipment needed. Choose Checkboxes from the question-type menu beside the equipment question's title. In Forms, Dropdown allows one choice; Checkboxes allows several, as described in the question-type reference.

From the form's Responses area, use More → Select destination for responses to choose a new or existing spreadsheet. This connection stores responses. It does not search an existing project table for a matching person and replace that person's equipment cell. Treat the responses as submitted requests unless you separately design how they become assignments.

That distinction matters when choosing the tool. For equipment loans that a coordinator approves, a list of incoming requests is useful. For a staff member changing duties several times a day, repeated submissions can leave the coordinator deciding which request is current. In that situation, editing the existing checkbox row is a more direct approach.

A correction does not always require a new submission. The owner can turn on Settings → Responses → Allow response editing, letting respondents return through their individual edit links to change the equipment requested. That link opens a particular submitted response; it does not locate and update a matching person's assignment in a separate working table. If requests may change after approval, explain how to keep the edit link and notify the coordinator of a correction. The coordinator can then compare the revised request with the equipment already approved.

Before distribution, publish the form, set who may respond, and copy the responder link, following Google's publishing instructions. If you enable Limit to 1 response, respondents must sign in to a Google Account. Check that requirement against the intended audience, particularly if external people need to submit without signing in.

Try one clearly marked sample request using the respondent's intended device and account. Select two equipment items, submit, and compare the form response with the linked sheet. This checks what the coordinator actually receives. Make sure whoever handles requests knows the sample is not a real booking and how it will be removed from the working queue.

Move existing entries and test the handoff

Keep the old multi-select column for comparison while transferring values. Start with examples containing one choice, several choices, and no choice. An entry for Training and Photography should become exactly those two checked boxes. Moving only the first item or checking every box changes the meaning of the record.

Do not silently convert an unanswered row into a confirmed “none.” If the original sheet does not say whether a blank was intentional, flag it for confirmation. Migration is a poor time to guess what someone meant. The new confirmation field can prevent the same ambiguity in future entries.

Then ask a teammate to open the new checkbox layout on their own phone. Check two boxes in their row, uncheck one, and reopen the sheet to verify that the remaining choice is intact. Repeat on another test row. If they cannot edit any input cell, the owner should check their Editor access and the people allowed to edit protected ranges. That is a different failure from being unable to choose a second dropdown item.

Check downstream reports as well. A checkbox can change correctly while a summary still reads the old dropdown column. Identify which columns each working report should now use, and change a sample record to see whether the reported assignment follows it. An input redesign is unfinished if the person allocating work still sees the old values.

Finally, make the handoff specific. Tell teammates which row to edit, which boxes to check, and how to remove a duty. For a form, provide the responder link and explain how to request a change after submission. These instructions complete the workflow that a mobile multi-select dropdown cannot currently provide.