> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/kenai-user-guide/resource-booking/booking-analytics.md).

# Understanding booking analytics

The analytics screen turns a resource's booking activity into utilisation metrics and charts, so you can see how much of a resource is used, when demand peaks, and whether it is overbooked. Each resource has its own analytics page. For what resource booking is and how the resource types fit together, see [About resource booking](/knowledge-hub/kenai-user-guide/resource-booking/resource-booking-overview.md).

## Open the analytics screen

A dedicated analytics page is available for each resource. Open a resource report (for example a Desk or Parking report) and select the **Analytics** tab. Each resource page has tabs for **Logs**, **Bookings**, and **Analytics**.

To change the period the analytics cover, open the date-range picker at the top right.

{% embed url="<https://app.arcade.software/share/P43S4fgziWqQf6tQqfrz?embed=true>" %}
Walkthrough: the Analytics tab on a resource report, covering each summary metric, the charts, the date range, and multi-site selection.
{% endembed %}

## The summary metrics

Five summary cards sit across the top of the screen:

* **Total Bays**: the maximum available bays at the location.
* **Avg Utilization**: the average percentage of bays used over the selected period.
* **Peak Utilization**: the highest level of usage reached, including the exact time it happened.
* **Peak Day**: the day that had the highest average usage.
* **Overbooking Incidents**: the number of intervals where more bays were booked than available.

## The charts

Below the metrics, four charts break the activity down different ways:

* **Bay Utilization Over Time**: daily utilisation trends.
* **Hourly Patterns**: average utilisation by hour of day.
* **Daily Patterns**: average utilisation by day of week.
* **Utilization Breakdown**: bay breakdown by status over time intervals, with a legend for **Available Bays**, **Booked Bays**, **Occupied Bays**, and **Overbooked Bays**.

## Viewing multiple sites

For accounts with access to multiple locations, you can view utilisation across sites. Use the site selector at the top of the screen to pick one site or select all of them to view combined data. The charts plot a series per selected site, and you can toggle individual site series in a chart's legend.

## Related

* [About resource booking](/knowledge-hub/kenai-user-guide/resource-booking/resource-booking-overview.md)
* [View, filter, and report on bookings and parking logs](/knowledge-hub/kenai-user-guide/resource-booking/manage-bookings.md)


---

# 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://help.security.gallagher.com/knowledge-hub/kenai-user-guide/resource-booking/booking-analytics.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.