Google Forms Logic: Skip Questions & Branching Explained

Updated July 2026 · 7 min read

"If they answer no, skip the next five questions." Every survey builder eventually needs this, and Google Forms can do it — just not the way dedicated survey tools do. Instead of rules attached to individual questions, Google Forms routes people between sections based on their answer to a multiple choice or dropdown question. Once you internalize that one idea, the rest is mechanical. Here's how it works, the patterns that cover most real forms, and where the system runs out of road.

The building block: sections

A section is a page of your form. Respondents see one section at a time and tap Next to continue. To create one, click the Add section icon (two stacked rectangles) in the editor's floating toolbar.

By default, sections run in order: 1 → 2 → 3 → Submit. Branching changes that default in two places:

• On a question: "Go to section based on answer" routes each option to a different section.
• After a section: the dropdown at the bottom of every section ("After section 2, continue to…") sets where respondents go when they finish that page.

You need both. The question-level rule splits paths; the after-section rule makes paths rejoin or end. Forgetting the second one is the most common branching bug — respondents finish their branch and fall straight into the other branch's questions.

How to set up "Go to section based on answer"

1. Create your sections first. Sketch the paths, then add a section per path. Example: Section 1 (routing question), Section 2 (path A), Section 3 (path B), Section 4 (shared final questions).
2. Add the routing question in the section where paths split. It must be multiple choice or dropdown — no other type offers branching.
3. Open the question's three-dot menu (bottom-right of the question card) and select Go to section based on answer.
4. Pick a destination for each option. A dropdown appears beside every answer: choose a section, or Submit form to end immediately.
5. Set the after-section destinations. At the bottom of each branch section, point it to the section where paths rejoin (or to Submit).
6. Test every path. Use the preview (eye icon) and walk through each answer combination before sharing.

Common patterns

The screener

Qualify respondents up front and end the form early for everyone else.

• Section 1: "Have you used our product in the last 30 days?" — Yes → Section 2 (the real survey), No → a short "thanks anyway" section or straight to Submit form.

Different paths per audience

One form serves several groups, each with its own questions.

• Section 1: "Which best describes you?" — Student → Section 2, Parent → Section 3, Teacher → Section 4. Each branch section's after-section rule points to Section 5, the shared closing questions.

The follow-up detail

Ask for detail only when it's relevant — the closest Google Forms gets to skipping a single question.

• Section 1: "Did anything go wrong with your order?" — Yes → Section 2 ("Tell us what happened", paragraph question), No → Section 3. Section 2's after-section rule also points to Section 3.

This pattern also powers event forms nicely — for example, only asking meal questions of guests who said yes in an RSVP form.

The limitations (know them before you build)

• Only multiple choice and dropdown can branch. Checkboxes can't — Google can't route someone who picked three boxes to three sections at once. Short answer, paragraph, linear scale, and grids can't branch either.
• No true conditional logic. You can't show or hide an individual question in place, combine conditions ("if A and B"), or branch on what someone typed. Logic is one question → one section jump.
• Section-level granularity. Skipping "just one question" means giving that question its own section, which adds a page break respondents will see.
• Shuffled options and branching don't mix well. If you shuffle option order on a routing question, double-check destinations — the mapping follows the option, but reviewing it is harder.
• Complexity grows fast. Past three or four branches, the section list becomes hard to reason about. Name sections descriptively ("Path B — Teachers") and test every route.

If your form genuinely needs multi-condition logic or answer piping, that's beyond Google Forms — but for screeners, audience paths, and optional follow-ups, sections cover it.

Setting up branching on your phone

Google doesn't make an official Google Forms mobile app, so on a phone you have two options:

• Mobile browser with desktop mode. Open forms.google.com, request the desktop site (Safari: the aA menu; Chrome: Desktop site), and use the editor as described above. The three-dot question menu and section dropdowns work, but they're small targets on a touchscreen.
• FormMaker. The app connects to your Google account and builds real Google Forms with a native, touch-first editor — so structuring a form on your phone doesn't require pinch-zooming a desktop page. When you're done, share the link or QR code straight from the app.

Either way, preview the form on your phone before sharing — most respondents will fill it out there. More mobile specifics in our complete mobile guide.

FAQ

Related guides

• RSVP form with Google Forms: template + step-by-step
• Google Forms on mobile: the complete guide
• How to create a Google Form on Android