When Occupancy Data Becomes Attendance Monitoring

An occupancy programme becomes an attendance system through a series of small steps, none of which is announced as a change of purpose.

The boundary discussed in “When Occupancy Data Becomes Attendance Monitoring” also matters when digital work systems are introduced alongside workplace analytics. A team evaluating this product overview in the context of how employee monitoring works should state the purpose, use only necessary settings and explain clearly what managers can review before any data is collected.

The steps

A report is produced by floor, and floors map to departments.

For a public, independent reference related to “When Occupancy Data Becomes Attendance Monitoring”, consult the ICO guidance on employment practices. Its principles provide a useful check on scope, terminology, governance and the claims made during procurement or review.

Somebody asks for it by team.

A manager uses it in a conversation.

HR asks for it during a dispute.

And within a year the system that measured space is measuring people, with none of the consultation or notice that would have been required had it been proposed that way.

Why it is tempting

The data exists, the question is live, and attendance policies in many organisations are difficult to enforce without it.

The alternative — managers knowing whether their people are in — requires management attention that the data appears to replace.

This is a real pressure and naming it is more useful than pretending it does not exist.

What it costs

The accuracy of everything else. Once people know occupancy data affects them, behaviour changes: badge in and leave, sit at the sensed desk, book the room and not use it.

The data stops describing the building and starts describing the incentive.

And the programme loses the cooperation it needed, including the complaints that were its best diagnostic signal.

What it does not deliver

Reliable attendance data, because the measures are proxies with known error.

A badge count is not attendance. A desk sensor is not presence. Using them as such produces disputes the organisation loses.

If you need attendance data, build an attendance system and say so, with the consultation that requires.

Holding the line

Report at a level that cannot map to a team.

Refuse team-level requests, in writing, with a reason.

Keep the desk-to-person mapping out of the system entirely.

And have the refusal come from a named person with authority, which the boundary note covers.

If the organisation decides to do it anyway

That is a legitimate decision for an organisation to make, provided it is made openly.

It requires its own purpose, its own notice, its own consultation and probably its own system.

What it should not do is reuse the space programme quietly, which is the choice that causes the damage.

The conversation to have early

Before deployment, agree what happens when somebody asks for attendance data.

Having the answer settled in advance, in writing, is what makes refusal possible later.

Settling it during the first request means the answer is whatever the requester's seniority dictates.

What to check

At what level is your data reported, and does it map to teams?

Has a team-level request been made?

Is the desk-to-person mapping retained anywhere?

And is the answer to a future attendance request already written down?