UX Writing for Digital Services - Check answers

People should get a 'Check your answers’ page before the confirmation or success screen. This gives them the chance to go back and change anything.

If a person decides to go back to a previous answer, the information they’ve already entered should be pre-populated.

Do not pre-populate:

• if the information is no longer valid
• when pre-populating could be a safety or security concern, for example, a password string from being shown

The answers pages should look the same way they did when a person last used them.

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 they change their response in a way that means you need to ask them more questions, do this before returning them to the check answers page.

If you have questions that are optional, let them know that they’ve skipped it without giving an answer. Do this by showing their response as ‘Not provided’.