ELD edits must preserve the original record and include the reason for the change. A carrier may propose corrections, but the driver must be able to review and accept or reject changes to the driver's record; automatically recorded driving time cannot simply be changed to hide movement.
What this means for your fleet
Use a standard edit reason that explains what was wrong, what evidence supports the correction, who proposed it, and what the driver decided. Investigate repeated edits as a process signal.
Choose the correct edit path
| Situation | Permitted response | Do not do |
|---|---|---|
| Driver selected the wrong non-driving status | Driver corrects it with the factual reason and recertifies as required. | Delete the original event or use a vague reason. |
| Carrier finds a likely error | Carrier proposes an edit; the driver reviews and accepts or rejects it. | Silently overwrite the driver’s record. |
| Automatically recorded driving belongs to another driver | Use the documented reassignment/unidentified-driving workflow with evidence. | Convert movement to off duty merely to remove a violation. |
| Personal conveyance or yard move was not selected in time | Preserve the driving event and add the allowed factual annotation. | Shorten driving time by retroactively relabeling the event. |
What to check
Use these checks before changing a log, policy, device, integration, or buying decision.
| Check | How to verify |
|---|---|
| 1. Open the original event and context | Keep the original event ID, status, time, location, vehicle, driver, surrounding events, dispatch or supporting context, and reason review began. |
| 2. Select the correct edit path | Retain the current rule/manual basis, permitted edit path, original value, proposed value, actor, driver-review requirement, and decision. |
| 3. Write a specific annotation | Save the specific annotation stating what was wrong, evidence used, correction, author, timestamp, affected event, and unresolved limitation. |
| 4. Route carrier proposals to the driver | Keep the carrier proposal, reason and evidence, notification, driver acceptance or rejection, timestamps, final record, and audit history. |
| 5. Retain the audit history | Retrieve the original and edited values, every actor and timestamp, annotations, driver responses, certification state, export result, and retention check. |
Common failure modes
- Using vague notes such as “fixed”.
- Pressuring acceptance.
- Changing records to improve a compliance score.
Limits and exceptions
This guide does not decide a fact-specific legal exception, certify a record, or guarantee a compliance, safety, cost, or audit outcome. Keep the original ELD record and any edit history. Use the current official rule for applicability and the exact installed-device manual for screen-by-screen actions.
Sources, review date, and limits
Reviewed August 10, 2026. Each source supports only the point described beside it. Rules and product details can change; recheck dynamic facts before changing a fleet workflow or signing a contract.
- Editing, annotation, certification, and original-record preservation — Federal Motor Carrier Safety Administration.
- Current first-party product, plan, feature, and support representations; dynamic facts require release-date recheck — Factor ELD.
Review the exact operation
Bring the driver, vehicle, trip, jurisdiction, current official rule, and original ELD record for a qualified determination. Factor ELD can demonstrate its current product; rule applicability remains a fleet compliance decision.