Loading tutorials…
Loading tutorials…
Google Forms has only one form of conditional logic: section-based branching. It is workable for simple flows and broken for anything complex. Here is what it can — and cannot — do.
Who this is forOperators with multi-path forms where Q3 should depend on Q2's answer. If your branching needs are simple (3-5 branches, no scoring), Google Forms works. If complex (calculator-based, multi-condition), you need Tally Pro or Typeform.
What you'll need
Step 1
Section-based branching: after a multiple-choice question, you can route to different sections based on the answer. That is it.
Google Forms branching only works with: Multiple Choice or Dropdown questions, and the branch jumps to a different SECTION (not a different question).
You cannot branch within a section. You cannot branch based on short-answer text. You cannot branch on calculated values.
If your form needs more complex logic, this is the ceiling. Either accept it or migrate.
Step 2
Click the "Add section" icon (looks like two horizontal lines). Each section is a page. Branching jumps between sections.
In the right-hand toolbar of the form editor, click the "Add section" icon.
A new section appears below your current questions. Name it (e.g., "For Founders" or "For Marketers").
Drag questions into the right sections. Each section gets its own questions.
Plan ahead: how many branches do you need? Create one section per branch.
Step 3
On the Multiple Choice question, click the 3-dot menu → "Go to section based on answer." Map each answer to its target section.
Open the Multiple Choice or Dropdown question that will trigger branching.
Click the 3-dot menu (bottom-right of the question card).
Select "Go to section based on answer."
Next to each answer option, a dropdown appears. Pick the target section for each answer.
Example: Answer "Founder" → "For Founders" section. Answer "Marketer" → "For Marketers" section.
Step 4
At the bottom of each section, set "After section X" to "Continue to next section," "Go to section [X]," or "Submit form."
Scroll to the bottom of each section. Find "After section X."
Default is "Continue to next section." Change to "Go to section [name]" to skip sections.
Set to "Submit form" if this section is a terminal branch (e.g., disqualified responses).
Critical: every branch path must end somewhere. Audit each section's after-behavior.
Step 5
Open Preview. Submit one response per branch. Verify each path reaches its intended section and final state.
Click the eye icon (Preview). Submit a response choosing each branch answer.
For each branch: verify the right sections appeared, the wrong sections did NOT appear, and the form ended where intended.
A form with 3 branches needs 3 separate test submissions.
Document any broken paths. Fix in the editor.
Common mistakes
Trying to branch on a non-multiple-choice question
What goes wrong: You want to branch based on short-answer or paragraph text. Google Forms cannot do this. You spend 2 hours trying to make it work before realizing.
How to avoid: Branching only works on Multiple Choice and Dropdown. If you need text-based branching, convert the question to multiple choice or migrate to a different tool.
Forgetting to set section-end behavior
What goes wrong: Branches lead users through unintended sections. Form runs longer than expected. Drop-off doubles.
How to avoid: Audit every section's "After section X" setting. Make every path explicit — either "Submit form" or "Go to [specific section]."
Building all branching in one form when sub-forms would work better
What goes wrong: Form has 12 sections, 8 branches, and no one can edit it without breaking something.
How to avoid: For wildly different flows, build separate forms and link to the right one from a router page. Easier to maintain.
Mixing branching with required fields incorrectly
What goes wrong: A required field is in a section that some branches skip. Users on those branches do not see the field, but Google Forms still expects an answer. Submit fails silently.
How to avoid: Mark fields optional if logic may skip them. Validate downstream if needed.
Outgrowing Google Forms and pretending you have not
What goes wrong: You spend 8 hours patching a multi-condition flow that Tally Pro or Typeform would handle natively. Sunk-cost continues to cost you.
How to avoid: If you need calculator-based logic, multi-condition AND/OR, or per-answer scoring, you have outgrown Google Forms. Migrate before adding more patches.
Recap
No. Branching only works on Multiple Choice (single-select) and Dropdown. If your branching depends on a multi-select, convert to single-select or migrate to a different tool.
No native support. Google Forms cannot do score-based branching. For quiz-style branching by score, use Tally Pro's calculator fields or Typeform.
Practical limit is 5-7 branches before maintenance becomes painful. Technical limit is the number of sections (unlimited).
Yes. Set 'After section X' to 'Go to section [earlier name].' Use sparingly — backward jumps confuse users and can create infinite loops if misconfigured.
Rebuild manually — no automated importer. Map your branches first, then rebuild question-by-question in Tally with logic jumps. ~30-60 min per form.
Google Forms
Google Forms is free, fast, and forgiving — which is why most surveys collect garbage data. This walks through the setup path that actually returns reliable answers.
Google Forms
Google Forms Quiz mode handles auto-grading and per-answer feedback, but the defaults are not quiz-friendly. This walks through the setup path that actually returns clean scored results.
Google Forms
Google Forms is free for a reason. This walks through the limitations that block real workflows — payments, branding, complex logic, deliverability — and the workarounds when you cannot migrate yet.
Google Forms
DIY surveys are great — until the data stops driving decisions, or your forms convert at 18%. Here is the honest framework: when the cost of self-managing exceeds the cost of hiring.