A branching form should remove irrelevant questions while still collecting everything needed for the chosen request. The common design mistake is to test only the first route. Another answer can send the customer into the wrong section, end the form too early or repeat questions.

Sketch the routes before editing the form. For a fictional small-business enquiry, “new website” might need project details, while “existing website problem” needs the affected address and symptom. Both routes might end with contact information and a clear confirmation.

Build a route table

For each answer to the routing question, record its destination section and where that section should go next. Include an “unsure” path if customers may not recognise your categories. The table should reach a submission point for every allowed answer.

Google’s dedicated branching guidance supports Go to section based on answer for Multiple choice and Dropdown questions. Create the sections, then set the answer destinations and the next-section choice at each section’s end. Do not assume a visually similar question type supports the same routing.

Rehearse the awkward paths

Use fictitious data to complete each route from beginning to end. Record the questions shown and confirm the final response contains the fields required for that route. Test an answer that deliberately ends the form as well as the longest route.

Then go back and change the routing answer during the test. Inspect the submitted result for stale or confusing information from the earlier path. Decide how staff should interpret any such result before accepting real enquiries.

Ask someone unfamiliar with the form to choose a route from the wording alone. If they repeatedly choose the wrong category, improve the question rather than adding more hidden logic.

After moving or removing a section, rerun the route table. A form that worked before restructuring does not prove the new path still reaches the correct questions and submission screen.

References: Google Forms branching.