> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/end-users/to-do/completing-tasks/completing-a-confirmation-task.md).

# Completing a Confirmation Task

Confirmation ensures that users acknowledge and understand published changes relevant to their roles.

The **Confirmation** cycle occurs after an object has been published, allowing participants to review updates and confirm they have read and understood the changes, ensuring all impacted personnel are aware of updates to corporate policies, procedures, or responsibilities.

***

## Interactive Tour

Learn how to complete a confirmation task.

{% @howdygo/embed url="<https://app.howdygo.com/share/09f7d3c0-3ade-4046-ae1e-9d458498c80d>" %}

***

## **Step-by-Step Guide**

{% stepper %}
{% step %}

### Accessing a Confirmation Task

In **To Do**, select a confirmation task in the list.

* Review the documentation by minimizing the submission banner.

{% hint style="info" %}
For more guidance on using To Do, [see this section.](/interfacing-help-files/end-users/to-do.md)
{% endhint %}
{% endstep %}

{% step %}

### Filling Out the Form

* Add a **Comment** to confirm you’ve reviewed and acknowledged the changes to the documentation.
  {% endstep %}

{% step %}

### Finish the Confirmation

* Click **Confirm** to complete the confirmation task.
  {% endstep %}
  {% endstepper %}

***

## See Also

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><strong>See the Next Task in the Lifecycle:</strong><br><br>Completing an Object for Review task</td><td><a href="/interfacing-help-files/end-users/to-do/completing-tasks/completing-a-review-task.md">Completing a Review Task</a></td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2F8nG8qsVK6hM8rgd9AOBg%2FIMS-V16-NAV-Library-Icons-146.png?alt=media&amp;token=4664da70-7b20-4661-a1ab-d4a6c3ff1c85">IMS-V16-NAV-Library-Icons-146.png</a></td></tr><tr><td><strong>Managing Your Tasks</strong><br><br>Learn the basics on how to manage your tasks in To Do</td><td><a href="/interfacing-help-files/end-users/to-do.md">Managing Your Tasks</a></td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FIicHnWRDxU9zPCTnLGLC%2FIMS%20Icons%20(1).png?alt=media&amp;token=f51f14ca-3e0c-466b-be24-aebe5b3d9570">IMS Icons (1).png</a></td></tr><tr><td><strong>Managing a Confirmation Cycle (Modelers Only)</strong><br><br>Learn how to customize confirmation cycles</td><td><a href="/interfacing-help-files/document-control/managing-documentation-lifecycle/managing-a-confirmation-cycle.md">Managing a Confirmation Cycle</a></td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FGOMPRWiAFtJn73zH4ChF%2FIMS-V16-NAV-Library-Icons-121.png?alt=media&amp;token=5cc3b777-9ee8-4990-8acd-b6766dc004a5">IMS-V16-NAV-Library-Icons-121.png</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://interfacing.gitbook.io/interfacing-help-files/end-users/to-do/completing-tasks/completing-a-confirmation-task.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.