Google Forms supports "branch to a section based on the answer." It lets you show different follow-up questions to different respondents — useful when "only people who said X should see Y."
The catch: this feature is convenient up to a point and limited fast. This guide covers the mechanics, then makes the practical call: three branching levels is the sign to redesign.
How Google Forms branching actually works
Branching in Google Forms is section-level, not question-level. That distinction matters.
[Section 1] Profile question
↓ if "Individual"
[Section 2A] Individual follow-ups
↓
[Section: end] Submit
[Section 1] Profile question
↓ if "Business"
[Section 2B] Business follow-ups
↓
[Section: end] Submit
In other words, you cannot pinpoint "change just this one next question." You always think in "swap the entire next section."
Only two question types support branching
Section-based branching is available only on:
- Multiple choice (single select)
- Dropdown
Checkboxes (multi-select), short answer, and scale questions cannot drive branching.
"Branch based on which checkboxes the respondent ticked" simply isn't feasible in Google Forms.
Steps to set up section navigation
1. Create sections in advance
Right-side panel → "Add section" (the bottom segmented icon). The trick is to create every destination section before wiring branches.
Section 1: Basic info
Section 2: Individual track
Section 3: Business track
Section 4: Wrap-up
2. Create a multiple-choice question
What type of customer are you?
○ Individual
○ Business
3. On the question, "︙" → "Go to section based on answer"
Toggle on, then pick a destination section per option.
Individual → go to Section 2
Business → go to Section 3
4. Set "After section X" at the end of each section
At the end of Section 2 (Individual), select "Go to Section 4." Skip this and respondents who chose "Individual" will roll into the Business questions next.
5. Test every path in preview
Top-right "eye" icon (preview) → walk through every branch in real time. Skipping testing leads to the classic accident: "I chose Individual but I'm seeing Business questions."
The real topic — common branching traps
Trap 1: Inserting a section later resets branching
Inserting a section into an existing form can reset existing branch settings (especially in the web UI).
Mitigations:
- Lock down the overall structure on paper or in a mind map before wiring branches
- Create all sections first, then drop questions in
- Treat major restructures as a new form rather than an edit
Trap 2: Forgetting "everything else" paths
For multiple-choice options where you don't specify a destination, the default is "continue to next section." With "Individual," "Business," "Other" and a missed destination on "Other," that group lands somewhere unintended.
Mitigation: explicitly set a destination for every option. Never leave "unset."
Trap 3: Required fields breaking the flow
If a required question in a section isn't answered, pressing "Next" throws an error and you can't proceed. It's not a branching bug — it's a required-field bug — but it looks identical to one at first.
Mitigation: when designing, mark branch-driving questions as required and follow-up detail questions as optional.
Trap 4: Trying to force checkbox branching
"Topics of interest (multi-select)" branching is impossible in Google Forms alone. A lot of people get stuck here.
Mitigations:
- Switch to single-select and ask for "most important"
- Drop branching, show all questions, let fields be empty
- Move to a different tool
Trap 5: Past three levels, testing collapses
Type → Individual → Income → $100k+ → Investing experience → Detail questions
A 4–5 level branch produces exponential test paths: 3 levels = 2×2×2 = 8 paths, 4 levels = 16. In reality only 2–3 paths get tested before launch, and the deep branches harbor bugs.
Mitigations:
- Past 3 levels, seriously evaluate moving tools
- Instead of nesting deeper, split into two surveys sent in sequence
- Build an explicit test checklist for every path
Practical thresholds for Google Forms branching
Rule of thumb for what Google Forms handles comfortably:
| Branch depth | Section count | Verdict |
|---|---|---|
| 1 level | ≤4 | Excellent fit |
| 2 levels | ≤8 | Workable |
| 3 levels | ≤15 | Significant test time |
| 4+ levels | 16+ | Switch tools |
Past that, moving to a dedicated survey tool reduces design time + test time + production bugs so much that it's cheaper in total.
Branching patterns other tools support
Things Google Forms structurally can't express:
- Multi-select combinations: "show only if A AND B were selected"
- Numeric range: "show only if value ≥ 30"
- Question-level visibility: toggle individual questions without breaking sections
- History-based branching: "deep-dive only respondents whose last-month NPS was ≤ 5"
- Computed-value branching: "if score sum ≥ 80, show additional questions"
Surveys that need any of these belong in a purpose-built tool.
Branching in Repoan
Repoan supports complex branching without code.
- Question-level visibility — show/hide individual questions without forcing section boundaries
- Checkbox-based branching — conditional logic on multi-select answers
- Numeric range / computed score branching — branch on Likert or NPS scores
- AI-assisted branching design — describe the logic in plain English ("ask details only to people who picked A") and the branching is generated for you
Wrap-up
Google Forms conditional logic in summary:
- Section-level only
- Driven only by multiple choice or dropdown
- Practical up to 3 levels, breaks down at 4+
- Adding sections later tends to corrupt existing branches
If "branching keeps breaking" or "testing takes forever" describes your reality, you've hit the design ceiling. Switching tools often drops design time by an order of magnitude.
Related reading: