DriveHubSUPPORT / TRIPS AND REPORTS
Investigate a distance that looks wrong
A distance can represent a recorded GPS trip, an estimate, or a value you entered. Check which one you are viewing before making a correction.
← All support answers01 / 04
First distinguish a recorded measurement from an estimate or manual value.
Open the trip and check its Route area and source information. A live recorded trip may have a GPS route. Some reconstructed routes are estimates, and a hand-entered trip has the distance you typed but no recorded GPS track. A route drawn along roads after GPS interruptions is not the same as a continuous GPS stream.
Reports use the distance unit selected in DriveHub Settings. Some trip and odometer screens may display a vehicle-specific unit instead, so check which screen and unit you are comparing before using another document or dashboard reading.
- Open the trip details and note the distance and displayed unit.
- Check whether the Route area says a route was recorded, rebuilt, or not recorded.
- If the trip was entered by hand, compare the value with the source you used when entering it.
02 / 04
Confirm the vehicle and journey endpoints before editing anything.
Check that the trip is assigned to the car you used. Vehicle settings can affect the unit displayed and the context used in a report. Then review the From and To names. An endpoint name is useful context, but it does not establish the exact route or correct the distance by itself.
Use a recorded route to understand the captured journey. You cannot stretch, shorten or redraw its GPS track to match an expected total. Do not add a duplicate to force a match.
- Check the vehicle shown in the trip header.
- Review From and To for a mistaken place or a name that needs correction.
- If the trip itself is missing or duplicated, use the relevant trip review action rather than adjusting an unrelated distance.
03 / 04
When readings bracket a period, use them to assess recorded distance across that same period.
An odometer reading is the car’s own total distance at a point in time. Two readings around a period give the distance the car travelled between them; trips DriveHub recorded over that same period provide a separate total. The difference can reveal that the log and the car’s odometer do not match, but it does not identify the exact missing journey on its own.
Compare the same vehicle and period. One reading or mismatched dates cannot provide a like-for-like check. Odometer requirements depend on country and filing setup.
- Open the vehicle’s odometer area and check the dates and values of readings around the period.
- Compare the odometer change with recorded trip distance for those same dates and that vehicle.
- Add or correct a reading only from the car’s actual odometer; do not use the trip total as a substitute.
04 / 04
Make a focused correction, then inspect the trip and export again.
Correct an editable vehicle or type only when verified. Trip details cannot edit a trip’s date or total distance. For a mistaken manual entry, save the right details, remove it, add it again and check for duplicates. Treat route estimates as estimates, not exact GPS evidence.
After saving, reopen the trip and confirm the value, unit and route note. Reports are generated from the saved trip details and report settings, so make a new export to verify the revised result. A report comparison does not alter the underlying GPS route.
- Correct only a trip detail that the review screen lets you change and that you have verified.
- For a wrong manual date or distance, record the right values, remove the mistaken entry, add it again, and check there is no duplicate.
- Reopen the trip and verify its details; export the report again to check the updated row or total.