Hours of Service • ELDT.LIVE
ELD Unidentified Driving Records: How Drivers and Carriers Must Review, Assign, and Retain Them
An ELD keeps recording when a CMV moves without an authenticated driver. Learn how drivers claim or reject the time, how carriers resolve unassigned events, what remains visible at roadside, and why the original record cannot simply be deleted.
Unidentified driving is a record—not a blank space
When a commercial motor vehicle begins moving and no driver is logged into the ELD, 49 CFR 395.32 requires the device to associate the non-authenticated operation with a single account labeled Unidentified Driver. The movement does not disappear, become off duty, or wait for someone to type it later. It becomes an electronic event that the responsible driver and motor carrier must review and resolve accurately.
The best prevention is to authenticate before motion
A driver should log into the correct carrier account, select the correct vehicle and trailer information, identify a co-driver when applicable, review the displayed duty status, and confirm that the ELD is connected before releasing the brakes. A shared login, another driver's account, an expired session, or a rushed tractor swap can place real driving on the wrong profile. Make the login check part of the same start-up routine as mirrors, brakes, lights, and the pre-trip inspection.
The ELD warns the driver and limits screen use
FMCSA guidance explains that if no driver is logged in, the ELD provides a visual or visual-and-audible warning once the CMV is in motion. It records accumulated driving and on-duty-not-driving time under the Unidentified Driver profile and allows no entry other than a response to the login prompt. A driver should stop at the first safe opportunity and authenticate; trying to operate the screen while moving creates a safety problem without curing the missing attribution.
Logging in creates a required review decision
Under Section 395.32(b), a driver prompted with unassigned driving must review the records. The driver must assume the events that belong to that driver or indicate that the events are not attributable to the driver. Tapping through the prompt without checking the vehicle, date, time, location, duration, odometer, engine hours, and surrounding work can place another person's driving on the wrong record or leave the driver's own time unresolved.
Claim the time when the facts show you drove
If the vehicle, route, time, and work match the driver's activity, the driver should claim the event through the ELD. The resulting record must reflect the driver's actual hours of service, including the effect on the 11-hour driving limit, 14-hour window, break requirement, and 60/70-hour calculation as applicable. A delayed claim does not create extra legal hours; it corrects the account to which the already-recorded movement belongs.
Reject a record that is not yours
A driver should indicate that an event is not attributable to that driver when the facts do not match. Before rejecting, compare the truck and trailer assignment, terminal time zone, location, dispatch or gate records, co-driver information, and shift timeline. Use the ELD's annotation function when available to state a concise factual reason, such as 'vehicle moved by shop before my assignment began,' rather than guessing at the operator or writing a vague note.
A rejection does not erase the event
FMCSA's current Unidentified Driving Time FAQ says rejected unidentified-driving events must remain available for roadside review for eight days and should be included in the ELD output file. Rejection means the driver disputes attribution; it is not a delete button. The motor carrier still must investigate and either assign the event correctly or annotate why it remains unassigned.
The carrier has an independent review duty
Section 395.32(c) requires the motor carrier to ensure that unidentified-driving records are reviewed. For each record, the carrier must either annotate why the time remains unassigned or assign it to the appropriate driver so the driver's hours of service are correct. A daily exception queue, named reviewer, supporting-document check, and documented escalation path are more reliable than waiting until an audit or roadside inspection reveals a growing backlog.
A carrier assignment is a proposal the driver must accept
FMCSA explains that unidentified time can be resolved when the driver claims it at the prompt or when the carrier later assigns it to the appropriate driver. A carrier assignment must be accepted by the driver. Authorized support staff may investigate and suggest the correction, but they cannot use the back office to make an inaccurate record final without the driver's confirmation rights.
Use evidence before assigning an event
A defensible review compares the ELD's vehicle, time, location, odometer, and engine-hour data with dispatch records, bills of lading, fuel transactions, tolls, gate logs, maintenance work orders, GPS or telematics data, trailer moves, DVIRs, and driver schedules. The goal is correct attribution, not simply clearing a dashboard alert. If evidence is incomplete, document what was checked and why the event remains unassigned while the investigation continues.
Original ELD events remain in the audit trail
When a driver assumes unidentified time, FMCSA says the original unidentified event remains with an inactive status and the system creates a new event for the driver using the original elements plus required driver input. Section 395.30 likewise protects original information and the edit history. A clean graph display does not mean the first record vanished, and carrier personnel should never promise that an event can be wiped from the system.
Automatically recorded driving cannot be shortened
The ELD technical specifications do not allow automatically recorded driving time to be shortened. FMCSA permits a driver who receives unidentified records to indicate an authorized special driving category when appropriate, but the facts and carrier authorization must support that category. Neither a personal-conveyance label, a yard-move label, nor an annotation can be used to hide highway driving or trim the recorded duration.
Correct an accidental claim through a documented edit
FMCSA says a driver who mistakenly accepts an unidentified event may edit the record afterward. The ELD must prompt for an annotation explaining the correction, and the carrier may also suggest an edit for the driver to confirm. Preserve the original, identify the actual operator if known, and explain the mistake. Do not offset a wrong claim by creating false off-duty time somewhere else in the log.
Team-driver corrections require both drivers' participation
If a team driver failed to log in and the movement was recorded under the co-driver, FMCSA guidance allows the generated data to be reassigned when both drivers were identified in each other's records as co-drivers. Each driver must confirm the change before it takes effect. The carrier should compare berth periods, fuel and dispatch events, and the drivers' explanations rather than shifting time to whichever person has more hours available.
Shop, wash-bay, and yard movements still need attribution
A mechanic, fueler, washer, hostler, or other employee may move an ELD-equipped CMV while the road driver is absent. The device will still record motion. The carrier should use a compliant process that identifies the actual operation and its regulatory treatment instead of routinely assigning every short move to the next driver. Drivers should review timestamps around maintenance, tractor swaps, loading, and terminal staging before accepting them.
Some related events can remain on the unidentified profile
Resolving the driving segment does not guarantee that every associated record moves to a driver's account. FMCSA notes that intermediate logs, engine power-up and shutdown events, and malfunction or diagnostic records may remain associated with the Unidentified Driver profile because those event types cannot be edited. A remaining system event is not automatically proof that the review failed; the carrier should understand which event types are attributable and document the disposition.
Thirty minutes triggers the unidentified-driving diagnostic
Under the ELD technical specifications, more than 30 minutes of unidentified driving accumulated in a 24-hour period triggers an unidentified-driving-records data diagnostic event. FMCSA says the indicator is activated across drivers logged into that ELD for the current day and the following seven days. The light is a compliance signal to review the underlying records, not permission to assign them to the first available account.
Clearing the diagnostic does not delete the records
FMCSA clarifies that the diagnostic can clear when the aggregate unidentified driving time for the current 24-hour period and previous seven consecutive days falls to 15 minutes or less. Only the diagnostic status becomes inactive. The underlying events remain in the required record history. Treating a cleared indicator as proof that all records were erased misunderstands how the ELD audit trail works.
The roadside view includes an Unidentified Driver report
Appendix A requires the inspected driver's profile and the Unidentified Driver profile to be available as separate roadside reports by display or printout when relevant unidentified records exist for the current 24-hour period or previous seven days. An inspector can therefore see unresolved or rejected events associated with the vehicle. Resolve issues before dispatch and be prepared to explain accurate annotations without altering the record during the inspection.
Carrier retention lasts at least six months
Section 395.32 requires the motor carrier to retain unidentified-driving records for each ELD for at least six months from the date of receipt. The carrier must make the applicable records available during an authorized safety inspection, audit, or investigation. Retention should cover resolved, rejected, and annotated records along with the preserved original information and edit history—not only the final graph that dispatch sees.
Certification still matters after the record is corrected
Section 395.30 requires the driver to review and certify that the ELD entries are true and correct. When a carrier proposes an edit or assignment, the driver confirms or rejects it and, when accepted, resubmits the record. A driver should not certify solely because dispatch requests it, and a carrier may not coerce a false certification. Read the updated totals, annotations, and duty-status sequence before approving the day.
Unplugging the ELD creates more evidence, not less
Disconnecting the device from the engine control module is not a way to avoid attribution. FMCSA guidance says an odometer jump after the ELD is unplugged and reconnected must be captured as a malfunction, and a loss of engine synchronization exceeding the technical threshold creates its own malfunction record. The ELD, ECM, GPS, dispatch, fuel, and toll data may expose the gap. Report a real equipment problem through the malfunction procedure rather than manipulating the connection.
Drivers need one accurate account and protected credentials
FMCSA's ELD guidance says a driver has one unique account with a carrier and a unique identification number and password. Do not share credentials, keep a previous driver's session open, or use a generic road-driver login. During a tractor exchange, the outgoing driver should finish and certify as required, log out, and ensure the incoming driver authenticates before movement. Account discipline prevents both unidentified time and time charged to the wrong person.
A carrier workflow should close the loop without coercion
A practical process reviews unidentified events daily; preserves the original data; contacts the likely driver with the supporting facts; records acceptance, rejection, or a reasoned unassigned annotation; verifies the driver's recertification when needed; and trends the causes by vehicle, terminal, shift, and user. Repeated events may point to training gaps, failing hardware, bad account provisioning, hurried swaps, or weak yard procedures. The corrective action should address the cause, not pressure drivers to accept time they did not operate.
Use a two-minute pre- and post-trip ELD routine
Before movement: authenticate, verify carrier and driver, select the vehicle and co-driver, confirm the ELD connection, and review pending unassigned time. After the trip: inspect the graph, compare miles and locations with the work performed, resolve prompts with truthful annotations, review carrier-proposed changes, and certify only when accurate. Report a login, synchronization, or account problem immediately so it can be corrected while the evidence is fresh.
Verify the current rule and the actual event
This guide was reviewed November 21, 2026 against 49 CFR 395.30 and 395.32 and Appendix A displayed by eCFR as current through November 19, 2026, plus current FMCSA ELD guidance. It is an educational compliance guide, not a determination of who operated a particular vehicle. Drivers and carriers should use the actual ELD data, supporting documents, carrier procedure, current federal text, and any applicable exception before assigning or certifying an event.
Educational summaries help you prepare, but official FMCSA and state licensing sources remain the authority for current requirements.
Official sources
49 CFR 395.32 — Non-authenticated driver logs ↗49 CFR 395.30 — ELD submissions, edits, annotations, and retention ↗Appendix A to Part 395 — ELD functional specifications ↗FMCSA ELD FAQ — Unidentified Driving Time ↗FMCSA — Editing and Annotations ↗FMCSA — Using ELDs ↗FMCSA Guidance — Carrier handling of unassigned driving records ↗FMCSA Guidance — Data recorded for an unidentified driver ↗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.