Skip to main content

Trucking Mind

Nineteen checks. One score. This checker tests your operation against 49 CFR 395 Subpart B: the registered device, the driver accounts, the cab packet, data transfer, records and malfunctions. FMCSA removed 133 ELDs from the registered list on Nov 12, 2026. The DOT release names Nov 24, 2026 for out-of-service enforcement on revoked devices. A driver with a revoked device is treated at roadside as having no ELD at all.

Answer each question honestly. Every answer updates the result as you change each field.

About your operation

The device

Accounts and drivers

The cab packet

Data transfer

Records and certification

Malfunctions and access

Ready for inspection: no gaps found

Carrier running hardwired ELDs: 18 of 18 checks pass (100% ready)

Every applicable requirement in 49 CFR 395 Subpart B is met. Keep the revoked-list check on a weekly routine: FMCSA removed 133 devices on Nov 12, 2026. The list keeps moving.

The checks

CheckResultDetail
Registered ELDPassEvery device is on the FMCSA registered list.
Revoked-list checkPassEvery device was checked against the revoked list after the Nov 12 action.
CalibrationPassDevices are calibrated and maintained per provider specs (395.22(f)).
Portable mountingN/AHardwired ELDs need no mounting check. Section 395.22(g) covers portable ELDs only.
Driver usernamesPassEvery account has a unique username, never a license number or SSN (395.22(c)(2)).
License verificationPassLicenses used to create driver accounts are valid and match the driver (395.22(b)(2)(iii)).
Proper log-inPassDrivers and support staff log in with proper identification data (395.22(e)).
Driver instructionPassDrivers are instructed on duty status, annotations and roadside transfer (395.24).
Data transfer sheetPassTransfer instruction sheet is in every cab (395.22(h)(1)).
Malfunction sheetPassMalfunction instruction sheet is in every cab (395.22(h)(2)).
Blank gridsPassBlank graph-grids for at least 8 days are in every cab (395.22(h)(3)).
Roadside data transferPassDrivers can produce and transfer records on request (395.24(d)).
Daily certificationPassDrivers review and certify each 24-hour record daily (395.30(b)).
Edit procedurePassCarrier-proposed edits need driver confirmation and recertification. Originals stay intact (395.30(d), (f)).
Supporting documentsPassDocuments are collected within 13 days and kept 6 months, 8 per day with earliest and latest times (395.11, 395.8(k)).
Records backupPassA backup copy of ELD records is kept 6 months on a separate device (395.22(i)(1)).
Unidentified drivingPassUnidentified driving is reviewed, annotated or assigned. Kept 6 months (395.32).
Malfunction procedurePassProcedure covers 24-hour notice, paper logs, 8-day repair and the 5-day extension request (395.34).
Driver record accessPassDrivers can access their own ELD records without going through the carrier (395.36).

The figures

FigureValueNote
Readiness score100%Share of applicable checks passed
Checks passed18 of 18Fails plus warnings listed below
Fails0 failsEach fail is a requirement the rule states plainly
Warnings0 warningsEach warning is an item to confirm, not a pass
Cab packet complete3 of 3 itemsData transfer sheet, malfunction sheet, blank grids for 8 days
Days to Nov 24 enforcement5 daysDOT release names Nov 24, 2026 for out-of-service enforcement on revoked devices. FMCSA notice points to Jan 12, 2027. Plan around the earlier date.
Data transfer methodTelematics plus localEvery registered ELD supports a primary method plus a backup

What to do

  • No actions for this result.

Notes

  • No user manual is required in the cab. FMCSA rescinded the ELD manual rule on Jul 22, 2026 (91 FR 37053). Do not fail a truck for a missing manual.
  • Two FMCSA dates conflict for the Nov 12 revoked devices: the DOT release names Nov 24, 2026 for out-of-service enforcement, while the FMCSA carrier notice points to Jan 12, 2027. Plan around Nov 24, the earlier date.

This checker applies 49 CFR 395 Subpart B to your answers. Confirm the result against the current regulation before you rely on it.

Your inputs stay in this browser. Nothing is sent to our servers. There is no account to create.

Disclaimer: This tool is provided for general information only. It is not legal advice — check the current regulation before you rely on a result.

Quick answer: ELD compliance means a registered device, clean driver accounts, a three-item cab packet, working data transfer, daily certification, six-month records and a written malfunction procedure, all under 49 CFR 395 Subpart B. The user manual is no longer required in the cab since Jul 22, 2026. The urgent item is the device itself: FMCSA removed 133 ELDs from the registered list on Nov 12, 2026. The DOT release names Nov 24, 2026 for out-of-service enforcement on revoked devices. This checker scores your operation against 19 requirements and lists the exact fix for each gap.

Last reviewed: · Focus keyword: ELD compliance checklist

What does ELD compliance actually require?

The ELD rule lives in 49 CFR Part 395, Subpart B, sections 395.20 through 395.38. It splits the work between carrier and driver. The carrier picks a registered device, manages the accounts, keeps the records and fixes malfunctions. The driver logs in properly, enters duty status, certifies each day and produces the records at roadside. An operation that buys a compliant device and stops there is not compliant. The device is one requirement among many. The account, packet, transfer and records duties fail just as often at inspection.

The rule has teeth at roadside. An inspector checks the device registration, the cab packet and the records for the current 24-hour period plus the previous seven days. A driver who cannot produce records, or whose device is not on the registered list, is treated as having no record of duty status. That is a citation under 395.8(a)(1). It can put the driver out of service. The same gaps surface in a safety audit, where the inspector reads the back-office records instead: the backup, the unidentified driving log, the edit history and the supporting documents. This checker tests both sides, the cab side and the office side, because an audit reads both.

SectionWho it bindsWhat it requires
395.22CarrierRegistered device, accounts, calibration, mounting, cab packet, backup, record production
395.24DriverDuty status entry, manual inputs, produce and transfer records on request
395.26DeviceAutomatic recording: date, time, location, engine hours, miles, driver, vehicle and carrier IDs
395.28Carrier plus driverPersonal use and yard moves: select before the status starts, annotate when prompted
395.30Driver plus carrierDaily certification, annotated edits, driver confirmation of carrier-proposed edits
395.32Carrier plus driverUnidentified driving reviewed, annotated or assigned, kept 6 months
395.34Driver plus carrierMalfunction notice in 24 hours, paper logs, repair in 8 days, extension request in 5 days
395.36CarrierDriver access to driver own ELD records without going through the carrier

The checker runs 19 checks across those sections and turns them into one readiness score. A fail is a requirement the rule states plainly. A warning is an item you could not confirm. An unconfirmed item is not a pass: it is a violation waiting for an inspector to find it. The mounting check applies only to portable ELDs, so a hardwired fleet scores out of 18 checks and a portable fleet out of 19. Work through the actions in order. The device comes first, because an unlisted or revoked ELD makes every other fix pointless until it is replaced.

Is your ELD still on the registered list?

On Nov 12, 2026, FMCSA removed 133 electronic logging devices from its Registered Devices List in the largest ELD revocation in agency history. FMCSA revoked 121 devices from 83 providers for failing the minimum technical requirements in Appendix A to Subpart B of Part 395. Twelve more devices were withdrawn by their own providers. The action followed smaller removals through 2026: four devices on Jan 13, fourteen on Mar 4, twelve on May 20, plus notices on Jun 23 and Jul 9 and five devices on Aug 6. The registered list is not a one-time purchase decision. It moves. A device that was compliant when you bought it may not be compliant today.

The deadline for replacing a revoked device is the subject of a live conflict between two FMCSA documents. The conflict matters because the two dates are seven weeks apart. The DOT press release of Nov 12 says carriers have up to 60 days to replace the revoked ELDs, but tells inspectors who encounter a revoked device on or after Nov 24, 2026 to cite 395.8(a)(1) and place the driver out of service. Nov 24 is twelve days after the announcement, not sixty. The FMCSA notice to carriers of Nov 13 also says carriers have up to 60 days, but names Jan 12 as the replacement date, printed with the year 2026, which reads as a typo for 2027. That notice does not mention Nov 24 at all. A CVSA regulatory update of Nov 13 supports the January date. As of Nov 19, 2026, FMCSA has not reconciled the two dates. This checker plans around Nov 24, the earlier date. If the 60-day date turns out to be the real one, you replaced a compromised device seven weeks early and lost nothing. If Nov 24 is real and you planned for January, your drivers sit at a scale house for ten hours each.

FMCSA also directs affected operators to discontinue using revoked devices at once and switch to paper logs or logging software while a registered replacement is installed. Do not wait for an enforcement date to stop using a revoked device. Check every device by name, model number and ELD identifier on the FMCSA lists at eld.fmcsa.dot.gov/List, where the registered list and the revoked list sit side by side. One caution from the Nov 12 action: the twelve self-revoked devices had not yet appeared on the revoked list on the evening of Nov 12, so a clean search on one day is not final. Recheck weekly. Our FMCSA Revoked ELD Checker looks a device up against the revoked list and shows the replacement deadline. A carrier that finds a revoked device in its fleet should also run the ELD Malfunction Countdown to track the paper-log period while the replacement is fitted.

What must be in the cab packet now that the manual is gone?

Until Jul 22, 2026, every truck carrying an ELD also had to carry the ELD user manual. That requirement is gone. A final rule published Jun 22, 2026 at 91 FR 37053 rescinded the manual requirement in former 395.22(h)(1), effective Jul 22, 2026. Trade press reported more than 3,000 citations for the missing manual in 2024 alone, which made it one of the most-cited ELD items on the road. A driver stopped today cannot be cited for a missing manual. A carrier auditing its own cabs should not fail a truck for one. This checker does not ask about the manual at all. The notes under the result say so plainly.

Three items remain in the cab packet. The rescission renumbered them, which is a trap for anyone reading an old citation. The current 395.22(h) lists (h)(1) an instruction sheet describing the data transfer mechanisms the ELD supports, with step-by-step instructions to produce and transfer records to an authorized safety official; (h)(2) an instruction sheet describing ELD malfunction reporting requirements and recordkeeping procedures during malfunctions; and (h)(3) a supply of blank driver records of duty status graph-grids sufficient for a minimum of 8 days. Before Jul 22 those same items sat at (h)(2), (h)(3) and (h)(4). A violation written after Jul 22 against (h)(4) cites a paragraph that no longer exists. A checklist copied from a pre-July source will point at the wrong items.

FMCSA guidance allows the packet in electronic form: the instruction sheets and the blank grids can live on a device. A logging software app meets the blank-grid requirement, under the electronic documents rule at 83 FR 16210 and 49 CFR 390.32(b). Paper still has a practical edge. The grids matter most during a malfunction, which is exactly when the device may be dead. A truck with electronic grids only and a dead tablet has no way to reconstruct the current day plus the previous seven days on paper, as 395.34(a)(2) requires. Keep paper grids in the cab even when the rest of the packet is electronic. Eight days is a minimum, not a target: a malfunction repair can run the full eight days. The extension request needs the paper record to continue past that.

How do drivers transfer ELD data at roadside?

Section 395.24(d) puts the duty on the driver: on request by an authorized safety official, the driver must produce and transfer the hours-of-service records from the ELD, following the instruction sheet the carrier provided. The ELD technical specifications in Appendix A to Subpart B define two transfer option groups. A telematics ELD transfers by wireless web services plus email. A local ELD transfers by USB 2.0 plus Bluetooth. Every registered ELD supports a primary electronic method plus one electronic backup. The on-screen display is the universal fallback when electronic transfer fails. The driver chooses the method, but the driver cannot refuse to present the records: refusal can bring an out-of-service order.

What the officer sees is the standardized output file, not the whole device. At roadside the ELD must show the current 24-hour period plus the previous seven consecutive days, per Appendix A section 4.9.1. The output file holds only the FMCSA-defined data elements: date, time, location, engine hours, vehicle miles, driver and vehicle and carrier identification, plus the duty status events. It does not expose the rest of the phone or tablet. Drivers who worry about privacy at roadside should know that the transfer is limited by design. The carrier has a separate duty under 395.22(i)(2) to retain ELD records in a way that protects driver privacy.

The practical failure is not the technology. It is the driver who has never run a transfer. A driver fumbling through menus while an inspector waits will eventually produce the display, but the delay invites a closer look at everything else. A failed transfer on the first method with no attempt at the backup looks like a device problem. Test the transfer with each driver before an inspection finds the failure: run the primary method, run the backup, then show the display. Note that a single failed roadside transfer does not by itself prove a data-transfer malfunction under the technical specifications. It proves the driver or the device needs attention before the next stop. The transfer instruction sheet in the cab packet exists for exactly this moment, which is why the checker treats it as its own item rather than folding it into the device check.

What records must a carrier keep and for how long?

The retention clock for ELD records is six months. It runs from the date of receipt, not from the date of the trip. Section 395.8(k)(1) requires the carrier to retain records of duty status and supporting documents for each driver for at least six months from receipt. Section 395.22(i)(1) requires a backup copy of the ELD records for six months on a device separate from the one holding the original data. Section 395.32(c)(2) requires unidentified driving records for at least six months. The driver carries a shorter clock: under 395.8(k)(2) the driver must keep a copy of each record of duty status for the previous seven consecutive days in possession while on duty. Under 395.8(a)(2) the driver must submit the records to the carrier within 13 days.

RecordSectionHow longWho keeps it
Records of duty status395.8(k)(1)6 months from receiptCarrier
Supporting documents395.8(k)(1), 395.116 months from receiptCarrier
ELD records backup395.22(i)(1)6 months, separate deviceCarrier
Unidentified driving records395.32(c)(2)6 months from receiptCarrier
Driver copy of RODS395.8(k)(2)Previous 7 days, in possessionDriver
RODS submission to carrier395.8(a)(2)Within 13 daysDriver
Supporting document submission395.11(b)Within 13 daysDriver

Supporting documents have their own selection rule in 395.11. It trips up carriers that keep everything or keep the wrong set. The carrier must retain the supporting documents generated or received in the normal course of business across five categories: bills of lading and trip records, dispatch records, expense receipts, electronic mobile communication records plus payroll records. A supporting document needs four data elements: a link to the driver, a date, a location and a time. The carrier need retain at most eight supporting documents per driver per 24-hour period. When more than eight exist the retained set must include the documents with the earliest and the latest time indications. A full day of electronic messages counts as one document. Toll receipts are extra for paper-log periods. Carriers working out purge dates for every record type can use the DOT Record Retention Schedule Checker.

Certification and edits sit on top of retention. Under 395.30(b) the driver must review the ELD records, correct inaccuracies, enter missing information and certify each 24-hour record immediately after the final entry, using the certification statement in the ELD. Under 395.30(c)(2) every change or addition must be annotated. Under 395.30(d) the carrier may propose edits only after the driver has submitted the records. A proposed edit takes effect only when the driver confirms or rejects it, implements the edit and recertifies. Under 395.30(f) the carrier must not alter or erase the original data. Automatically recorded driving time cannot be edited into non-driving time. A carrier that edits logs in the back office without the driver is not fixing records. It is falsifying them. The penalty schedule in Part 386 Appendix B treats falsification as one of the most serious record offenses. Drivers checking their own hours against the limits can use the HOS Calculator to see where each clock stands.

What happens when an ELD malfunctions?

A malfunction is not a free pass to paper logs. Section 395.34 sets a tight sequence with three clocks. The carrier clock is the one that ends the paper period. The driver must note the malfunction and give written notice to the carrier within 24 hours. The driver must then reconstruct the record of duty status for the current 24-hour period plus the previous seven consecutive days on graph-grid paper logs, unless the driver already holds those records or they are retrievable from the ELD. The driver keeps paper logs until the ELD is serviced and back in compliance. That is why the cab packet carries eight days of blank grids: the paper period is designed to last exactly as long as the repair window.

The carrier must correct the malfunction within eight days of discovering it or receiving the driver notification, whichever comes first. If the repair needs more time, the carrier must notify the FMCSA Division Administrator for the state of its principal place of business within five days after the driver notification, with the contents listed in 395.34(d)(2): the carrier name and address, the driver name, the ELD make and model, the date of the malfunction and the location, plus a statement of the good-faith effort to repair and why more time is needed. A request that meets the requirements keeps the carrier deemed in compliance until FMCSA decides. A carrier that misses the five-day request window and runs past eight days on paper is operating without a compliant ELD. The ELD Malfunction Countdown tracks all three deadlines from the malfunction date.

Data diagnostic events are different from malfunctions. The distinction matters for the paperwork. A diagnostic event flags a data inconsistency, such as missing location data or an unidentified driver profile with driving time. Under 395.34(c) the driver follows the carrier and provider recommendations to resolve it and still reviews and certifies the record. No 24-hour notice and no paper logs are required for a diagnostic event alone. A malfunction means the ELD can no longer record hours accurately or present them to an inspector. That triggers the full 395.34 sequence. Appendix A Table 4 lists seven malfunction codes and six data diagnostic codes. A driver who treats a malfunction as a diagnostic event, or a diagnostic event as a malfunction, gets the paperwork wrong in both directions.

Who is exempt from the ELD rule?

Not every driver needs an ELD. This checker is built for the drivers who do. The four ELD exceptions sit in 395.8(a)(1)(ii)(A)(1) through (4): a driver who must complete a record of duty status on not more than eight days within any 30-day period; a driver in a driveaway-towaway operation where the vehicle being driven is part of the shipment; a driver in a driveaway-towaway operation where the vehicle being transported is a motor home or a recreation vehicle trailer; and a driver operating a vehicle manufactured before model year 2000, as reflected in the vehicle identification number as shown on the vehicle registration. The pre-2000 test is the vehicle model year on the registration, not the engine year. Paragraph (a)(1)(iii) is often misread as the exceptions list. It is not. It is the expired transition paragraph that governed the period before Dec 18, 2017. It has no live effect.

Short-haul drivers sit outside the ELD rule on a different footing. The short-haul exception in 395.1(e) exempts a qualifying driver from 395.8 entirely, which means no record of duty status and no ELD, as long as the driver stays within the 150 air-mile radius and returns to the reporting location within the allowed hours. A short-haul driver who breaks the radius or the hours on a given day must complete a record of duty status for that day. A driver who breaks it more than eight days in 30 days needs an ELD. The ELD Exemption Checker runs the full decision tree, including the eight-day counter. Drivers testing the short-haul conditions can use the Short-Haul Exemption Checker. The HOS Exemption Quiz covers the wider set of hours-of-service exceptions.

Exempt does not mean record-free. A driver using one of the four (a)(1)(ii) exceptions still keeps a record of duty status, on paper, in duplicate, on the specified graph grid under 395.8(a)(1)(ii)(B). A short-haul driver keeps time records under 395.1(e)(1). Exemptions are also trip by trip: a driver who is exempt on Monday because the vehicle is pre-2000 and drives a 2024 truck on Tuesday needs an ELD on Tuesday. The checker asks whether all, some or none of your drivers must use ELDs. It refuses to score an operation where no driver needs one, because the right next step there is confirming the exception, not auditing a device nobody uses. The fine for operating without a required ELD is set in the Part 386 Appendix B penalty schedule. The FMCSA Fines Calculator shows the current amounts.

How do you use the ELD Compliance Readiness Checker?

Work through the questions in order. The checker updates with every change, so you can fix an answer and watch the score change.

  1. Pick your role, your ELD type, plus whether your drivers must use ELDs.
  2. Answer the device questions: registration, revoked-list check, calibration, mounting.
  3. Answer the account, cab packet and data transfer questions.
  4. Answer the records, certification, malfunction and access questions.
  5. Read the readiness score, the check table and the gaps to fix.
  6. Work through the actions, then recheck the result before the next inspection.

Run the check again after every fix. The score moves with each answer, so a carrier that replaces a revoked device, stocks the cab packet and sets up the backup can watch the result climb from high risk to ready in one session. Keep the revoked-list check on a weekly routine: the list changed five times in 2026 before November, then 133 devices went in a single day.

Frequently asked questions

Do I still need an ELD user manual in the truck?

No. FMCSA rescinded the ELD user manual requirement on Jul 22, 2026, in a final rule published at 91 FR 37053. The cab packet now holds three items: the data transfer instruction sheet, the malfunction instruction sheet, plus blank graph-grids for at least 8 days. A driver cannot be cited for a missing manual. This checker does not ask about one.

What is the deadline to replace a revoked ELD?

Two FMCSA dates conflict. The DOT press release of Nov 12, 2026 names Nov 24, 2026 for out-of-service enforcement on the 133 revoked devices. The FMCSA notice to carriers of Nov 13 points to Jan 12, 2027. FMCSA has not reconciled the two dates as of Nov 19, 2026. Plan around Nov 24, the earlier date. Stop using a revoked device at once.

How long must a carrier keep ELD records?

Six months from the date of receipt. That covers records of duty status and supporting documents under 395.8(k)(1), the ELD records backup on a separate device under 395.22(i)(1), plus unidentified driving records under 395.32(c)(2). The driver must carry the previous 7 days of records while on duty and submit records to the carrier within 13 days.

Can a carrier edit a driver log without the driver?

No. Under 395.30(d) the carrier may propose edits only after the driver has submitted the records. The edit takes effect only when the driver confirms or rejects it, implements the edit and recertifies. Under 395.30(f) the carrier must not alter or erase the original data. Automatically recorded driving time cannot be edited into non-driving time.

What must a driver do when an ELD malfunctions?

Under 395.34(a) the driver must note the malfunction and give the carrier written notice within 24 hours, reconstruct the record of duty status for the current 24-hour period plus the previous 7 days on graph-grid paper logs. Keep paper logs until the ELD is serviced. The carrier must correct the malfunction within 8 days or request an extension within 5 days.

What counts as an ELD exception?

Four exceptions sit in 395.8(a)(1)(ii)(A)(1) through (4): a record of duty status required on not more than 8 days in any 30-day period, driveaway-towaway where the driven vehicle is part of the shipment, driveaway-towaway of a motor home or recreation vehicle trailer, plus a vehicle manufactured before model year 2000 per the VIN on the registration. Short-haul drivers are exempt under 395.1(e).

Related tools

Sources

Follow on WhatsApp Ask by Voice