How to add conditional logic to Google Forms

Last updated September 2026 · ~8 minute read

Short answer: Google Forms calls it branching, and it only works on two question types. Google's help page is explicit: “‘Go to section based on answer’ is only available for Multiple choice and Dropdown question types.” Split the form with Add section, then on a Multiple choice or Dropdown question click More → Go to section based on answer and give each option its own destination. A form can hold up to 75 sections.

Almost everyone who gets stuck here is stuck on the same thing: they built the routing question as a checkbox or a short answer, and the menu item they were told to look for is not there. It is not hidden, greyed out or behind a paid tier — Google never offers it for those types. So start with the restriction, not the click-path.

Why you can't branch on this question type

Google states the rule as a tip on its Show questions based on answers page, and it is the whole explanation for the most common complaint about Forms logic:

“Go to section based on answer” is only available for Multiple choice and Dropdown question types.

That is the entire supported set. Everything else — checkboxes, short answer, paragraph, linear scale, multiple-choice grid, checkbox grid, date, time, file upload — has no branching option in its More menu. Nothing appears and then refuses to work; the menu item is simply absent, which is why so many people assume their form is broken.

The reasoning is easy to see once you look at what branching has to decide. It needs one destination per submission:

• Checkboxes let someone tick three boxes at once. Three answers, three destinations, no way to pick between them.
• Short answer and paragraph have no fixed list of answers, so there is nothing to hang a destination on.
• Grids and scales produce one answer per row or a number, not a choice from a list the editor can enumerate.

The fix: add a dedicated router question — a single Multiple choice or Dropdown question whose options map one-to-one onto the paths you need — and let the checkboxes and text questions live inside the sections it routes to. You get the branching you wanted and keep the question types you wanted, they just are not the same question.

Set it up, step by step

These are Google's own instructions, from Show questions based on answers and Edit your form, in the order you actually do them.

1. Split the form into sections

1. Open a form in Google Forms.
2. Click Add section. Google's wording: “To add a section break, click Add section.”
3. Name the new section.

A section is a page. Branching can only send someone to a section, so anything you want to show or skip as a unit has to be in one of its own.

2. Make the routing question Multiple choice or Dropdown

Set the type before you go looking for the menu item. If the question is anything else, step 3 has nothing to show you.

3. Turn on per-answer destinations

Google's steps, verbatim:

1. Open a form in Google Forms.
2. At the bottom right, click More → Go to section based on answer. If you want the survey to end based on an answer, you can also choose Submit form.
3. Choose specific sections to send people to.

Each answer option grows its own destination drop-down. Submit form is the one worth remembering: it ends the response there, which is how you build a screener that politely stops people who do not qualify.

4. Give every option a destination

Options you do not touch stay on Continue to next section. That is a real answer, not an empty one — leave it only where the next section genuinely is the right next page for that answer.

5. Close each branch at the section end

Google: “At the bottom of each section, you can choose which section people go to next.” This control is the reason so many branched forms leak. If section 2 is the staff path and section 3 is the student path, section 2 must be told where to go next — otherwise everyone who finishes it falls straight into the student questions.

When a question's answer and the section end both name a destination, the answer wins. Google's Apps Script reference for the page break puts it this way: “If the previous page contained a MultipleChoiceItem or ListItem with a navigation option, that navigation overrules this navigation.” Treat the section-end setting as the fallback for everyone the questions did not already route.

A worked example: staff and students

One form, two audiences, no duplicate questions. Four sections:

1. Section 1 — Who are you? A Multiple choice question with exactly two options: Staff and Student.
2. Section 2 — Staff questions. Department, years of service, whatever else.
3. Section 3 — Student questions. Year group, course, and so on.
4. Section 4 — Everyone. Comments, contact details, the shared tail.

Now wire it:

• On the section 1 question: More → Go to section based on answer. Send Staff → Section 2, Student → Section 3.
• At the bottom of section 2, set the next step to Section 4. This is the step people forget, and it is the one that keeps staff out of the student questions.
• At the bottom of section 3, leave it on Continue to next section — section 4 already is the next section.

Then fill the form in twice, once down each path, before you send it anywhere. Branching bugs are invisible in the editor and obvious the moment you answer the question yourself.

Limits and things Google doesn't promise

• 75 sections. Google's Edit your form page: “After you've created a form, you can add and edit up to 300 pieces of content, like questions, descriptions, images, and videos. To organize your form by topic, you can add up to 75 sections.” In practice the 300-item content budget runs out first.
• Two question types. Multiple choice and Dropdown, and no others.
• One destination per answer. There is no AND/OR, no “if answer A and answer B”, and no condition built on a typed value. Google Forms branching is a lookup table from one answer to one section.
• Destinations are not documented as forward-only. Google's help page says only “Choose specific sections to send people to.” It does not say a destination must be later in the form, and Google's own Apps Script enum includes RESTART — “Restart the form from the beginning, without clearing answers entered so far”. Backward jumps are easy to turn into loops, so map the flow before you build it.
• Required questions and the progress bar: Google's branching documentation says nothing about how either behaves on a skipped section. We are not going to guess — test your own form with a required question inside a branch and watch what happens before you rely on it.

Google Forms branching vs. conditional logic elsewhere

One honest caveat on that last row but one. Forms+ has a Conditional logic feature that shows or hides individual questions from earlier answers, which is finer-grained than sections. It is enforced in the app's native fill view, not by Google — a respondent opening the same form in a browser sees Google's section branching only. Use it for in-app workflows; use sections for links you send out.

Frequently asked questions

Why is “Go to section based on answer” missing from my question?

Because the question is the wrong type. Google documents the restriction plainly: “Go to section based on answer” is only available for Multiple choice and Dropdown question types. It is not greyed out on a checkbox or short answer question — it simply is not in the More menu at all. Change the question to Multiple choice and the option appears.

Can I branch on a checkbox or short answer question in Google Forms?

No. Branching is restricted to Multiple choice and Dropdown. A checkbox question lets a respondent pick several answers at once, which would demand several destinations, and a short answer question has no fixed set of answers to attach destinations to. The usual workaround is to add a single Multiple choice router question whose options map one-to-one onto the paths you need.

How many sections can a Google Form have?

Up to 75. Google's Edit your form help page states: “After you've created a form, you can add and edit up to 300 pieces of content, like questions, descriptions, images, and videos. To organize your form by topic, you can add up to 75 sections.” The 300-item content budget usually runs out before the 75 sections do.

What happens when a question sets a destination and the section also sets one?

The answer's destination wins. Google's Apps Script reference for the page break says: “If the previous page contained a MultipleChoiceItem or ListItem with a navigation option, that navigation overrules this navigation.” So the section-end setting is the fallback for everyone whose answer did not route them somewhere else.

Can I set up conditional logic on a Google Form from my phone?

Yes, in Forms+ on iPhone and iPad. It has Add section in the editor toolbar, “Go to section based on answer” in the question menu for Multiple choice and Dropdown questions, per-option destinations of Continue to next section, Go to section N, or Submit form, and a read-only Branching map that draws the whole flow. The changes are saved to your real Google Form.