How to Add Branching Logic to Google Forms on iPhone (2026)

Does Google Forms Have Conditional Logic?

Yes — Google Forms has one form of conditional logic, called “Go to section based on answer,” and it routes respondents to different sections based on how they answer a multiple-choice or dropdown question. It’s free, it’s native, it’s available on every Google account, and it’s documented in Google’s own Show questions based on answers help page.

What it is not is a rules engine. There’s no way to show or hide an individual question, no “if answer contains” conditions, no logic that reads two answers together, and no visual builder that draws your flow. Google Forms branches pages, not questions. Once that model clicks, the feature is straightforward to build and easy to reason about — and the rest of this guide is mostly about the places where the model bites.

How Branching Works — Sections + One Question

Branching in Google Forms is two ingredients: sections act as pages, and one single-answer question decides which page comes next. Everything you build is a combination of those two things, so it helps to hold the model in your head before you start tapping.

Think of it as a flow with two separate decisions. First, the routing question — a multiple choice or dropdown — sends each respondent into one branch based on their answer. Second, and independently, each section decides where it goes when it ends: continue to whatever section follows, jump to a specific section, or submit the form. The first decision is the one everybody sets up. The second is the one everybody forgets, and it’s why branched forms misbehave.

A practical consequence of the page model: if you want a question to appear only for certain people, that question needs a section of its own. There’s no inline reveal. One conditional follow-up question means one extra section, which is fine for two or three of them and unwieldy for twenty.

It’s also worth knowing what the model does not remember. Branching reads the answer to the question the rule is attached to, and nothing else — it can’t look back at what someone chose two sections ago, can’t combine “answered A here and B there,” and can’t feed an earlier answer into later question text. Each branch point is an isolated decision. In practice that means the routing question has to be the one that actually determines the path, asked at the moment the path splits, rather than something you hope to act on later in the form.

Set Up Branching on iPhone (Step-by-Step)

Building a branching form on an iPhone follows the same order every time: create the sections first, then attach the routing rule to the question, then fix up how each section ends. Doing it in that order avoids the frustration of trying to point a rule at a section that doesn’t exist yet.

The iPhone-specific advice is simple: sketch the paths before you build them. On a laptop you can scroll a long branched form and see its shape; on a 6-inch screen you’re working through a keyhole, and it’s easy to lose track of which section you’re editing. Two minutes with a pen — question → branch A → shared closing section, branch B → submit — saves ten minutes of scrolling. Name sections after their path rather than “Section 3,” because the destination dropdown shows those names and generic ones make routing errors nearly invisible. If you’re building the form itself from scratch first, our how to create a Google Form on iPhone guide covers that groundwork.

The Limits You’ll Hit

Google Forms’ branching is deliberately minimal, and knowing its four hard limits up front tells you whether it fits your form or whether you’re about to fight it. Most frustration with the feature comes from expecting a rules engine and finding a page router.

The checkbox restriction is the one people argue with, and it’s structural rather than arbitrary: a respondent can tick three boxes at once, and three boxes pointing at three sections gives the form no single destination to choose. The section-level restriction is the one that costs the most work, because every conditional question needs its own section. And the absence of score-based branching surprises teachers most often — Forms can grade a quiz, but it can’t route on the result. Independent guides covering the same ground, such as Formswrite’s 2026 write-up on Google Forms conditional logic, land on the same list.

If you need genuine question-level conditions, a visual rules editor, or logic that reads several answers at once, that’s a different class of tool — Jotform, Typeform, and Cognito Forms all do it. Worth saying plainly even though it points away from Google Forms: if your flow needs that, no amount of section juggling will get you there comfortably.

The Mistake That Sends Everyone Down the Wrong Path

The single most common branching bug isn’t in the routing question at all — it’s a section whose ending was left on “Continue to next section.” That’s the default for every section, and it means a branch, once finished, flows into whatever section happens to come next in the form rather than to where you intended.

Picture the classic setup: Section 1 asks “New or returning customer?” and routes to Section 2 (New) or Section 3 (Returning). Someone answers “New,” works through Section 2, reaches the end — and because Section 2 still says continue to next section, they slide straight into Section 3, the returning-customer branch, and answer questions written for somebody else. The routing rule was correct; the exit was never set.

The fix is mechanical: go through every section, bottom to top, and set its ending on purpose — jump to a shared closing section (“Thanks, one last question…”), or submit the form. Then preview each path end to end, one branch at a time. Two more things worth knowing while you’re in there: keep one routing question per section, because when a section contains several, only the last one’s rule actually applies; and remember that respondents can go back and change an answer, which reroutes them and can leave answers in sections they no longer pass through.

When to Use Branching (and When to Skip It)

Branching earns its keep when different people genuinely need different questions — and adds pure overhead when they don’t. The useful cases share a shape: one early question splits your audience into groups whose remaining questions barely overlap.

• Registration triage — new versus returning attendees, or ticket types with different follow-up questions.
• Skipping irrelevant questions — “Did you use the service?” routing non-users past ten questions they can’t answer.
• Quiz or feedback paths — sending people to a different explanation section depending on which answer they chose.
• Screening forms — an early disqualifying answer routes straight to Submit form instead of wasting someone’s time.

Skip it when the form is short, when the “conditional” question is harmless for everyone to see, or when a single well-worded optional question would do the job. Branching multiplies what you have to test: three paths mean three previews after every edit, and on a phone that’s real time. Teachers in particular tend to reach for branching before they need it — our Google Forms for teachers on iPad and iPhone guide covers the classroom patterns that are worth the sections, and for grading flows the grade a Google Forms quiz on iPad and iPhone guide explains why score-based routing has to happen after the fact rather than inside the form.

Managing Branched Forms on iPhone

Branching is a native Google Forms feature, available free on any account — no app adds it, and ours is no exception. What a good iOS editor changes is how painful it is to manage a branched form on a small screen, where the real difficulty lives.

Forms for Google Drive (by Pipiform) is a native iOS app for building and editing Google Forms on iPhone and iPad, and its value here is structural clarity: moving between sections, keeping track of which questions sit in which section, and editing a multi-path form without the constant scroll-and-hunt of the mobile web editor. To be exact about the boundary — the app surfaces Google’s section-level branching; it does not add question-level conditional logic or a visual rules editor, because Google Forms itself has neither.

If you’re doing heavier restructuring — reordering questions, splitting an existing long form into sections after the fact — a bigger screen still helps, and our editing Google Forms on iPad guide covers that workflow, Split View and all.

Summary

Google Forms gives you one conditional logic tool — “Go to section based on answer” — and it routes at the section level from multiple-choice and dropdown questions only. Checkboxes can’t branch (multiple answers, no single destination), single questions can’t be shown or hidden without giving them their own section, answers don’t carry forward, and quiz scores can’t drive routing. You can build all of it from an iPhone in Safari; the trick is to create and name your sections first, attach the rule second, and then set every section’s ending on purpose — that default “Continue to next section” is what quietly merges branches and sends people down paths meant for someone else. Sketch the flow before you build, preview each branch once, and Google’s minimal logic will carry a surprising amount of weight. When you need real rules instead of pages, that’s the moment to look at a different tool.