Microsoft Forms' branching is a level more flexible than Google Forms'. It works per question, so you don't have to swap entire sections.
That said, even with flexible mechanics, the editor has a "you can't see the whole tree" weakness. Complex branching becomes unmanageable fast. This guide covers the basics, the comparison with Google Forms, and the signs it's time to move on.
Microsoft Forms branching basics
Vs. Google Forms
| Dimension | Microsoft Forms | Google Forms |
|---|---|---|
| Granularity | Per question | Per section |
| Supported question types | Choice, rating, yes/no, etc. | Multiple choice / dropdown only |
| Overall view | List form | Section list |
| Adding later | Relatively safe | Tends to reset |
Microsoft Forms is more flexible in branching, which also makes it easier to build complex structures that are harder to manage.
Steps
1. Create the source question
Multiple choice, rating, yes/no — selection-style questions drive branching.
2. "︙" → "Add branching"
From the question's bottom-right menu, click "Add branching." You switch into the branching editor.
3. Pick a destination for each option
What type of customer are you?
○ Individual → jump to Q3
○ Business → jump to Q5
○ Other → end of form
For each option, choose "Next," "Jump to specific question," or "End of form."
4. Test in preview
The "Preview" button shows actual behavior. Walk every branch before publishing.
Mid-level — what separates pros
Branching from rating/scale questions
NPS and Likert scales can drive branches:
How likely are you to recommend us? (0–10)
- 0–6 (Detractors) → dissatisfaction deep-dive
- 7–8 (Passives) → improvement suggestions
- 9–10 (Promoters) → referral intent question
Combined with NPS auto-categorization, score-segment deep-dives fit into a single form.
Jump to "End of form"
To exit early based on an answer ("Thanks — this survey isn't for you"), branch a specific option to "End of form." Useful for screening questions.
Coordinating multiple questions
Q1 = "Contract: Yes" → show Q2, Q3 → Q5
Q1 = "Contract: No" → show Q4 → Q5
Per-question control gives you logic flexibility beyond Google Forms.
The real topic — Microsoft Forms' branching limits
Limit 1: No visible overall tree
The branching editor shows "destination per question" as a list. There's no flowchart-style global view.
5–10 simple branches are fine. Past 15 questions or 3 levels, it gets hard to hold the whole structure in your head:
- "If I picked Individual at Q3, where do I land?" — you trace it mentally
- Detecting accidental loops by eye is hard
- Handing the design off to someone else is extremely hard
Limit 2: No branching from checkboxes
Microsoft Forms cannot branch from a multi-select either.
Requirements like "if respondent picked both A and B, show additional questions" aren't expressible.
Mitigations:
- Switch to single-select ("most important")
- Drop branching and show all questions
- Move to a different tool
Limit 3: No compound conditions (AND/OR)
"Q1 = A AND Q3 ≥ 5" — compound conditions aren't supported. Microsoft Forms branching is locked to "one path per option per single question."
Limit 4: No computed-score branching
"If summed score across multiple questions ≥ 80, show additional questions" — not possible in Microsoft Forms alone.
Limit 5: Test effort grows exponentially
Three levels with three options each = 27 paths. Manual testing of every path takes tens of minutes and bugs slip through.
Mitigations:
- Design to stay within two levels
- Build an exhaustive test-path checklist
- Past 3 levels, evaluate a different tool
Fit assessment — when Microsoft Forms branching works
| Design complexity | Microsoft Forms fit |
|---|---|
| 1 level / 3–5 paths | Excellent fit |
| 2 levels / 10 paths | Workable |
| 3 levels / 20 paths | Test time and handoff become issues |
| 4+ levels / complex | Switch tools |
| Score-based branching | Not native |
| Multi-select branching | Not supported |
Branching feature comparison — Microsoft Forms vs. Google Forms
| Dimension | Microsoft Forms | Google Forms |
|---|---|---|
| Per-question branching | Yes | No |
| Per-section branching | Yes | Yes |
| Visual overview | Weak | Weak |
| Branch from rating | Yes | No |
| Edit-after-launch safety | Decent | Fragile |
| Multi-select branching | No | No |
| Computed-score branching | No | No |
"Microsoft Forms is more flexible on simple branching; both hit ceilings at complexity" — that's the summary.
Field-tested practices for branching design
Practice 1: Sketch the tree before entering it into the tool
Draw the flowchart on paper, FigJam, or Miro before typing it into the editor. Design mistakes drop dramatically.
Practice 2: Separate "shared" and "branched" question blocks
Common (all): Q1–Q3
↓
Branch → Q4 onward is conditional
↓
Common (all): final Q (free text, attribute confirmation)
This isolates the conditional logic to a central block that's easier to manage.
Practice 3: Keep branch destinations to three or fewer
More than three branches means "this should be multiple surveys." Don't cram everything into one form — splitting by goal often improves response rate too.
Practice 4: Test every path
Before publishing:
- Walk every combination of branching options
- Check the "doesn't match anything" fallback
- Check early-exit paths
A test-path table with checkboxes prevents production bugs.
Branching in Repoan
Repoan aims for "Microsoft Forms' flexibility + complex-branch handling."
- Per-question branching — granular visibility control
- Multi-select-based branching — "if A AND B were selected"
- Numeric range / score-computed branching — branch on Likert totals or NPS scores
- AI-assisted branching design — describe the logic in plain English ("only ask details to people who picked A") and the branching is generated
- Flowchart view — visualize the entire structure
Wrap-up
Microsoft Forms branching:
- Per-question and flexible (a level above Google Forms)
- Can branch from rating questions (NPS-friendly)
- No global view; hard to manage past 3 levels
- Multi-select and computed-score branching aren't native
If "this is getting complicated," "testing takes too long," or "handing this off would be brutal" describes your reality, the design has hit a limit. Moving to a purpose-built tool is worth evaluating.
Related reading: