Unassigned driving time must be reviewed and either assigned to the correct driver or explained with a documented reason. A fleet should not clear the queue simply to make a dashboard look clean.
What this means for your fleet
Review daily using vehicle, time, location, login, dispatch, maintenance, and yard context. Route a proposed assignment to the driver when required, and measure recurring root causes such as shared credentials or missed login.
Worked unidentified-driving review
At 06:12 a tractor moves 0.7 miles in the terminal with no driver logged in. Dispatch shows no load movement; maintenance records show a technician moved the truck after service. The reviewer links the event to the vehicle, time, gate/yard context, technician work order, and carrier procedure, then records the specific disposition. The event is not assigned to the next driver merely because that driver used the truck later.
If evidence instead identifies a logged-out driver, the carrier uses the documented assignment/proposed-edit workflow and the driver reviews it. Recurring events are grouped by cause—missed login, shared credential, maintenance, yard process, or device assignment—so the fleet fixes the workflow rather than clearing a queue.
What to check
Use these checks before changing a log, policy, device, integration, or buying decision.
| Check | How to verify |
|---|---|
| 1. Triage by vehicle and time | Keep each original event with vehicle, timestamp, location and movement; sort by vehicle/time and retain the queue snapshot and triage owner. |
| 2. Check dispatch and maintenance context | Attach dispatch, login, maintenance, mechanic, yard and assignment context for the same vehicle/time and document conflicts or missing evidence. |
| 3. Assign through the documented workflow | Retain the proposed driver and reason, notification, original event, driver response, accepted/rejected result, administrator action, and audit history. |
| 4. Record a specific explanation when unassigned | Keep the event, specific non-driver explanation, supporting maintenance/yard evidence, reviewer, disposition, and retained original record. |
| 5. Fix the root cause | Document the recurring cause, affected vehicles/users, corrective account or process change, owner, completion evidence, recurrence measure, and retest. |
Common failure modes
- Generic “not mine” annotations.
- Assigning to a driver without evidence.
- Hiding yard or mechanic movement.
Limits and exceptions
This guide does not decide a fact-specific legal exception, certify a record, or guarantee a compliance, safety, cost, or audit outcome. Keep the original ELD record and any edit history. Use the current official rule for applicability and the exact installed-device manual for screen-by-screen actions.
Sources, review date, and limits
Reviewed August 10, 2026. Each source supports only the point described beside it. Rules and product details can change; recheck dynamic facts before changing a fleet workflow or signing a contract.
- Unidentified and unassigned driving-time workflow — Federal Motor Carrier Safety Administration.
- Editing, annotation, certification, and original-record preservation — Federal Motor Carrier Safety Administration.
- Current first-party product, plan, feature, and support representations; dynamic facts require release-date recheck — Factor ELD.
Review the exact operation
Bring the driver, vehicle, trip, jurisdiction, current official rule, and original ELD record for a qualified determination. Factor ELD can demonstrate its current product; rule applicability remains a fleet compliance decision.