service-manual 6 linked patterns checked
GOV.UK Service Manual: Structuring forms
Documents form-structure guidance that starts by splitting forms across multiple pages with each page containing one thing, while acknowledging that a question can require more than one form field.
Read with a purpose
What this source can teach
Use this source to study a complete public-service task and the guidance that supports its implementation.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Complete complex form | Choose a complete complex form when many related configuration fields need one inspectable surface and cross-section comparison matters. | Section navigation changes the visible section without discarding draft values. | GOV.UK form-structure guidance anchors the decision not to use long complex forms when one thing per page is clearer for users. |
| Multi-step form | Choose a multi-step form when the transaction has several ordered pages or sections that need saved progress. | Continue validates and saves the current step before unlocking the next required step. | GOV.UK form-structure guidance supports splitting forms across pages, one thing per page, saving as users go, and branching or loops. |
| Review before submit | Choose review before submit when users need to verify multiple captured answers immediately before committing a transaction. | Review loads only after required upstream answers are saved or clearly marks missing required sections. | GOV.UK form-structure guidance supports collecting answers across pages and saving them as users go before final review. |
| Single-page form | Choose a single-page form when the task has a short related set of fields that users should review together. | Tab order follows the same top-to-bottom order users see on screen. | GOV.UK form-structure guidance supports starting with one thing per page and merging pages when user research shows that is better for the task. |
| Single-question page | Choose a single-question page when one conceptual question deserves focused reading and answering before the next task step. | Back returns to the previous page or step without clearing the current answer. | GOV.UK form-structure guidance supports one thing per page while distinguishing one question from one field. |
| Wizard | Choose a wizard when the product must guide users through a strict or mostly strict setup sequence with dependent choices. | Next validates and stores the current step before moving forward. | GOV.UK form-structure guidance supports distinguishing ordinary multi-page forms from heavier guided setup assistants. |
Evidence Role
This source is treated as service-manual evidence. Its value comes from the specific claims and setting described above.
Publisher: Government Digital Service. Last checked: .