Why do the three sources disagree?
The tracker knows when the engine ran. The driver-ID reader knows which tag was presented. The roster knows who was meant to drive. Each one fails in its own way, and a driving-hours report is only as right as the trips it starts from.
- Drivers forget to present the tag, or the reader is not wired to ignition.
- Tags are shared, swapped or copied between drivers.
- The roster changes on the day and nobody updates the file.
What do the seven results mean?
Every trip gets the first result that applies, in this order.
- Agrees
- Check
- Disagrees
| Result | Ignition | Driver-ID tag | Roster |
|---|---|---|---|
| Matched | Trip | Tag read | Same vehicle, in shift |
| No ID tag | Trip | Empty | Shows who was due |
| Tag on two vehicles | Two trips | Same tag, same time | Not used |
| Unknown tag | Trip | Read | Not in roster |
| Outside the shift | Trip | Tag read | Starts or ends outside |
| Wrong vehicle | Trip | Tag read | Rostered elsewhere |
| Not rostered | Trip | Tag read | No shift then |
Overlap (min) = max(0, min(trip end, shift end + tolerance) - max(trip start, shift start - tolerance))Share inside = overlap / trip minutesMatched when share inside >= your share, same tag and same vehicleMatch rate = matched minutes / all driving minutes
How do you prepare the two files?
Export the trips
From your platform, export one row per trip with vehicle, start, end and the driver-ID tag read during the trip.
Export the roster
One row per shift with the driver name, the tag number, the vehicle and the shift times.
Paste or load both
Header names are matched for you. Tags such as 0004512 and 4512 are treated as the same tag.
What should you fix first?
- A vehicle with much driving and no ID: check the reader, its wiring and whether it is set to ask for a tag.
- One tag on two vehicles at once: the tag is shared or copied. Issue new tags.
- Unknown tags: add them to the roster or block them.
- Wrong vehicle and not rostered: update the roster when plans change on the day.
- Idle shifts: a driver was rostered but no tag was read. Check that driver's tag.
Assumptions and limits
- All times are read as local clock times, as they appear in your files. Use the same time zone in both files.
- Driving time here is ignition-on time per trip. Idling inside a trip is counted as driving.
- The tool does not check driving or rest limits. It checks that the data about who drove is consistent.
- A tag in different formats, such as hex and decimal, is not converted here. Convert it first.
Next step: the hours themselves
Once the trips are assigned to the right driver, check driving and rest limits in your fleet platform or a driving-hours checker.