Space Utilization Analytics

Space utilization analytics turns continuous occupancy signals into floor and zone heatmaps that show where people actually spend time, and where they do not. For an asset manager, the value is not a prettier dashboard. It is a defensible view of chronically underused space that can inform tenant fit-out guidance and lease renegotiation without relying on anecdotal walk-throughs alone.

The pipeline typically combines IoT presence or people-counting sensors with models that clean, aggregate, and map utilization over time. Commercial platforms in this space include Density, Siemens Enlighted, and HqO, among others. The model’s job is to map utilization patterns. The asset manager still decides whether to recommend a fit-out change, consolidate floors, or reopen commercial terms.

Useful heatmaps need more than a few days of raw counts. Typical inputs include:

• Zone- or desk-level presence, people-count, or PIR and badge-correlated occupancy streams with stable zone IDs mapped to floor plans
• Floor and suite geometry so utilization can be expressed per rentable area, not only as raw headcount
• Calendar context such as working days, holidays, and known events that would otherwise look like anomalies
• Lease and suite attribution so underuse can be tied to a tenant or common area rather than an anonymous polygon
• Optional booking or access-control signals used only as corroboration, not as a substitute for sensor history

When sensor history is too thin, coverage is sparse, clocks drift across devices, or zone boundaries changed mid-period without a clean remap, the system should return empty output rather than a heatmap. A half-filled map invites false confidence. Empty is the correct answer until the observation window and coverage meet the policy you set for that asset.

Processing usually follows a fixed sequence. First, raw events are de-duplicated and aligned to a common time grid. Short spikes from cleaning crews or deliveries are filtered or labeled so they do not inflate peak utilization. Second, occupancy is aggregated by zone and by hour, day, and week, then normalized by zone area so a large lobby is not compared unfairly to a small focus room. Third, the model scores chronic underuse: low utilization that persists across comparable periods, not a single quiet Friday.

Output is typically a floor plan overlay with intensity by zone, plus ranked lists of underused and contested spaces. Peak, average, and distribution metrics matter together. A conference suite that sits empty most days but spikes twice a week needs a different conversation from a bank of desks that never fill. The heatmap is evidence of pattern, not a verdict on tenant performance.

Human review remains mandatory before any commercial action. Lease language, service-level commitments, and relationship context sit outside the model. The asset manager reviews the map, checks known exceptions (renovation, hybrid policy pilots, temporary vacancies), and only then decides whether to pursue fit-out advice or renegotiation.

Start with chronic underuse, not one-off lows. Ask which zones stay below your utilization threshold across several comparable weeks, and whether those zones are tenant-controlled, shared, or landlord-managed. Shared amenities that never fill may support reprogramming. Tenant demised areas that stay empty may support a conversation about rightsizing, sublease support, or redesign toward denser collaboration space, depending on the lease.

Fit-out decisions benefit from pairing heatmaps with qualitative intent. If focus rooms are empty while open collaboration zones overflow, the issue may be layout, not headcount. If entire floors show sustained low density after return-to-office policies stabilized, consolidation or partial floor release may be on the table. The model surfaces where; the asset manager and tenant decide what.

Lease renegotiation uses the same maps as shared evidence, not as an automatic rent adjustment. Bring the observation window, coverage notes, and any empty-output periods to the table so both sides understand what was measured. Avoid treating sensor-derived density as a proxy for productivity or lease compliance unless the contract explicitly defines that link.

Cross-check energy and comfort signals when they exist. Persistent underuse alongside high HVAC runtime can point to schedule misalignment, which is often cheaper to fix than a physical remodel. Related work on energy and ESG monitoring sits naturally next to utilization reviews.

A practical cadence for most multi-tenant assets is weekly automated refresh with a monthly asset-manager review, plus ad hoc pulls ahead of lease events or fit-out scopes. Weekly maps catch drift; monthly reviews prevent reacting to noise. Before major decisions, re-run the pipeline with an explicit observation window and confirm that no zone remap or sensor outage invalidated the period.

Governance should record who approved acting on a heatmap, which suites were in scope, and whether the model returned empty for any floor. Keep tenant-facing exports limited to agreed metrics. Occupancy heatmaps can reveal patterns tenants consider sensitive; treat them as operational intelligence with access controls, not as public building marketing.

When tenants ask about space or amenities in natural language, route those questions to a tenant query channel rather than improvising from a raw map. Utilization analytics informs the landlord side of space strategy; day-to-day tenant answers need a separate, permissioned path.

• 24/7 Tenant Query Agent
• ESG & Energy Consumption Monitor
• Move-In Condition Documentation