The short-haul exception can replace the driver's daily RODS/ELD record with qualifying time records only when every condition of the applicable exception is met. “Local” work or returning home most nights is not enough by itself.
What this means for your fleet
Track the operating radius, reporting location, start and release time, and exception eligibility for each day. Define what happens on a day that exceeds a limit and how the fleet counts non-qualifying days.
Federal short-haul conditions to test for the day
The current federal short-haul exception uses a 150 air-mile radius and a 14-hour duty window, along with return to the normal work-reporting location and required time records. It is a day-specific test, not a permanent fleet label. A driver who breaks a condition must use the required RODS method for that day and should not assume an ELD exception without checking all applicable facts.
What to check
Use these checks before changing a log, policy, device, integration, or buying decision.
| Check | How to verify |
|---|---|
| 1. Identify the exact short-haul provision | Cite the exact current short-haul provision and retain driver/carrier type, normal reporting location, operation, reviewer, and dated scope decision. |
| 2. Record reporting location and time | Keep each day's reporting location, start/release times, total on-duty time, driver, vehicle, source time records, and exceptions. |
| 3. Monitor radius and duty window | Record route points and air-mile calculation, duty window, return result, limit breach alert, reviewer, and day-level pass/fail result. |
| 4. Switch workflow on a non-qualifying day | Complete a day that fails a condition; retain detection, required RODS/ELD transition, statuses, edits, certification, dispatch action, and review. |
| 5. Retain the required time records | Retain the required time records by driver/date with start, end, total hours, carrier owner, six-month destruction date, retrieval test, and gaps. |
Common failure modes
- Calling every city route short haul.
- Failing to detect a limit breach.
- Assuming an ELD exception removes HOS obligations.
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.
- Current 49 CFR Part 395 text covering HOS limits, exceptions, RODS, supporting documents, ELD duties, and technical requirements — Office of the Federal Register and U.S. Government Publishing Office.
- Official ELD exceptions and exemptions FAQ — 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.