How to Evaluate an Occupancy Analytics Platform for Smart Buildings

Meet Butlr

Discover what spatial intelligence can do for you.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

An occupancy analytics platform collects and analyzes data about the presence, movement, and behavior of people in physical spaces, combining sensors, edge processing, cloud analytics, and user interfaces to present metrics such as headcount, dwell time, traffic flows, and space utilization.

Key terms

Ambient intelligence: systems that sense and respond to people in an unobtrusive way.
Thermal sensing / camera-free sensing: detection methods that measure heat signatures rather than capturing images, often used to protect privacy.
Real-time analytics: processing and delivering insights with minimal delay.

Occupancy analytics supports operational goals by providing data-driven insights that improve efficiency, occupant experience, and safety.

Operational efficiency: optimize HVAC, lighting, and cleaning schedules based on actual usage.
Space optimization: right-size workspaces, meeting rooms, and shared resources.
Health and safety: manage density for compliance with safety guidelines.
Cost savings: lower energy and real estate costs through data-driven decisions.
Experience improvements: reduce friction and improve services, for example by finding available workspace.

Understanding these outcomes helps you frame evaluation criteria around measurable business value.

When comparing platforms, evaluate technical, operational, privacy, and business dimensions. Use the following criteria and questions to guide selection.

1. Sensor technology and accuracy

Evaluate sensing modality and validated detection performance.

What sensing modality is used (thermal, PIR, Wi‑Fi/Bluetooth, camera-based, CO2)?
What is the detection accuracy for headcount and presence? Ask for independent validation or error margins.
How does the system handle occlusion, groups, and overlapping bodies?
What is the minimum and maximum detection range and field of view?

Why it matters: Higher raw accuracy reduces manual correction and builds trust in downstream insights.

2. Privacy and anonymity

Confirm privacy-preserving design and configurable data handling.

Are there camera-free options or de-identified data processing?
Is anonymization done on-device or at the edge to avoid raw personal data transfer?
Are data retention policies clear and configurable?

Why it matters: Privacy-preserving sensing lowers legal and cultural barriers to deployment.

3. Real-time capability and latency

Decide if you need immediate vs aggregated insights and verify latency.

What is the data sample rate and system latency?
Are there event-driven alerts for thresholds, e.g., occupancy exceeded?
Can the platform stream real-time data to building systems or third-party apps?

Why it matters: Real-time data enables responsive control of systems like HVAC and signage.

4. Analytics, reporting, and actionable outputs

Assess built-in dashboards, advanced analytics, anomaly detection, and export capabilities.

Are dashboards customizable for utilization, trends, and peak times?
Does the platform provide dwell time, transition paths, and peak density analytics?
Are there anomaly detection and automated recommendations?
Are exports and APIs available for BI or CAFM integration?

Why it matters: Rich analytics convert observations into decisions and quantify ROI.

5. Integration and interoperability

Ensure the platform fits your ecosystem and supports common protocols.

Which protocols and connectors are supported (BACnet, Modbus, MQTT, REST)?
Is it compatible with building automation, booking systems, and analytics platforms?
Does it support SSO and identity management?

Why it matters: Seamless integration avoids silos and enables coordinated automation.

6. Scalability and coverage

Consider scale, sensor density, and limits on site sizes or data streams.

How easily can the system scale across floors, buildings, or campuses?
What sensor density is required for reliable metrics?
Are there limitations on number of sensors or simultaneous streams?

Why it matters: Scalability affects total cost, deployment timeline, and long-term viability.

7. Deployment approach and maintenance

Assess installation complexity, power needs, firmware updates, and SLAs.

Installation: wireless vs wired, ceiling mount vs wall.
Power requirements and battery life for wireless sensors.
Support for remote firmware updates, self-calibration, and health monitoring.
Service-level agreements and warranty terms.

Why it matters: Low-friction deployment and minimal maintenance reduce total cost of ownership.

8. Security and compliance

Verify encryption, access controls, audit logs, and relevant certifications.

Is data encrypted in transit and at rest?
Are there access controls, audit logs, and role-based permissions?
Does the vendor comply with industry standards and certifications?

Why it matters: Security reduces risk and helps meet regulatory obligations.

9. Cost model and ROI

Understand pricing, payback timelines, and hidden costs.

Pricing structure: hardware, subscription, per-sensor fees, or tiered analytics.
Expected payback from energy savings, reduced real estate, or efficiencies.
Hidden costs: cabling, mounting, commissioning, and support.

Why it matters: A realistic ROI assessment helps prioritize investments.

10. Vendor expertise and references

Evaluate vendor track record, case studies, and availability of professional services.

Industry experience and similar building projects.
Case studies and reference deployments.
Availability of site surveys, professional services, and change management support.

Why it matters: Experienced vendors help avoid pitfalls and accelerate outcomes.

Actionable metrics validate platform usefulness and should align with your reporting needs.

Real-time headcount and occupancy percentage per zone.
Peak occupancy times and usage patterns.
Average dwell time and repeat visits.
Space utilization heatmaps and transition flows.
Utilization of desks, meeting rooms, and shared amenities.
Alerts for over-occupancy or unusual patterns.

Ask vendors for sample dashboards and data exports that match your reporting needs.

A pilot reduces risk and validates vendor claims in your environment. Follow a structured approach to test performance, integration, and business impact.

Define objectives: choose 3–5 measurable outcomes, e.g., reduce HVAC runtime 15%.
Select representative spaces with varied room types and traffic patterns.
Baseline measurement: collect existing usage and energy data for comparison.
Deploy sensors and configure the platform for your metrics.
Validate data: compare platform counts with manual observations or turnstile logs.
Run the pilot for at least 4–8 weeks to capture variability.
Assess results against objectives and decide on scale-up; document lessons learned for sensor placement, reporting, and integration.

Use this checklist in vendor conversations to probe technology, integration, deployment, and business outcomes.

How does your sensing technology work and what are its privacy implications?
What accuracy and coverage can you guarantee in spaces like ours?
Can you integrate with our BMS and facility software? Which protocols do you support?
What real-time outputs and alerts do you provide?
What is the deployment timeline and typical disruption level?
How are security and data governance handled?
What is the total cost of ownership and expected ROI?
Can you provide customer references and case studies for similar buildings?
Do you offer pilots and what are their terms?

Some providers focus on ambient intelligence using heat-based, camera-free sensing. These systems detect human presence by thermal signatures rather than capturing images, which can be useful when privacy and anonymity are priorities.

When evaluating such offerings, verify independent accuracy tests and understand how on-device processing and data retention are handled. For example, Butlr offers a heat-based, camera-free platform that focuses on anonymous, real-time occupancy and activity insights; ask vendors for similar implementation details and validation data.

Before signing a contract, confirm the solution meets technical, privacy, integration, and business requirements.

The platform meets your accuracy, privacy, and latency requirements.
Integration points and data formats align with your systems.
Pilot results match vendor claims and business goals.
Costs, support terms, and SLAs are transparent and acceptable.
Security, compliance, and data governance policies are satisfactory.

Assess vendor competence to ensure long-term success and smooth deployments.

Industry experience and a track record in similar building types.
Case studies, reference deployments, and measurable outcomes.
Availability of professional services for site surveys, commissioning, and change management.

Evaluating an occupancy analytics platform requires balancing technical performance, privacy, integration, and business value. Start with clear objectives, run a representative pilot, insist on measurable outcomes, and validate vendor claims. With the right criteria and validation, occupancy analytics can unlock energy savings, better space utilization, and improved occupant experience in your smart building program.