AI ELD
Apr 6, 2026
Most fleet managers recognize the alert when it appears. The back-office system flags a driving segment under an account that belongs to nobody, logged automatically because the vehicle moved while no driver was authenticated. The segment sits there, unresolved, accumulating against the carrier's compliance record while the underlying question goes unanswered: who drove the truck, and why does this keep happening?
This article covers what unidentified driving actually is under FMCSA's technical specifications, the exact conditions that convert it from a minor data note into a recordable diagnostic event, every legitimate reason it occurs, and the specific steps both drivers and carriers are legally required to take to resolve it.
FMCSA's ELD Technical Specifications, found in 49 CFR Part 395, Subpart B, Appendix A, define "Unidentified Driver" precisely: it refers to the operation of a commercial motor vehicle equipped with an ELD without an authenticated driver logged into the system. When this happens, the ELD automatically captures driving time and attributes those records to a dedicated "Unidentified Driver account" until the motor carrier and the applicable driver review the records and assign them correctly under 49 CFR 395.32.
This is not a malfunction. It is not a technical failure. Unidentified driving is a data diagnostic condition that the ELD is designed to detect, record, and flag for human review. The device is working exactly as intended when it captures unidentified driving. The compliance obligation is what happens next.
The governing regulation for the carrier side is 49 CFR 395.32(c): a motor carrier must either annotate the record with an explanation of why the time remains unassigned, or assign the time to the appropriate driver. The motor carrier must retain unidentified driving records for a minimum of six months from the date of receipt as part of its HOS ELD records, and those records must be available to authorized safety officials upon request.
There is a threshold most carriers do not know exists, and crossing it changes the compliance status of every driver on that vehicle.
Under section 4.3.2.8.2 of 49 CFR Part 395, Subpart B, Appendix A, an unidentified driving records data diagnostic event is triggered when more than 30 minutes of driving in a 24-hour period are recorded under the unidentified driver profile. When that threshold is crossed, three things happen simultaneously:
First, the data diagnostic indicator activates on the ELD. Second, it activates not just for the driver who eventually logs in, but for all drivers authenticated on that device, covering the current 24-hour period and the following seven days. Third, the diagnostic event becomes a visible flag in the back-office system that an investigator reviewing the carrier's records will find immediately.
Below 30 minutes of aggregate unidentified driving in a 24-hour period, the event is recorded internally but does not trigger the diagnostic indicator. FMCSA guidance confirms that below the 15-minute aggregate level, the event does not generate a data diagnostic notification at all. This matters operationally: a brief move of a few minutes to reposition a truck at a terminal is not the same compliance exposure as 45 minutes of unidentified highway driving.
The cascade effect on other drivers is the detail most carriers miss. When a vehicle repeatedly generates unidentified driving above the 30-minute threshold, every driver who later logs into that ELD sees the diagnostic indicator for a full week. If a compliance review is conducted during that period, the investigators working through the driver sample encounter a fleet-wide diagnostic warning that signals inadequate carrier oversight, not just one driver who forgot to log in.
Understanding all the situations that legitimately generate unidentified driving is as important as understanding the regulatory response, because the resolution path depends on knowing what actually happened.
Driver log-in failures are the most common cause and the one most often discussed. The ELD begins recording driving automatically when the vehicle exceeds 5 miles per hour. If a driver climbs in, starts the engine, and pulls away before authenticating on the device, those first minutes of movement go into the unidentified driver profile. The same happens when a driver fails to log out at shift end and a second driver takes the vehicle without logging in under their own credentials.
Yard moves and facility moves generate a substantial volume of unidentified events for fleets operating terminals or distribution facilities. A mechanic repositioning a truck for an inspection, a yard hostler moving a trailer to a dock, or a driver moving a vehicle between parking spots without logging in all create unidentified driving records. Under 49 CFR Part 395, Subpart B, Appendix A, carriers can configure the ELD to authorize a yard move category for specific drivers, which resolves the compliance issue for those movements. Fleets that have not set up yard move authorization in their ELD system settings are generating avoidable unidentified events every day.
Short-haul exempt drivers operating ELD-equipped vehicles are a source of unidentified driving that many carriers do not anticipate when they first set up their fleet. Short-haul drivers operating within the 100 air-mile radius who meet the requirements under 49 CFR 395.1(e) are not required to use an ELD. But when those drivers operate vehicles equipped with ELDs shared with non-exempt drivers, the device records their driving under the unidentified driver profile. FMCSA guidance specifically addresses this scenario: carriers can configure the ELD to mark a driver account as exempt, which prevents the unidentified driving diagnostic from triggering when that driver moves the vehicle.
Team driver scenarios produce unidentified driving when co-driver handoffs are not executed correctly in the ELD. If Driver A is logged in and driving, and Driver B takes over without completing the handoff sequence, the continued movement may be attributed to Driver A or fall into an unidentified segment depending on the ELD's specific implementation.
Agricultural exemption operations generate unidentified events when drivers operating under the agricultural HOS exemption move ELD-equipped vehicles during the exempt period. FMCSA's guidance is specific: the driver should reject the unidentified driving records and the carrier should annotate the record to explain that the vehicle was operating under an agricultural HOS exemption.
The distinction between these causes matters at the resolution stage because the annotation or assignment must accurately reflect what actually happened. Annotating a mechanic's yard move as "driver forgot to log in" is inaccurate documentation, and inaccurate annotations during a compliance review create additional problems rather than resolving the original one.
Every time a driver logs into an ELD that has unidentified driving records on it, the device is required to prompt them with a warning indicating that unassigned driving time exists on the vehicle. This prompt is not optional and cannot be bypassed. The driver must take one of two actions before proceeding.
If the driving belongs to the logging-in driver, they accept it. The records then transfer to their profile and are recorded under their authenticated account. One critical point from the technical specification: the ELD must not allow automatically recorded driving time to be shortened. A driver cannot accept unidentified driving and then reduce the time associated with it. The acceptance applies to the full recorded segment.
If the driving does not belong to the logging-in driver, they must reject it. The rejection indicates that the records are not attributable to them. Under the CVSA ELD inspection standards, rejected unidentified driving events must remain available on the device for review at roadside for eight days and must be included in any output file transferred to law enforcement. The driver's rejection does not erase the records; it marks them as reviewed but unattributed, which then requires carrier-side resolution.
There is also a category of events that cannot be assumed by any driver at all. Intermediate logs, login and logout records, engine power-up and shutdown events, and malfunction and diagnostic records are not editable and cannot be transferred from the unidentified driver profile to a driver's account. When a driver assumes unidentified driving time, the associated duty status changes move to their profile, but these background system events remain under the unidentified driver profile. FMCSA guidance notes that ELD providers may program their systems to annotate these remaining events with a notation that they were assumed by the named driver, which allows inspectors to reconcile the record without treating it as an unresolved gap.
Once a driver has reviewed unidentified driving records, the obligation shifts entirely to the motor carrier. Under 49 CFR 395.32(c), the carrier must assign the time to the correct driver or annotate the record with a written explanation of why it cannot be assigned. Neither option is a default. The carrier must take an affirmative action, and that action must be documented in the ELD system with enough specificity to explain the event.
Annotations like "unknown" or "no driver" are not adequate explanations under a compliance review. An annotation that explains the event accurately, whether that is a mechanic move, a yard repositioning by a specific non-driver employee, a short-haul exempt driver operating the vehicle, or an agricultural exemption scenario, is what satisfies the regulatory requirement.
During a roadside inspection, the unidentified driver profile is treated as a separate report. FMCSA's technical specification at section 4.8.1.3 of Appendix A requires that both the driver's profile and the unidentified driver profile be available at roadside either by printout or display, but only when unidentified driver records exist for the current 24-hour period or the previous seven days. If there are no such records, the separate report is not required. If they do exist, both must be provided to the officer. This is a specific procedural requirement that officers are trained to check, and a driver who cannot produce the unidentified driver report when it exists is generating an additional inspection finding on top of the underlying unidentified driving records.
For carriers, unresolved unidentified driving found during a compliance review is treated as a carrier-level violation, not merely a driver data issue. An auditor finding a pattern of unidentified events across multiple vehicles with no carrier annotations and no driver assignments is seeing evidence of inadequate safety management controls. Under the same 10% critical violation threshold discussed in the fleet manager logbook audit checklist, a pattern of unresolved unidentified events across 30 reviewed records can trigger a compliance rating consequence.
The most effective resolution approach separates the driver-side and carrier-side steps clearly, because different systems and different people are responsible for each.
Driver-side resolution at login requires three things: recognizing the prompt when it appears, accurately identifying whether the driving belongs to them, and completing the accept or reject action before proceeding. Carriers that train drivers on this specific sequence rather than assuming they will figure it out from the ELD interface see significantly fewer unresolved unidentified events in their back-office system. The prompt should not be dismissed without action, and the action should not be accepted by default when the driver is unsure whether the driving is theirs.
Carrier-side resolution in the back office should be treated as a daily task for fleet managers, not a monthly reconciliation item. The AI ELD fleet dashboard surfaces unidentified driving events across all vehicles in real time, so the back-office review does not require manually checking each vehicle's log individually. For each event, the fleet manager should determine the cause from available records, assign the time to the correct driver if the driver can be identified, or annotate the record with an accurate explanation if assignment is not possible. Carriers operating under AI ELD's monitoring plan have a team that flags these events for resolution within the shift rather than the following business day.
For rejected events, the carrier annotation is the only resolution path. The records stay in the system, they remain available at roadside, but a clear and accurate carrier annotation converts a potentially problematic finding into a documented and explainable record.
For events caused by short-haul exempt drivers on shared vehicles, the long-term fix is configuring the exempt driver accounts in the ELD system so the device does not generate diagnostic events when those drivers operate the vehicle. This is a one-time setup task but it eliminates a recurring source of unidentified events for carriers who run mixed exempt and non-exempt fleets.
A single unidentified driving event from a driver who pulled away before logging in is a training issue. A pattern of unidentified events across multiple vehicles over multiple days is a process failure.
The practical signal from the fleet manager's audit perspective is that unidentified driving frequency tracks closely with how well a fleet's ELD login procedures are actually followed in the field versus how they exist on paper. Fleets that see the same vehicles repeatedly generating unidentified events during the same shift patterns typically have a dispatch or dispatch handoff process that does not account for ELD authentication. Fixing the dispatch process eliminates the unidentified events far more reliably than re-training individual drivers.
The six-month retention requirement for unidentified driving records also means that an FMCSA audit conducted today will review records going back to the same period last year. A fleet that resolved its unidentified driving problem three months ago but did not properly annotate the events from four months ago still has six months of exposure in its records. The annotation and assignment obligations apply retroactively to any records still within the retention window.
Understanding the full mechanics of what generates and what resolves unidentified driving is the prerequisite for reducing it. Carriers that treat it as a simple "driver forgot to log in" problem miss the configuration fixes, the carrier-side annotation obligations, the roadside availability requirements for rejected events, and the diagnostic cascade that affects every driver on a vehicle that crosses the 30-minute threshold. The ELD system for trucks functions correctly when it flags unidentified driving. The compliance obligation is what the carrier does with the flag.
For questions about how to configure exempt driver accounts, set up yard move authorizations, or review unidentified events across your fleet, the AI ELD support team can walk through the setup, or you can start a free 14-day trial to see how unidentified events surface in the dashboard.
eCFR. "49 CFR 395.32: Non-authenticated driver logs." The governing regulation placing the assignment or annotation obligation on motor carriers, and the six-month retention requirement for unidentified driving records. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-395/subpart-B/section-395.32
eCFR / Cornell Law. "49 CFR Part 395, Subpart B, Appendix A: Functional Specifications for All Electronic Logging Devices." Sections 4.1.5 (Unidentified Driver account definition), 4.3.2.8.2 (driver review and assignment mechanism; driving time cannot be shortened), 4.8.1.3 (roadside requirement for both driver and UD profile reports). Source for the 30-minute threshold that triggers the data diagnostic event and the 7-day cascade to all authenticated drivers on that ELD. https://www.law.cornell.edu/cfr/text/49/appendix-A_to_subpart_B_of_part_395
FMCSA. "ELD Malfunctions and Data Diagnostic Events FAQs." March 2022 (revised). Source confirming that an unidentified driving records data diagnostic event occurs when more than 30 minutes of driving in a 24-hour period is recorded under the unidentified driver profile. Distinguishes data diagnostic events from compliance malfunctions. https://www.fmcsa.dot.gov/regulations/hours-service/elds/eld-malfunctions-and-data-diagnostic-events-faqs
FMCSA. "FAQ: What must a motor carrier do with unassigned driving records from an ELD?" Confirms the carrier must annotate or assign under 49 CFR 395.32(c); confirms the six-month retention obligation. https://www.fmcsa.dot.gov/hours-service/elds/what-must-motor-carrier-do-unassigned-driving-records-electronic-logging-device
FMCSA ELD FAQ. "Unidentified Driving Time." Complete FAQ page covering driver review and accept/reject obligations, the short-haul exempt driver configuration option, agricultural exemption annotation procedures, the requirement for rejected events to remain available at roadside for 8 days, and intermediate event types that cannot be assigned to any driver profile. https://eld.fmcsa.dot.gov/FAQ/Topics?name=Unidentified_Driving_Time
FMCSA ELD Technical Specifications FAQ. Source for the treatment of event types 2, 5, 6, and 7 (intermediate, login/logout, power-up/shutdown, malfunction/diagnostic) as non-editable and non-assignable; source for the carrier's ability to suggest edits routed to the driver for confirmation under 49 CFR 395.32(c). https://eld.fmcsa.dot.gov/FAQ/Topics?name=ELD_Technical_Specifications
CVSA. "ELD Inspection Bulletin 2017-05." Source for the roadside enforcement treatment of unidentified driving: both the driver profile and the unidentified driver profile must be available as separate reports; confirmed that rejected events must remain in the output file and be available for roadside review for 8 days. https://www.cvsa.org/wp-content/uploads/gravity_forms/5-fa84048acc570f0b993b2091535c6442/2024/03/Inspection-Bulletin-2017-05-ELDs.pdf