> 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/auditors/managing-internal-audits-apps/planning-and-executing-audits/confirm-schedule.md).

# Confirm Schedule

Review and confirm the audit schedule, assignments, and collection timelines.

## Workflow Overview

<i class="fa-location-dot">:location-dot:</i> **Current Task:** Confirm Schedule

<i class="fa-user">:user:</i> **Performed By:** Team Leader (e.g., Audit Lead, Audit Supervisor, Engagement Lead)

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

***

## Accessing the Task <a href="#accessing-the-task" id="accessing-the-task"></a>

The **Confirm Schedule** task can be accessed through any of the following:

* The **To Do** module.
* The **Notification Panel** (via the **Notification Bell**).
* The **direct link** provided in the email notification.

***

## Completing the Task

Once all required assignments have been completed and submitted, review the audit schedule to ensure it is accurate, complete, and ready to proceed.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

{% hint style="success" %}
For guidance on common form features and functions, see [**Working with Forms**](/interfacing-help-files/end-users/exploring-apps/working-with-forms.md).
{% endhint %}

{% hint style="info" %}

#### Saving Your Work

To save progress without submitting, click **Save** in the top-right corner of the panel.&#x20;

* The task remains in the **To Do** module for you to revisit and complete later.
  {% endhint %}

***

{% stepper %}
{% step %}

### Review Audit Schedule & Assignments

Carefully review the audit schedule and assignments to confirm accuracy and completeness:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td>✅ <strong>Schedule &#x26; Participants</strong></td><td>Is the schedule clearly defined, and are all required participants assigned?</td></tr><tr><td>✅ <strong>Auditor Assignments</strong></td><td>Are responsibilities appropriately distributed across auditors for all requirements?</td></tr><tr><td>✅ <strong>Collector Assignments</strong> <em>(if applicable)</em></td><td>Are responsibilities appropriately distributed across collectors for all evidence?</td></tr><tr><td>✅ <strong>Collection Schedule</strong> <em>(if applicable)</em></td><td>Are collection timelines realistic and aligned with the overall audit schedule?</td></tr></tbody></table>

***

{% endstep %}

{% step %}

### Finalize Schedule

From the **Task Resolution** dropdown, select one of the following actions:

* **Confirm**

  Confirm the schedule, allowing the audit to proceed as planned.

  → Next Steps: [Evaluate Requirements](/interfacing-help-files/auditors/managing-internal-audits-apps/planning-and-executing-audits/evaluate-requirements.md) | [Evidence Overview](/interfacing-help-files/auditors/managing-internal-audits-apps/planning-and-executing-audits/evidence-overview.md) | [Collect Evidence](/interfacing-help-files/auditors/managing-internal-audits-apps/planning-and-executing-audits/collect-evidence.md)

{% hint style="danger" %}

#### Task Availability

The **Evidence Overview** and **Collect Evidence** tasks are generated only if at least one requirement is included in testing.

* A requirement is included only if **all** of the following conditions are met:
  * It was configured to undergo testing (**Requires Testing?** selected).
  * It is linked to one or more tests
  * At least one linked test has associated evidence

* If any condition is not met, the tasks are skipped.
  {% endhint %}

* **Reject**

  Reject the schedule if updates or corrections are needed, returning it for revision.

  → Next Step: [Schedule Audit](/interfacing-help-files/auditors/managing-internal-audits-apps/planning-and-executing-audits/schedule-audit.md)

{% hint style="info" %}
Once updated, assignments are revalidated before the schedule is submitted again for confirmation.
{% endhint %}

After selecting the appropriate resolution, click **Submit** to record your decision and advance the workflow.

***

{% endstep %}
{% endstepper %}

***

## See Also

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Tracking &#x26; Monitoring Audits</strong></td><td>Monitor the status and progress of audits using lists and dashboards.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FNZOvD3ldHJ3i1zsvDksS%2FCR-V16-Icons-1.png?alt=media&amp;token=7c420cc4-9abf-4601-8fc3-8e9769771b27">App-V16-Icons-1.png</a></td><td><a href="/interfacing-help-files/auditors/managing-internal-audits-apps/tracking-and-monitoring-audits.md">Tracking &amp; Monitoring Audits</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/auditors/managing-internal-audits-apps/planning-and-executing-audits/confirm-schedule.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.