Google Forms supports “Go to section based on answer” for Multiple choice and Dropdown questions. Its official routing instructions, checked October 24, 2026, also describe choosing the next destination at the bottom of each section. ChatGPT can help prepare the routing specification; you configure and test the actual form.
Separate the branches before writing extra questions
This original fictional equipment desk needs these approved paths:
| Section | Contents | Destination |
|---|---|---|
| 1: Request type | Multiple choice: Borrow equipment / Report a repair | Borrow to 2; Repair to 3 |
| 2: Borrow details | Item and requested collection date | Go to 4 |
| 3: Repair details | Asset identifier and problem description | Go to 4 |
| 4: Contact | Approved contact fields | Submit form |
Place Sections 2 and 3 in that order. Then deliberately inspect Section 2's footer. The default continuation can lead to Section 3, which is exactly the unwanted path. Choose Section 4 explicitly for both branch sections.
Use the organization's approved contact and response-handling wording. The example supplies no anonymity promise, urgency guarantee or automatic stock reservation. A borrow request is not an approved checkout.
Give ChatGPT the two kinds of destination
Prepare a Google Forms implementation specification. Do not create,
publish or submit a form.
Purpose and approved question wording: [PASTE]
Branch rules and allowed answers: [PASTE]
Section names and physical order: [ENTER]
Required/optional fields on each route: [ENTER]
Approved contact fields and response destination: [ENTER]
Return every branching question's type and answer-to-section mapping.
Also list the destination at the end of EVERY section, including
branches that must skip the next physical section. Use only supplied
rules; flag missing destinations. Do not use Checkboxes for a native
Go to section based on answer control. Give one test case per route
with sections visited, excluded sections and completion behavior.
Keep test responses separate from collected operational responses.
OpenAI's prompting guidance supports this explicit context and output format. A route table is useful because you can compare it directly with the native controls, without relying on a model's claim that the form is ready.
Set the native controls and walk each route
In Google Forms, add the four sections, use a Multiple choice question in Section 1, and enable Go to section based on answer from that question's menu. Assign Borrow equipment to Section 2 and Report a repair to Section 3. Then set each branch section's ending destination to Section 4.
Use the form's preview to check two fictional responses:
- Borrow: visit 1, 2 and 4; never see the repair asset identifier or problem-description fields.
- Repair: visit 1, 3 and 4; never see the collection-date question.
Complete all required fields on the visited branch. Confirm the other branch does not appear on the way to completion. Test in a designated copy or follow the owner's test-response procedure; previewing the form is not a separate guarantee about where submitted test responses go.
These are expected paths to test, not a report of an executed Google Form. If Borrow reaches Section 3, correct Section 2's footer and repeat both paths. A correct answer destination in Section 1 will not fix that footer.
Keep routing separate from the later analysis
Before distributing the maintained form, confirm its actual response destination and the wording people will see. Retain the route table so later edits can be tested against the same paths.
For analysis, a repair field skipped by a borrower is not a negative answer or a failed response. The survey-analysis guide explains preserving missingness and denominators. First finish the native form check: each requester should reach the relevant questions and then the common contact section.