Tracking time without building a surveillance system
Mobile workforce products offer continuous location and activity monitoring. Very few maintenance questions require any of it.
Field service and mobile workforce tools routinely offer more than time capture: continuous GPS tracking, vehicle telematics, geofenced alerts, idle detection, photographic verification of attendance. Teams comparing monitoring approaches can review employee monitoring software, while still defining the operational question, proportional data and privacy boundaries first.
Each has a legitimate narrow use. Enabled together, by default, because they came with the package, they create a monitoring apparatus that answers questions nobody asked and carries obligations nobody has assessed.
Start from the question
The operational questions a maintenance department actually has about time are a short list.
- How long does this task take, so the schedule is realistic? Job start and finish.
- Where is the non-wrench time going, so it can be reduced? Five categories, sampled.
- Was the contracted attendance actually made? Attendance record with a timestamp at the site.
- Are people being paid correctly? Attended hours.
- Who is nearest to this emergency? Current location — at the moment of dispatch.
The last one is the only question that needs location at all, and it needs it at a moment, not continuously. A dispatch tool that shows position when a job is being assigned answers it; a permanent breadcrumb trail of everywhere a technician drove does not answer it better. For a wider operational and compliance reference, consult CISA cybersecurity performance goals.
Confirming that someone was at the site when they said they were requires one location check. Recording their route all day is a different thing with different obligations and no additional operational value.
The legal position is not optional
Monitoring employees is regulated in most jurisdictions, and the requirements commonly include a lawful basis, prior notice, proportionality, an assessment where the monitoring is systematic, and limits on retention. Covert monitoring is unlawful in many places except in narrowly defined circumstances.
Vehicle tracking is a particular trap: where a vehicle may be used privately, tracking it outside working hours generally requires a privacy mode and an explicit policy. Systems deployed without one collect data about employees' personal movements, which is a problem the organisation has created for itself and will eventually have to answer for.
Lone worker safety is a separate system
Technicians working alone, in plant rooms, at height or on remote sites have a genuine safety case for location awareness, and it deserves to be taken seriously rather than used as the justification for general monitoring.
Built properly it is staff-activated or task-triggered, clearly bounded, visible to the worker, used only for the safety purpose and retained briefly. Bolting safety monitoring onto the time system merges two purposes with different justifications and inherits the weakest one for the most intrusive data.
Retention is where most policies fail
Organisations think about what to collect and rarely about how long to keep it. Attendance records supporting payroll need retaining for a statutory period; the granular events behind them do not.
Separate the two, write down the periods, and automate the deletion. Manual deletion is deletion that does not happen, and a location history kept indefinitely is a liability that grows every day it is retained.
The test worth applying
Before enabling a capability, ask whether you would be willing to show the team exactly what is collected, who can see it, and how long it is kept.
If yes, the measure is probably proportionate — and you should do the showing, because transparency is most of what makes tracking tolerable. If no, the discomfort is the finding, and the honest conclusion is that the capability is not proportionate to any question you have.