Google Forms supports section-based branching: if a respondent selects answer X, they skip to section Y. This works at the section level only - there is no question-level display logic. For complex surveys with multiple nested branches, Google Forms has real limitations. Pirai AI converts document-based branching logic to the closest Google Forms equivalent automatically.
How Branching Logic Works in Google Forms
Google Forms branching routes respondents to different sections based on their answer to a specific question. The branch trigger must be a Multiple Choice or Dropdown question. Linear Scale, Grid, and Short Answer questions cannot trigger branching. The routing is set at the question level - one question routes to one of several sections depending on which option the respondent selects.
The key constraint is that branching operates at the section level, not the question level. You cannot show or hide individual questions within a section based on earlier answers. To create conditional question paths, you must put each conditional question in its own section or group questions that share the same display condition into the same section.
Setting Up Branching Logic Step by Step
Structure your survey into sections
Plan your branching paths before building. Each unique path needs its own section. For a survey that routes pet owners to different questions than non-owners, you need at least three sections: shared intro, pet owner questions, non-owner questions, and shared closing. Add sections using the "Add section" button (the horizontal line icon in the right toolbar).
Add a Multiple Choice routing question
Place your routing question at the point where the paths diverge. This must be a Multiple Choice or Dropdown question. The answer options will each route to a different section. Name your routing question clearly so you can identify it when setting up the routing logic.
Set the routing for each answer
Click the three-dot menu on the routing question. Select Go to section based on answer. A dropdown appears next to each answer option. Set each one to the section respondents should see if they select that answer. Set "After section [X]" routing to Go to next section, Submit form, or a specific section as needed.
Set section-end routing
At the bottom of each section, click the section name to expand settings. Set what happens when the respondent reaches the end of the section: continue to next section, go to a specific section, or submit the form. This controls how paths converge back to shared questions after diverging.
Test every path
Click the eye icon (Preview) to open the form as a respondent. Test each possible answer to the routing question and confirm the correct sections appear. Do not publish until every branch path has been tested end-to-end.
Real Limitations of Google Forms Branching
Section-level only, not question-level. The most significant limitation is that you cannot show or hide individual questions based on earlier answers. Every question in a section appears to every respondent who reaches that section. This forces complex surveys into large numbers of short single-question sections, which becomes unmanageable for surveys with more than 3-4 branch points.
Only Multiple Choice and Dropdown can trigger branching. If your routing question is a text entry, Linear Scale, or Grid question, it cannot trigger branching. You cannot branch on a numeric threshold ("if age is under 18, go to section B") - only on specific selected options.
No nested conditions. Google Forms does not support "if X AND Y, then show Z." Each routing question routes based on a single answer selection. Multi-condition display logic (common in Qualtrics) has no equivalent.
No embedded data or profile-based routing. Google Forms cannot route respondents based on information passed via URL parameters or from a respondent database. Every routing decision must come from an in-form question.
Workarounds for Complex Logic
For surveys requiring more than 3-4 branch paths, the most practical workarounds are: splitting the survey into multiple separate Google Forms with a link in the thank-you message directing respondents to the appropriate follow-up form; using Google Forms' section structure to approximate question-level display logic by isolating each conditional question into its own section; or migrating the survey to a platform with true display logic such as Qualtrics, REDCap, or SurveyMonkey.
Converting Branching Logic from Survey Documents
If your survey document contains skip logic or display logic annotations (e.g. "IF Q5=Yes, SKIP TO Q12" or "SHOW Q8 IF Q3=2 OR 3"), Pirai AI converts the branching structure to Google Forms section routing in the Apps Script output. Simple single-condition branches are converted automatically. Complex nested or multi-condition logic is flagged in the script with comments indicating what needs to be manually configured in the Form editor after the script runs.
For surveys where the branching logic is too complex for Google Forms to handle well, Pirai AI can convert the same document to Qualtrics or REDCap instead, where full display and skip logic is supported natively. Select a different target platform in the same session without re-uploading.
Frequently Asked Questions
Add sections for each branch path. Place a Multiple Choice or Dropdown question where the paths diverge. Click the three-dot menu on the question and select 'Go to section based on answer.' Map each answer option to the section respondents should see if they select it. Set section-end routing to control where each path goes after completing a branch.
No. Google Forms branching operates at the section level only. You cannot show or hide individual questions within a section. To show a question conditionally, it must be in its own section that is only shown when a specific answer is selected in a routing question.
Only Multiple Choice and Dropdown questions can trigger section branching. Linear Scale, Short Answer, Paragraph, Grid, Date, and Time questions cannot trigger branching. If your routing question is a text entry or rating scale, you will need to add a separate Multiple Choice routing question.
Pirai AI reads the skip logic annotations in your survey document (e.g. 'IF Q3=Yes, SKIP TO Q8') and converts them to Google Forms section routing in the Apps Script output. Simple one-condition branches are converted automatically. Multi-condition or nested logic is flagged for manual configuration. For surveys with complex logic, converting to Qualtrics or REDCap via Pirai AI may be more appropriate than Google Forms.
Convert Your Survey to Google Forms in Minutes
Upload a Word, PDF, or Excel document. Pirai AI preserves matrix questions, Likert scales, and branching logic. No Drive access required.
Start Converting Free