When should a long form become a multi-step journey?
Twelve fields do not automatically justify twelve screens. Some answers belong together, while others only make sense after an earlier choice. A stepped form is useful when it follows the decisions the visitor actually needs to make. This guide addresses a different problem from writing field labels: deciding what belongs on the same screen, what should wait, and what must happen when someone changes their mind near the end.
Draw two genuine routes first
Consider an illustrative interior design enquiry with two routes: renovating an existing space and planning a new one. The first may require current dimensions and photographs; the second may begin before a location is confirmed. These are teaching examples, not client records. Write down the information each route needs. Identify the shared questions before giving everyone the same long questionnaire. Include a reasonable answer for details the visitor cannot yet know.
Learn from a real question-page example
The GOV.UK question-page example shows a focused decision presented through a heading, choices and a continuation action. A public-service pattern is not a universal commercial template. In our enquiry example, choosing the service first is useful; splitting a name and email address into separate screens may merely add transitions. Explain the proposed structure through the dependencies between answers, rather than an arbitrary target number of pages.
Make the progress description honest
For this example, three labels could work: needs, details and review. If changing the service introduces additional questions, avoid promising an exact completion time before the route is known. Show completed stages with words as well as colour. If visitors will need to prepare a file, explain that at the beginning. In a small prototype session, ask what they expect to see next. A mismatch is a reason to revise stage names or question order.
Treat going backwards as its own task
Someone reaching the final stage may need to revise their budget range. If your design forces them to start again and re-enter everything, the steps are not helping. Try the browser back button, the interface back link and any stage navigation separately. Make sure answers that become irrelevant after a change do not remain in the final summary. Decide where information is stored and for how long; do not casually retain sensitive answers indefinitely in the browser.
Separate reviewing from sending
The GOV.UK check-answers example places a summary beside routes for changing individual answers. For our enquiry, show service, scope and contact details in a readable review. Explain that reaching this screen has not sent the request. Label the final action with its actual purpose, such as “Send enquiry”. The following confirmation should reflect a genuinely received record; arriving at the last stage is not proof of successful submission.
Approve the journey through a complete task
On a phone, ask a participant to start a renovation enquiry, enter details, change the service, review the summary and submit in a test environment. Record hesitation and lost information. Also inspect the received record with the team that will handle the enquiry. In a website design project, this is an operational journey as well as a visual interface. For choosing the individual questions, see our separate enquiry form guide.
Frequently asked questions
Should a short contact form use steps too?
Try one screen first. Moving a few related questions onto separate pages may add interactions without making the task clearer.
Will steps increase enquiries?
That requires evidence. Observe completion, corrections and errors with people attempting the same task instead of predicting results from form length alone.