> 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/work-area-performance-report.md).
# Work Area Performance Report
### Overview
The **Work Area Performance Report** is the most detailed level of the Performance Report structure.
It focuses on a single work area and provides daily operational visibility.
Users can:
* Review checklist completion
* Monitor daily performance
* View comments and verification activities
* Identify missed or incomplete records
* Export operational reports
### Accessing the Work Area PR
1. Locate the work area card
2. Click the Work Area **Report** icon
3. The Work Area PR window opens
### Work Area Report Layout
The report window displays:
| Section | Description |
| ----------------------- | ---------------------------------------- |
| Work Area Name | Selected work area |
| Timeline View | Daily activity across the selected month |
| Record Rows | Individual operational records |
| Performance % | Completion/compliance percentage |
| Status Indicators | Daily operational status |
| Comments & Verification | Review and activity actions |
| Export Options | Export report to PDF or Excel |
### Report Table & Status Indicators
The main section of the Work Area PR is displayed as a timeline table that provides a day-by-day overview of operational performance for the selected work area and reporting period.
The table is organized using:
* Date columns across the top
* Record rows on the left side
* Performance percentages for each record
* Color-coded status indicators for daily activity tracking
Each column represents a day within the selected month.
The report uses color indicators to represent daily record status.
| Color | Meaning |
| --------------------- | -------------------------------------------------- |
| Green | Completed / compliant |
| Red | Missed / Expired |
| Light Grey | Closed / Inactive |
| Purple / Blue | Active Task / In Progress |
| No Colors | Future Records / No Schedule Applied |
| Number in Triangle | Number of days have a warning record |
| Yellow Warning Badge | Total warning recorded for that date |
| Red Badge with Number | Number comments recorded for that date or per form |
---
# 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/work-area-performance-report.md?ask=&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.
