ELD edits, malfunctions and unidentified driving

Logs can be corrected without erasing the original record. Resolve actual driving attribution, then distinguish an ELD malfunction from a data diagnostic event.

Try
Chinese, English and citations
All tasks

11 / ELD EDITS, MALFUNCTIONS AND UNIDENTIFIED DRIVING

ELD edits, malfunctions and unidentified driving

Logs can be corrected without erasing the original record. Resolve actual driving attribution, then distinguish an ELD malfunction from a data diagnostic event.

Logs can be corrected without erasing the original record. Resolve actual driving attribution, then distinguish an ELD malfunction from a data diagnostic event.

Scope

For drivers and carriers subject to federal ELD rules. This topic does not expand personal-conveyance or yard-move allowances or authorize relabeling actual road driving to create hours.

01

Start with these requirements

Annotate edits and obtain the driver’s confirmation

CTAC PLAIN-LANGUAGE EXPLANATION
What the rule requires
Drivers must review, correct when necessary and certify records. Post-submission changes require recertification; the driver confirms or rejects carrier-proposed edits. Preserve original data, and do not coerce acceptance of inaccurate edits.

(b) (b) Review of records and certification by driver. (1) A driver must review the driver's ELD records, edit and correct inaccurate records, enter any missing information, and certify the accuracy of the information.

(b)(2) (2) Using the certification function of the ELD, the driver must certify the driver's records by affirmatively selecting “Agree” immediately following a statement that reads, “I hereby certify that my data entries and my record of duty status for this 24-hour period are true and correct.” The driver must certify the record immediately after the final required entry has been made or corrected for the 24-hour period.

(b)(4) (4) If any edits are necessary after the driver submits the records to the motor carrier, the driver must recertify the record after the edits are made.

(2) The driver or support personnel must annotate each change or addition to a record.

(d) Motor carrier-proposed edits. (1) On review of a driver's submitted records, the motor carrier may request edits to a driver's records of duty status to ensure accuracy. A driver must confirm or reject any proposed change, implement the appropriate edits on the driver's record of duty status, and recertify and resubmit the records in order for any motor carrier-proposed changes to take effect.

(2) A motor carrier may not request edits to the driver's electronic records before the records have been submitted by the driver.

(e) (e) Coercion prohibited. A motor carrier may not coerce a driver to make a false certification of the driver's data entries or record of duty status.

(f) (f) Motor carrier data retention requirements. A motor carrier must not alter or erase, or permit or require alteration or erasure of, the original information collected concerning the driver's hours of service, the source data streams used to provide that information, or information contained in any ELD that uses the original information and HOS source data.

Read the full section (English)

Uses a fixed source edition; check the original and statutory history for operative dates and exceptions.

Handle unidentified ELD driving according to the actual driver

CTAC PLAIN-LANGUAGE EXPLANATION
What the rule requires
On login, drivers review unidentified driving, add their own driving to their record, and indicate when it is not theirs. The carrier must also review, assign it to the proper driver or explain why it remains unassigned, and retain the required records for six months.

(a) (a) Tracking non-authenticated operation. The ELD must associate the non-authenticated operation of a commercial motor vehicle with a single account labeled “Unidentified Driver” as soon as the vehicle is in motion, if no driver has logged into the ELD.

(b) (b) Driver. When a driver logs into an ELD, the driver must review any unassigned driving time when prompted by the ELD and must:

(b)(1) (1) Assume any records that belong to the driver under the driver's account; or

(b)(2) (2) Indicate that the records are not attributable to the driver.

(c) Motor carrier. (1) A motor carrier must ensure that records of unidentified driving are reviewed and must:

(i) Annotate the record, explaining why the time is unassigned; or

(ii) Assign the record to the appropriate driver to correctly reflect the driver's hours of service.

(2) A motor carrier must retain unidentified driving records for each ELD for a minimum of 6 months from the date of receipt.

Read the full section (English)

Uses a fixed source edition; check the original and statutory history for operative dates and exceptions.

For a malfunction, notify promptly and reconstruct accessible records

CTAC PLAIN-LANGUAGE EXPLANATION
What the rule requires
Within 24 hours of discovering an ELD malfunction, the driver must notify the carrier in writing, reconstruct the current day and preceding seven days except records already available or retrievable, and continue the required paper records until compliance resumes. The carrier generally has eight days from discovery or notification, whichever is earlier, to repair, replace or service it; an extension request must be submitted to FMCSA within five days after the driver notifies the carrier and is subject to agency approval.
Conditions and exceptions
Handle data diagnostic events according to carrier and ELD-provider recommendations; not every alert permits prolonged paper logging.

(a)(1) (1) Note the malfunction of the ELD and provide written notice of the malfunction to the motor carrier within 24 hours;

(a)(2) (2) Reconstruct the record of duty status for the current 24-hour period and the previous 7 consecutive days, and record the records of duty status on graph-grid paper logs that comply with § 395.8, unless the driver already possesses the records or the records are retrievable from the ELD; and

(a)(3) (3) Continue to manually prepare a record of duty status in accordance with § 395.8 until the ELD is serviced and brought back into compliance with this subpart.

(c) (c) Driver requirements during ELD data diagnostic events. If an ELD indicates that there is a data inconsistency that generates a data diagnostic event, the driver must follow the motor carrier's and ELD provider's recommendations in resolving the data inconsistency.

(d) (d) Motor carrier requirements for repair, replacement, or service. (1) If a motor carrier receives or discovers information concerning the malfunction of an ELD, the motor carrier must take actions to correct the malfunction of the ELD within 8 days of discovery of the condition or a driver's notification to the motor carrier, whichever occurs first.

(d)(2) (2) A motor carrier seeking to extend the period of time permitted for repair, replacement, or service of one or more ELDs shall notify the FMCSA Division Administrator for the State of the motor carrier's principal place of business within 5 days after a driver notifies the motor carrier under paragraph (a)(1) of this section. Each request for an extension under this section must be signed by the motor carrier and must contain:

Read the full section (English)

Uses a fixed source edition; check the original and statutory history for operative dates and exceptions.

WORKED EXAMPLE

02

Unfamiliar driving appears after changing trucks

Illustrative scenario: a driver logs in to an assigned truck and sees unidentified driving left from the previous shift.

  1. Check the facts and claim only your driving

    Check handover times, vehicle and actual driving; do not accept another person’s driving merely to clear an alert.

  2. Have the carrier investigate

    Refer the unmatched record to the carrier, preserve explanations and edit history, and certify accurate logs.

The goal is an accurate record, not simply an alert-free screen.

03

Common mistakes in day-to-day work

“Dispatch fixed it, so I need not review it”

The driver still confirms or rejects proposed edits and recertifies the final record; an edit is not automatically lawful.

Full text and sources

REGULATION TEXT · ENGLISH

§ 395.30 ELD record submissions, edits, annotations, and data retention.

§ 395.30 ELD record submissions, edits, annotations, and data retention.

Source:www.ecfr.gov49 CFR 395.30
Open official website
Source edition date
2026-10-08
Captured

Edition noteOfficial-source snapshot; current consolidated law and subsequent amendments have not been verified.

Read the English originalHide the English original

Loading this English original…

REGULATION TEXT · ENGLISH

§ 395.32 Non-authenticated driver logs.

§ 395.32 Non-authenticated driver logs.

Source:www.ecfr.gov49 CFR 395.32
Open official website
Source edition date
2026-10-08
Captured

Edition noteOfficial-source snapshot; current consolidated law and subsequent amendments have not been verified.

Read the English originalHide the English original

Loading this English original…

REGULATION TEXT · ENGLISH

§ 395.34 ELD malfunctions and data diagnostic events.

§ 395.34 ELD malfunctions and data diagnostic events.

Source:www.ecfr.gov49 CFR 395.34
Open official website
Source edition date
2026-10-08
Captured

Edition noteOfficial-source snapshot; current consolidated law and subsequent amendments have not been verified.

Read the English originalHide the English original

Loading this English original…

Drafted from linked official texts and agency guidance. Both language interpretations are CTAC AI-assisted drafts pending human review; examples are illustrative, not member records. Capture dates are not legal effective dates.

CTAC plain-language explanations are not official translations or case-specific legal advice. Check scope, source editions and current official notices.