> For the complete documentation index, see [llms.txt](https://support.meetuma.ai/uma-knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.meetuma.ai/uma-knowledgebase/data-and-reporting/analytics-pro/dashboard/space-usage-and-trends.md).

# Space Usage and Trends

<figure><img src="/files/qy56qidNd2SGanExyTXH" alt=""><figcaption></figcaption></figure>

### Overview

The Space Usage and Trends dashboard delivers a complete picture of how rooms, desks, parking, and zones are reserved and used across your estate. It cross-references calendar reservations with real sensor data so you can distinguish *booked* space from *occupied* space and identify where workplace investments deliver value.

Use this dashboard to:

* Right-size the workplace portfolio
* Identify and reduce no-show waste
* Compare booking behaviour across teams, neighbourhoods, and resource types
* Provide environmental evidence for individual meetings
* Support real-estate and floor-redesign decisions with quantitative data

***

### Dashboard Structure

The dashboard is organised into seven tabs:

1. **Space Usage**
2. **Reservations Insights**
3. **User Reservations Insights**
4. **Reservation Sensor Insights**
5. **Data**
6. **Map**
7. **Floor Heatmap**

***

### Tab 1 — Space Usage

The headline tab summarising overall workplace activity by combining sensor and calendar utilisation in a single view.

#### Resource Count KPIs

<figure><img src="/files/tI6Oo5JS7Cgl6a0Ov8eC" alt=""><figcaption></figcaption></figure>

A row of six cards summarising the connected estate: **Total Resources**, **Rooms**, **Desks**, **Parking Spaces**, **Zones**, and **Other Resources**.

*Use it to:* validate the inventory under analysis before drawing conclusions.

#### Utilisation Trend — Sensor vs Calendar

<figure><img src="/files/CrrWOCw9AAE760UmxqUH" alt=""><figcaption></figcaption></figure>

*Line chart with Hourly / Daily / Weekly / Monthly granularity tabs.*

Plots calendar utilisation alongside sensor utilisation across the selected period.

*Use it to:* quantify the gap between booked space and used space — the foundation of any no-show and space-efficiency conversation.

#### Weekly Peak Usage

<figure><img src="/files/eQPjwbdgk01xzBHcXRe7" alt=""><figcaption></figcaption></figure>

*Bar chart.*

Shows the busiest day of the week for both sensor and calendar utilisation.

*Use it to:* align cleaning, security rotas, hospitality, and HVAC schedules with peak demand.

#### Utilisation by Resource

<figure><img src="/files/8y3E9HJIRONuUbAGika1" alt=""><figcaption></figcaption></figure>

*Horizontal bar chart, ranked.*

Lists every monitored resource by sensor utilisation percentage.

*Use it to:* identify chronically under-used or over-subscribed resources for repurposing or scaling.

#### Utilisation by Neighbourhood

<figure><img src="/files/feZXPQg6NI2JFEegaQmI" alt=""><figcaption></figcaption></figure>

*Horizontal bar chart with grouped sensor and calendar series, plus a resource-count column.*

Aggregates utilisation by neighbourhood so workplace teams can compare zones rather than individual rooms.

*Use it to:* support neighbourhood-based working strategies and team relocation decisions.

#### Utilisation by Resource Type

<figure><img src="/files/UfKQyJzf3c0ng1C5tGT7" alt=""><figcaption></figcaption></figure>

*Grouped bar chart.*

Compares sensor and calendar utilisation across resource types (rooms, desks, parking, zones).

*Use it to:* settle the perennial question — *do we need more meeting rooms or more desks?*

#### Utilisation by Resource Capacity

<figure><img src="/files/ixLL4NF2dEgRV3UKCLxh" alt=""><figcaption></figcaption></figure>

*Bar chart, excluding desks.*

Groups rooms and zones by capacity band and shows utilisation per band.

*Use it to:* uncover capacity mismatches — for example, low utilisation of large boardrooms while small huddle rooms are constantly full.

#### Calendar Utilisation vs Sensor Utilisation

<figure><img src="/files/CfsMO2TRaViu6Len2sov" alt=""><figcaption></figcaption></figure>

*Scatter plot with diagonal reference line.*

Each point represents one resource, plotted by its calendar utilisation (x-axis) against its sensor utilisation (y-axis). Resources on the diagonal are used as booked; points below the line indicate no-shows; points above indicate ad-hoc usage.

*Use it to:* spot booking-discipline outliers and resources where actual demand exceeds reservations.

#### Daily Usage Heatmap

<figure><img src="/files/fWPlPwiXmh9UCADoodmE" alt=""><figcaption></figcaption></figure>

*Calendar heatmap, month by month.*

A dense grid showing daily sensor and calendar utilisation per resource, with colour intensity reflecting usage.

*Use it to:* identify long-term patterns, holiday troughs, return-to-office trends, and resource-specific seasonality.

***

### Tab 2 — Reservations Insights

A reservation-centric view focused on counts, breakdowns, and no-show analysis.

#### Reservation Breakdown by Resource Type

<figure><img src="/files/WzPSEp8V5w422ivUK1Lo" alt=""><figcaption></figcaption></figure>

*Pie chart.*

Distribution of reservations across rooms, desks, parking, and other resource types. Tooltips reveal visited and no-show counts per slice.

#### Reservation Breakdown by Room Size

<figure><img src="/files/BkT8dRKNVdrfHdiecNFB" alt=""><figcaption></figcaption></figure>

*Pie chart.*

Reservations grouped by room capacity bands.

#### Reservations Trend

<figure><img src="/files/qxZAbpAfx4yRKnE2UeMr" alt=""><figcaption></figcaption></figure>

*Dual-line chart with Daily / Weekly / Monthly granularity tabs.*

Reservation totals plotted alongside no-shows over time, with percentage breakdowns in tooltips.

*Use it to:* monitor booking-discipline trends and the effect of policy changes.

#### Reservations Time Breakdown

<figure><img src="/files/3XpsCZXHw7AK9wv3lGmq" alt=""><figcaption></figcaption></figure>

*Stacked chart.*

Reservations distributed across time periods (morning / afternoon / all-day) to reveal preferred booking patterns.

#### Total Reservations by Resource

<figure><img src="/files/B0Vix7MiFBkPheTz9A05" alt=""><figcaption></figcaption></figure>

*Comparison chart.*

Direct side-by-side comparison of confirmed reservations and no-shows by resource.

#### Reservations by Neighbourhood

<figure><img src="/files/PQOizHJ7Lwa57QJS03Gc" alt=""><figcaption></figcaption></figure>

*Bar chart.*

Reservation activity grouped by neighbourhood.

#### Reservations by Team

<figure><img src="/files/Wwmo9umV1oMpNS6GW0h6" alt=""><figcaption></figcaption></figure>

*Bar chart.*

Reservation activity grouped by team, useful for chargeback or team-level workplace planning.

***

### Tab 3 — User Reservations Insights

Individual user behaviour. Each chart supports a Top N filter to focus on the most active bookers.

#### Reservations by User

<figure><img src="/files/0uHV10rNaF48JllospZU" alt=""><figcaption></figcaption></figure>

*Horizontal stacked bar chart.*

Total reservations per user, segmented by resource type. Tooltips show no-show counts.

#### Reservations Time Breakdown by User

<figure><img src="/files/FFuUKJCYxIupDNJWVbwM" alt=""><figcaption></figcaption></figure>

*Horizontal stacked bar chart.*

Per-user time-of-day patterns split into Morning / Afternoon / All Day.

#### Reservation Status by User

<figure><img src="/files/YEe17dxZB2xLBRysxUPo" alt=""><figcaption></figcaption></figure>

*Horizontal stacked bar chart.*

For each user, plots confirmed reservations against no-shows.

*Use it to:* surface users with persistently high no-show rates for targeted communications.

#### Reservation Duration by User

<figure><img src="/files/llcJHkNFqeTpLk0xDTyI" alt=""><figcaption></figcaption></figure>

*Horizontal stacked bar chart.*

Total hours booked per user, segmented by resource type. Useful when reservation count alone is misleading — a small number of long-day desk bookings can outweigh many short room bookings.

***

### Tab 4 — Reservation Sensor Insights

Links each reservation to the environmental conditions recorded during it.

#### Sensor Metrics Trend During Reservations

<figure><img src="/files/pcY1eY1KKRCRcZuYfhC8" alt=""><figcaption></figcaption></figure>

*Multi-panel synchronised line chart.*

One panel per sensor metric (occupancy, temperature, CO₂, humidity, noise) for a selected resource. Panels share a synchronised tooltip so all metrics align on the same point in time.

*Use it to:* understand how a single room performs environmentally when in use.

#### Reservation Sensor Pivot Table

<figure><img src="/files/WgdnVtidWLmFyfmfhsaO" alt=""><figcaption></figcaption></figure>

*Sortable data grid with colour-coded cells.*

Each row is a single reservation. Columns include organiser, resource, type, floor, building, start, end, duration, status, and the average / minimum / maximum readings for every sensor type, with status bands shown as colour gradients (dark green → green → yellow → light red → dark red).

*Use it to:* investigate complaints, build evidence for room-condition issues, or audit specific meetings. The pivot table ignores the resource filter so the full data set remains searchable.

***

### Tab 5 — Data

Detailed underlying data sets for export, audit, and offline analysis.

#### Calendar Events Table

<figure><img src="/files/cTuuftveYeHMTisX0NHd" alt=""><figcaption></figcaption></figure>

*Sortable data grid (15+ columns).*

Every calendar event in the period: organiser, resource, attendee count, duration, status, ad-hoc detection, and more.

#### Utilisation Table

<figure><img src="/files/Eev464h3igbVCwdZxfx8" alt=""><figcaption></figcaption></figure>

*Sortable data grid.*

Daily presence duration, working duration, and utilisation percentage per resource.

Both tables support sorting, pagination, and CSV export.

***

### Tab 6 — Map

#### Reservations Map View

<figure><img src="/files/5pZeSpydWRri8qFqJpyN" alt=""><figcaption></figcaption></figure>

*Interactive geographic map.*

Every building plotted on a world map, colour-coded by reservation activity and no-show rate. Hover any building to see total reservations, confirmed count, resources, and no-show rate.

*Use it to:* compare site performance across a multi-location estate.

***

### Tab 7 — Floor Heatmap

#### Reservation Floor Heatmap

<figure><img src="/files/IqR7uHjL01H0qdbiLZoO" alt=""><figcaption></figcaption></figure>

*Colour-coded overlay on an interactive 2D floor plan.*

Utilisation intensity rendered directly onto the building's floor plan, with green / amber / red bands indicating relative usage.

*Use it to:* visualise spatial patterns — under-used neighbourhoods, hot-desk clusters, and floor-level imbalance — directly on the architectural layout.

***

### Filters & Controls

All tabs share a common filter bar:

* Building, Floor, Resource, Resource Type
* Date range with presets and custom ranges
* Granularity (where applicable)
* Time zone

The Reservation Sensor Pivot table and the Bookings vs No-Shows trend ignore the resource filter to preserve search and aggregate context.

### Overview

The Space Usage and Trends dashboard delivers a complete picture of how rooms, desks, parking, and zones are reserved and used across your estate. It cross-references calendar reservations with real sensor data so you can distinguish *booked* space from *occupied* space and identify where workplace investments deliver value.

Use this dashboard to:

* Right-size the workplace portfolio
* Identify and reduce no-show waste
* Compare booking behaviour across teams, neighbourhoods, and resource types
* Provide environmental evidence for individual meetings
* Support real-estate and floor-redesign decisions with quantitative data

***

### Dashboard Structure

The dashboard is organised into seven tabs:

1. **Space Usage**
2. **Reservations Insights**
3. **User Reservations Insights**
4. **Reservation Sensor Insights**
5. **Data**
6. **Map**
7. **Floor Heatmap**

***

### Tab 1 — Space Usage

The headline tab summarising overall workplace activity by combining sensor and calendar utilisation in a single view.

#### Resource Count KPIs

A row of six cards summarising the connected estate: **Total Resources**, **Rooms**, **Desks**, **Parking Spaces**, **Zones**, and **Other Resources**.

*Use it to:* validate the inventory under analysis before drawing conclusions.

#### Utilisation Trend — Sensor vs Calendar

*Line chart with Hourly / Daily / Weekly / Monthly granularity tabs.*

Plots calendar utilisation alongside sensor utilisation across the selected period.

*Use it to:* quantify the gap between booked space and used space — the foundation of any no-show and space-efficiency conversation.

#### Weekly Peak Usage

*Bar chart.*

Shows the busiest day of the week for both sensor and calendar utilisation.

*Use it to:* align cleaning, security rotas, hospitality, and HVAC schedules with peak demand.

#### Utilisation by Resource

*Horizontal bar chart, ranked.*

Lists every monitored resource by sensor utilisation percentage.

*Use it to:* identify chronically under-used or over-subscribed resources for repurposing or scaling.

#### Utilisation by Neighbourhood

*Horizontal bar chart with grouped sensor and calendar series, plus a resource-count column.*

Aggregates utilisation by neighbourhood so workplace teams can compare zones rather than individual rooms.

*Use it to:* support neighbourhood-based working strategies and team relocation decisions.

#### Utilisation by Resource Type

*Grouped bar chart.*

Compares sensor and calendar utilisation across resource types (rooms, desks, parking, zones).

*Use it to:* settle the perennial question — *do we need more meeting rooms or more desks?*

#### Utilisation by Resource Capacity

*Bar chart, excluding desks.*

Groups rooms and zones by capacity band and shows utilisation per band.

*Use it to:* uncover capacity mismatches — for example, low utilisation of large boardrooms while small huddle rooms are constantly full.

#### Calendar Utilisation vs Sensor Utilisation

*Scatter plot with diagonal reference line.*

Each point represents one resource, plotted by its calendar utilisation (x-axis) against its sensor utilisation (y-axis). Resources on the diagonal are used as booked; points below the line indicate no-shows; points above indicate ad-hoc usage.

*Use it to:* spot booking-discipline outliers and resources where actual demand exceeds reservations.

#### Daily Usage Heatmap

*Calendar heatmap, month by month.*

A dense grid showing daily sensor and calendar utilisation per resource, with colour intensity reflecting usage.

*Use it to:* identify long-term patterns, holiday troughs, return-to-office trends, and resource-specific seasonality.

***

### Tab 2 — Reservations Insights

A reservation-centric view focused on counts, breakdowns, and no-show analysis.

#### Reservation Breakdown by Resource Type

*Pie chart.*

Distribution of reservations across rooms, desks, parking, and other resource types. Tooltips reveal visited and no-show counts per slice.

#### Reservation Breakdown by Room Size

*Pie chart.*

Reservations grouped by room capacity bands.

#### Reservations Trend

*Dual-line chart with Daily / Weekly / Monthly granularity tabs.*

Reservation totals plotted alongside no-shows over time, with percentage breakdowns in tooltips.

*Use it to:* monitor booking-discipline trends and the effect of policy changes.

#### Reservations Time Breakdown

*Stacked chart.*

Reservations distributed across time periods (morning / afternoon / all-day) to reveal preferred booking patterns.

#### Bookings vs No-Shows

*Comparison chart.*

Direct side-by-side comparison of confirmed reservations and no-shows by resource.

#### Reservations by Neighbourhood

*Bar chart.*

Reservation activity grouped by neighbourhood.

#### Reservations by Team

*Bar chart.*

Reservation activity grouped by team, useful for chargeback or team-level workplace planning.

***

### Tab 3 — User Reservations Insights

Individual user behaviour. Each chart supports a Top N filter to focus on the most active bookers.

#### Reservations by User

*Horizontal stacked bar chart.*

Total reservations per user, segmented by resource type. Tooltips show no-show counts.

#### Reservations Time Breakdown by User

*Horizontal stacked bar chart.*

Per-user time-of-day patterns split into Morning / Afternoon / All Day.

#### Reservation Status by User

*Horizontal stacked bar chart.*

For each user, plots confirmed reservations against no-shows.

*Use it to:* surface users with persistently high no-show rates for targeted communications.

#### Reservation Duration by User

*Horizontal stacked bar chart.*

Total hours booked per user, segmented by resource type. Useful when reservation count alone is misleading — a small number of long-day desk bookings can outweigh many short room bookings.

***

### Tab 4 — Reservation Sensor Insights

Links each reservation to the environmental conditions recorded during it.

#### Sensor Metrics Trend During Reservations

*Multi-panel synchronised line chart.*

One panel per sensor metric (occupancy, temperature, CO₂, humidity, noise) for a selected resource. Panels share a synchronised tooltip so all metrics align on the same point in time.

*Use it to:* understand how a single room performs environmentally when in use.

#### Reservation Sensor Pivot Table

*Sortable data grid with colour-coded cells.*

Each row is a single reservation. Columns include organiser, resource, type, floor, building, start, end, duration, status, and the average / minimum / maximum readings for every sensor type, with status bands shown as colour gradients (dark green → green → yellow → light red → dark red).

*Use it to:* investigate complaints, build evidence for room-condition issues, or audit specific meetings. The pivot table ignores the resource filter so the full data set remains searchable.

***

### Tab 5 — Data

Detailed underlying data sets for export, audit, and offline analysis.

#### Calendar Events Table

*Sortable data grid (15+ columns).*

Every calendar event in the period: organiser, resource, attendee count, duration, status, ad-hoc detection, and more.

#### Utilisation Table

*Sortable data grid.*

Daily presence duration, working duration, and utilisation percentage per resource.

Both tables support sorting, pagination, and CSV / JSON / PDF export.

***

### Tab 6 — Map

#### Reservations Map View

*Interactive geographic map.*

Every building plotted on a world map, colour-coded by reservation activity and no-show rate. Hover any building to see total reservations, confirmed count, resources, and no-show rate.

*Use it to:* compare site performance across a multi-location estate.

***

### Tab 7 — Floor Heatmap

#### Reservation Floor Heatmap

*Colour-coded overlay on an interactive 2D floor plan.*

Utilisation intensity rendered directly onto the building's floor plan, with green / amber / red bands indicating relative usage.

*Use it to:* visualise spatial patterns — under-used neighbourhoods, hot-desk clusters, and floor-level imbalance — directly on the architectural layout.

***

### Filters & Controls

All tabs share a common filter bar:

* Building, Floor, Resource, Resource Type
* Date range with presets and custom ranges
* Granularity (where applicable)
* Time zone

The Reservation Sensor Pivot table and the Bookings vs No-Shows trend ignore the resource filter to preserve search and aggregate context.


---

# 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://support.meetuma.ai/uma-knowledgebase/data-and-reporting/analytics-pro/dashboard/space-usage-and-trends.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.