Quick Answer
Unassigned driving time is vehicle movement the ELD recorded while no driver was logged in — the miles land in an "unidentified driver" profile attached to the truck. Drivers must review and accept or reject those segments at login, and carriers must either assign them to the right person or annotate why they belong to no one. Left unmanaged, unassigned time is the single fastest way to look like a log falsifier at an audit, even when the real cause was a mechanic's road test.
Key Takeaways
- Every mile the truck moves without a login becomes unidentified driving attached to the vehicle — it never just disappears.
- Legitimate causes are common: mechanics, yard staff, a driver who forgot to log in — but each still needs assignment or an annotation.
- Drivers see pending unidentified segments at login and must accept the ones that are theirs; rejecting your own miles is falsification.
- A weekly review that drives unassigned time to zero is one of the strongest audit signals a small fleet can build.
Where orphan miles come from
The ELD is wired to the engine, not to good intentions — if the wheels turn, it records. The usual sources: a driver who pulled out before logging in, a mechanic's test drive, a porter shuttling the truck at a terminal, or a co-driver mix-up. None of these are scandals. All of them create the same artifact: driving time attached to the truck's unidentified profile, waiting for someone to claim it.
Why enforcement cares so much
Unassigned time is also how log falsification looks: a driver out of hours logs out, drives three more, and hopes the orphan miles vanish into the vehicle profile. Because the honest causes and the dishonest ones produce identical data, auditors and inspectors treat unexplained unassigned time as a red flag by default — it was one of the named tells in this year's tampering-focused enforcement. The burden of explanation sits on the carrier, and "we never got around to it" is not an explanation.
The driver's half of the job
At login, a compliant ELD presents pending unidentified segments. The rule is simple: accept what's yours, reject what isn't, and never the reverse. Accepting a mechanic's miles corrupts your own log; rejecting your own miles is falsification with your name on the timestamp. Ten seconds of honest attention at every login keeps your record clean.
The carrier's half of the job
Every unassigned segment needs one of two endings: assigned to the correct driver, or annotated with a short explanation and retained — "Road test, R&R Diesel, brake repair order #4412" is all it takes. For a small fleet, the workable routine is a weekly ten-minute review: open the unidentified driving report, assign the known, annotate the explainable, investigate the mystery miles the same week they appear. Six-month-old orphan miles are unexplainable almost by definition.
Make it structurally rare
The cleanup routine matters, but prevention is cheaper: make "log in before the wheels turn" the non-negotiable habit (it tops our rookie-mistakes list), give mechanics and yard staff a documented procedure for moves, and check the unassigned report before every audit window rather than during one. A fleet whose unidentified profile sits at zero has, in one metric, told an auditor most of what they came to learn.
Published July 2026. Educational, not legal advice — confirm procedures against current FMCSA requirements.
FAQ
Does unassigned driving time go away on its own?
No — it stays attached to the vehicle's unidentified driver profile until someone assigns it or annotates it, and auditors can see how long it sat there.
What if the unassigned miles were a mechanic's road test?
That's a legitimate cause — annotate the segment with the shop, reason, and date, and retain it. The explanation is what separates housekeeping from a red flag.
Can I reject unidentified miles that are actually mine?
No. Rejecting your own driving to protect your hours is log falsification — the exact behavior the unassigned-time review exists to catch.
