Creating Radio Button Questions
Creating Radio Button Questions in Google Forms
To get a single-choice (radio button) question in Google Forms:
- Open the form at forms.google.com
- Click Add question
- Open the question-type dropdown → select Multiple choice
- Write the question text and add each answer option
- Toggle Required if an answer must be given
- Preview: selecting a second option should clear the first — this confirms it's radio-button behavior, not checkboxes
Progress:
- Step 1: Determine answer cardinality (exactly one vs. several allowed)
- Step 2: Pick the correct question type
- Step 3: Add question text and options
- Step 4: Configure optional settings (Other, Required, branching, shuffle, answer key)
- Step 5: Preview and verify radio behavior
- Step 6: Review wording and option order before publishing
Step 1 — Determine answer cardinality. Ask: can the respondent realistically pick more than one answer? If no, use single-choice. If yes, it's a checkbox question, not multiple choice.
Step 2 — Pick the correct type using this decision table:
| Google Forms type | Answers allowed | Best use |
|---|---|---|
| Multiple choice | One | Short list where every option should stay visible |
| Checkboxes | Several | "Select all that apply" questions |
| Dropdown | One | Longer list that should take less vertical space |
Step 3 — Add question text and options. Add an "Other" option only when a genuine write-in answer is plausible — don't add it by default.
Step 4 — Configure optional settings:
- Required: prevents submission without an answer
- Go to section based on answer: use for branching logic when different answers should route to different sections
- Shuffle option order: use for neutral surveys/quizzes to reduce order bias; leave off when options have a natural sequence (e.g., time slots, scale values)
- Answer key (quiz mode): mark the correct option and assign points
- Images: can attach to the question or to individual answer options
Step 5 — Preview and verify. Selecting a second option must clear the first selection. If both stay selected, the wrong type was chosen.
Step 6 — Review before publishing. Check wording, option order, and the Required toggle — especially important when questions were AI-generated or exported from a draft tool.
Example 1: Input: Need a question for "Which session will you attend?" with 3 fixed session names. Output: Multiple choice question type, 3 options listed in session order (not shuffled, since time order matters), Required turned on, no "Other" option (sessions are fixed).
Example 2: Input: Need a question for "Which snacks would you like at the event?" with multiple options allowed. Output: Use Checkboxes, not Multiple choice — several answers are valid, so radio buttons would be the wrong control.
Example 3: Input: A 15-option list of countries for "Which country are you dialing from?" Output: Use Dropdown instead of Multiple choice — one answer only, but the long list should collapse to save vertical space.
- Match the control to the real constraint: one answer → Multiple choice or Dropdown; several answers → Checkboxes.
- Use Dropdown instead of Multiple choice once the option list gets long (roughly 7+ items) to keep the form scannable.
- Leave Shuffle off whenever options have an inherent order (times, dates, scale points, ranked lists).
- Add "Other" sparingly — only when a write-in response adds real value, not as a default safety net.
- If generating questions with AI (e.g., FormGPT), always review wording, option order, and the Required setting before publishing — don't trust the draft blindly.
- Using Checkboxes and asking people to "choose only one" in the text. The control still permits multiple selections regardless of instructions — respondents get the wrong visual cue and may ignore the text. Use Multiple choice instead.
- Confusing Multiple choice (one answer) with "multiple choice" in the colloquial quiz sense (which often implies several options, not several answers). In Google Forms, "Multiple choice" always means single-select radio buttons.
- Forgetting to toggle Required on questions that must be answered before submission.
- Adding "Other" to every question by default, cluttering the form with write-in fields that aren't needed.