The Desks page in Insights shows how your desk spaces are being used. Instead of stopping at floor-level averages, it breaks down to areas and desks, so you can move from "Floor 3 is low" to "these two areas have near-zero occupancy while the rest is overbooked," and act on that directly.
Desks insights
In the top navigation, click Insights. Then select Spaces in the left sidebar, followed by Desks. The page opens with your full building loaded, grouped by area by default. At the top of the page, four summary cards give you an instant read on the selected period. Below them, an expandable table lets you drill from floor level down to individual desks.
Both the cards and the table draw from two independent inputs: booking data from workspace reservations and occupancy data from sensors. It is worth knowing that either column can show 0% or be empty, depending on how your spaces are set up. This is expected behavior, not missing data.
A few common scenarios:
If an area uses area-level booking rather than individual desk booking, each desk in that area will show 0% on the booking column. The booking is registered on the area, not the desk.
If your building uses (people count) sensors on area-level rather than per-desk sensors, occupancy at the individual desk level will be empty. The data exists at area level but cannot be broken down further.
Keeping this in mind will help you read the numbers with confidence.
Summary cards
Total areas: The number of desk areas in your building that have at least one desk and at least one data record in the selected date range. When filters are active, this reflects the filtered count. The search bar does not affect this number; only the structured filters (policy, capacity, amenities, activities) do.
Total desks: The total desk count across all areas in scope. Desk count is based on the seat capacity configured in Mapiq, not on live sensor readings. When filters are active, this reflects the desks in the filtered areas.
Desk booking rate: The average booking utilization across all areas that have booking data, weighted by desk count. A larger area contributes more to this figure than a smaller one. Areas without booking data are excluded entirely.
Desk occupancy rate: The same calculation applied to sensor data. Only areas with sensor readings are included.
💡 Both rates are weighted by desk count. An area with 40 desks carries more weight than one with 4.
The table
The table is structured as floors, then areas, then individual desks. You can expand any floor to see its areas, and any area to see its desks. Each row shows:
Name: the space name as set in Mapiq
Capacity: the desk count for the area, or 1 for a single desk
Location: the floor
Policy: the booking policy (Desk booking, Area booking, or Ad hoc use)
Bookings: booking use as a bar and percentage
Occupancy: sensor use as a bar and percentage
Floors are ordered top to bottom by their physical level. Both columns are shown when data exists. If only one source has data for a space, that row still appears with the available column filled and the other blank.
💡 When you filter the table, parent row figures recalculate using only the filtered rows. If you filter out two of four desks in an area, the area rate reflects the two remaining desks, not the full area.
How the rates are calculated
Bookings is the share of desk-hours, during your set office hours, covered by a confirmed booking. It is calculated per desk, then rolled up to area and floor level using a desk-count-weighted average.
Occupancy is the share of hours, during set office hours, where a sensor detected someone at a desk or in an area. It uses the same rollup logic. For areas with (people count) sensors configured to area instead of per-desk sensors, Mapiq converts the reading to a ratio: people detected divided by seat count. These areas show up in the table with sensor data just like per-desk-sensor areas.
Filtering and searching
Search: The search bar at the top of the table filters rows by name at all levels. It stays active when you change the grouping and is included in shared links.
Grouping: The
Group by areabutton in the filter bar lets you switch between no grouping, group by area, or group by floor and area.Column filters: Click the filter icon on a column header to filter by that column. The
Policycolumn filter lets you show only spaces with a specific booking policy.Filter panel: Click
Filtersin the filter bar to open the full filter panel. Here you can filter by:Policy: Area booking, Desk booking, or Ad hoc use
Capacity: a min and max desk count
Amenities: equipment on the space (adjustable desk, dual monitor, locker, and more)
Activities: activity types set for areas (Focus, Collaboration, and more)
When filters are active, a Reset filters button clears them all in one click.
Sorting: Click any column header to sort. Rows with no data for that column always appear at the bottom.
💡 When you search for specific areas or desks, Mapiq indicates if the area or desk changed within the period your filtering on. For example changes in capacity have their effect on the calculations.
Column visibility
Use the All columns toggle in the filter bar to show or hide columns. Your choices are saved in the URL and included in any shared link.
Exporting to CSV
Click Export in the top right to download the table as a CSV. The file includes the active date range, office hours, and any active filters, so it makes sense to anyone you send it to.
Sharing a filtered view
The Share button in the top right creates a link that captures the full state of the page: filters, sort order, column visibility, grouping, and the search query. Anyone who opens the link sees the exact same view, with no setup needed.
Behind the scenes
Desk-count-weighted averages — floor and area rows use a weighted average, not a simple one. Each child row is weighted by its desk count, so a 40-desk area has more impact on the parent row than a 4-desk area. The parent always reflects the actual mix of spaces beneath it.
Two independent data sources — the page runs separate queries for booking and sensor data, then merges the results per area and desk. A row always appears even when only one source has data.
People count sensor support — for areas with a people count sensor instead of per-desk sensors, Mapiq converts the reading to a ratio (people detected / seat capacity × 100%). These areas appear in the table with sensor data the same way per-desk-sensor areas do.
Virtualized rendering — only the rows in view are rendered at any time. This keeps the page fast in large buildings with hundreds of desks.
Filter-reactive rollups — when filters remove rows, all parent row figures recalculate from the remaining rows only. The numbers always reflect the filtered set, not the full unfiltered total.
💬 Need More Help?
If you'd like some extra assistance, reach out via the Messenger (question mark in the corner) and chat with our support team, or send us an email at [email protected].
We're always ready to help! 😉