Show Different Google Forms Questions Based on an Answer

To show different questions based on an answer in Google Forms, put the questions in separate sections and route people to the right section from a multiple-choice or dropdown answer. A client intake form can then ask about the service a client needs without showing questions for other services.

Google Forms conditional questions work through sections

Google Forms conditional questions are sections that respondents reach according to an earlier answer. The form does not hide individual questions within a section. Instead, you place each set of questions in its own section and send respondents to the section that applies to them.

Picture a client intake form for a business that offers consultations and document preparation. Everyone needs to provide contact details. Consultation clients should then see questions about availability and meeting goals. Document clients should see questions about the material they need prepared. Putting those service-specific questions in separate sections keeps each client on a relevant path.

Use branching when an answer changes what you genuinely need to ask next. If every client can answer the same short set of questions, a single section is simpler to build and maintain. A broad question such as “Tell us about your project” may be enough when the differences between services are small.

Branching changes the respondent’s route through the form, not what happens after submission. If you later want to draft a client proposal from a Google Form response, treat that as a separate task. First make sure the intake form collects the right information.

The client intake form needs a shared start and separate service paths

Put questions every client must answer before the branching question, then create a section for each distinct service path. In the intake example, the opening section asks for contact details and which service the client wants. A consultation section asks about meeting goals and availability. A document preparation section asks what needs preparing and what source material the client has.

Before building, write each path on paper. Mark questions that belong to everyone, questions that belong only to one service, and any final questions everyone should answer. This prevents the same contact question from appearing in several places and makes the section order easier to check.

Keep each branch focused on information needed for that service. If consultation clients do not need to supply source material, do not put that question in a section they will visit. If both groups need to state a deadline, put that question in a shared section after the branches, or ask it before the service choice.

Choose an answer option for people whose needs do not fit either service only if you have a useful destination for them. An “Other” path could lead to a short description question. Otherwise, a simple service choice may be clearer than an extra branch that collects little information.

How to add branching in Google Forms with a service question

To add branching in Google Forms, create sections first, then route each answer from a multiple-choice or dropdown question. Open the form editor, add the opening questions, and use the section control to create separate sections for consultation and document preparation. Give each section a clear title so you can recognize it when selecting destinations.

In the opening section, add a multiple-choice question asking which service the client needs. Add an answer choice for each path. Open that question’s menu and select “Go to section based on answer.” A destination selector appears beside each choice. Set consultation to the consultation section and document preparation to the document preparation section. A dropdown question can also serve as the routing question.

Place the routing question in the section where respondents make the choice, before they reach either service path. A checkbox question is not the right choice for this setup because respondents can select several answers, while this route needs one destination. If clients may need both services, ask them to choose the main reason for contacting you, or use a shared set of questions instead.

Check the destination beside every answer choice, including any choice added later. Creating a new option does not replace the need to decide where that option should send someone.

A shared ending keeps clients out of the wrong branch

Set the route at the bottom of each service section so clients reach a shared ending rather than the next service section. In the client intake example, add a final section for questions such as the preferred way to be contacted. Then use the section navigation setting at the bottom of both the consultation and document preparation sections to send respondents to that final section.

Section order alone is not enough to protect a branch. If the consultation section sits immediately before the document preparation section and is left to continue to the next section, consultation clients may see document questions too. The answer-based route gets them into the correct branch; the setting at the end of that branch determines where they go afterward.

If there are no shared questions to ask after a service section, set that section to submit the form instead. Do the same for an “Other” section if its short description is the last thing you need. Keep contact details near the start so every route collects them.

This distinction matters when you later send a Slack alert only for answers that need follow-up. Routing controls which questions a client sees. An alert uses the submitted answers and is a separate automation.

Preview every answer path before sharing the form

Test each service choice in the form’s preview, from the first question through submission. Select consultation and confirm that the consultation questions appear, the document questions do not, and the shared ending appears if you made one. Start a fresh preview for document preparation and check the opposite path. Test an “Other” choice as well if the form offers it.

Pay particular attention to questions marked required. A required question in the section a client visits must be answered before they can continue. Questions in a section they never visit should not become an obstacle, but previewing each path is the practical way to catch a misplaced question or route. If a client cannot submit, check which section contains the required question and whether the preceding section points to the intended destination.

Run through the form again after adding, removing, or reordering sections. Look at both the answer destinations and the navigation setting at the bottom of each branch. A route that worked before an edit may no longer describe the path you meant to offer.

Submit sample responses if you need to inspect what the responses contain. Keep them clearly separate from real client inquiries, then remove them if they should not remain with live intake records.

Branching is enough until the work begins after submission

Google Forms branching is enough when the goal is to ask relevant questions and collect the resulting answers. It is a form feature, not a workflow that sends messages, books appointments, or prepares documents. For a small client intake process, a clear form and a person reviewing each submission may be all that is needed.

If the next job is to arrange a meeting, decide first whether a client’s answer provides enough detail for scheduling. The separate guide to creating Google Calendar events from form responses addresses that work. If the next job is a client-facing document, decide which submitted fields belong in it before considering a workflow to make a PDF from each form response.

Keep the service question easy to interpret even if you plan to automate later. An ambiguous choice makes manual review harder and gives later workflows less reliable information. Avoid branching merely to collect data you might someday use.

The decision rule is simple: use sections when different answers require different questions; keep a single path when everyone can answer the same questions; consider a separate automation only when something needs to happen after the form is submitted.

Sources consulted

• Google Forms Help (support.google.com)

Start a free course