The most-out-of-date number in corporate property is the badge-swipe utilisation report. It was already a bad proxy when everyone came in five days a week (it counts entry, not occupancy) and it became actively misleading when hybrid work fragmented attendance across the week. The number a property team needs in 2026 is occupancy: how many people are on the floor, per zone, per hour, anonymously. Not who came in. How full it is.
We don't have a corporate pilot running yet. This post is about how we'd configure one.
01 · WHAT A FOUR-WEEK PILOT WOULD COVERWhat a four-week pilot would cover
The smallest useful corporate deployment is one floor. Six zones is a reasonable cut: open-plan north, open-plan south, two meeting-room banks, the social area, the kitchen. One edge sensor per zone, emitting anonymous counts per second. No faces, no badge linking, no per-person tracking.
After four weeks of trailing data, the report would surface:
- Anchor-day occupancy curves: typically Tuesdays and Wednesdays peak; Mondays and Fridays don't.
- Zone-level utilisation: meeting rooms sized wrong for the team mix show up immediately.
- Catering-window pressure: kitchen density between 11:45 and 12:45 reveals whether staggering is needed.
None of those numbers would come from a badge log. None of them would require identifying anyone.
02 · WHAT A PROPERTY TEAM WOULD DO WITH THE NUMBERSWhat a property team would do with the numbers
Three operational moves would come out of a four-week deployment:
- Right-size the schedule. Quiet days don't need full HVAC, full lighting, full reception cover. The data lets the property team make the case to facilities: the load is the load, not the policy.
- Re-program the under-used rooms. Small meeting rooms that show 11% utilisation aren't earning their footprint. The data argues for a re-fit-out, and designing the space around how people actually use it is how the re-fit pays off.
- Re-time the catering. A kitchen that pegs at noon, three days a week, is a service-design problem, not a catering one. We covered the measurement side in the cafeteria and lobby occupancy monitoring deep dive.
None of those moves are HR decisions. They are property decisions, made from property data.
03 · THE REASON IT ISN'T A BADGE LOGThe reason it isn't a badge log
Badge logs are a temptation because they're already in place. They tell you who entered the building. They are silent on three things property cares about:
- Whether anyone stayed. A badge swipe at 9:01am doesn't say much about a 9:30 standup.
- Where they were on the floor. Floor north or south, kitchen or meeting room: the badge has no opinion.
- The actual density, hour by hour. A badge gives a person-count by gate. Occupancy gives a person-count by space.
The privacy answer matters here too. A badge-derived utilisation report is HR-adjacent: it can be back-tracked to individuals. An anonymous occupancy report is property-only; it can't be back-tracked to anyone, because the architecture never produced an identifier.
04 · THE CONVERSATION WE'D EXPECT WITH THE CFOThe conversation we'd expect with the CFO
The conversation isn't "we should downsize the floor". It is "we should operate the floor for its actual load profile". That's a different conversation, with a different decision tree:
- Compress the schedule on quiet days, not the footprint.
- Re-fit-out under-used zones to higher-frequency uses.
- Hold the floor for the busy days, as the busy days are still busy.
05 · WE'RE LOOKING FOR THE FIRST CORPORATE PILOTWe're looking for the first corporate pilot
If your property portfolio's utilisation number is still a badge swipe, talk to us about a pilot.