Unassigned ELD Driving: Assign, Annotate, or Reject

What unassigned driving is

Unassigned driving is time the ELD recorded the vehicle in motion without a driver logged in. The device still measured the movement. It simply has no authenticated driver to hang it on. That happens when someone drives off without logging in, when a shop tech moves the truck, when a driver logs out too early in a fuel island, or when the login fails and the truck rolls anyway.

The segment is not spare time and it is not invisible. It sits in the ELD until a driver claims it or the carrier annotates why it remains unassigned. Leaving it untouched is not a neutral choice. At the roadside it reads as driving nobody wants to own. In an audit it reads the same way.

This is not the 8-day paper-log procedure for a broken ELD. That procedure lives on what to do in an ELD malfunction. Do not open a paper log because an unassigned segment exists. Identify the driver or explain the movement.

What the driver sees at the next login

49 CFR 395.32 requires the ELD, when a driver logs in, to prompt a review of unassigned driving time that belongs to that vehicle. The driver is supposed to claim the segments the driver actually drove or reject the segments the driver did not drive. The prompt is the driver's moment to tell the truth. Tapping past it without reading the times and locations is how the wrong person inherits a yard move, or how a real drive stays unassigned.

If you drove from the yard to the shipper before the login completed, claim that segment. Annotate that the login was late and the movement is yours. The claim puts the driving on your 11-hour, 14-hour, and 60-or-70 totals, which is where it already belonged. Rejecting your own drive to protect the clocks is a false record.

If you did not drive it, reject it. A rejection is not an accusation. It tells the carrier the segment is still unassigned and still needs an explanation. Do not claim a segment you did not drive because a dispatcher asked you to clear the queue.

Assign the time only to the driver who drove

On review, the motor carrier identifies unassigned driving and, when it can tell who was in the seat, proposes that the time be assigned to that driver. The proposal follows 49 CFR 395.30 on carrier-proposed edits. The driver confirms or rejects. A carrier-proposed change does not take effect until the driver confirms it and recertifies the record. The carrier cannot silently rewrite the day.

Assign the person who drove. Use dispatch records, the camera if you lawfully have one, the fuel receipt, and the bill of lading. If two people might have moved the truck, do not flip a coin. A wrong assignment is a false duty status for the driver who accepts it and a hole for the driver who actually drove.

Team drivers have a narrow edit path in 395.30(c)(3) when the ELD assigned driving to the wrong co-driver and each was already shown as the other's co-driver. That is a swap between the two people who were in the truck. It is not a license to move hours onto a driver who was off duty somewhere else.

There is no legitimate method here for parking a deadhead on an unassigned line so the driving driver stays under 70. If that is the outcome you want, you are building a false log. Stop and put the hours on the person who drove.

Annotate when you cannot assign

Some movement has no driver to assign. A technician repositions the tractor in the yard. A tow company loads it. The explanation is an annotation on the unassigned event: who moved it, why no driver was logged in, and the time and place. The annotation is part of the record. It is not a second, silent edit that erases the first.

Keep the supporting note with the file. A shop work order, a gate log, or a message from the tech is the document that makes the annotation believable. An annotation that says yard move, with no name and no time, will not survive a comparison to GPS that shows the truck on the highway.

If you later discover the driver, propose the assignment then. Update the annotation to say the earlier unknown is now identified. Do not leave a highway segment annotated as a yard move after you know it was a trip. The original data stays. The correction sits on top of it, attributed to the person who made it.

Roadside inspection includes unassigned events

An officer can ask for the ELD transfer and can look at unassigned driving. We do not look at those is not a strategy. A clean certified graph next to a pile of unassigned highway miles is a log problem, not a software quirk. What the inspection asks for, and how the transfer works, is the ELD roadside inspection. This page does not repeat that manual.

Before the truck leaves, the carrier should be able to say, for every unassigned segment on that vehicle in the recent record, either the driver who accepted it or the annotation that explains it. If you cannot say that, do not send the truck and hope the officer skips the screen.

Drivers should know how to show the prompt history: what they accepted, what they rejected, and the annotation text. Freezing at the question is how a small yard move becomes a roadside violation. Practice it once, on a real segment, before the inspection is the teacher.

What not to do with the segment

Do not delete it. 395.30(f) says the carrier must not alter or erase, or permit or require alteration or erasure of, the original information collected on the driver's hours of service. Unassigned driving is part of that information. A vendor who offers a purge button is offering a violation.

Do not assign it to a driver who has hours left. Do not split it across two logs to keep each under a cap. Do not log the driver off duty for the same minutes the unassigned line shows the truck on the interstate. The GPS and the graph will be read together.

Do not treat a pattern of unassigned driving as normal. A driver who regularly moves the truck before logging in is avoiding the driving line. Coach the login, then discipline the repeat, and still assign the miles to that driver. The coaching does not replace the assignment. The assignment does not excuse the next omitted login.

The same habit protects the 70-hour recap. Miles that never land on a driver never land on the total, and the total is then a wish. Put the miles on the log they belong to, let the recap go up, and plan the next load on the real number.

Keep a simple weekly count of unassigned segments by truck. A truck that produces them every day has a login problem, a shop-move problem, or a driver who is rolling before authentication. The count is not a punishment by itself. It tells you which unit to fix before an inspection picks the unit for you. Write down the disposition of each segment the day it appears, not the week an auditor asks.

If the disposition is still blank at dispatch, the truck stays.

Frequently Asked Questions