Let users check their answers before submitting information to a service.
There is a coded example of a check your answers page in the GOV.UK Prototype Kit.
When to use this pattern
Show a single Check answers page immediately before the confirmation screen for small to medium-sized transactions.
When designing a very large transaction with multiple sections, it may help to include a Check answers pages at the end of each section.
This can be valuable for services where different users might be completing each section. You should test this approach with your users to find out if it’s helpful.
How it works
Check answers pages help to:
- increase users’ confidence as they can clearly see that they have completed all the sections and that their data has been captured
- reduce error rates as users are given a second chance to notice and correct errors before submitting data
Make the page easy to understand
On your Check answers page you should:
- make it clear there’s a task to perform on the page
- make it clear that the transaction won’t be complete until a user confirms their information is correct
- break the content up into sections when you can
- only show sections that are relevant to users – for example, if they’ve said they’re from the UK, don’t show sections for questions they haven’t answered about locations outside of the UK
- rephrase questions if you need to – for example, you don’t need to label every individual line of an address, and you can rewrite long questions as shorter statements
- make sure the submit button clearly shows the action it performs – for example ‘Change your tax details’ or ‘Send your claim form’
Let users go back and change their answers
You should provide a ‘Change’ link next to each section on your Check answers page so that users can add or change the information.
The answers pages should look the same way they did when the user last used them, with all their answers pre-populated.
When they’ve finished, the ‘Continue’ button should return them to the Check answers page. They should not need to go through the rest of the transaction again.
If a user changes their response in a way that means you need to ask them more questions, do this before returning them to the Check answers page.
Research on this pattern
Get in touch
If you’ve got a question, idea or suggestion share it in #govuk-design-system on cross-government Slack (open in app) or email the Design System team on email@example.com