> 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/site-performance-report.md). # Site Performance Report ## Overview The **Site Performance Report (Site PR)** provides high-level operational visibility across sites, departments, work areas, and operational activities within the organisation.

As the highest reporting level within the Performance Report structure, the Site PR is designed to help management and compliance teams monitor operational performance, compare compliance results, and analyse organisational performance across multiple locations. The Site PR includes two reporting views designed for different operational and analytical purposes. | Report Type | Description | | --------------- | --------------------------------------------------------------------------------------------------- | | Detailed Report | Displays hierarchical operational performance across sites, departments, work areas, and operations | | Trend Report | Displays operational performance trends over time using graphical reporting | *** ## Report Types The **Site Performance Report (Site PR)** includes two reporting views designed for different operational and analytical purposes. | Report Type | Purpose | | --------------- | --------------------------------------------------------------------------------------------------- | | Detailed Report | Displays hierarchical operational performance across sites, departments, work areas, and operations | | Trend Report | Displays operational performance trends over time using graphical reporting | *** ### Detailed Report The **Detailed Report** provides a structured operational view across: * Sites * Departments * Work Areas * Operations This view focuses on current operational performance and compliance visibility.

Users can progressively expand operational levels to review more detailed information and performance scoring. #### Key Features * Hierarchical operational structure * Expandable site and department views * avg(Score) performance indicators * Operational comparison across locations * Compliance and operational visibility * Scheduled email reporting * Export functionality #### Best Used For * Reviewing current operational performance * Monitoring site and department compliance * Comparing operational scores * Identifying underperforming areas * Drill-down operational visibility *** ### Trend Report The **Trend Report** provides a graphical view of operational performance trends over time. This report displays historical performance scores using charts and visual analytics to help users monitor long-term operational performance.

The Trend Report focuses on trend analysis rather than hierarchical operational structures. #### Key Features * Graphical performance reporting * Monthly performance trend analysis * Historical score comparison * Year selection and navigation * Visual operational analytics * Long-term performance monitoring #### Best Used For * Monitoring operational performance trends * Comparing historical performance results * Identifying recurring operational patterns * Reviewing long-term compliance improvement * Supporting management reporting and analysis --- # 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/site-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.