> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/command-centre/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/command-centre/visitor-management-powered-by-kenai/resource-booking/manage-bookings.md).

# Manage and report on bookings

Each resource has its own report page in the Kenai dashboard where you review bookings, tailor the columns, filter to a timeframe, save views, and export. Parking adds a second surface, **Logs**, that reports actual on-site vehicle usage rather than the bookings made in advance. This page covers both. For what resource booking is and how the resource types fit together, see [About resource booking](/command-centre/visitor-management-powered-by-kenai/resource-booking/resource-booking-overview.md).

## Open a report

Every resource summary tile on the dashboard links to its booking report.

1. On the dashboard home, find the **RESOURCES** card.
2. Select a tile (for example **DESK THIS WEEK** or **PARKING TODAY**) to open that resource's report for today or the current week.

The report opens on the **Bookings** tab. Each resource page has tabs for **Logs**, **Bookings**, and **Analytics**.

{% embed url="<https://app.arcade.software/share/6NFb7cRdFAPEQk8XP9jN?embed=true>" %}
Walkthrough: opening the Desk Bookings report from the dashboard and using its column, filter, date, and export tools.
{% endembed %}

## What a booking report shows

The **Bookings** tab lists every booking made through the system. The default columns are:

* **Reference**
* **Person**
* **Email**
* **Site**
* **Event Schedule**: **Date**, **Start**, **End**
* **Booking Schedule**: **Date**, **Start**, **End**

The footer shows the row count, for example **Rows: 18 Total Rows: 18**.

## Tailor the report

The same set of tools sits on every booking report. Use them to shape what the report shows before you export it.

{% stepper %}
{% step %}

### Set the date range

Open the date-range selector at the top right (it shows the current range, for example **Jun 23, 2026 to Jun 30, 2026**). Pick a custom range or a preset: **Today**, **Tomorrow**, **Yesterday**, **This Week**, **Last Month**, **This Month**, or **Next Month**, then **Apply**. Use **Reset** to clear it.
{% endstep %}

{% step %}

### Choose and arrange columns

Open **Columns** to add, remove, and reorder fields so the report shows the information most relevant at the time. Beyond the defaults, parking reports expose fields such as **Classification**, **Status**, **Type**, **Allocation Group**, **Bay Group**, **Parking Lot**, **Parking Section**, **Vehicle Make**, **Model**, and **Registration**.
{% endstep %}

{% step %}

### Filter the list

Open **Filters** to narrow the bookings to what you need.
{% endstep %}

{% step %}

### Save the view

Open **Saved Views** to store the current column, filter, and date configuration so you can restore it later. Use **Save Current View** to keep the current setup, or **Reset to Default** to revert.
{% endstep %}

{% step %}

### Export the report

Use the export control near the top-right toolbar to download the report. Parking reports export in **CSV** or **Excel** format. The selected dates and filters are retained in the export.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Note**: a search bar and Kenai's **AI Assistant** are available in the report toolbar to help you find bookings.
{% endhint %}

## Bookings vs. logs (parking)

Parking has two report surfaces, and they answer different questions.

* The **Bookings** tab reports on all bookings made through the system, not on the vehicles that have actually arrived and parked on the premises.
* The **Logs** tab reports actual parking usage: the physical vehicles entering and taking the spaces configured at the venue.

Open the **Logs** tab from a parking report to see the **Parking Logs** page. It has its own columns for the data captured on site, including **Photo**, **Visitor**, **Booking**, **Vehicle (Make / Model / License Plate)**, **Type**, **Mode**, **Host**, **Site**, and **Company**. The same column selector, filters, saved views, search, AI Assistant, date selector, and export tools are available here.

To see the booking behind a log entry, select its reference number in the **Booking** column. A **Booking Details** dialog opens, showing fields such as **Booking Reference**, **Assigned Parking Lot**, **Parking Area**, **Classification**, **Allocation Group**, **Bay Group**, **Booking Start**, and **Booking End**.

{% embed url="<https://app.arcade.software/share/n8jW7boosFEBldxXnrmR?embed=true>" %}
Walkthrough: reporting on the Parking Bookings page, switching to Parking Logs for actual usage, and opening a booking's details from a log entry.
{% endembed %}

## Related

* [About resource booking](/command-centre/visitor-management-powered-by-kenai/resource-booking/resource-booking-overview.md)
* [Understanding the resource booking analytics screen](/command-centre/visitor-management-powered-by-kenai/resource-booking/booking-analytics.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 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://help.security.gallagher.com/command-centre/visitor-management-powered-by-kenai/resource-booking/manage-bookings.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.
