Monitoring in an industrial setting sits at the intersection of three regulatory regimes that are rarely considered together.
General orientation. Requirements differ substantially by jurisdiction and change; take advice for yours.
Workplace safety
A general duty to provide a safe workplace, in essentially every jurisdiction.
Risk assessment obligations, commonly including manual handling, workplace transport and, increasingly, work organisation and pace.
Specific rules on vehicle and pedestrian separation, lifting equipment, and pre-use inspection.
Incident recording and reporting thresholds, with defined timescales.
Consultation with workers on safety matters, which is a requirement rather than good practice in many places.
These duties frequently support monitoring — recording pre-use checks, detecting proximity — and they also constrain pace-setting, since a system of work must be safe.
Data protection
Monitoring identified workers processes personal data, engaging the full set of obligations.
Lawful basis, where consent from an employee is frequently not considered freely given because of the power imbalance.
Notice, proportionality and purpose limitation.
Impact assessment before systematic monitoring, required in several jurisdictions.
Access rights for the individual.
Retention limits, where excess retention is itself a failure rather than a safe default.
Restrictions on automated decisions with significant effects, commonly requiring human involvement and a route to contest.
Special categories, including health data, with stronger requirements — which is why inferring health from movement data is a poor idea.
Employment law
Consultation on changes to working conditions, including pace and organisation, in many jurisdictions.
Collective agreements, which may restrict monitoring independently of statute.
Working time, including rest breaks, which interacts directly with any measurement of time away from a workstation.
Discrimination, where a uniform rate target may disadvantage workers with disabilities or health conditions, and adjustments may be required.
The two directions of pressure
Safety regulation pushes toward more measurement: record checks, detect proximity, assess exposure.
Data protection pushes toward less: minimise, aggregate, limit retention, limit purpose.
Both apply simultaneously, and designing for one while ignoring the other creates exposure in the other direction.
The reconciliation is usually aggregation: most safety purposes are served by location and condition data rather than by individual traces, and most data protection concerns fall away once attribution is removed.
Emerging attention
Algorithmic management — automated target setting, allocation and discipline — is under active regulatory attention in several jurisdictions, with new obligations appearing around transparency, human review and contestability.
A deployment designed around automated rate enforcement is building on ground that is moving, which is a practical argument for the human-decision arrangement described elsewhere.
What to do
Map the applicable regimes once, and identify where a single control satisfies several requirements, which most do.
Document the proportionality reasoning, which is what an assessment is for and what a regulator asks about.
Consult, which appears in all three regimes.
Keep the record of what you decided and why, because the question arrives years later and reconstruction is not possible.
Mapping the regimes once
The three bodies of rules overlap, and mapping them individually wastes years.
List what applies: safety, data protection, employment, and any sector rules.
Extract the requirements touching measurement, pace and monitoring.
Map each to a control you operate, noting the evidence it produces.
Identify controls satisfying several requirements, which most do.
Identify the genuine gaps, which is usually a short list.
Maintain the mapping as rules change, rather than rebuilding it before each audit or inspection.
Documenting the proportionality reasoning
What a regulator asks for, and what cannot be reconstructed afterwards.
What less intrusive alternative was considered, specifically — aggregation, equipment tagging, zone resolution, sampling.
Why it was rejected, with the operational reason.
What safeguards were added instead.
Who decided, and when.
Recorded at the time, because a reasoning reconstructed two years later during a dispute is worth very little and looks worse than none.
Also in this section