Waste-hauling fleets should classify vehicles and routes, then design ELD or time-record workflows for early starts, dense stop cycles, transfer stations, landfills, roll-off work, and shared trucks.
What this means for your fleet
Repeated short movements and jobsite activity can create login, assignment, and status errors even on local routes. A daily exception review should focus on shared vehicles and unassigned movement.
Worked operating scenario
A shared roll-off truck runs an early dense-stop route through a transfer station and landfill. The fleet records short-haul facts, controls driver handoff, reviews unidentified movement, maps collection/disposal work, and tests power/mounting before relying on the device.
What a passing test includes
Check each item in the same scenario: Classify route and short-haul eligibility; control shared-truck login; map collection and disposal work; review unassigned movement; test rugged mounting and power. 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. Classify route and short-haul eligibility | Classify representative collection and disposal routes with reporting location, radius, duty window, vehicle, commerce facts, provision, and reviewer result. |
| 2. Control shared-truck login | Keep unique driver logins, shared-truck assignments, handoff times, device displayed user, unidentified movement, correction, coaching, and retest. |
| 3. Map collection and disposal work | Time collection stops, compactor or loading work, disposal-site queues and public-road legs; map actual work to statuses and retain dispatch context. |
| 4. Review unassigned movement | Preserve each unassigned movement with truck, time, location, login, route/maintenance context, proposed assignment, driver response, and final disposition. |
| 5. Test rugged mounting and power | Retain mounting and cable photos, connector, stable-power observations through engine cycles and vibration, engine values, defect, correction, and repeat test. |
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 ELD exceptions and exemptions FAQ — Federal Motor Carrier Safety Administration.
- Unidentified and unassigned driving-time workflow — Federal Motor Carrier Safety Administration.
- Current first-party application and manual download options — Factor ELD.
- 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.