When an ELD location appears wrong, preserve the event and compare its timestamp, recorded location, vehicle movement, device status, and vendor diagnostics. Do not alter a duty record merely to make a map look cleaner.
What this means for your fleet
Compare the ELD event timestamp, location or location description, vehicle movement, phone permissions, and another trusted location source. Ask the provider to identify the cause; preserve the original record and annotate only confirmed corrections.
Diagnose the pattern before changing anything
| Observed pattern | Check next | How to verify the result |
|---|---|---|
| One point offset while the truck is stationary | Event type, timestamp, required location precision, nearby reference point | The provider identifies expected behavior or a confirmed defect |
| Repeated jumps during movement | Positioning diagnostic, phone permissions, device placement, power, event sequence | A repeat route no longer produces the pattern |
| Location belongs to another truck | VIN, vehicle profile, device serial, reassignment history | Identity is corrected and new engine-on events map to the right vehicle |
| Map pin differs from duty record | Separate optional live map data from required ELD event data | The source field and correction authority are documented |
What to check
| Check | How to verify |
|---|---|
| 1. Check whether the issue is isolated or repeated | Compare similar events across several trips and timestamps. Note whether the offset repeats with the same device, phone, vehicle, or location. |
| 2. Compare timestamps and movement | Save ELD event times, vehicle movement, location descriptions, and a second trusted location source for the same interval. |
| 3. Capture device status and permissions | Capture device/app versions, GPS and background permissions, connection state, diagnostic events, and screenshots. |
| 4. Restart only under the vendor procedure | Record the vendor procedure used, pre-restart evidence, exact restart time, affected records, and post-restart test. |
| 5. Open a support case with evidence | Keep the support case, evidence attached, vendor explanation, remediation, affected dates, and repeat-test result. |
Common failure modes
- Calling every map offset a compliance violation.
- Changing duty status to fix a pin.
- Discarding screenshots and event IDs.
Limits and exceptions
Use this guide to plan your checks; it does not determine whether a legal exception applies, certify a record, or guarantee compliance, safety, savings, or audit results. Preserve original ELD records and edit history. Use the current rules to determine applicability and the manual for your installed device for operating instructions.
Sources and review date
Reviewed August 10, 2026. Check the latest rules and product information before changing your procedures or signing a contract.
- FMCSA ELD technical questions — Federal Motor Carrier Safety Administration.
- Editing, annotation, certification, and original-record preservation — Federal Motor Carrier Safety Administration.
- Factor ELD products, plans, and support — Factor ELD.
Reproduce the issue before changing the record
Have the event time, vehicle, driver, device and app versions, screenshot or code, and recent maintenance or reassignment history ready. Ask Factor ELD to show the relevant product workflow. Your fleet remains responsible for compliance decisions.