(f)Application Forms

< Pattern Library

Overview

Generic application forms are a way of requesting necessary information from the user so that they may be considered for a programme.

Use of this pattern

• Know why you’re asking every question
• Only add a question if you know that you need the information for the application
• Only add a question if you know why you need the information
• Only add a question if you know what you’ll do with it
• Only add a question if you know which users need to give you the information
• Only add a question if you know how you’ll check the information is accurate
• Only add a question if you know how to keep the information up to date and secure
• Start with questions that will let users know if they’re not eligible for the service, so you don’t waste people’s time
• Use ‘branching’ questions so people only have to answer questions that are relevant to them
• You need to decide which group of users you want to prioritise. Make sure you know the relative size of your different user groups and how your decisions will affect them

How it works

• Before you start, make a list of all the information you need from your users Start by splitting the form across multiple pages with each page containing just one thing, for example:

one piece of information you’re telling a user one decision they have to make one question they have to answer User research will tell you when you can merge pages together. For example, if you’re designing an internal service for government users who need to repeat and switch between tasks quickly.

Starting with one thing on a page helps people to:

understand what you’re asking them to do focus on the specific question and its answer find their way through an unfamiliar process use the service on a mobile device recover easily from form errors It also helps you to:

save a user’s answers automatically as they go capture analytics about each question handle branching questions and loops

Structure your form to help users Asking a question doesn’t necessarily mean you should use one form field. For example, date of birth is best captured with 3 text fields.

For page titles you can use either a question or a statement. For example, ‘What is your date of birth?’ or just ‘Date of birth’.

Use questions or statements consistently to help users get into a rhythm of answering. This lets them focus on the content of the questions rather than their presentation.

Research on this pattern

• https://www.gov.uk/service-manual/design/form-structure

Related patterns

• ...

Other