Check answers

Enable users to check, review, edit and confirm the information they have provided before completing a significant final action, such as submitting an application.

Use this pattern when information is collected across multiple pages or steps and users need to confirm accuracy before submission.

This helps users avoid errors, feel confident that their information is complete and accurate before submitting, increasing trust in the service.

When not to use

Do not use this page when the journey consists of a single, simple form page where answers are already visible.

How it works

Content

Page heading

Use a clear page heading that tells the user to check their answers. For example ‘Review your answers before you submit’

Summary of question and answers given

Display each question together with the answer provided by the user. Present the content in a structured format that is easy to scan.

Layouts must support both short and long answers. Use a wider layout for long, free-text responses so content can be read comfortably. Use a narrower layout like a two-thirds layout for short answers where this improves clarity and space efficiency.

Sections

Group related questions into sections where this improves readability or when there is a large amount of information to review. Section headings should reflect the structure used earlier in the journey.

Optional questions

Clearly indicate when a question has not been answered because it was optional. Make it explicit that no answer was provided, rather than leaving the space blank.

Conditional or branched questions

Only display questions and answers that are relevant to the user’s journey. Do not show questions that were skipped due to branching or conditional logic.

Uploaded documents

Show any uploaded documents the user provided, including the file name and status. Provide a way to review or replace uploaded files where appropriate.

Interaction and UI behaviour

Enable users to edit answers

Provide clear navigation to edit answers. Users must be able to navigate back to previous steps and edit their answers if needed. This can be achieved through direct links or buttons. After editing, return the user to the check answers step.

Complete and submit

Provide a single primary action that allows the user to complete the review and submit their information. Do not include competing primary actions on this step.

Confirmation before submitting

Make it clear that the user needs to confirm that the information shown is correct and before they choose to continue.

Require a declaration if needed

For sensitive or high-risk submissions, require an explicit declaration before submission. This may be done using a checkbox or digital signature.

Follow the digital signature pattern for implementation guidance.

[FUNCTIONAL] Signature