Unassigned Driving Time: ELD Audit Guide
By Justin Seyl, NATMI Certified Director of Safety
Unassigned driving time is any mileage an ELD records without a driver logged in, and the rule says a carrier has to either assign that time to the right driver or write down why it can't be assigned. I've personally overseen more than 650,000 citations and directed over 10,000 Safety Fitness Determination upgrades, and I'll tell you straight — unresolved unassigned time is one of the fastest ways to turn a routine compliance review into a false-log finding.
Waypoint True built Verity to catch this before an auditor does. Most carriers treat unassigned driving like background noise, something the back office will "get to eventually." Then a DOT investigator pulls six months of logs, finds a pile of unassigned miles with no annotation and no driver tied to them, and now you're not explaining a data gap. You're explaining why your records don't match reality. That's a completely different conversation, and not one you want to be having for the first time with an investigator sitting across the table.
What Counts as Unassigned Driving Time on an ELD?
Unassigned driving time, also called unidentified driver time, is drive time the ELD picks up when the vehicle's moving but nobody's logged in. Under 49 CFR 395.32(a), the ELD has to dump that activity into a default account labeled "Unidentified Driver" the second the truck moves without an authenticated login. It's not a glitch. It's the ELD doing exactly what it's built to do — record movement, name attached or not.
This happens more than most safety managers want to admit. A driver forgets to log in before pulling out of the yard. A mechanic moves a tractor during a shop check. A second driver on a team run doesn't switch accounts fast enough at the swap. None of that's automatically a violation. It's unassigned time, and the rule hands you a clear path to clean it up. What's not optional is pretending it isn't there.
What Must a Driver Do When Logging Into the ELD?
When a driver logs in and there's unassigned driving time sitting in the system, that driver has a direct duty under 49 CFR 395.32(b): review the unassigned records when prompted, then claim the ones that belong to them or flag the ones that don't. That's not a line buried in a training manual somewhere. It's built right into the login sequence on a compliant ELD. The problem is drivers click through these prompts fast, especially first thing in a shift when they're heads-down on pre-trip and dispatch. A driver who dismisses the prompt without actually looking at it leaves you holding an unresolved record. That's a training problem, plain and simple, and it's exactly what Verity flags for safety managers so you fix it at the source instead of finding it buried in an audit folder six months later.
What Is the Carrier's Legal Duty on Unassigned Driving Time?
The driver's login review is only half of it. The carrier's got its own separate duty under 49 CFR 395.32(c)(1): review every unidentified-driving record and either annotate why it stays unassigned or assign it to the right driver so the hours-of-service record's actually accurate. You can't just lean on the driver clicking through a prompt and call it done. Somebody on your end has to close the loop. That matters because the general accuracy rule in 49 CFR 395.30(a) puts both the driver and the carrier on the hook for making sure ELD records are correct. If you're running a fleet or managing safety, that means someone's pulling unassigned-driving reports on a regular schedule — not waiting for a roadside inspection or compliance review to surface the problem for you. If a chunk of time genuinely can't be assigned, write it down. Maintenance moved the truck during a shop visit, a yard check got done by non-driver staff, whatever actually happened — a documented annotation protects you. Silence doesn't.
How Long Must Unassigned Driving Records Be Kept?
You've got to hold unidentified-driving records for at least six months from the date received, per 49 CFR 395.32(c)(2). That's its own retention clock, separate from the general hours-of-service recordkeeping duty under 49 CFR 395.8, which also sets a six-month floor for records of duty status and supporting documents. Both rules run side by side, and an auditor can come asking for either one. ELDs also have to generate a required backup copy under 49 CFR 395.22(i)(1), stored on a separate device from where the original data lives, held for that same six months. If your system isn't keeping unidentified-driver data on its own clean trail for the full window, you've got a gap that's going to show up the second an investigator asks for historical logs.
Why Does Unresolved Unassigned Driving Flag a Carrier for Audit Trouble?
Unresolved unassigned driving time is a standard item investigators check during a compliance review — they look for unassigned miles and ask you to explain them. If you can't, that stops being a quirky data gap and starts looking like a records problem. A false record of duty status under 49 CFR 395.8(e)(1) is listed as a critical violation in Appendix B to 49 CFR Part 385, and a pattern of critical violations counts against a carrier's safety rating. The ELD technical specifications (Appendix A to Subpart B of 49 CFR Part 395) also have the device record an unidentified driving records data diagnostic event when more than 30 minutes of unidentified driving builds up in a 24-hour period. That's not a safety-rating cutoff — it's an internal system trigger — but it tells you how closely this is supposed to be watched. Enforcement attention on ELD record integrity has only gotten sharper. This is where waiting starts costing you money. If you're sitting on months of unassigned driving data with no annotations and no assignments, don't wait for a DOT letter to find out how bad it looks. Get your logs in front of a Verity log audit at Waypoint True and find out where your exposure actually sits before an investigator finds it for you.
How Waypoint True Helps With Unassigned Driving Time
When you bring us a file, we start by pulling every unidentified-driving record across the retention window and checking whether it was actually handled the way 49 CFR 395.32 requires — not just sitting somewhere in the ELD backend. We verify the driver login-review prompts were working and got answered, confirm the carrier-side annotate-or-assign step got done for every segment, and flag any gap where time sat unresolved too long. Where we find a real dispute — a mechanic moving a unit, a misattributed team-driving segment, a vehicle that changed hands mid-shift without a clean handoff — we document it the way an auditor expects to see it, with a clear annotation trail instead of a guess. And where we find a genuine gap with nothing on file, we tell you straight, because that's the kind of news you want from us in a quiet office, not from an investigator mid-review. From there we hand you a direct next step: what to fix in your login procedures, what to correct in your record review process, and what to document going forward so this doesn't happen again.
Justin Seyl is a NATMI Certified Director of Safety and NATMI Certified Audit Specialist with more than 25 years in CDL compliance. He has personally overseen more than 650,000 citations and directed more than 10,000 Safety Fitness Determination upgrades. He is the founder of CDL Consultants, CDL360 and CDL Manager.
Sources
- 49 CFR Part 395.32
- 49 CFR Part 395.30
- 49 CFR Part 395.8
- 49 CFR Part 395.34
FAQ
Is unassigned driving time automatically a violation?
No. Unassigned driving time by itself isn't a violation under 49 CFR 395.32. It becomes a problem when the carrier fails to review it and either annotate why it's unassigned or assign it to the right driver. Leaving it unresolved is what creates exposure, not the fact that it happened in the first place.
Who is responsible for resolving unassigned driving time, the driver or the carrier?
Both carry separate duties. The driver has to review unassigned records at login under 49 CFR 395.32(b) and claim or disclaim them. The carrier has to independently review and annotate or assign every unidentified record under 49 CFR 395.32(c)(1). One doesn't cover for the other.
How long does a carrier have to keep unidentified-driving records?
At least six months from the date received, per 49 CFR 395.32(c)(2). That runs alongside the general six-month retention rule for hours-of-service records under 49 CFR 395.8(k)(1) and the six-month ELD backup-data retention rule under 49 CFR 395.22(i)(1).
Can unresolved unassigned driving time hurt a carrier's safety rating?
It can, indirectly. If unresolved unassigned time gets treated as a false record of duty status under 49 CFR 395.8(e)(1), that's listed as a critical violation in Appendix B to 49 CFR Part 385, and a pattern of those counts against a carrier's safety rating in a compliance review.
What should a carrier do if unassigned driving time genuinely can't be attributed to a driver?
Document it. Write a clear annotation explaining what happened, whether that's a non-driver employee moving the vehicle or a mechanical check, and keep that annotation with the record for the full retention period required under 49 CFR 395.32(c)(1). A documented explanation holds up. Silence doesn't.
Does a high volume of unassigned driving time trigger an automatic FMCSA flag?
The ELD technical specifications in Appendix A to Subpart B of 49 CFR Part 395 have the device record a data diagnostic event when more than 30 minutes of unidentified driving builds up in a 24-hour period. That's an internal ELD system trigger, not a published safety-rating threshold, but it shows how closely the agency expects this data to be watched.