Compliance • ELDT.LIVE
ELD Log Edits and Certification: What Drivers Can Change, Must Approve, and Cannot Erase
An ELD correction is not a delete button. Learn how drivers review and certify logs, annotate edits, handle carrier proposals and unidentified driving, and protect the original record.
Accurate logs require active review
An ELD automatically captures important events, but it does not know every fact about a driver's workday. It may record vehicle movement while the wrong account is active, remain in an on-duty status after a task ends, or lack a manually entered period of work performed away from the truck. Federal rules place responsibility on both the driver and motor carrier to ensure ELD records are accurate. Treat daily review as a safety and compliance task, not a quick screen tap at the end of a shift.
Know the difference between an edit and an annotation
An edit changes or adds information in the electronic record within the ELD's permitted functions. An annotation is a note explaining a record, event, entry, or edit. The original record is not overwritten simply because the display now shows a corrected duty status. Under 49 CFR 395.30, each change or addition must be annotated. A useful note states what was wrong, what actually occurred, and why the correction is being made without adding irrelevant personal information.
The driver reviews before certifying
For each 24-hour period, the driver must review the ELD record, correct inaccurate information, enter missing information, and certify accuracy. Check duty-status boundaries, locations, vehicle and trailer identifiers, carrier name, shipping-document information when required, co-driver information, special categories, annotations, and unidentified driving prompts. Compare the graph with the work actually performed, not only with the ELD's remaining-hours summary.
Certification follows the final required entry
Section 395.30 requires the driver to use the ELD certification function after the final required entry has been made or corrected for the 24-hour period. Selecting the certification response is an affirmative statement that the data entries and record of duty status are true and correct. Do not certify merely because a dispatcher, payroll deadline, or device reminder appears. Resolve known errors and document any necessary correction first.
Submission and certification are connected
The driver submits certified ELD records to the motor carrier. Section 395.8 requires submission within 13 days of the 24-hour period covered by the record, although a carrier may set an earlier internal deadline. Certification does not freeze an inaccurate log forever: if an edit becomes necessary after submission, the driver must review the change and recertify the corrected record.
Drivers can correct permitted mistakes
Subject to ELD edit limitations, a driver may correct a duty status, enter omitted on-duty time, add missing information, and annotate an event. Common examples include correcting a forgotten status change after loading, entering work performed before reaching the truck, fixing a vehicle identifier, or explaining a location issue. Use the ELD's supported edit process and prompts; do not create a second record or alter a device outside its normal functions.
Automatically recorded driving is protected
An ELD records vehicle motion as driving time. FMCSA guidance states that an edit may not reduce the total driving time automatically captured by the device. A driver cannot simply convert inconvenient driving to off duty, sleeper berth, or on-duty not driving. Limited assignment procedures exist for unidentified driving and certain team-driver mistakes, but the accumulated vehicle-motion time is not erased.
The original event remains in the record
Federal rules prohibit the carrier from altering or erasing the original hours-of-service information, source data, or ELD information that uses those data. The device keeps the original event together with permitted edits, annotations, identities, dates, and times. This audit trail protects record integrity and explains why a correction may still reveal what the ELD first recorded. A clean-looking graph is not proof that the original event disappeared.
Carrier staff propose; the driver decides
After reviewing a driver's submitted records, authorized carrier personnel may propose an edit to improve accuracy. They may not request edits before the driver submits the record. The driver must confirm or reject the proposed change, implement the appropriate correction, and recertify and resubmit before a carrier-proposed change takes effect. A back-office suggestion is not automatically true merely because it came from safety, payroll, or dispatch.
Review the evidence behind every proposal
Compare a carrier edit with the actual trip: dispatch timestamps, bills, gate records, fuel receipts, location data, messages, and your own notes. Accept only a change that accurately describes the duty status. If a proposal is wrong, reject it and give a concise explanation through the available process. If part of it is correct, communicate what should be changed rather than approving a broader inaccurate adjustment for convenience.
False certification and coercion are prohibited
A carrier may not coerce a driver to make a false certification. A driver or carrier also may not make a false duty-status report or tamper with the ELD so required data are not accurately recorded and retained. Pressure to relabel loading as off duty, remove driving, invent sleeper time, or accept another person's movement should be documented and escalated through the carrier's safety process. Never trade an accurate record for a load appointment.
Unidentified driving starts when nobody is logged in
When a CMV moves without an authenticated driver, the ELD associates the operation with a single Unidentified Driver account. This can happen when a driver forgets to log in, maintenance moves the vehicle, a yard employee relocates it, or the wrong account is active. The event is not automatically assigned based on who later uses the truck. It must be reviewed and resolved using the facts.
Respond to the prompt when you log in
When prompted, a driver must review unassigned driving time and either assume the records that belong to the driver or indicate that the records are not attributable to that driver. Check vehicle, date, time, location, duration, and surrounding events before choosing. Do not claim movement simply to clear the screen, and do not reject your own movement because accepting it would reduce available hours.
The carrier must resolve unidentified records
The motor carrier must review unidentified driving records and either annotate why time remains unassigned or assign the event to the correct driver. The carrier retains unidentified driving records for at least six months and must make relevant records available during an authorized safety inspection, audit, or investigation. Repeated unidentified events should trigger a process review—login training, account controls, maintenance procedures, and device operation—not routine unexplained rejection.
Team-driver corrections have special conditions
If an ELD assigned driving time to the wrong member of a team, Section 395.30 permits reassignment when both drivers were identified as co-drivers in each other's records for that period. Each affected driver should review the event and follow the ELD confirmation process. This narrow team correction is not general permission to move driving time between unrelated accounts, dispatchers, mechanics, or a convenient driver profile.
Missing on-duty time must be added
An ELD cannot automatically detect every non-driving task. Warehouse work, inspection, loading, training, fueling, paperwork, compensated work for another employer, and other qualifying activities may need a manual entry when performed away from the connected vehicle. Add the correct beginning and ending time, duty status, location, and annotation. Logging into the truck later does not transform earlier work into off-duty time.
Keep the record current during the day
Section 395.8 requires records to remain current to the last duty-status change. Change status when the work changes instead of relying on a large reconstruction at the end of the shift. Before moving, confirm the correct driver is authenticated, the vehicle is selected, co-driver information is accurate, and any special driving category is properly authorized and selected. Small real-time checks prevent difficult edits later.
Prepare for roadside review before departure
Make sure the ELD can display or transfer the current day's record and the required previous records, and that missing information from another device or carrier is available in the required form. Know the device's data-transfer steps, display mode, malfunction indicator, and instruction materials. An officer sees the complete event history and annotations, so concise, factual notes are more useful than vague comments such as 'fixed,' 'dispatch said,' or 'system error.'
Use a disciplined end-of-day routine
Park safely; confirm the final duty status; review every status segment and location; add missing work; resolve unidentified-driving prompts; read carrier-proposed edits; annotate each correction; verify vehicle, trailer, shipment, and co-driver information; certify only when accurate; submit under the carrier procedure; and recheck any record returned for correction. This guide reflects Title 49 eCFR displayed as current through November 3, 2026 and reviewed November 5, 2026; verify current rules, ELD instructions, and carrier procedures for the actual operation.
Educational summaries help you prepare, but official FMCSA and state licensing sources remain the authority for current requirements.
Official sources
49 CFR 395.30 — ELD submissions, edits, annotations, and retention ↗49 CFR 395.32 — Non-authenticated driver logs ↗49 CFR 395.8 — Driver's record of duty status ↗Appendix A to 49 CFR Part 395 Subpart B — ELD functional specifications ↗FMCSA — Editing and Annotations ↗FMCSA — ELD-recorded data that may not be edited ↗ELDT.live independently creates and reviews its content. We do not present practice questions as official examination questions and do not guarantee a licensing result.