The room calendar is full. People say they cannot find space. Yet a walk around the office reveals several empty rooms.
That observation is worth investigating before approving more meeting space. Bookings describe intent. Usage data can help explain what happened, provided the system measures the right thing and the data is complete enough to support a decision.
Define the numbers before comparing them
Booked time is the time reserved on a calendar. Occupied time is an observation from a supported sensing or usage system. Neither automatically tells you how many people attended, whether the equipment worked, or whether the meeting was productive.
Check how each system defines usage. A device in a call, an active presentation, and a detected person are different signals. If the measures are not comparable, a chart can make a room look empty simply because its particular activity was not captured.
Check what your installed platform supports
Q-SYS Reflect’s October 2026 release notes describe booking-versus-usage analysis and occupancy rankings. They also identify a material limitation: Space Usage supports certain RMS and AiO Bar systems and does not currently support Q-SYS Cores. Having Q-SYS equipment somewhere in a room does not establish that the room supplies this data.
Crestron’s October 14 XiO Cloud documentation update includes occupancy tiles and capacity alerts. Verify supported devices, sensing, configuration, and subscriptions for your own deployment before planning around any dashboard feature.
Build a coverage list showing which rooms report which measures. Mark missing data as missing. Do not turn an offline sensor or an unmapped room into zero utilization.
Compare rooms that serve similar work
Use a representative period that includes normal working patterns. One holiday week or an unusually large event can distort the picture. Check room mapping, business hours, time zones, and calendar connections before drawing conclusions.
Compare similar room types and capacities. A training room may have fewer bookings but support sessions that cannot happen in a small huddle room. Look for repeated patterns, then ask the teams using those spaces what explains them.
Bring support history into the discussion
An avoided room may be unreliable, uncomfortable, difficult to find, or poorly matched to the meeting. Usage data alone cannot select among those explanations.
Review support tickets, failed joins, and reported audio or display problems alongside booking patterns. Ask whether staff reserve a second room as insurance or move a meeting after an equipment failure. Those behaviors can make demand appear larger than it is.
| Pattern to investigate | Possible next step |
|---|---|
| Frequent reservations with little observed use | Review booking habits and cancellation practices |
| One room avoided despite demand nearby | Inspect reliability, usability, and suitability |
| Consistent occupancy beyond available capacity | Evaluate additional or differently sized space |
| Large gaps in sensing or reporting | Improve the evidence before approving a major change |
Make a room decision, not an employee scorecard
Use the data to improve space and service. Agree with the responsible teams on access, retention, and appropriate reporting. Aggregate room-level patterns can inform a budget conversation without turning the project into individual employee monitoring.
Document the decision, its supporting evidence, and what remains uncertain. Then measure again after the change. If booking rules improve but room complaints persist, the original explanation may have been incomplete.
Our guides to AV support evidence and room scheduling panels provide useful context. VIcom can help establish a practical room-data baseline using the systems you already have and identify where additional evidence would change the decision.
Connect with VIcom by filling out the form below.
