> 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/change-request-application/tracking-and-monitoring-change-requests/change-request-dashboard.md).

# Change Request Dashboard

View trends, priorities, and risks with interactive charts and metrics.

Use the **Change Request Dashboard** to track and analyze change requests. With it, you can:

* Monitor request status
* Identify priorities and risks
* Review completion trends over time

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

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

***

{% stepper %}
{% step %}

### Viewing Dashboard Metrics

The dashboard displays several charts, each offering a different perspective on your change requests.

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th>What It Shows</th><th>Use It To</th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td align="center"><strong>Change Requests by Status</strong></td><td>The number of requests in each status (e.g., Not Started, Open, Closed).</td><td>Monitor overall progress at a glance</td><td></td></tr><tr><td align="center"><strong>Change Requests by Priority</strong></td><td>The number of requests by priority level (e.g., Minor, Major, Critical).</td><td>Focus on high-priority requests</td><td></td></tr><tr><td align="center"><strong>Completed Action Items &#x26; Tasks per Month</strong></td><td>The number of action items and tasks completed each month.</td><td>Spot workload trends and adjust resources accordingly</td><td></td></tr><tr><td align="center"><strong>Change Requests by Impact</strong></td><td>The number of requests by impact level (e.g., Low, Medium, High).</td><td>Identify high-risk requests</td><td></td></tr><tr><td align="center"><strong>Completed Change Requests</strong> <strong>per Month</strong></td><td>The number of requests completed each month, based on due dates.</td><td>Track whether deadlines are consistently being met.</td><td></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 **Open** slice in the **Status** chart to view all open change requests in a modal window.

***

{% 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://interfacing.gitbook.io/interfacing-help-files/end-users/change-request-application/tracking-and-monitoring-change-requests/change-request-dashboard.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.