ELD Records Checklist

Supporting documents are paper records that verify the accuracy of ELD log data — fuel receipts, toll records, scale tickets, bills of lading, and dispatch records. Under 49 CFR 395.8(k)(1), the carrier must retain supporting documents that can identify the driver, date, location, and time. The regulation does not set a fixed number per day, but auditors expect enough records to verify on-duty status when log data is questioned.

An ELD malfunction does not end the HOS compliance obligation — it triggers a documented fallback. Under 49 CFR 395.34, the driver notes the malfunction in writing and reconstructs logs on paper for the period the device was down. The carrier has eight days to repair or replace it. What matters for an audit is the paper trail: when the malfunction was reported, what the driver recorded during the affected period, and when the device was fixed. A malfunction with no documentation looks like a records gap. A malfunction with a dated driver note, a repair invoice, and paper logs for the affected days is a clear, resolved event.

The operating carrier is responsible for records compliance, which means the carrier needs a way to access or receive ELD data from leased owner-operators before the audit, not on the day of the request. Whether that is a shared account, a periodic export from the operator, or a data feed from the ELD system is a logistics question the lease agreement should answer before any loads are dispatched. Discovering at audit time that an operator uses a different ELD platform with no transfer process is one of the harder problems to work around quickly.