Vehicle Location History You Can Actually Query
The question always arrives late: was that vehicle at the site on the fourteenth, and for how long. KO Fleetz keeps a searchable positional archive per vehicle, with stops resolved into places and durations, so a three-week-old dispute takes minutes rather than an afternoon.
The invoice arrives three weeks late and disputes a Tuesday nobody remembers
A customer queries a waiting-time charge from the middle of last month. Your invoice says the vehicle sat at their gate for three hours. They say ninety minutes. Both parties are certain, both are working from memory and a driver's handwritten sheet, and the amount in question is smaller than the cost of arguing about it properly.
Meanwhile the records that could settle it are scattered. The tracker holds positions, but only for as long as the platform retains them, and nobody checked what that period was until the moment it mattered. The driver has rotated off that route. The gate log, if it exists, is on paper in a hut.
The same gap opens up for anything retrospective. An insurer wants to know the route taken. A regulator asks whether a vehicle entered a restricted zone. A depot manager suspects a van is doing weekend work. Every one of those questions is answerable in principle and painful in practice, because raw position rows are not an answer. They are homework.
An archive that answers in sentences, not coordinates
KO Fleetz retains every reported fix per vehicle against a known retention window that you can see and configure, not discover during a dispute. Position, timestamp, speed and ignition are kept together, because a coordinate without engine state cannot distinguish parked from crawling.
On top of the raw track sits interpretation. Consecutive fixes at one location collapse into a stop with an arrival time, a departure time and a duration. Stops resolve to named places where a geofence exists and to reverse-geocoded addresses where one does not. The answer reads as three hours eleven minutes at the Hanwell depot, which is a sentence a customer can argue with or accept.
This page is the archive, not the cinema. If you want to watch a single journey unfold with the speed trace running underneath it, that is Trip Replay. Location History exists for the other shape of question: across a date range, across many vehicles, where was this asset and when, exported to something you can attach to an email.
Capabilities
What KO Fleetz vehicle location history gives your team
Date-range position query
Pick a vehicle and a window, from an hour to a quarter, and get the track back with every fix, its timestamp and its speed intact.
Stops resolved into places
Clustered fixes become a stop with arrival, departure and duration, named by geofence where one exists and reverse-geocoded where it does not.
Visible retention policy
How long positional data is kept is a setting you can read and change, rather than a limit you find out about during a dispute.
Was-it-here lookup
Ask KO Fleetz whether any vehicle was inside a given area during a given window and get the list back, instead of opening each vehicle's track one at a time.
Exportable records
Any query becomes a file with the underlying fixes and their timestamps, suitable for attaching to a claim, an audit response or a customer credit note.
Multi-vehicle overlay
Put several vehicles' historical tracks on one map for the same period, which is how duplicated coverage and overlapping routes become obvious.
Distance and time reconstruction
Derives travelled distance and moving time per day from the position record itself, giving an independent check on odometer readings and driver sheets.
Access trail on lookups
Historical location data is sensitive, so who queried which vehicle's movements, and when, is itself recorded.
How it works
How KO Fleetz does it
Step 1: Decide the retention window first
Retention is a commercial and legal decision, not a technical default. Match it to how late your disputes and claims actually arrive.
Step 2: Name the places that matter
Depots, customer sites and yards get named once. The archive then reports stops by place rather than by coordinate: data becomes an answer.
Step 3: Query by vehicle, area or window
Start from whichever end of the question you have. A vehicle and a date, or a location and a period, both converge on the same underlying record.
Step 4: Export the evidence
Take the result out as a file with its timestamps attached, so the conversation with the customer or the insurer starts from a record rather than a recollection.
Outcomes
What changes
- Retrieval, within the retention window
- Any date
- Places and durations, not raw coordinates
- Named stops
- Evidence a third party will accept
- Exportable
- To settle what used to take an afternoon
- Minutes
Frequently asked questions
That is a policy you set rather than a fixed number we impose, and it is worth deciding on purpose. The right window is driven by how late your problems arrive: if payment disputes surface sixty days after the job and insurance claims take longer still, a thirty-day retention will fail you exactly when you need it. Longer retention costs storage. Shorter retention costs arguments. Pick knowingly.
Shape of question. Location History is an archive you query across ranges and across vehicles: where was this van in March, which vehicles entered this yard last week, export the lot. Trip Replay reconstructs one journey in sequence with speed, stops and events aligned on a timeline, for when you need to understand what happened rather than retrieve where something was.
KO Fleetz does not let reported fixes be edited through the interface, which is the property that makes the archive worth anything in a dispute. Records leave only through the retention policy expiring or a deletion request handled deliberately at administrator level. Lookups are themselves logged. If the data could be quietly adjusted by whoever was losing the argument, none of it would be evidence.
Yes, and gaps are shown rather than smoothed over. The usual causes are mundane: no cellular coverage, so fixes buffer and arrive late; a device losing power; or an underground car park where satellites are unreachable. The archive marks the discontinuity instead of drawing a confident straight line through it. An invented track between two real points is worse than an honest gap.
It is a real obligation, and treating it as purely a technical matter is how fleets get into trouble. In most jurisdictions this is personal data when it can be linked to a driver, which means you need a lawful basis, a defensible retention period, driver transparency and controlled access. KO Fleetz provides the levers: configurable retention, role-based access and logged lookups. The policy is yours to write.
As a cross-check, yes, and it is a useful one. Distance derived from the fix sequence is independent of anything a driver writes down, so a large divergence between the two is worth a conversation. Do not expect them to match exactly. GPS-derived distance slightly understates real travel because it connects sampled points, and tyre wear and calibration move the odometer's own figure.
Settle your oldest open dispute
Give KO Fleetz a vehicle, a date and a disagreement, and see what the archive says actually happened.