# 4.3.9 Check answers

<figure><img src="https://1280346931-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3hE0Uutsp0Izues1Vdfb%2Fuploads%2Fgit-blob-3b0f34c51e4e2830663a8616e90cfe49dacfef5e%2FCheck%20your%20answers.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1280346931-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3hE0Uutsp0Izues1Vdfb%2Fuploads%2Fgit-blob-cfd0af94eaa8c36167aca733ce7ccf5047e3c6a1%2FCheck%20your%20answers-%20Example%20implementation%20(1).png?alt=media" alt=""><figcaption><p>Check your answers example implementation</p></figcaption></figure>

By allowing users to review, make changes, or confirm their answers, this pattern helps prevent errors in data submission.

The long term benefits of this pattern are:

* users will be confident while using your service as they can visually confirm that all their information has been accurately captured.
* reducing incorrect and incomplete information will result in lower error rates in applications.

## **When to use this pattern**

Use this pattern when you need to capture information from users on a form that spans multiple pages or steps.

## **How it works**

* Use a clear heading that clearly communicates the purpose of the page, such as "Check your answers before sending your application"
* Show the summary of questions and answers given. Ensure the information is organised and easy to scan.
* Consider the type of answers expected from users. For longer answers, utilize a full-width layout to accommodate the content. For shorter answers, a two-thirds layout may be appropriate to optimise space.
* Break content into sections if needed. If there is a large number of questions or if it improves the clarity, divide the content into relevant sections.
* Clearly indicate when a question has not been answered because it was optional. Make it evident to the user that the answer was not provided.
* Provide navigation to edit answers. Offer users a straightforward way to navigate back to previous steps and edit their answers if needed. This can be achieved through direct links or buttons that allow users to easily access and modify specific questions.
* Include a call to action button at the bottom of the page that helps the user take the final action such as submitting their application.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://specs.govstack.global/overview/23q4/govstack-ui-ux-guidelines/4-design-patterns/6-page-templates/7.14-check-answers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
