Don't Treat GPS Movement as Engine Hours
When the map shows that a machine has moved, keep that movement record and the hours source distinct, and do not backfill engine hours from travel, ignition, or a distance estimate.
Imagine a plant or fleet lead opening a utilisation file after a machine has clearly changed position. The map shows travel between two site pins, or a geofence exit and entry. The hours field for the same window is blank, delayed, or looks too small. The temptation is to fill the gap from the track — to treat distance, a typical speed, or “it must have been running” as engine hours. This article is a practical office and field method for that moment: name the movement record and the hours source separately, and do not invent hours from GPS movement.

Illustration for this article; it does not show a customer deployment, measured result or certified installation.
GPS movement is not an hours reading
A location record that changes position is a movement record. It can show that the asset was not in the same place at two times. It is not, by itself, a reading of engine hours, work time, or utilisation.
Engine hours come from a named hours source — a cab meter, a verified machine interface, or another field the office has locked and can still explain. A track, a geofence event, or a distance total is a different kind of evidence. Treating movement as hours collapses two questions into one number: whether the asset moved, and how the engine or the hours source counted time. Hardware that supports tracking, sensors and operational visibility can supply both kinds of record; it does not make them the same measurement. Keep the same label discipline already used for engine hours vs powered-on time: powered-on time is not automatically work time, and a motion or location change is not a system of engine hours.
What movement can and cannot show
Before anyone backfills hours from a track, write down what the movement record actually is, and what it does not prove.
| Record | What it can support | What it does not mean |
|---|---|---|
| Position change | The reported location was not the same at two timestamps, subject to the quality of those points. | That the engine ran for the elapsed time, or that the move was self-propelled work. |
| Distance or path | A reported path length or sequence of points in the receiving system, with event time and receipt time kept apart. | That distance can be divided by a typical speed to produce engine hours. |
| Geofence exit or entry | A named site boundary was reported as crossed or occupied, if the geofence itself is defined. | That time inside or between geofences is work time or engine hours. |
| Ignition or supply, if present | A separate powered-on or ignition signal, when that field exists and is named. | That ignition, powered-on time, or movement can stand in for the locked hours source. |
Movement can also occur without the work you intend to count. A machine can be towed, carried on a low-loader, shunted in a yard, or loaded as an attachment. A GPS jump, a stale point that later updates, or a poor fix can look like travel. If the move type cannot be named, write UNKNOWN with an owner and a date — do not fill engine hours to make the window look complete. Location quality is a separate method; see the construction-site GPS accuracy method when the question is whether the points themselves are usable.
Do not backfill a blank or delayed hours field from travel
Do not invent engine hours from distance, from an average or typical speed, or from the elapsed time between two pins. Do not copy a geofence dwell into the hours column. Do not treat “the machine moved, so it must have been running” as a reading. Do not use ignition or powered-on time as a silent substitute when the locked source is engine hours.
If the hours field is blank, delayed or stale in a window where the map shows travel, that is a missing or delayed hours problem, not a reason to estimate the missing value from the track. Keep the gap visible, and pause utilisation comparisons that would fill it, as already set out in Don't Treat a Missing or Delayed Hours Reading as Zero. A later hours jump after that gap is a catch-up question under the hours source, not proof that the travel “explains” the increment; see Don't Treat a Sudden Hours Jump After a Gap as One Day's Work.
Backfilling invents a third series that neither the locked hours source nor the location record produced as engine hours. A utilisation chart that looks complete after the fill can make a towed move, a transport leg, or a reporting delay look like billable or serviceable work. This article does not publish a distance-to-hours factor, a speed rule, or a measured LEXUNYU field result. Until the office has a written rule that movement must not replace the hours source, treat any hours figure derived from the map as incomplete.
Keep movement events and the hours source distinct
Leave both records visible in the shared note or export. Do not overwrite a blank hours field with a travel estimate so the day looks finished. Record, at least:
- the machine identity and the workflows that use the hours field;
- the locked hours source — field name, unit, last value and timestamp, or UNKNOWN if the source is not named, following the same lock described in How to Lock the Hours Source When a Cab Meter and a Telematics Feed Disagree;
- the movement record — first and last points or geofence events in the window, event time and server receipt time, reported distance if the system provides one, and whether the move type is known (self-propelled, towed, carried, yard shunt) or UNKNOWN;
- whether the hours field in that window is present, delayed, stale, or blank, without filling the gap from the track;
- open hypotheses for any mismatch: a towed or loaded move, a reporting delay on the hours source, a GPS jump, mixed clocks, a source change, or UNKNOWN.
A listed hypothesis is a prompt for the next check, not a licence to invent hours. If the hours source itself changed in the same window, that is a break between two hours series, not a reason to use the map as a bridge; see Don't Treat a Change of Hours Source as One Continuous Record. For installation issues that appear before any platform review, see five heavy-equipment installation mistakes. Use the blank machinery installation data record (CSV) to keep the observations together. A one-machine hours sample should still start from a locked hours source, not from a track — see How to Sample Engine Hours on One Machine Before a Fleet Rollout.
What you can and cannot conclude
A useful movement-versus-hours record can support statements such as:
- this machine has a named hours source, and a separate movement record for the same window, with these receiving fields;
- the hours field in that window was present, delayed, stale, or blank, and was not filled from the track;
- the move type is named, or is written UNKNOWN pending a check (towed, carried, self-propelled, or a suspected GPS artefact);
- utilisation, hire or service decisions that would use map-derived hours in place of the locked source are incomplete.
The same record does not prove:
- a universal distance-to-hours factor, speed rule, or pass/fail threshold;
- that travel time, geofence dwell, ignition or powered-on time is engine hours;
- that a blank hours field can be replaced by the path, or that a later hours jump equals the travel just seen;
- fleet-wide utilisation, hire or maintenance decisions built on map-derived hours;
- destination-market marks, batch consistency, or any customer case study, inventory level or traffic metric (those remain UNKNOWN unless separately evidenced).
Movement-versus-hours is also a different problem from two complete, contemporaneous hours readings that disagree, and from a change of hours source. This article deals with the temptation to invent hours from a track, not with choosing between two hours totals, and not with splicing two hours series. For device-class context on powered plant, see how plant machinery trackers work and how to choose a heavy-equipment tracking device. Confirm the current A300 configuration path on the A300 product page before any sample discussion. A blank sensor or hours field on an otherwise online tracker is a field-diagnosis question first — see GPS Tracker Online but Sensor Data Missing.
Pause rules before utilisation comparisons
Pause a utilisation comparison, a weekly ranking, or a hire-hours difference when any of these are true:
- any machine in the comparison has hours derived from GPS movement, distance, speed, geofence dwell, or “it must have been running”;
- the hours field is blank, delayed or stale in a window where the map shows travel, and someone has filled the gap from the track;
- the move type is UNKNOWN, or a towed, carried or transport leg has been counted as engine work;
- event time and receipt time are mixed, or freshness is still UNKNOWN;
- the hours source is still UNKNOWN, or the UI still merges engine hours, powered-on time, ignition and movement under one label;
- the asset has no fixed power (trailers, containers and many attachments need a different device class — see no-fixed-power guidance);
- the project only needs a basic location record with no machine hours field to validate;
- a closed file was quietly rewritten so the day’s hours look complete after a map-based fill.
A movement record without a usable hours reading is a reason to keep the gap visible, or to mark the comparison as incomplete — not a reason to estimate hours from the path. For rental handover and off-hire windows, investigate movement type and the hours source before using a difference; see telematics for excavator and equipment rental. For site-level questions beyond hours, see choosing GPS tracking for construction sites. For the wider China-sample workflow, use how to validate a China GPS tracker sample before a bulk order. Platform connection depends on the selected protocol, fields and receiving system and is confirmed per project — see keep your existing system and adding GPS hardware to an existing fleet platform.
Frequently asked questions
If the map shows the machine moved, can we fill in missing engine hours from that travel?
No. A track that changed position is a movement record, not an hours reading. If the hours field is blank, delayed or stale, keep the gap visible and do not invent hours from distance, speed or a geofence stay.
Can we convert distance or an average speed into engine hours?
No. A distance-to-hours conversion invents a series that the locked hours source did not produce. Average speed, typical cycle times and 'it must have been running' estimates are not a substitute hours reading.
What if the machine was towed, loaded or repositioned, but the track still moved?
Movement can occur without the engine doing the work you want to count: towing, a low-loader, a yard shunt, or a GPS jump that only looks like travel. Treat those as movement hypotheses until the hours source and the move type are named, not as utilisation.
Is GPS movement the same as powered-on time or ignition time?
No. Movement, powered-on time and engine hours are different labels. Powered-on time is not automatically work time, and a motion or location change is not a system of engine hours. Keep the labels separate, and lock the hours source the office will use. For the label distinction between engine hours and powered-on time, see Engine Hours vs Powered-On Time.