> 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/occupancy.md).
# Occupancy 👥
### Overview
The Occupancy dashboard answers a simple question: *how many people are actually using the workplace, where, and when?* It uses presence and people-counting sensors so the figures reflect physical attendance rather than calendar reservations.
Use this dashboard to:
* Track real attendance against capacity
* Understand peak demand by hour, day, and resource
* Identify under-used areas suitable for consolidation
* Validate booking behaviour against actual occupancy
* Inform return-to-office and hybrid-working decisions
***
### Dashboard Structure
The dashboard is organised into four tabs:
1. **Monitoring**
2. **Data**
3. **Map**
4. **Floor Heatmap**
***
### Tab 1 — Monitoring
#### People Count Overview
*Compact KPI card.*
Average people count for the period with a delta against the previous period.
#### People Count Trend
*Line chart with Hourly / Daily / Weekly granularity tabs.*
Occupancy over time, with optional reference bands marking comfort and capacity thresholds.
*Use it to:* analyse return-to-office momentum and identify periods of unusually low or high attendance.
#### Average People Count by Resource
*Horizontal bar chart, ranked.*
Average occupancy per resource, ordered from most to least occupied.
*Use it to:* identify chronically empty or chronically full rooms, desks, or zones.
#### Average People Count by Weekday
*Bar chart.*
Average occupancy by day of the week.
*Use it to:* understand the hybrid-working pattern of the building — typically Tuesday / Wednesday / Thursday peaks.
#### Capacity vs Attendee
*Grouped bar chart.*
For each resource, displays its capacity alongside the actual attendee count.
*Use it to:* identify mismatches — large rooms used by small groups, or undersized rooms regularly overflowing.
***
### Tab 2 — Data
#### People Count Table
*Sortable data grid.*
Minimum, maximum, and average occupancy readings per resource, with resource type and configured capacity. Supports CSV, JSON, and PDF export.
#### Utilisation Table
*Sortable data grid.*
Presence duration and working-hours utilisation metrics per resource.
***
### Tab 3 — Map
#### Sensor Map View
*Interactive geographic map.*
Buildings plotted on a world map, colour-coded by occupancy. Hover any building to see live occupancy, capacity, and resource counts.
*Use it to:* compare attendance trends across multiple sites at a glance.
***
### Tab 4 — Floor Heatmap
#### Occupancy Floor Heatmap
*Colour-coded overlay on an interactive 2D floor plan.*
Every monitored resource on the floor is rendered as a heat point with a colour band:
* 🟢 Green — ≤ 50% of capacity
* 🟡 Amber — 50–80% of capacity
* 🔴 Red — above 80% of capacity
Desks default to a capacity of one when no explicit capacity is configured.
*Use it to:* visualise where in the floor plan demand concentrates — essential for redesign, neighbourhood planning, and consolidation projects.
***
### Filters & Controls
* Building, Floor, Resource, Resource Type
* Date range with presets and custom ranges
* Granularity tabs on trend chart
### Overview
The Occupancy dashboard answers a simple question: *how many people are actually using the workplace, where, and when?* It uses presence and people-counting sensors so the figures reflect physical attendance rather than calendar reservations.
Use this dashboard to:
* Track real attendance against capacity
* Understand peak demand by hour, day, and resource
* Identify under-used areas suitable for consolidation
* Validate booking behaviour against actual occupancy
* Inform return-to-office and hybrid-working decisions
***
### Dashboard Structure
The dashboard is organised into four tabs:
1. **Monitoring**
2. **Data**
3. **Map**
4. **Floor Heatmap**
***
### Tab 1 — Monitoring
#### People Count Overview
*Compact KPI card.*
Average people count for the period with a delta against the previous period.
#### People Count Trend
*Line chart with Hourly / Daily / Weekly granularity tabs.*
Occupancy over time, with optional reference bands marking comfort and capacity thresholds.
*Use it to:* analyse return-to-office momentum and identify periods of unusually low or high attendance.
#### Average People Count by Resource
*Horizontal bar chart, ranked.*
Average occupancy per resource, ordered from most to least occupied.
*Use it to:* identify chronically empty or chronically full rooms, desks, or zones.
#### Average People Count by Weekday
*Bar chart.*
Average occupancy by day of the week.
*Use it to:* understand the hybrid-working pattern of the building — typically Tuesday / Wednesday / Thursday peaks.
#### Capacity vs Attendee
*Grouped bar chart.*
For each resource, displays its capacity alongside the actual attendee count.
*Use it to:* identify mismatches — large rooms used by small groups, or undersized rooms regularly overflowing.
***
### Tab 2 — Data
#### People Count Table
*Sortable data grid.*
Minimum, maximum, and average occupancy readings per resource, with resource type and configured capacity. Supports CSV, JSON, and PDF export.
#### Utilisation Table
*Sortable data grid.*
Presence duration and working-hours utilisation metrics per resource.
***
### Tab 3 — Map
#### Sensor Map View
*Interactive geographic map.*
Buildings plotted on a world map, colour-coded by occupancy. Hover any building to see live occupancy, capacity, and resource counts.
*Use it to:* compare attendance trends across multiple sites at a glance.
***
### Tab 4 — Floor Heatmap
#### Occupancy Floor Heatmap
*Colour-coded overlay on an interactive 2D floor plan.*
Every monitored resource on the floor is rendered as a heat point with a colour band:
* 🟢 Green — ≤ 50% of capacity
* 🟡 Amber — 50–80% of capacity
* 🔴 Red — above 80% of capacity
Desks default to a capacity of one when no explicit capacity is configured.
*Use it to:* visualise where in the floor plan demand concentrates — essential for redesign, neighbourhood planning, and consolidation projects.
***
### Filters & Controls
* Building, Floor, Resource, Resource Type
* Date range with presets and custom ranges
* Granularity tabs on trend chart
---
# 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/occupancy.md?ask=&goal=
```
`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.