> 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/tracking-and-monitoring-audits/completed-audits.md).

# Completed Audits

Use the **Completed Audits** module to view and review audits that have been finalized and closed.

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

***

## Working with Audits

Follow the steps below to locate and review audits efficiently.

{% stepper %}
{% step %}

### Filtering Audits

Use the **Search Panel** to filter the audits shown in the grid. You can filter by:

* **Audit ID:** Enter the unique identifier for the audit.
* **Audit Name:** Enter the full or partial name of the audit.

{% hint style="info" %}

#### Actions:

* **Filter:** Click to apply your criteria and update the grid with matching results.
* **Clear Filter:** Click to remove all filters and restore the full list of audits.
  {% endhint %}

***

{% endstep %}

{% step %}

### Accessing Audits

To open a specific audit, click the **View** ( ![](https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FIAlpvjgSBR3lKZjwsXm7%2FIMS-KI-L-9.svg?alt=media\&token=262f3701-b544-43fe-b1bc-d17a29a18e55) ) icon next to it.

* The audit opens in read-only mode, where you can:
  * Review all details
  * [View or download attached templates](/interfacing-help-files/end-users/exploring-apps/working-with-forms/generating-templates.md)

{% hint style="success" %}
**Tip:** Use the following columns in the grid to quickly assess audit scope and coverage:

* **Total No. of Audit Programs**
* **Total No. of Requirements**
  {% endhint %}

***

{% endstep %}
{% endstepper %}

***


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://interfacing.gitbook.io/interfacing-help-files/auditors/managing-internal-audits-apps/tracking-and-monitoring-audits/completed-audits.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.