What is a multi step form?

Where the breaks should go

Draw each step around one kind of information, not around an even number of fields. The W3C forms tutorial gives the example of an online shop that separates shipping from payment, and that instinct generalises: who you are, what you need, when and where, then the agreement. A step named by its content reads as progress, while four steps of three unrelated fields each reads as paperwork. Two refinements help. Put anything that decides eligibility early, so nobody fills in three pages before learning they cannot apply. Put the heaviest asks late, such as uploads, a declaration or a signature, once people have invested enough to finish. A step with a single field is usually a sign the grouping is wrong, unless that one question is a deliberate gate.

What a step form owes the person filling it in

Three things, and most broken wizards miss one. First, orientation: a heading or page title that says which step this is and how many remain, which the W3C tutorial recommends putting in the title itself so a screen reader announces it on arrival. Second, a way back that keeps what was typed. The GOV.UK design system includes a back link on every question page because some people do not trust the browser back button while entering data, and the W3C guidance is that anything already entered on the current step should be kept when they move. Third, a chance to check. On a long application a final review of every answer before the submit button prevents the correction emails that otherwise arrive the next morning.

When one page is the better choice

Splitting is not automatically an improvement. A short form of five or six questions gains nothing from pages and loses a tap for every step. People filling in a form with documents beside them often want to scan the whole thing first, so they can gather what is needed before they begin, and a wizard hides exactly that. Forms that will be printed, or saved as a record, are easier as one page. Even progress indicators are not a free win: the GOV.UK design system advises testing a form without one first and notes that services have removed them without any effect on completion. The honest test is to watch five people fill in both versions and count the hesitations, rather than assuming the wizard is friendlier.

The cost nobody sees: answers held until the end

In most step forms the answers from earlier pages wait in the browser until the final button is pressed. Somebody who leaves on step three has typed two pages of information that was never sent, and the form owner never learns they existed. That changes how a step form should be designed. Ask for the information you would most regret losing where it makes sense to ask for it, rather than saving everything for a final page. Keep the last step short, because a long final page is where finishing feels furthest away. And treat a sudden drop in submissions after a change to the steps as a warning, since the abandoned attempts will not show up anywhere else.

Steps in the form builder

There are two ways to get steps. A classic form set to its paginated layout mode, one of three alongside flow and single column, shows one page at a time with Back and Next, a thin progress bar across the top and a Page X of Y badge. A conversational form goes further and gives every question its own screen, with a progress bar that counts the screens visited against those still ahead. Conversational forms can also skip screens with jump rules on the Logic tab, and Back returns along the path the respondent actually took. Either way, a response is only created when the form is submitted, so nothing from an unfinished attempt is stored.

Questions people ask