Dry-van carriers need dependable HOS records across pickup, detention, drop-and-hook, relay, and delivery workflows, with clean driver and tractor assignment at every handoff.
What this means for your fleet
The main preventable failures are missed logins after tractor swaps, unexplained detention, unassigned driving after maintenance or yard work, and dispatch plans that ignore available hours.
Worked operating scenario
A drop-and-hook relay uses two drivers and one tractor. At each handoff the fleet verifies login, active vehicle, prior unidentified movement, detention annotation, available hours, and transfer capability. The relay closes only when both records and the tractor event history reconcile.
What a passing test includes
Check each item in the same scenario: Standardize tractor handoff; review unassigned driving daily; capture detention context; integrate dispatch with read/write controls; rehearse roadside transfer. Note who reviewed the result, which current rule or product source was used, any exception, and what the fleet will do next.
What to check
Use this operating matrix before buying or configuring a system. A completed answer is more useful than a generic feature check.
| Check | How to verify |
|---|---|
| 1. Standardize tractor handoff | Retain outgoing/incoming driver, tractor/VIN, trailer, device, account, handoff time, login/logout, assignment result, defect, and acceptance. |
| 2. Review unassigned driving daily | Keep every original event with tractor, time, location, login, dispatch or maintenance context, proposed assignment/explanation, driver response, and disposition. |
| 3. Capture detention context | Attach appointment, arrival/departure, dock and loading timestamps, messages, actual duty statuses, annotations, delay owner, and review result. |
| 4. Integrate dispatch with read/write controls | Keep integration fields, direction, source of record, read/write permissions, test payload, retry/conflict behavior, audit history, and daily reconciliation. |
| 5. Rehearse roadside transfer | Save the in-cab materials, requested range, supported method, routing entry, receipt or displayed result, failure branch, defect, and retest. |
Three checks before a route or rollout
- Applicability: Identify the driver, vehicle, trip, commerce, jurisdiction, and exact rule used for the decision.
- Operations: Rehearse the status, assignment, connection, and evidence exceptions most likely on this route.
- Follow-through: Name who reviews daily exceptions, trains drivers, maintains devices, and preserves records.
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.
- Official carrier and driver implementation resources, compliant-device selection, transfer, training, and operating guidance — Federal Motor Carrier Safety Administration.
- Current first-party product, plan, feature, and support representations; dynamic facts require release-date recheck — Factor ELD.
Test the workflow on a representative route
Bring a vehicle, driver, route, mobile device, and the operation-specific exception scenario described in this guide. Factor ELD can demonstrate its current product; rule applicability remains a fleet compliance decision.