DOT Serenity
Sign In

Compliance Resource

06 / OPERATIONS

Hours of Serviceand ELD

Understand the administrative side of hours-of-service applicability, supporting documents and electronic logging responsibilities.

Last Reviewed
2026-09-16
Reading Time
2 min
Who This Is For
Motor carriers determining whether the ELD requirement applies to their drivers.

Scroll To Read ↓

In This Guide

At A Glance

  • The ELD requirement follows from the duty to keep a record of duty status under §395.8 — not every driver has that duty
  • Four named exceptions exist: short-haul, the 8-day paper-log allowance, driveaway-towaway, and pre-2000 engines
  • Exception status can change if a driver's routes or duties change
  • This guide covers applicability only, not real-time HOS monitoring
01

What This Guide Covers

Who is required to use an electronic logging device under FMCSA's rule, and the specific, named exceptions to that requirement — the administrative question, not real-time hours-of-service monitoring.

02

How This Area Fits Your Operation

Any driver required to keep a record of duty status (RODS) under 49 CFR 395.8 must generally use an FMCSA-registered ELD. The rule recognizes specific, limited exceptions: the short-haul exception (no RODS required at all, so no ELD either), drivers using paper RODS no more than 8 days in any rolling 30-day period, driveaway-towaway operations, and vehicles older than model year 2000. A driver's exception status isn't fixed forever — if their typical route or duty pattern changes, whether an exception still applies needs to be re-checked, not assumed to carry over.

Diagram: Hours of Service and ELD connects to the following records: Determination of whether each driver falls under an ELD exception; ELD provider and device-assignment information, where an ELD is used; Paper RODS, for drivers using the 8-day exception; Any malfunction documentation and the required driver/carrier response records. Related dates or events: Ongoing: re-confirming exception status if a driver's duties or routes change.
03

Records To Organize

  • 01Determination of whether each driver falls under an ELD exception
  • 02ELD provider and device-assignment information, where an ELD is used
  • 03Paper RODS, for drivers using the 8-day exception
  • 04Any malfunction documentation and the required driver/carrier response records
04

Dates That May Require Attention

  • Ongoing: re-confirming exception status if a driver's duties or routes change
05

Common Administrative Mistakes

  • Assuming a short-haul driver is automatically exempt without checking the specific mileage/duty-hour conditions that define the exception
  • Not re-evaluating exception status when a driver's typical route or schedule changes
06

When To Confirm The Requirement

The exact mileage radius, duty-hour limits and other conditions attached to each ELD exception are defined precisely by FMCSA and can change — confirm the current exact terms of any exception you're relying on directly with FMCSA before treating a driver as exempt.

07

Official Sources

DOT Serenity is an independent service and is not affiliated with, endorsed by, or operated by FMCSA, USDOT or any other government agency. Links above go directly to each agency’s own official site.

08

How DOT Serenity Fits

How DOT Serenity Fits

This area is in development. Today, DOT Serenity can flag whether the ELD/hours-of-service requirement applies to your operation and surface the related recordkeeping duty as a reminder. It is not connected to any ELD provider, does not receive live logs, and does not track driver hours.

09

Important Boundary

DOT Serenity is not an ELD and does not replace the carrier's own logging system.

Ready For
Compliance Without
The Chaos?

Organize the records. See what’s coming. Get support when you need it.

Work
With Us