Every record says how its wait ended and how complete its GPS trail is: in "What the evidence shows", in the GPS evidence panel and in the timeline (Record stopped).
How a wait ends
- The driver tapped Stop.
- The truck left the terminal: GPS showed it outside the terminal's outline (or its zones) for 3 minutes, with at least 2 precise readings. The end time is backdated to the first reading outside.
- Half a mile from the start: before the truck reached the terminal (a wait started in the line), the same check applies to half a mile around where the wait started.
- The phone stopped reporting: a wait is closed when the phone has been silent for 12 hours, or after 24 hours. It ends at the last time the phone was seen, so the silent hours aren't billed. The record shows "Recording interrupted".
Speed alone doesn't end a wait. Readings less accurate than 100 meters are ignored.
After a GPS jump
A reading that moves faster than a truck can (over 100 mph) never ends a wait by itself. The driver is asked "Did you leave the terminal?":
- Yes, I left: the wait ends, and the record says the driver confirmed it.
- No, I'm still here: the wait goes on, and the record shows "Driver said they were still there", with when.
- No answer: the wait ends once the truck has been outside for 10 minutes, and the record says to check the end time with the driver.
After an automatic stop, the driver can add a note saying what happened (until the carrier sends the charge); it shows in the timeline.
GPS problems worth a look
The GPS evidence is incomplete when, for example:
- there are long gaps (no GPS for over 30 minutes) or too few points for the length of the wait
- many points are imprecise
- there's no GPS near the start or the end
- the location jumped
- a mock-location app was used
Started or ended outside the site, and short gaps, are notes rather than problems. Records with problems show GPS incomplete in the Records list, and carriers are warned before sending them (the fuel buyer sees the same warning).
Records from EDI, the API or an import have no driver GPS: they say "Times reported, not tracked by GPS".
None of this blocks anything: check the times with the driver, then send, approve or dispute.