Every fleet has them. You open the ELD back office and find a stack of driving events sitting under “Unidentified Driver,” and nobody remembers who moved the truck. Ignore that pile long enough and it becomes a problem during a roadside inspection, a compliance review, or a full audit. This guide covers why unassigned driving piles up, what the regulations require drivers and carriers to do about it, and how to build a weekly review that keeps the account clean.
What Unassigned Driving Actually Is
Under 49 CFR 395.32(a), when a commercial motor vehicle is moving and no driver is logged in to the ELD, the device records that driving under one account. The regulation calls it “a single account labeled ‘Unidentified Driver.'” The ELD technical specification in Appendix A to Subpart B of Part 395 says the same thing in section 4.1.5(a): the ELD “must associate all non-authenticated operation of a CMV with a single ELD account labeled unidentified driver.”
The device doesn’t care who is behind the wheel or why. It reacts to motion. Under spec section 4.3.1.2(a)(1), “Once the vehicle speed exceeds the set speed threshold, it must be considered in motion.” Section 4.3.1.2(a)(3) says that threshold “must not be configurable to greater than 5 miles per hour.” Section 4.4.1.1 then requires the ELD to “automatically record driving time when the vehicle is in motion by setting duty status to driving,” unless the driver selected personal conveyance or yard move before the vehicle started moving.
In plain terms, once the truck goes past the threshold and nobody is logged in, the ELD starts logging driving time to the Unidentified Driver account.
Why Unassigned Miles Pile Up
The ELD records the time correctly. The trouble is that people don’t follow up on it. These are the usual sources.
Forgotten Logins
A driver hops in, fires up the truck, and pulls out before logging in. The ELD is required to push back. Under spec section 4.1.5(b)(1), it must “Provide a visual or visual and audible warning reminding the driver to stop and log in to the ELD.” Drivers in a hurry tune that out, and the miles land in the unidentified account.
Shop and Yard Moves
Mechanics, yard jockeys, and wash bay staff move trucks all day, and most of them never log in. Each of those moves creates an unassigned event that someone has to explain later.
Slip-Seat and Team Operations
When several drivers share equipment, it gets hard to say who moved a truck and when. If a handoff doesn’t include a clean logout and login, the time between drivers can end up with nobody.
Connectivity and Hardware Issues
Tablets die, apps crash, and Bluetooth drops. On some systems, if the driver’s session falls off while the truck keeps rolling, that driving can be recorded as unidentified. How this plays out depends on the ELD vendor.
Nobody Owns the Account
This is the main reason the pile grows. Drivers handle their own logs and dispatch handles loads, so the Unidentified Driver account often has no owner. Without someone responsible for it, it fills up month after month.
The Driver’s Side: Claim It or Reject It
Drivers have a role in this before the office ever sees the events. Under spec section 4.6.1.6(a), when driving has been logged under the unidentified profile, “the ELD must prompt the driver(s) logging in with a warning indicating the existence of new unassigned driving time.”
Under 49 CFR 395.32(b), “the driver must review any unassigned driving time when prompted by the ELD.” The driver then has two options:
- “Assume any records that belong to the driver under the driver’s account,” or
- “Indicate that the records are not attributable to the driver.”
Drivers, the lesson is simple. If you moved that truck, claim the time. If you didn’t, reject it. Don’t tap past the prompt.
What If a Driver Claims the Wrong Event?
Mistakes can be fixed. According to the FMCSA ELD FAQ, “Driving time assumed from the unidentified driver profile in error may be returned to the unidentified driver profile.” The FAQ also confirms, “Yes, a driver can edit their record after erroneously accepting a driving event.”
The Personal Conveyance Trap
Some drivers claim unassigned time and then try to relabel it as personal conveyance so it doesn’t count against their hours. The FMCSA FAQ prohibits this: “Drivers may not assume driving time from the unidentified driving profile and convert it to Off-Duty (PC) or On-Duty Not Driving (YM).” The FAQ also says that for special driving categories such as yard moves and personal conveyance, “Selection and deselection of the special driving category must be indicated at the time the status changes.” If PC or yard move wasn’t selected at the time, it can’t be added afterward to make unassigned miles disappear.
The Carrier’s Side: Annotate or Assign
Whatever drivers don’t claim stays with the carrier. Under 49 CFR 395.32(c)(1), carriers have two options for every unidentified driving record:
- Annotate under 395.32(c)(1)(i): “Annotate the record, explaining why the time is unassigned.”
- Assign under 395.32(c)(1)(ii): “Assign the record to the appropriate driver to correctly reflect the driver’s hours of service.”
The FMCSA FAQ restates it: “a motor carrier must either annotate the record and explain why the time is unassigned” or assign it. Leaving the records alone is not an option.
When to Assign
If you can identify the driver from dispatch records, fuel receipts, gate logs, GPS, or the driver’s own account, assign the time. Spec section 4.3.2.8.2(b)(1) allows it: “ELD events recorded under the ‘Unidentified Driver’ profile may be edited and assigned to the driver associated with the record.” The FMCSA FAQ adds that a driver “can be assigned unidentified driver records recorded under the Unidentified Driver profile.”
Assigning time from the office does not finish the job. Under 49 CFR 395.30(d)(1), “A driver must confirm or reject any proposed change.” The driver also has to recertify and resubmit the records before the change takes effect. Until the driver accepts, the edit is only a proposal.
When to Annotate
If the movement belongs to a mechanic, a yard move by non-driving staff, or anything else that isn’t a driver’s hours of service, annotate it with a specific explanation. A note like “Moved by shop tech from bay to fuel island for service” holds up. A note like “N/A” does not.
The Lines You Cannot Cross
Several regulations limit how carriers can clean up these records:
- 49 CFR 395.30(c)(2): “The driver or support personnel must annotate each change or addition to a record.” Every edit needs a reason.
- 49 CFR 395.30(e): “A motor carrier may not coerce a driver to make a false certification.” You can’t pressure a driver into accepting time that isn’t theirs, or into rejecting time that is.
- 49 CFR 395.30(f): Carriers “must not alter or erase, or permit or require alteration or erasure of, the original information collected.” The original data stays, and edits are added on top of it.
- 49 CFR 395.8(e)(1): “No driver or motor carrier may make a false report in connection with a duty status.”
Assigning hours to whichever driver has the most available time to keep everyone legal is a false report. Don’t do it.
The Diagnostic That Exposes You
The ELD also flags excessive unidentified driving with a diagnostic. Under spec section 4.6.1.6(c), “more than 30 minutes of driving in a 24-hour period” of unidentified driving triggers an “unidentified driving records” data diagnostic event. Once triggered, the indicator turns on for all drivers logged into that ELD “for the current 24-hour period and the following 7 days.”
That means one careless trip can leave a diagnostic indicator lit for every driver in that truck for more than a week. Under section 4.6.1.6(d), the event can be cleared once unidentified driving for the current 24-hour period and the previous 7 consecutive days “drops to 15 minutes or less.” Getting the time claimed by, or assigned to, the right driver is what brings that number down. An annotation explains time that really belongs to nobody, but it stays under the Unidentified Driver profile, so it still counts toward the diagnostic until it ages out of the 8-day window.
What Inspectors and Auditors See
At the roadside, spec section 4.8.1.3(a) requires the ELD display or printout to show the inspected driver’s profile and the unidentified driver profile as separate reports, and “both reports must be printed or displayed and provided to the authorized safety official.” If the ELD holds any unidentified driving from the current day or the previous seven, an inspector who looks at a driver’s logs sees that unassigned driving too.
During an audit, 49 CFR 395.32(c)(3) requires carriers to produce unidentified driving records “During a safety inspection, audit or investigation by an authorized safety official.”
Retention Requirements
Under 49 CFR 395.32(c)(2), “A motor carrier must retain unidentified driving records for each ELD for a minimum of 6 months from the date of receipt.” Under 49 CFR 395.8(k)(1), records of duty status and supporting documents must be kept “for a period of not less than 6 months from the date of receipt.” Under 49 CFR 395.8(k)(2), “The driver shall retain a copy of each record of duty status for the previous 7 consecutive days.”
The Weekly Unassigned Driving Review
A weekly review keeps the pile from coming back. Here is a workable routine for ops managers.
Step One: Pull the Report by Unit
Run the unidentified driving report for every ELD in the fleet. Sort by truck so you can see which units are repeat offenders.
Step Two: Check for Active Diagnostics
Look first for any unit where unidentified driving crossed the 30-minute mark in a 24-hour period. Those trucks have a lit diagnostic, so work them first. Assigning the time to the right driver is what clears the indicator; annotations alone won’t.
Step Three: Match Events to People
Cross-reference each event with dispatch, shop work orders, yard logs, and fuel transactions. If a driver can be identified, propose the assignment and follow up until they accept or reject it.
Step Four: Annotate Everything Else
Any event that legitimately belongs to non-driving activity gets a specific annotation the same week. Don’t let open items carry into the next review.
Step Five: Fix the Root Cause
Look for patterns. If the same terminal keeps producing shop moves, train the shop staff. If the same driver keeps forgetting to log in, coach them. If one tablet keeps dropping connection, replace it. Annotations clear the records, but fixing the cause is what keeps new ones from appearing.
Step Six: Document the Review
Keep a simple record of who reviewed the account, when, and what was resolved. When an auditor asks about your process, a dated record is far more convincing than “we check it regularly.”
Unassigned driving events are a routine part of running a fleet, but an unmanaged backlog will draw an auditor’s attention. The rules are straightforward. Drivers claim or reject the time when the ELD prompts them. Carriers annotate or assign whatever is left. Nobody falsifies, coerces, or erases anything. Give the Unidentified Driver account a named owner, review it every week, and fix the habits that cause it to fill up. Then when an inspector or auditor asks for your unidentified driving records, you’ll have clean, documented records to hand over.
0 Comments