Check a possible duplicate trip

01 / 04

Compare the trip details

DriveHub does not merge every pair of trips that looks alike. During CSV import it can mark a row as a possible duplicate by comparing its start time and distance with trips already in the app. It does not compare addresses or cars, so a match is not proof.

Timed rows match when starts are within five minutes and distances within 1%. Date-only rows match by calendar day and distance, which can flag two similar drives. Review proposed skips before committing. Live-trip cleanup uses a separate overlap check; it will not discard manually entered trips and may miss duplicates.

1. Open Trips and compare the suspected records’ dates, start times, distance, addresses and vehicle. Check whether one came from automatic tracking and another from an earlier import.
2. If the possible duplicate appeared during import, read the preview row and its date/time before continuing. A date-only source has less detail than a timed record.

02 / 04

Review duplicate matches in an import

The importer checks duplicate rows inside a CSV or Excel (.xlsx) file and against trips already stored. For repeated rows inside one file, the first occurrence is kept. When saved trips match, the preview offers an option to skip those rows; it is on by default. Review the suggested rows first; turning the option off can import a second copy.

1. Open Reports, start Import Trips and choose the CSV or Excel (.xlsx) file.
2. Check the parsed dates, units and duplicate preview. Correct the date order or unit if the preview reveals a misread value.
3. Leave the option to skip trips already in DriveHub on when a row is the same drive. Turn it off only after confirming that a similar row is a separate trip.
4. Complete the import, then open Trips and check the imported period and a few records against the source file.

• Import trips

03 / 04

Remove only the extra record

If both copies are already saved, open each trip and compare the full details before deleting anything. Keep the record with the correct time, distance, addresses, vehicle and any review answers. Deleting removes its distance from totals and reports on your devices; the matching rule does not automatically clean up older duplicates for you.

1. Open the trip you identified as the extra copy, choose Delete Trip and confirm.
2. Return to Trips and confirm the intended copy remains. Compare with the source file first if you are unsure which record is correct.
3. To recover a deleted trip, open Trips → Recently Deleted and choose Restore within 30 days.

• Make a mileage report

04 / 04

When the match is wrong or missing

A false match is possible when two separate drives start close together and have nearly the same distance. A duplicate can also escape the preview when its time differs by more than five minutes, its distance differs by more than 1%, or source rows provide only incomplete dates. The importer cannot infer intent from similar addresses or a matching car.

If you imported the wrong row, compare the source file with Trips before importing it again; the importer may skip it as a match. A deleted trip is kept in Recently Deleted on this iPhone for 30 days. Restore it from there; permanently deleting it removes the recovery copy.

1. Check the report period, vehicle and trip filters after correcting the list.

• Review trips and reports