Drayage fleets need an ELD workflow built around ports, terminals, queues, chassis changes, short moves, and frequent dispatch updates while preserving accurate duty records.
What this means for your fleet
Gate queues, yard movement, terminal geofences, chassis pickup, and local interstate work can look similar on a map but have different operational context. Define when yard move is allowed and how drivers document delays.
Worked operating scenario
A driver enters a terminal queue, makes an authorized yard move, swaps chassis, leaves on a public road, and loses cellular service. The pilot verifies start/end of yard move, annotation, tractor/driver identity, queue context, offline recording, reconnect, and final exception review.
What a passing test includes
Check each item in the same scenario: Map port and terminal geofences; set yard-move policy; control tractor and driver swaps; capture queue and dispatch context; test connectivity recovery. 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. Map port and terminal geofences | Map each terminal, yard, public-road boundary, and approved special-driving area; retain the policy owner and review date. |
| 2. Set yard-move policy | Test yard-move authorization, selection, annotation, end conditions, and the first ordinary-driving event at a real facility. |
| 3. Control tractor and driver swaps | Record driver, tractor, device, login, handoff time, unassigned-driving review, and acceptance result for each swap. |
| 4. Capture queue and dispatch context | Attach terminal appointment, queue timestamps, dispatch messages, duty-status decisions, and driver annotations. |
| 5. Test connectivity recovery | Run a controlled connection loss and recovery; retain queued events, reconciliation result, defect, support case, 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.
- Official recording-HOS FAQ covering duty status, personal conveyance, yard move, team-driver records, odometer/location data, and edits — 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.
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.