Check answers page

Why use this pattern

Let users check their answers before submitting information to a service.

Check answers design pattern

When to use this pattern

Show a check answers page immediately before the confirmation page.

If a service takes payment, show a check answers page immediately before the payment page. The payment page is followed by the confirmation page.

When to use this pattern

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 a form.

Make the page easy to understand

On your check answers page, you should:

  • Make it clear there’s one primary task to perform on the page – for example ‘Finish and go to checkout’.
  • Make it clear that the transaction will not 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 Yukon, do not show sections for questions they have not answered about locations outside of Yukon.
  • Rephrase questions if you need to – for example, you do not 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 contact and mailing details’ or ‘Change type(s) and number of certificate(s)’.

Let users go back and change their answers

You should provide a ‘Change’ button next or underneath each section on your check answers page so that users can add or change the information. Use a secondary button for these buttons.

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.

Last update:
jan 28, 2019