Once measurement is attributed to a person, it is monitoring of that person at work, whatever the system is called internally. Treating it otherwise creates legal exposure and destroys the cooperation the operation depends on.
General orientation. Requirements differ substantially by jurisdiction and change; take advice for yours.
What it is
Continuous measurement of a named person's work, frequently second by second.
Retained, often for long periods.
Reviewable by people the worker may not know.
Capable of capturing far more than intended: break duration, toilet visits, conversations, time spent anywhere in the building.
Increasingly automated, with alerts and in some deployments automated consequences.
The obligations that commonly apply
Notice. Workers must generally be told that monitoring occurs, what is collected, why, and for how long it is kept. A clause in an induction pack is usually insufficient.
Proportionality. The monitoring must be justified against the purpose, with less intrusive alternatives considered and the consideration documented.
Purpose limitation. Data collected for safety or process improvement should not be repurposed for performance management. This is where most facilities quietly fail.
Impact assessment, required in several jurisdictions before systematic monitoring.
Consultation with workers or their representatives, which is a legal requirement in a number of places rather than good practice.
Access rights. The worker may have a right to see the data held about them.
Restrictions on automated decisions with significant effects, which in several jurisdictions require human involvement and a route to contest.
What to settle before deployment
Scope: what is measured, on whom, where.
Granularity: individual, team, or zone. Choose the coarsest that answers the question.
Purpose, stated narrowly and in writing.
What it will not be used for, stated explicitly and enforced.
Retention, with a justification.
Who may see individual data, under what trigger.
Exclusions: welfare facilities, break areas, medical rooms, enforced technically rather than by policy.
The route to challenge a measurement, with an actual response.
Telling people properly
Before deployment, not after.
Specifically: what is collected, by which system, when it is on, who sees it.
In plain language and in the languages the workforce actually uses, which matters more in this sector than most.
With the reason, which workers generally accept when it is honest.
Answer the obvious question directly: yes, this could show that you were slower than usual on Tuesday. Say what will and will not happen as a result.
The purpose limitation line
The boundary that matters most.
Safety data used for productivity discipline produces under-reporting of safety events, which defeats the safety purpose entirely.
Process data repurposed as individual targets produces gaming and the injury risks covered separately.
State the limitation in writing, and enforce it. Where an exception is genuinely required — a serious misconduct investigation — define who authorises it and record that it happened.
A facility that quietly repurposes monitoring data finds out once, and the loss of cooperation is not recoverable within the tenure of the people involved.
The impact assessment
Required before systematic monitoring in several jurisdictions and useful regardless.
What is monitored, specifically, including granularity.
Why, with the operational question it answers.
Who is affected and how many.
What less intrusive alternatives were considered and why they were rejected. Aggregation is almost always one of them.
What safeguards apply: access restriction, retention, purpose limitation, exclusions.
What the residual impact on those monitored is.
Retained as evidence that the proportionality question was asked rather than assumed.
The first hard case
Someone will propose using the data for something outside its stated purpose, and that decision is the real policy.
Decide in advance who decides, because deciding under pressure produces the wrong answer.
If the answer is yes, everyone learns what the system is for within a week.
If the answer is no, and the reason is stated publicly, the assurance becomes credible in a way no document achieves.
Record the decision either way, so the next request has a precedent.
Expect the request within the first year. It always comes.