Unassigned driving time appears when vehicle movement is recorded by the ELD but not assigned to a driver's log. Carriers should review the event, determine whether it belongs to a driver, assign it if it does, annotate and document why if it does not, train drivers to log in before moving, and monitor repeat patterns. Not every unassigned event is a violation, but leaving them unresolved raises risk. Verify current requirements. This is general information, not legal advice.
Every ELD produces unassigned driving. A truck moves, no driver profile is logged in, and the device records the motion as unidentified. The event itself is normal. What matters is what you do with it. Left in a pile, unassigned driving reads to an auditor like driving time nobody wanted to claim. Reviewed and resolved, it is a non-issue.
What is ELD unassigned driving time?
Unassigned driving time is driving time the ELD recorded that is not assigned to a specific driver. The device connects to the engine and captures movement, but if no driver is logged in, or the wrong profile is active, the time lands in an unassigned or unidentified bucket for someone to resolve. It may happen because of login issues, yard movement, shop movement, driver error, or other operational reasons. It should not be ignored. For the broader device pitfalls, see our common ELD mistakes, and for the service side, HOS and ELD auditing. You can also check current FMCSA ELD guidance.
Why unassigned driving time happens
Understanding the cause tells you how to resolve it. This is a general guide; verify against your own records and ELD provider instructions.
| Cause | What it may mean | What to review | What to document |
|---|---|---|---|
| Driver forgot to log in | Legitimate driving time not claimed | Which driver was operating the unit | The assignment to the correct driver |
| Wrong driver selected | Time attributed to the wrong profile | Who actually drove the vehicle | The correction and why it was made |
| Mechanic or shop movement | Non-driver moved the vehicle | Shop or maintenance records | An annotation noting the shop movement |
| Yard movement | Movement within a yard by yard staff | Yard context and who moved it | Why it was not assigned to a driver |
| ELD data sync issue | A technical hiccup created the event | Device status and provider guidance | The technical explanation and any ticket |
| Unidentified short movement | A brief move nobody claimed | Time, distance, and location | The review outcome |
| Driver rejects assignment | Proposed time was declined | Whether the driving actually belongs to them | The follow-up and resolution |
What the regulation requires: 49 CFR 395.32
Unassigned driving time has a specific regulatory home. Under 49 CFR 395.32, motor carriers must examine unidentified driving records and do one of two things:
- Assign the record to the appropriate driver, to correctly reflect that driver's hours of service.
- Annotate the record, explaining why the time is unassigned (for example, a shop movement, a yard movement, or a driver error that was investigated and found not to be HOS-relevant driving).
The regulation also requires:
- Unidentified driving records must be retained for no less than 6 months.
- During inspections, audits, or investigations, carriers must make unidentified driving records available for the relevant time period.
- When drivers log in to the ELD system, they must review any unassigned driving time and either claim those records as their own or indicate they are not attributable to them.
This is what distinguishes a carrier running a real compliance process from one that is ignoring unassigned events and hoping nothing comes up.
What carriers should do with unassigned driving time
Run a consistent process rather than assigning on autopilot. Verify current requirements for your operation.
| Step | What to do | Who should review | Record to keep |
|---|---|---|---|
| Review the event | Open each unassigned event, do not batch-clear | Safety manager or log auditor | Note that the event was reviewed |
| Identify vehicle and time | Confirm the unit, date, and time | Log auditor | Vehicle and timestamp |
| Check dispatch and route context | See who was assigned to the unit then | Dispatch and safety | The dispatch or route reference |
| Ask the driver where appropriate | Confirm with the likely driver | Safety manager | The driver's explanation |
| Assign if it belongs to a driver | Attribute the time to the correct driver | Log auditor | The assignment record |
| Annotate if it does not | Explain a shop or yard movement | Log auditor | The annotation |
| Document why it was not assigned | State the reason clearly | Safety manager | The written reason |
| Track repeat patterns | Watch for the same driver or unit repeating | Safety manager | A coaching log entry |
What happens if a driver rejects an unassigned driving event
When a driver logs in and is presented with unassigned driving time, they can claim it or reject it. If a driver rejects time that actually belongs to them, the carrier must investigate and resolve it. Rejection does not erase the record. Under 49 CFR 395.32, the unidentified record stays in the system and must still be reviewed, annotated, or assigned. A carrier that lets drivers routinely reject their own driving time without follow-up is building a documentation problem, not solving one.
The carrier-side workflow after a rejection:
| Step | What to do | What to document |
|---|---|---|
| Pull the event | Review the timestamp, vehicle, location, and distance | The event details and review date |
| Check dispatch | Who was assigned to that unit at that time? | The dispatch record for that unit |
| Ask the driver | What were you doing at that time? Were you in the vehicle? | The driver's explanation |
| Check for other causes | Was it a mechanic, yard staff, or another driver? | The alternative explanation if confirmed |
| Resolve the record | Assign to the correct driver OR annotate with the confirmed explanation | The annotation or assignment and reason |
| Retain the record | Keep the unidentified driving record for at least 6 months per 49 CFR 395.32 | The original event and the resolution |
Can unassigned driving time become an HOS issue?
It can raise questions, especially if it appears to hide driving time or if the carrier repeatedly ignores it. It may matter during audits or log reviews. We do not claim every unassigned event is a violation, because many are legitimate shop or yard movements. The difference is whether you reviewed and resolved them or let them pile up. For how HOS issues age and where they show up, see how long HOS violations stay on your record and the common HOS violations that hurt CSA scores. Unresolved patterns are also part of how brokers look at HOS violations.
Driver training points
- Log in before moving the vehicle.
- Verify the correct driver profile.
- Use annotations correctly.
- Tell dispatch or safety when a mistake happens.
- Understand personal conveyance and yard move.
- Do not reject legitimate driving time.
- Keep supporting documents where needed.
The status confusion behind a lot of unassigned driving is covered in our guide to personal conveyance vs yard move.
Common unassigned driving mistakes
- Ignoring unassigned driving reports.
- Automatically assigning without review.
- Never documenting why events were left unassigned.
- Letting drivers reject legitimate driving.
- Failing to train shop and yard movement procedures.
- Treating ELD software as the safety manager.
- Not looking for repeat patterns.
Weekly unassigned driving review checklist
This fits inside your normal log audit rather than a separate process. For the full cadence, use our driver log auditing checklist.
- Pull the unassigned driving report.
- Sort by unit and driver.
- Review high-mileage or repeated events first.
- Compare against dispatch records.
- Ask for a driver explanation where needed.
- Assign or annotate.
- Document unresolved events.
- Add repeat issues to the driver coaching log.
Unassigned driving is not the crime. Ignoring it is. When I open an ELD and find weeks of unassigned events nobody touched, that is the story an auditor reads too: nobody is minding the data. Two minutes an event, reviewed and annotated, and the whole thing becomes a non-issue. Batch-clearing it without review is just a different way of not looking.
Need Help Reviewing ELD Records?
Book a free compliance review. We will pull a sample of your unassigned driving, show you the patterns, and build a review process that holds up.
Book a Free Compliance Review →HOS & Log Auditing
We audit ELD data, resolve unassigned driving, coach repeat offenders, and document the review so it holds up in an audit.
Get HOS Support →How Fleet Regulators helps with ELD review: we help carriers review ELD records, identify unassigned driving patterns, document decisions, coach drivers, and build repeatable log-audit processes. We do not guarantee HOS compliance, CSA improvement, audit outcomes, or insurance savings.
Frequently Asked Questions
Unassigned driving time is vehicle movement the ELD recorded that was not assigned to a driver's log. The device captured the motion, but no driver profile claimed it. Carriers should review each event, determine whether it belongs to a driver, and assign or annotate it. Verify current requirements and follow your ELD provider instructions.
Common reasons include a driver forgetting to log in before moving, the wrong driver being selected, a mechanic or yard person moving the vehicle, a data sync issue, or a short unidentified movement. It is not automatically wrong, but it needs review so the record is accurate.
Not always. If the driving belongs to a driver, it should be assigned. If it does not, such as a shop or yard movement, the carrier should annotate and document why it was not assigned to a driver rather than ignoring it. Consistent, documented review is the goal.
An ELD can allow a driver to accept or reject proposed unassigned driving. A driver should not reject legitimate driving time that belongs to them. When a driver rejects an event, the carrier still needs to review and resolve it, and document the outcome.
It can raise questions, especially if it appears to hide driving time or if the carrier repeatedly leaves it unresolved. Not every unassigned event is a violation, but unresolved patterns can matter in a roadside inspection or audit. Documentation and consistent review reduce that risk.
Reviewing it regularly, such as during a routine log audit, is the practical approach so events are resolved while the context is fresh. Waiting until an audit to reconstruct months of unassigned events is where carriers get into trouble. Fit it into your existing log-audit cadence.
Document the event review, the vehicle and time, the dispatch or route context, any driver explanation, whether it was assigned or annotated, and the reason it was not assigned if it was not. Keep repeat issues in a coaching log. The record is how you show a review happened.
Yes. We help carriers review ELD records, identify unassigned driving patterns, document decisions, coach drivers, and build a repeatable log-audit process. We do not guarantee HOS compliance, CSA improvement, an audit outcome, or insurance savings.