Consulting Before You Deploy
A requirement in several jurisdictions and the step that most improves the design. What to consult on, and what the answers change.
Location tracking is the kind of measure that engages consultation duties, and skipping it is the most common procedural failure in this field.
Why it is required
Technical systems capable of monitoring employees trigger co-determination rights in a number of European jurisdictions, and a works council can block deployment.
In Italy, prior authorisation from the labour inspectorate is required for remote monitoring systems, and decisions in 2025 have shown that obtaining it is not sufficient — the conditions attached to it must actually be met.
Collective agreements may impose their own requirements.
And a data protection impact assessment is expected for location monitoring, which asks for the views of affected people where appropriate.
Why it improves the design
Drivers know which journeys are personal and will tell you exactly where the pause control needs to be.
They know the dead zones where fixes fail, which saves you a month of investigating phantom data.
They know which geofences will misfire — the depot next to a main road, the customer with two entrances.
They raise the questions the workforce will ask anyway, while you can still change the answer.
What to consult on
Which of the four purposes this serves, stated plainly.
What is collected and what is not, with the negative list explicit.
Whether tracking stops outside working hours, and how.
Retention, in days.
Who can see individual location, and under what circumstances.
Whether any of it will be used in performance management, which is the question people actually have.
The questions you will be asked
Prepare these, because they arrive every time.
"Can you see where I am right now?" A yes or no, and if the honest answer is uncomfortable the design is the problem.
"Does it track me at the weekend?"
"Will this be used against me?" Answer with the written purpose limitation and who enforces it.
"What happens if I forget to switch the pause on?" A real usability question needing a real answer.
"Who can look, and is it logged?"
Doing it properly
Before procurement, not after a contract is signed.
With representatives where they exist.
With someone present who can change the design.
With a written response to every point, published to everyone consulted.
Say what changed. Something should have, and if nothing did, the consultation was an announcement.
Respond in writing
What separates consultation from an announcement.
Record everything raised, including what you disagree with.
Respond to each point specifically.
Say what changed — something should have.
Say what did not, and why, including where the reason is cost.
Publish the response to everyone consulted, not only to representatives, because otherwise it is remembered as a meeting.
Check the difficult case
Use the staffing workflow to frame one representative test for this issue. The useful evidence is the record created when a worker challenges an event, a manager reviews it and an administrator exports it.
Independent reference
For an external point of reference, see ACAS. This recognised employment-relations source can help frame consultation before a system changes how work is observed.