> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/performance-report/department-performance-report.md).

# Department Performance Report

### Overview

The **Department Performance Report (Department PR)** provides operational visibility across departments and their associated work areas within a selected site.

<figure><img src="https://1434231645-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBHjO1cs4TsZlF7kQONIF%2Fuploads%2Ffavsz3BWX772bEU95Cl9%2FChatGPT%20Image%20Jun%2017%2C%202026%2C%2009_38_43%20AM.png?alt=media&amp;token=a64f788f-f8c4-4e83-be37-f4f158691bf8" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1434231645-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBHjO1cs4TsZlF7kQONIF%2Fuploads%2FeBD9HnwWEbGmlfZOwZaI%2FScreenshot%202026-05-21%20at%2011.20.22.png?alt=media&amp;token=451f02c8-7938-4048-9b3f-c339ed60c16e" alt=""><figcaption></figcaption></figure>

It acts as the middle reporting layer within the Performance Report structure, sitting between the Site Performance Report and the Work Area Performance Report.

The Department PR is designed to provide:

* department-level operational visibility,
* work area performance comparison,
* compliance monitoring,
* and operational trend analysis.

***

## Report Types

The Department Performance Report includes two reporting views:

<figure><img src="https://1434231645-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBHjO1cs4TsZlF7kQONIF%2Fuploads%2FpA92h41w2TJszki34xdn%2FScreenshot%202026-05-21%20at%2011.54.55.png?alt=media&amp;token=ba0b131c-715d-4504-901a-74a132032888" alt=""><figcaption></figcaption></figure>

| Report Type     | Description                                                                     |
| --------------- | ------------------------------------------------------------------------------- |
| Detailed Report | Displays hierarchical operational performance across departments and work areas |
| Trend Report    | Displays operational performance trends over time using graphical reporting     |

***

## Purpose

The Department PR helps organisations:

* Monitor operational performance across departments
* Compare work area operational scores
* Review departmental compliance performance
* Identify underperforming operational areas
* Support operational reporting and auditing

***

## Common Use Cases

The Department PR may be used to:

* Review department-level operational performance
* Compare work area performance within departments
* Monitor departmental compliance consistency
* Identify recurring operational issues
* Support operational and management reviews
* Prepare for audits and compliance assessments

***

## Who Uses This Feature?

The Department PR is commonly used by:

| Role                | Purpose                                            |
| ------------------- | -------------------------------------------------- |
| Department Managers | Monitor operational performance within departments |
| Supervisors         | Review work area performance                       |
| QA Teams            | Review compliance and operational consistency      |
| Compliance Teams    | Monitor verification and operational performance   |
| Operational Leaders | Review departmental operational visibility         |
| Auditors            | Validate operational and compliance activities     |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.didge.io/home/performance-report/department-performance-report.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 `automate deployments from our CI pipeline` 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.