> 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/audit-dashboard.md).

# Audit Dashboard

View audit performance, compliance trends, and follow-up actions with interactive charts and metrics.

Use the **Audit Dashboard** to track and analyze audits. With it, you can:

* Monitor audit completion and timeliness
* Identify compliance gaps and risks
* Track relationships between audits, quality events, and CAPAs

{% hint style="info" %}
**Navigation:** Go to **Apps** > **QMS Dashboards** > **Audit Dashboard**.
{% endhint %}

***

## Using the Dashboard

Follow the steps below to explore, analyze, and act on data.

{% stepper %}
{% step %}

### Viewing Dashboard Metrics

The dashboard displays several charts, each offering a different perspective on audit performance and activity.

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th>What It Shows</th><th>Use It To</th></tr></thead><tbody><tr><td align="center"><strong>No. of Audits On Time vs. Past Due</strong></td><td>The number of audits completed on time compared to those that are past due.</td><td>Monitor audit timeliness and identify delays in execution</td></tr><tr><td align="center"><strong>No. of Audits That Triggered a Quality Event vs. No. of Quality Events That Triggered a CAPA</strong></td><td>The number of audits that resulted in quality events, and the number of quality events that led to CAPAs.</td><td>Understand how audit findings translate into downstream actions and improvements</td></tr></tbody></table>

***

{% endstep %}

{% step %}

### Interacting with Charts

Interact with charts to explore details and uncover specific data:

* **Hover** over data points (e.g., bars or pie slices) to view tooltips showing the category and item count.
* **Double-click** a data point to drill down from a summary view into a detailed list.
  * **Example:** Double-click the **Past Due** slice in the **On Time vs. Past Due** chart to view all related items in a form.

***

{% endstep %}

{% step %}

### Exporting or Downloading Charts

Export charts for reporting or offline use.

* Select the **hamburger menu** ( <i class="fa-bars">:bars:</i> ) in the top-right corner of the chart.
* Choose an export format:
  * PNG image
  * JPEG image
  * SVG vector image
  * Text file
  * XLS file

<figure><img src="https://manula.r.sizr.io/large/user/10696/img/audit-dashboard-3_v2.png" alt="" width="188"><figcaption></figcaption></figure>

***

{% 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/audit-dashboard.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.