Trackers, Plug-Ins and Phone Apps
Three ways to collect position, each with a different relationship to the person, and the one that follows them everywhere.
The physical form of the tracker decides more about the deployment than the software does.
Hardwired units
Installed into the vehicle's electrics, typically at the fuse box or OBD connection.
Always powered, which means always collecting unless configured otherwise.
Hard to remove, which is the point for asset protection and the problem for personal use.
Best for: vehicles that stay on site, where the data genuinely concerns an asset.
Watch: they run when the vehicle is parked at someone's house, all night, unless suspension is configured.
Plug-in devices
Into the diagnostic port, removable in seconds.
Which is a feature rather than a flaw where personal use is permitted: unplugging is a pause control that needs no software.
Some fleets treat unplugging as misconduct, which converts the feature back into continuous tracking and has produced disputes.
If you permit removal for personal journeys, say so in writing, because an unwritten tolerance is not a control.
Phone applications
The most intrusive option and the cheapest to deploy.
The phone goes everywhere: the vehicle, the house, the doctor, the pub.
On a personal device it is worse, because the employer is asking to install monitoring on something the person owns and pays for.
Background collection continues unless the app is genuinely stopped, and users frequently believe closing it is enough when it is not.
If an app is the method, a working pause and a visible indicator are not optional, and a company device is a much cleaner position than a personal one.
Choosing between them
Ask what the tracked object should be.
A vehicle that never goes home: hardwired is fine.
A vehicle taken home: plug-in, or hardwired with configured suspension.
A person on foot who needs lone worker protection: an app or a dedicated safety device, with position read on alarm rather than logged.
A person whose vehicle is their own: nothing. Tracking an employee's private vehicle is restricted or criminal in several jurisdictions and is rarely defensible anywhere.
The questions to ask a vendor
Can collection be suspended, by whom, and does the suspension actually stop transmission?
What does the device do when the vehicle is off?
Is there a visible indicator when collection is active?
On phones: what runs in the background, and what does the user see?
Verify the answers. Watch the data for an evening and see whether anything arrives after the shift ended.
Run the overnight test
The single most informative check in any trial.
Park a vehicle at someone's house overnight.
In the morning, look at what the system recorded.
Positions through the night mean continuous collection is on and that a home address is now in your records.
Nothing until the ignition turns means suspension is working.
Almost nobody runs this test, and it answers the most consequential question about the deployment.
An implementation prompt
During configuration, employee time clock 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 GSMA. Its mobile-industry resources offer external context for devices, connectivity and network-dependent field systems.