Tracking Outside Working Hours
Where almost every enforcement case in this field has landed. Why continuous tracking of a take-home vehicle is the default failure.
If you read the decided cases in this area, one pattern dominates: the tracking did not stop when the working day did.
Why it happens by default
Trackers are hardwired and run continuously. Stopping at the end of a shift requires a deliberate configuration.
The system does not know when the shift ended, unless something tells it.
Personal use is permitted in a large share of fleets, and the vehicle goes home.
Nobody decided to track private life. The system simply kept running, which is how most of these deployments become unlawful without anyone intending it.
What the record then contains
A home address, precisely.
Evenings and weekends.
Visits to a doctor, a clinic, a place of worship, a union meeting, a solicitor.
By inference: health, beliefs, family arrangements, associations — categories that carry additional protection in most data protection regimes.
None of this serves fleet management, which is the stated purpose in almost every case.
What regulators have concluded
General orientation, not legal advice; check your jurisdiction.
Continuous tracking that extends beyond working time has been found disproportionate in decisions across several European jurisdictions.
Tracking during breaks has been found excessive, even within the working day.
A system with an available pause feature that the employer did not enable has been treated as an aggravating factor rather than a neutral one, in an Italian decision in 2025.
Retention of route history for months has been found to breach storage limitation where the operational purpose needed days.
The consistent theme is not that tracking is forbidden. It is that the amount collected exceeded the purpose stated.
The three ways to stop it
A pause control the driver operates, marking a journey as personal. Simple, and it puts the decision with the person whose private life it is.
Automatic suspension outside the shift, driven by the rota or by an ignition-off period.
Not collecting continuously at all — geofence events and daily totals have no out-of-hours dimension to worry about.
The third is the strongest and it is available more often than people assume.
What to check in your own deployment
Does a record exist for last Saturday? If yes, you are tracking outside working hours.
Is there a pause control, and is it enabled?
Does anyone know how to use it? An enabled feature nobody has been shown is not a control.
What is the retention, and does it cover journeys that were personal?
Four questions, answerable in an hour, and the answers determine whether the deployment is defensible.
Check last Saturday
One query that settles whether this applies to you.
Pull the records for a weekend.
If positions exist, you are tracking outside working hours, whatever the policy says.
If they exist for a vehicle that goes home, they include a home address and everything inferable from it.
Do this before anyone else does, because it is the first thing an inspector or a claimant's representative will ask for.
An implementation prompt
During configuration, remote employee monitoring software can prompt questions about fields, ownership and output. Confirm current capabilities and document each plan, integration or policy assumption.
Independent reference
For an external point of reference, see the ACAS website. Its employment guidance provides a neutral reference when defining availability and working-time boundaries.