A form allows people to enter details to get goods, services or information. It is one of the main ways people interact with our websites and apps.
Understand if a form is needed
People fill in forms because they want or need something.
They have a task they need to complete or a service they need to get, for example paying for something online or getting a quote.
Forms can often be difficult for people to use.
Consider other ways to get information
Sometimes people create a form without thinking about alternatives.
There might be other ways to achieve the outcome you want. Consider whether email, a phone call or a video would be easier for your users.
Ask the right questions
Only ask for what you need
To know what questions are needed, understand:
- how you’ll act on the information you get
- why it’s necessary for your service
If it’s not needed, do not ask.
If it might be needed in the future, only ask at that point.
This is because the more you ask of people, the more effort they must put in. The more effort that is needed, the more likely people are to drop out of the form.
This can mean:
- people do not use us
- customers resent us
- our brand reputation is damaged
- it costs us more to maintain the data
- it costs us more to serve customers as they use more costly contact channels
To understand what’s needed and why, you could use a ‘question assessment’ to list out and evaluate each question. This can help you decide which form fields are required and know how you’ll use the information that’s collected.
Use this to remove any questions that are not essential, or not respectful of people’s data.
We’ve based our question assessment on the question protocol referenced in Adam Silver’s blog post ‘Designing the child funeral fund service’.
Download the question assessment template.
Ask personal questions sensitively
People may be reluctant to give information if:
- they do not know why we’re asking for it
- they do not know what we’ll do with it
- we do not ask in a sensitive way
- it does not allow them to answer in a way that they want
- it’s about a subject that’s hard for them
Consider circumstances that are non-traditional, or subject matters that could be difficult for people. For example, be sensitive when asking for information about:
- children and family, consider people who have estranged family or are recently bereaved
- relationships, consider people who are in non-traditional relationships or are going through a break-up
- sex, gender and titles, consider people who do not want to tell us this information
If you must ask for personal or sensitive information:
- explain why you’re asking
- word the question respectfully
- choose an appropriate question format, for example, a large free text box may be intimidating for people who have low literacy
This can help people understand how to answer.
The NHS has more information about considering the sensitivities around your questions.
Structure questions so that they require the least effort for the user
Structure questions in a way that:
- gives us the information we need to provide the service
- requires the least effort from the user
For example, if the user can choose:
- only one option from a small list, consider using radio buttons
- multiple options, consider using checkboxes
Think about situations that might make options hard to choose from. Give people a way out, for example an ‘other’ or ‘none of these’ option.
Help people complete the form
Set expectations early
Sometimes people get some or all the way through a form only to realise they cannot use the service or are not eligible in some way. This can cause frustration and stress for people.
Be clear and up front about who your form is for and what they can expect.
For example, if only people aged 18 or over can use your service, then you need to state this clearly at the start.
Tell people what they need to know before they start entering details.
They might need:
- an image of themselves
- their bank details
- relevant dates
Do not set timescales for filling in a form, for example, ‘this form only takes 10 minutes’. This is insensitive and frustrating to those who may take longer. Instead, you could tell people how many questions they may need to answer. For example, ‘this form has 5 questions’.
Where needed, set expectations upfront for how long it will take to get back to someone after they have submitted the form. For example, ‘we will respond with a quote within 3 working days’.
Give information at the right point
Understand at what point in the user journey someone would need to know information, and give it only at the point it’s needed.
People who have short-term memory or cognitive conditions, or are distracted, may not retain information easily or for a long time. If someone may need to refer back to information, make it available to them in a way that makes that possible. This could be information given online, or through another channel, for example:
- an email confirming an order, that tells people how they can change an item
- a text message that reminds someone of an upcoming appointment
Give different routes depending on what’s needed
Try to send people down a route that makes sense for them, based on answers they give or options they choose. For example, if someone chooses certain options at the start of the form this might mean you can send them down a route with tailored content or fewer questions.
Put questions in a logical order
Research what order of questions works well for your audience.
Make sure each question is unique and only asks for one thing at a time.
If your form is long or complex, break it down into several pages with one question on each page. This can make them easier to answer.
Group questions about similar subjects into sections.
Help people to fix mistakes
Build services that are flexible enough to allow users to give data in a way that they would naturally. For example, allow users to enter a postcode in upper or lower case, with or without a space.
Validate only after someone submits the form, or section of the form. Do not validate as someone is typing or before they move beyond a section, they may still be editing their answers.
Validation messages should be factual and help the user understand how to fix the error and move on.
After the form
When a user submits the form, tell them we have received the information and what the next steps are. For example, tell them if they will get an email confirming their order, or if they will get a call from us to discuss something.
Include when this will happen. This helps set expectations and can stop people having to ask us.
Research what the most appropriate onward journey is for your users and include a link to that journey. This could be a related service or returning to a landing page where they can get to other services they may need.
Allow people to check and edit their answers
Where possible, allow people to review and edit their answers. It gives people an opportunity to fix any errors they’ve made and will increase the accuracy of the data we get.
Research and improve
Research your form with people throughout the development process. You should do a mix of qualitative research and usability testing. Make sure that at least 1 in 5 participants are disabled or have access needs.
Analytics data can also help you to see where people might be struggling with your form.
Keep improving your form based on the outcomes you get from research.
Form elements and patterns
We have a lot of the parts that make up forms available as reusable elements and patterns. You can use these ready made bits of design and code to create your form.
Changelog for this page
|18 January 2022||First version of page published|
|20 January 2023||Minor content changes|