ELD Regulations Guide

This is the baseline recordkeeping rule. It defines the duty-status record itself, the four core status buckets, and the information that has to be captured for each 24-hour period.

• Legacy logbook requirement for drivers who must keep a record of duty status.
• Defines what must be recorded, including driving, on-duty not driving, off-duty, and sleeper berth time.
• In modern operations, an ELD is the tool most carriers use to satisfy this recordkeeping obligation instead of a handwritten log.

This is the applicability gate for the ELD subpart. It tells you when the ELD rules apply and frames who falls into the ELD regime.

• Mandates ELD use for most drivers who would otherwise be keeping RODS under § 395.8.
• Works with the broader Part 395 exceptions that commonly matter in practice, including short-haul operations, limited-days logging, certain driveaway-towaway operations, and pre-2000 model year engines.
• Useful starting point when you need to answer the threshold question: does this driver or fleet need an ELD at all?

This section covers the carrier-side operating obligations around ELD use. It is where account management, registration, calibration, mounting, and required in-vehicle materials become concrete compliance duties.

• Requires use of registered ELDs and proper account management for drivers and support staff.
• Connects directly to the technical ELD regime, including engine-linked operation, roadside transfer readiness, and required user documentation carried in the vehicle.
• Read this together with Appendix A if you are evaluating whether a device and deployment actually meet the spec.

This is the driver-side operational rule. It governs how the driver uses the ELD in the field, interacts with records, and handles abnormal situations.

• Defines everyday driver interaction with the ELD, including logging in under the correct account and reviewing the record.
• Works with the surrounding ELD sections on edits, supporting materials, and malfunction handling.
• Important for training, roadside inspection readiness, and documenting what drivers must do when the device cannot operate normally.

This is the actual technical specification. If you are building, validating, or certifying an ELD system, this appendix is the implementation document that matters most.

• Defines the output file structure, data elements, event types, and integrity checks.
• Covers engine synchronization, motion status, geo-location, account behavior, diagnostics, and malfunction handling logic.
• Specifies the transfer mechanisms and communications standards used for roadside and carrier-side data exchange.