Occupancy and estate data that facilities can act on.

The KPI is agreement between presence and reservation systems. Ghost occupancy destroys soft-services planning.

See space & occupancy.

Open plan, meeting rooms and labs need different sensing. We pick for the building you have — not a catalogue demo.

Prefer anonymised counts unless a named use case demands identity. DPOs and works councils are stakeholders from week one.

Week 1–2: agree KPIs with FM and soft services. Week 3–6: pilot one floorplate with booking-system agreement as the headline metric. Week 7–12: decide scale, retention, and whether visitor wayfinding stays separate. Hardware choice follows the building you have — open plan, labs and meeting rooms need different sensing.

Peak and trough occupancy by floorplate, agreement between sensors and booking systems, soft-services load that tracks reality, and meeting-room honesty without a vanity map. Average occupancy lies — we design for the days that break your cleaning and catering model.

Integration into the IWMS you already run beats inventing a parallel estate stack. See space & occupancy.

Prefer anonymised counts unless a named use case demands identity. DPOs and works councils are in the room early. Wayfinding for visitors stays separable from staff analytics unless governance explicitly allows one stack.

Pilots live on one wing or floor with soft-services owners at the table — not a sensor demo that never reaches the FM operating rhythm.

Facilities teams need occupancy and wayfinding they can act on — cleaning, energy, space planning — without creating a surveillance culture. Criteria:

• Decision-grade occupancy — zone or desk signals tied to cleaning, HVAC or booking systems you already run.
• Radio fit to floorplate — BLE, anonymous people-counting or badge RTLS chosen for the decision, not vendor preference.
• Privacy by default — aggregate first; identifiable staff location only with purpose and notice.
• Estate operations ownership — KPIs facilities can run weekly without an IT project for every report.
• TCO across buildings — anchors, batteries, licences and multi-site expansion priced honestly.

Workplace vendors sell soft sensors and apps. RTLS vendors sell badge precision. Facilities should buy the lightest locating layer that moves estate KPIs.

• Desk sensors installed without an agreement on what 'good occupancy' means for cleaning and leasing.
• Badge tracking for space analytics when anonymous counts would suffice — privacy blowback.
• Data trapped in a vendor portal with no feed to CAFM/IWMS.
• Pilot on one quiet floor that does not represent peak density.
• No change plan for occupants — opt-out confusion and trust damage.

• Can we start with anonymous occupancy and upgrade later without rip-and-replace?
• Which CAFM/IWMS/BMS integrations are production-proven — evidence please?
• What is five-year cost per floor including batteries and licences?
• How do you prevent re-identification of individuals from 'anonymous' feeds?
• Who supports sensors and firmware across our multi-building estate?

TRACIO advises on locating for workplace and industrial facilities without selling sensors, badges or AMR fleets. We help you pick the minimum viable radio, wire privacy defaults, and integrate to the estate systems you already trust.

Soft-sensor and workplace-experience vendors pitch desk occupancy, booking analytics and employee apps. Industrial RTLS vendors pitch badge-grade precision. Facilities usually need decision-grade occupancy for cleaning, energy and space — often achievable with anonymous counts or zone BLE without identifying every person.

Over-collecting identity creates works-council and trust problems without improving HVAC setpoints. Under-integrating creates pretty portals that never reach CAFM, IWMS or BMS. Demand production integrations, multi-building TCO and a path from anonymous to identifiable only when a named purpose appears.

Pilot on floors that represent peak density and mixed tenant behaviour. Quiet executive floors are poor proof for a tower.

• Agree the estate decisions occupancy will change (cleaning zones, meeting-room rightsizing, energy setbacks).
• Choose the lightest radio that feeds those decisions.
• Wire privacy defaults and occupant communication before install.
• Connect to CAFM/IWMS/BMS; retire duplicate spreadsheets.
• Review weekly KPIs facilities owns — not a vendor customer-success deck.

TRACIO stays independent of sensor and badge vendors so the plan stays estate-led.

First, confirm anonymous occupancy cannot meet the estate decision — if it can, do not buy identifiable locating. Second, require a production feed into CAFM or IWMS within the pilot window, not a roadmap slide. Third, demand five-year cost per floor with battery and licence escalators disclosed. Independent advice exists to keep those checks honest when vendors and SIs are optimising for footprint.

Week 1–2: agree KPIs with FM and soft services. Week 3–6: pilot one floorplate with booking-system agreement as the headline metric. Week 7–12: decide scale, retention, and whether visitor wayfinding stays separate. Hardware choice follows the building you have — open plan, labs and meeting rooms need different sensing.

Peak and trough occupancy by floorplate, agreement between sensors and booking systems, soft-services load that tracks reality, and meeting-room honesty without a vanity map. Average occupancy lies — we design for the days that break your cleaning and catering model.

Integration into the IWMS you already run beats inventing a parallel estate stack. See space & occupancy.

Prefer anonymised counts unless a named use case demands identity. DPOs and works councils are in the room early. Wayfinding for visitors stays separable from staff analytics unless governance explicitly allows one stack.

Pilots live on one wing or floor with soft-services owners at the table — not a sensor demo that never reaches the FM operating rhythm.

Facilities teams need occupancy and wayfinding they can act on — cleaning, energy, space planning — without creating a surveillance culture. Criteria:

• Decision-grade occupancy — zone or desk signals tied to cleaning, HVAC or booking systems you already run.
• Radio fit to floorplate — BLE, anonymous people-counting or badge RTLS chosen for the decision, not vendor preference.
• Privacy by default — aggregate first; identifiable staff location only with purpose and notice.
• Estate operations ownership — KPIs facilities can run weekly without an IT project for every report.
• TCO across buildings — anchors, batteries, licences and multi-site expansion priced honestly.

Workplace vendors sell soft sensors and apps. RTLS vendors sell badge precision. Facilities should buy the lightest locating layer that moves estate KPIs.

• Desk sensors installed without an agreement on what 'good occupancy' means for cleaning and leasing.
• Badge tracking for space analytics when anonymous counts would suffice — privacy blowback.
• Data trapped in a vendor portal with no feed to CAFM/IWMS.
• Pilot on one quiet floor that does not represent peak density.
• No change plan for occupants — opt-out confusion and trust damage.

• Can we start with anonymous occupancy and upgrade later without rip-and-replace?
• Which CAFM/IWMS/BMS integrations are production-proven — evidence please?
• What is five-year cost per floor including batteries and licences?
• How do you prevent re-identification of individuals from 'anonymous' feeds?
• Who supports sensors and firmware across our multi-building estate?

TRACIO advises on locating for workplace and industrial facilities without selling sensors, badges or AMR fleets. We help you pick the minimum viable radio, wire privacy defaults, and integrate to the estate systems you already trust.

Soft-sensor and workplace-experience vendors pitch desk occupancy, booking analytics and employee apps. Industrial RTLS vendors pitch badge-grade precision. Facilities usually need decision-grade occupancy for cleaning, energy and space — often achievable with anonymous counts or zone BLE without identifying every person.

Over-collecting identity creates works-council and trust problems without improving HVAC setpoints. Under-integrating creates pretty portals that never reach CAFM, IWMS or BMS. Demand production integrations, multi-building TCO and a path from anonymous to identifiable only when a named purpose appears.

Pilot on floors that represent peak density and mixed tenant behaviour. Quiet executive floors are poor proof for a tower.

• Agree the estate decisions occupancy will change (cleaning zones, meeting-room rightsizing, energy setbacks).
• Choose the lightest radio that feeds those decisions.
• Wire privacy defaults and occupant communication before install.
• Connect to CAFM/IWMS/BMS; retire duplicate spreadsheets.
• Review weekly KPIs facilities owns — not a vendor customer-success deck.

TRACIO stays independent of sensor and badge vendors so the plan stays estate-led.

First, confirm anonymous occupancy cannot meet the estate decision — if it can, do not buy identifiable locating. Second, require a production feed into CAFM or IWMS within the pilot window, not a roadmap slide. Third, demand five-year cost per floor with battery and licence escalators disclosed. Independent advice exists to keep those checks honest when vendors and SIs are optimising for footprint.