> 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/evidence-overview.md).

# Evidence Overview

Monitor the status and progress of all audit evidence.

## Workflow Overview

<i class="fa-location-dot">:location-dot:</i> **Current Task:** Evidence Overview

<i class="fa-user">:user:</i> **Performed By:** Lead Evidence Collector

{% hint style="warning" %}
This task is not represented in the process map because it is not a workflow step. It is used only for oversight and status tracking and does not affect workflow execution or progression.
{% endhint %}

***

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

The **Evidence Overview** 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.

{% hint style="danger" %}

#### Task Availability

The **Evidence Overview** task is issued concurrently with the [**Evaluate Requirements**](/interfacing-help-files/auditors/managing-internal-audits-apps/planning-and-executing-audits/evaluate-requirements.md) task. However, it is generated only if at least one audit 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 task is skipped.
  {% endhint %}

***

## Using the Overview

Following confirmation of the audit schedule, this task is issued to support the monitoring of evidence collection and the review of progress.

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

{% hint style="warning" %}
This form is read-only and intended for monitoring purposes only.
{% endhint %}

{% stepper %}
{% step %}

### Reviewing Evidence

If you need to inspect evidence for a specific test:

* Double-click the record, or
* Click **Edit** ( <i class="fa-pen">:pen:</i> )

This opens the **Review Collected Evidence** form, where you can:

* View submitted samples
* Read existing comments
* Add your own comments

{% hint style="info" %}

#### Commenting Guidelines

* You can **edit**, **delete**, or **reply** to your own comments.
* You can **reply** to others' comments but cannot edit or delete them.
  {% endhint %}

***

{% endstep %}

{% step %}

### Tracking Status

Use the **Status** column to monitor the current state of each evidence item and quickly identify where action may be required.

* **Scheduled** — The start date of the evidence collection round has not yet been reached.
* **In Progress** — The current date is within the start and end dates of an evidence collection round, and the evidence has not yet been submitted.
* **Overdue** — The evidence has not been submitted by the end date of an evidence collection round.
* **Under Review** — The evidence has been submitted and is awaiting review.
* **Approved** — The evidence has been reviewed and approved.
* **Rejected** — The evidence has been reviewed and rejected.

***

{% endstep %}

{% step %}

### Viewing Additional Metrics

Use these metrics in the grid to identify potential issues:

* **Rejected Count** — The number of times the evidence has been rejected
* **Sample Count** — The current number of samples collected for the evidence

{% hint style="info" %}
These values update in real time, reflecting the latest changes.
{% endhint %}

***

{% endstep %}
{% endstepper %}

***

## Completion & Closure

You do not need to complete this task manually. It closes automatically when one of the following occurs:

* All evidence for the audit have been reviewed and approved by the Lead Evidence Collector.
* The Lead Auditor has signed off on the audit in the [Review & Approve Audit Results](/interfacing-help-files/auditors/managing-internal-audits-apps/planning-and-executing-audits/review-and-approve-audit-results.md) task.

{% hint style="info" %}
Once closed, the task remains available in the **To Do** module with a status of <mark style="color:$success;">**`Completed`**</mark>, allowing you to revisit it at any time to view the final evidence status and progress report.
{% endhint %}

***

## 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/evidence-overview.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.