Multi step form best practices

A multi step form trades one long page for several short ones. Done well, each step is a small, obviously finishable job and the form feels shorter than it is. Done badly, the same fields are chopped into arbitrary pages, the respondent cannot see how much is left, and the step that needs a document nobody warned them about comes fourth.

The best practices come down to six decisions. Split only where the sections are different jobs. Use as few steps as those jobs need. Put the easiest step that confirms the person is in the right place first. Show progress as a plain count, if at all. Make Back safe. And because a half finished form cannot be saved and resumed, tell people everything they will need before they start.

When to split a form into steps

Nielsen Norman Group’s article on wizards is the clearest statement of the trade. Splitting a process into steps puts less on each page, so less effort goes on scanning and filtering, and each control gets more room. The costs are real too: it is harder to compare or move information between steps, and steps suit people doing something rarely rather than people entering the same data every week. The W3C’s accessibility tutorial on multi page forms adds a reason that is easy to underrate: breaking a long form into logical stages makes it less daunting, particularly for people with cognitive disabilities or less experience with computers.

That gives a practical rule. Split when the sections are different jobs, ideally needing different things to hand. Keep one page when the form is a single job, however many fields it has.

The childcare enrolment form is a good test case. Its 21 fields fall into five sections that are genuinely separate conversations: the child, the parents and guardians, health, the subsidy, and consents. Health needs the Medicare number and the immunisation history statement. Subsidy needs a myGov claim. Consents end in the parents’ signatures. A parent can finish one of those and feel it is done, which is the whole point of a step.

How many steps

One per job, and each named for what it asks. The W3C’s principles for multi step forms are to split by logical groups of controls, to repeat overall instructions on every page, and to make optional stages easy to recognise and skip. None of that works if a step is just “Page 3”.

The examples on this site use the section heading as the step label. The dental intake form runs “Step 1: about you”, “Step 2: your health”, “Step 3: consent”, and its welcome screen promises exactly that: three steps, about eight minutes. The catering order form uses three as well, “who and where”, “what and how many”, “delivery”, which maps onto how a caterer actually thinks about an order.

If you are going past five or six steps, check whether you are running two forms at once. A long application with a separate referee report is two forms sent to two people.

What goes on the first step

Start with the step that is easiest to answer and that confirms the form is the right one. NN/g notes that wizards work because people do not have to decide the order themselves; the corollary is that you have to choose it well.

For an enrolment, that is the child, because it is the reason the parent opened the form. For an order, it is who and where. For anything with eligibility rules, it is those rules, so nobody writes three essays before discovering they could not apply. The community grant application opens with the organisation’s name, ABN and legal type before a word about the project, because an ineligible organisation should find out in thirty seconds.

Save the heavy step for later, once people are invested, and keep the final step short: the declaration and the signature. GOV.UK recommends a check answers page just before confirmation, because seeing everything once more raises confidence and catches errors. On a paginated form the Back button is how people review, so a light final page makes that review cheap.

Progress indicators

Less is more here. GOV.UK’s question pages guidance says to start by testing the form without a progress indicator, to try improving the order, type or number of questions first, and only then to add a simple step or question count. It also warns against the busy indicator that lists every step and lets people jump between them: often not noticed, space hungry, poor on small screens and hard to label well. It cites a GOV.UK service that removed a 12 step indicator with no effect on completion rates or times.

The W3C suggests telling people on the first step how many steps follow, and letting each step say where they are.

A paginated classic form does the simple version automatically: a thin progress bar along the top of the card and a “Page 2 of 5” counter in the corner. The counter is hidden when a logo band occupies that corner, so if progress matters for a long form, put the logo somewhere else or say the step number in the section heading, which is what the examples do.

Saving progress and the Back button

NN/g recommends letting people leave a wizard midway and resume later. A respondent here cannot save a half finished form and come back to it, so design around one sitting:

• Announce what they need. The childcare welcome screen says “Five steps. Have your CRNs, Medicare number and the immunisation history statement from myGov ready.” The grant application says “Four steps, about 25 minutes, in one sitting.”
• Make Back safe. Back returns to the previous page with every answer still in place, and it is greyed out on the first page, so nobody loses work by checking something.
• Catch errors early. Required fields are checked when somebody presses Next, with a message naming the missing field. Put required fields where people will not skim past them, not at the very bottom of a page.

On a phone, a paginated form falls back to a single scrolling column, because a fixed page does not fit a small screen. That is another reason to name sections as steps: the headings still orient a phone user who never sees a page break. If most of your respondents are on phones and each question stands alone, one question per screen may suit them better; the page on survey fatigue covers why long forms lose people either way.

A step plan by form type

The table at the end of this article sets out a step plan for nine common form types: how many steps, what each covers and what belongs first. It is a starting point, not a rule. The last row matters as much as the others: a signup, an RSVP or a short survey should not be split at all.

Common mistakes

• Splitting by field count. Pages of six fields each, cut wherever six happens to land, give people steps with no meaning.
• Surprise documents. A step that needs a certificate nobody mentioned is where a one sitting form gets abandoned.
• Instructions only on page one. Repeat the one instruction that matters, such as who can sign, on the step where it applies.
• The hardest step first. Essays and medical history before contact details make the form feel longer than it is.
• A progress indicator on a two page form. It is noise. Two pages need a clear heading, not a bar.
• Assuming everyone sees pages. Phone users scroll. Write headings that work both ways.

For the levers beyond step structure, such as field count, order and mobile layout, see how to improve form completion rate.

Build it

The multi step form builder page shows a paginated classic form, and the guide to turning a long classic form into steps covers the Layout panel settings. In short: a classic form lays out as Flow, Single Column or Paginated, pages follow the form’s page size (A4 portrait, A4 landscape, Letter or custom), and a Space component nudges a break. The builder has 41 component types across classic and conversational forms; conversational forms already ask one question per screen. The welcome screen carries the estimated time, the four access types decide who can open the form, and the four add-ons (e-signing, webhooks, email alerts, redirect) handle what happens after the last step.