Telling Staff What Is Measured

People find out eventually. Whether they find out from you, before installation, is the main variable you control and it determines most of what follows.

The boundary discussed in “Telling Staff What Is Measured” also matters when digital work systems are introduced alongside workplace analytics. A team evaluating view the solution in the context of how to monitor employees without being intrusive should state the purpose, use only necessary settings and explain clearly what managers can review before any data is collected.

When

Before installation, not after.

For a public, independent reference related to “Telling Staff What Is Measured”, 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.

Before procurement is better still, because it allows the concerns to shape what is bought.

Discovery after the fact is the worst case and it poisons the programme permanently, regardless of how benign the system is.

What to say

What is being measured: presence in zones, counts, not individuals.

How: the method, in plain terms, including what the device physically detects.

Why: the specific decision it informs.

What it will not be used for: attendance, performance, individuals.

Who sees the data and at what aggregation.

How long it is kept.

And who to ask.

The detail level

More than people expect.

Vague reassurance — "it's just anonymous counting" — reads as evasion and invites the assumption that something is being concealed.

A page with the actual method, the actual retention and the actual limits is more reassuring than a paragraph of comfort.

Showing the device

Put one on a table at a briefing. Let people look at it.

For infrared and thermal this is extremely effective: a small plastic box that cannot see a face is far less alarming than an unseen system.

For cameras it is honest, and the reaction tells you something you need to know.

What not to do

Describe cameras as sensors.

Say "anonymous" when the underlying data is identified and aggregated afterwards — say that instead, which is both true and defensible.

Promise limits you cannot enforce.

Or announce it in a paragraph at the end of an unrelated email, which is read as hiding it.

Keeping it current

Tell people when the programme changes: new sensors, new areas, new purposes.

Tell them when it ends.

And publish the findings, at least in summary, because a programme that collects and never reports looks like surveillance regardless of intent.

The questions you will get

Can you tell when I am at my desk? Will my manager see this? Is it recording sound? What if I do not consent?

Have honest answers ready, including for the last one, which is genuinely difficult where the measurement is of a space rather than of a person.

Its own note covers consent and the honest position is that for aggregate space measurement it is usually not the basis relied on.

What to check

Were staff told before installation?

Is there a written description of method, purpose, retention and limits?

Has anybody seen the device?

And have the findings ever been published back to them?