Most organisations running a hybrid mandate have two datasets and quietly substitute one for the other.
The first is occupancy: badge swipes, desk bookings, wifi associations, maybe sensors. The second is work: what people did, how fragmented their time was, what shipped. The first is easy to get, arrives daily, and has a number that goes up. The second is harder.
So the first becomes the metric, and the question drifts from "is this working" to "are people complying".
What occupancy is genuinely good for
This is a real dataset with real uses, and it is worth being precise about them because the misuse tends to discredit the whole thing.
Facilities planning is the obvious one and the strongest. How much space do you actually need, which floors are consistently empty, is the ratio of desks to people right, should that office exist at all. These are expensive decisions and occupancy data answers them properly.
Operational questions follow: whether the booking system reflects reality, where the meeting-room shortage actually is, how catering and cleaning should be scheduled, which days are peak so facilities can staff them.
All of that is legitimate, useful, and about the building. None of it is about whether the work is going well.
The substitution error
The slide happens because a mandate needs a success metric and occupancy is the only number available in week one.
But consider what badge data cannot see. Whether the person spent the day in back-to-back video calls with colleagues who came in on different days. Whether they got a single uninterrupted hour. Whether the commute cost them two hours and the collaboration gained them twenty minutes. Whether anything shipped.
A team can hit 100% of its office-day target and have a worse week than the one before, and the occupancy dashboard will show green. That is not a measurement gap, it is measuring a different thing — and the return-to-office evidence is thin enough that assuming presence implies benefit is not safe.
The secondary cost is behavioural. Once people understand that presence is the measure, presence is what they produce: come in, badge in, find a desk, do the same work they would have done at home, resent the commute. Compliance rises and nothing else does. The hybrid policy piece covers designing around this rather than into it.
Coordinated days are the variable that matters
The single finding that changes outcomes here is not how many days but whether they are the same days.
An uncoordinated three-day mandate produces offices full of people video-calling colleagues who chose different days. You have paid the full commute cost across the whole workforce and bought none of the collaboration the policy was justified by. Occupancy looks excellent.
Contact-breadth data is what exposes this, and it is the measurement most hybrid programmes never take. If the number of distinct colleagues someone interacts with does not rise on office days, coordination is not happening regardless of how full the floor is.
The compliance angle people miss
Desk booking and badge data is personal data where it identifies individuals, and it attracts the usual obligations — purpose, proportionality, transparency, retention.
The specific risk is repurposing. Occupancy collected for facilities planning, then used to identify individuals below an attendance target, is a new purpose. In the UK, EU, Canada and Australia that needs its own lawful footing and its own notice rather than inheriting the facilities one. "We already had the data" is not a basis.
It is also the kind of repurposing that becomes almost inevitable once the data exists and a mandate is under pressure, which is why the sensible control is deciding the excluded uses up front — the same argument as in the retention guide.
What to actually do
Keep occupancy for the building. Use it for space decisions, where it is the right instrument and genuinely valuable.
For whether the policy is working, measure the thing the policy promised. Collaboration, focus, ramp time for new joiners, delivery. Compare office against home rather than against a target. Read it at team level over months, because a fortnight of either is noise.
And be willing to conclude that the mandate is not delivering. That is a possible answer, and an occupancy dashboard is structurally incapable of producing it, which is part of why it gets used.
Where ProdView fits
ProdView measures the work side: focus time and fragmentation, meeting load, how attention distributes, after-hours patterns. That is what lets you compare an office day against a home day on something other than attendance. Activity and application metadata only, never screen content, aggregate-first, with employees seeing the same dashboard managers do.
When not to pick us: you want occupancy, desk booking or space planning. We have no badge integration, no sensors and no location data, and we would not be the right tool — buy a workplace or facilities platform for that and keep it pointed at the building rather than at people.
Try before you commit
Three seats are free forever, which is enough to compare one team's office days against their home days. Most organisations have never run that comparison and are surprised by it either way. The meeting cost calculator prices whatever the coordination turns out to cost.
General information as of October 2026, not legal advice.