ELD Records and HOS Supporting Documents: What the Auditor Actually Checks

There's a belief among small carriers that buying an ELD ended their hours-of-service recordkeeping problem. The device logs everything, the data lives in the cloud, done. Then the audit letter arrives asking for six months of records of duty status plus the supporting documents to verify them, and the carrier discovers the ELD was only ever half the requirement.

Here's the framing that makes the rest of this make sense: the ELD is a sensor, not a filing system. Part 395 has a paper trail that exists alongside the device, and that trail is what auditors actually pull on.

First: do you even need an ELD?

Most drivers who must keep records of duty status (RODS) must use an ELD. The exceptions are narrow and specific — and worth knowing precisely, because each is also a recordkeeping rule in disguise:

• Short-haul (§395.1(e)(1)). A CDL driver operating within a 150 air-mile radius of the normal work reporting location, returning and released within 14 hours, doesn't need RODS or an ELD. But the carrier must keep time records — start, end, and total hours per day — for 6 months. The exemption trades the ELD for a different record, not for nothing. And the HOS limits themselves (11-hour driving, 10 hours off, 60/70-hour) still fully apply; you're exempt from the log, not the rules.
• Pre-2000 engine. Vehicles with an engine model year 1999 or older are exempt. It's the engine, not the VIN — a 2003 glider with a 1998 engine qualifies; a 1999 truck with a remanufactured 2010 engine doesn't.
• Driveaway-towaway. When the vehicle being driven is itself the commodity being delivered.
• 8-days-in-30 (§395.8(a)). A driver required to keep RODS no more than 8 days in any 30-day period may use paper logs instead of an ELD. Useful for mostly-short-haul operations with occasional long runs.

If none of those fit, you're an ELD operation. The rest of this post is your recordkeeping map.

The HOS rules the records have to prove

Quick orientation, because every record below exists to verify these limits (§395.3, current since the 2020 rule):

• 11 hours of driving after 10 consecutive hours off duty, inside a 14-hour window that starts when you come on duty.
• A 30-minute break after 8 cumulative hours of driving — satisfiable by any non-driving status, including on-duty-not-driving.
• 60 hours in 7 days or 70 in 8, reset by a 34-hour restart.
• Sleeper splits: 10 hours may be split 8/2 or 7/3 — the longer period at least 7 consecutive hours in the berth, the shorter at least 2 — with neither qualifying period counting against the 14-hour window.

The 6-month rule, three ways

Part 395's retention requirements come in a cluster, and all three run six months:

1. RODS — 6 months (§395.8(k)). Every record of duty status, which for an ELD operation means the ELD data itself.
2. A back-up copy of ELD records — 6 months, on a separate device (§395.22(i)). This is the one nobody reads. The regulation requires the carrier to retain a back-up distinct from where the original data sits. In practice, your ELD vendor's cloud portal is the original; a periodic export you control is the back-up. If your vendor relationship ends badly — or the vendor ends, period — "the data was in their portal" is not a defense an auditor accepts.
3. Supporting documents — 6 months (§395.11). Covered next, because this is the half of the requirement small carriers don't know exists.

The driver-side counterpart: the driver must be able to produce the current day plus the prior 7 days of records at roadside, on the device or via transfer.

Supporting documents: the verification layer

The supporting documents rule exists because logs can lie and devices can be gamed. §395.11 requires the carrier to retain documents that verify RODS accuracy — and it defines exactly five categories:

1. Bills of lading, itineraries, schedules, or equivalents showing trip origin and destination
2. Dispatch records, trip records, or equivalents
3. Expense receipts related to on-duty-not-driving time — fuel, lumper fees, scale tickets, hotels
4. Electronic mobile communication records through a fleet management system
5. Payroll records, settlement sheets, or equivalents showing driver payment

The mechanics:

• The driver submits supporting documents to the carrier within 13 days.
• The carrier retains up to 8 documents per driver per 24-hour period. If more than 8 exist, keep at least the first and last of the day by time — those bracket the duty day, which is exactly what an auditor uses them for.
• Documents must be retrievable and matchable to the driver and date (§395.11(e)). Six months of fuel receipts in a shoebox technically exist; if you can't link a receipt to a driver-day, it doesn't do its regulatory job.

For a one-truck operation, this is genuinely manageable: most owner-operator days produce a rate confirmation, a fuel receipt or two, and a settlement — three to five documents, well under the cap. The discipline isn't volume; it's filing them by date as you go instead of reconstructing the year when the letter arrives.

What does an auditor do with them? Cross-checks. The fuel receipt timestamped 2:14 PM in Amarillo against a log showing sleeper berth in Albuquerque at 2:00 PM is how false-log violations get written. Your supporting documents are either your corroboration or your contradiction — which is the strongest argument for filing them yourself, matched to your logs, before anyone else does the matching for you.

The in-cab packet and the registered-device problem

Two ELD administrative requirements that surface at roadside and in audits:

The onboard information packet (§395.22(h)). Every ELD-equipped truck must carry: the user's manual, an instruction sheet for transferring data to an officer, a malfunction instruction sheet, and blank paper RODS grids sufficient for at least 8 days. These may be electronic — a PDF folder on the cab tablet satisfies it — but the blank grids are the item to take literally. They're not bureaucratic decoration; they're the fallback you'll be living on the day the device fails.

Your ELD must be on the FMCSA registered list — and stay on it. ELDs are self-certified by their vendors, and FMCSA removes devices that fail compliance review. It happens regularly: multiple devices were pulled from the list as recently as December 2025. When a device is revoked, carriers get a replacement window — typically 60 days — before drivers running the dead device are cited as having no ELD at all, with out-of-service exposure. The uncomfortable part of self-certification is that the cheapest device on the market is certified by the same mechanism as the best one. Check the registered list before you buy, and put a recurring reminder on checking it after — your vendor is not guaranteed to tell you they've been delisted.

When the ELD malfunctions

A malfunction is where the recordkeeping system proves it was real or reveals it wasn't. §395.34 gives the sequence:

1. Driver notes the malfunction and provides written notice to the carrier within 24 hours.
2. Driver reconstructs the current day and prior 7 days on paper grids — unless that data is retrievable from the device — and runs paper logs until it's fixed. (This is what the 8 days of blank grids in the packet are for.)
3. The carrier repairs or replaces the device within 8 days. Need longer, the extension request goes to your FMCSA Division Administrator within 5 days. Running past 8 days without an authorized extension risks an out-of-service order.

A practical note: most real-world "malfunctions" are power and connectivity — a loose harness, a diagnostic-port connection that vibrated free — and the device often comes back the same day. The regulatory clock doesn't care. The notice, the paper logs, and the 8-day window apply from the moment of malfunction, and the carriers who handle it cleanly are the ones whose blank grids were actually in the cab.

Personal conveyance: the honest version

The special driving categories — personal conveyance and yard moves — deserve a post of their own, but the audit-relevant core: personal conveyance is off-duty CMV movement, allowed only when you're relieved of all work responsibility, and never for the operation's commercial benefit. Driving to dinner from the truck stop is PC. Repositioning 80 miles closer to tomorrow's shipper "off duty" is the single most-flagged PC abuse, and your own ELD's GPS trail is what flags it. Yard moves are on-duty-not-driving, on private property only. Both are FMCSA guidance rather than regulation text, which means precision matters more, not less — guidance is what the officer at roadside is trained on.

What the auditor asks for, and what fails

In the HOS portion of a new-entrant audit, expect a request for specific drivers and date ranges: the RODS, and the supporting documents for those same days. The common findings, in rough order of frequency:

• Missing supporting documents. The logs exist; the verification layer doesn't. Six months of it.
• False logs. RODS contradicted by fuel receipts, tolls, GPS, or bill-of-lading times. The most serious finding — falsification is the kind of violation that fails audits outright.
• Unassigned driving time. ELD-recorded vehicle movement claimed by no driver. Small fleets accumulate it through yard moves and shop runs done without logging in; it has to be reviewed and annotated, not ignored.
• Form-and-manner errors. Missing trailer numbers, shipping document numbers, or location entries on the logs.
• No back-up copy. "It's in the vendor portal" — see above.

The quiet advantage of doing this right

Here's the thing the compliance-vendor industry rarely says plainly: for a one-truck operation, the ELD already does the hard part. The gap between you and a clean HOS audit is a filing habit — supporting documents matched to dates as they happen, a monthly data export you control, blank grids in the cab, and one recurring check that your device is still on the registered list.

Roadworthy HQ handles the storage half of that: HOS supporting documents upload against driver and date so they're matchable the way §395.11(e) requires, your ELD back-up exports live alongside them under the same 6-month retention enforcement, and the audit binder generator assembles the RODS-plus-supporting-documents package in the structure an auditor asks for. The device side — picking hardware that stays on the registered list and keeps a solid harness connection — is its own subject, and one we'll cover separately.

This article is general guidance, not legal advice. 49 CFR Part 395 and FMCSA's published ELD guidance are the authoritative sources, and the rules described are current as of 2026 — including a few pending rulemakings (sleeper-berth flexibility is a pilot program, not a rule change) that we'll cover if and when they become law.