Electronic Logging: Exemptions, Edits and Malfunctions
The device records automatically and the record cannot be unwritten. Everything that follows an error is therefore an annotation problem, and carriers that try to solve it by deletion produce the one finding an investigator does not treat as clerical.
The rule in short
A driver required to keep records of duty status must use a registered electronic logging device under 49 CFR 395.8 and the subpart beginning at 49 CFR 395.20. The exemptions are narrow: short-haul drivers, drivers logging eight days or fewer in thirty, driveaway-towaway operations, and older engines. Driving time recorded automatically may be annotated but never shortened or erased, and a malfunctioning device must be repaired within eight days.
The mandate is narrower than most people state it and stricter than most people implement it. It reaches drivers who are required to keep records of duty status, and it forbids one specific act: reducing or erasing driving time the device captured on its own. Everything else about the record is negotiable through annotation.
Who the requirement reaches
Section 31137 of title 49 directed the agency to require devices for drivers required to keep records of duty status, and 49 CFR 395.8 carries that through. The trigger is therefore the record obligation, not the vehicle. A driver operating a commercial motor vehicle who is relieved of the record of duty status obligation by an exception in 49 CFR 395.1 is outside the device requirement for the same reason.
That structure produces four practical exemptions. The short-haul driver operating within the air-mile radius and released within the stated window keeps time records instead of logs. A driver who keeps records of duty status on eight days or fewer in any period of thirty days may use paper for those days. Driveaway-towaway operations where the vehicle being driven is itself the commodity delivered are excluded. So is a vehicle whose engine is older than model year 2000, because the device draws its data from the engine control module.
What an edit can and cannot do
Section 395.30 governs corrections. A driver may edit and annotate his own record. A carrier may propose an edit, but the proposal has no effect until the driver accepts it, and a rejected proposal leaves the original standing with the rejection recorded. Every edit carries an annotation, and the original entry remains retrievable beside the edited version, so the record grows rather than changes.
One category is closed. Driving time automatically recorded by the device may not be shortened, and it may not be deleted. A driver who believes the device recorded driving that was not his may annotate the entry to say so, and the carrier may annotate its own explanation, but the minutes stay on the record. The dispute is resolved by the annotations and the supporting documents, not by making the entry disappear.
Missing logs and late annotations are routine review findings. Evidence that recorded driving time was reduced is a different category, because the regulation contemplates no circumstance in which it is permissible. Investigators look for edits that shorten driving segments and for accounts with editing privileges that no driver ever accepted a change from. A carrier that permits back-office deletion as normal practice has built a falsification pattern out of what began as an attempt to fix a mistake.
Unassigned driving and the review duty
Section 395.32 addresses driving the device recorded while nobody was logged in. The carrier must review those records and either assign them to the driver who was operating, in which case that driver must accept or reject the assignment, or annotate them with an explanation of why the time is not attributable to a driver. Yard moves by mechanics and short repositioning at a terminal are the ordinary explanations, and they have to be written down.
The reason this receives so much attention in an investigation is that it is measurable without reading anything. A carrier with hundreds of unassigned hours has either a training problem or an attribution problem, and both point at the same place. Where unassigned time correlates with drivers near the weekly limit described in the driving, duty and rest limits, the inference an investigator draws is not favorable.
| Situation | What the record must show | Who acts | Deadline |
|---|---|---|---|
| Driver corrects his own entry | Edit plus annotation, original retained | The driver | Before certifying the day |
| Carrier proposes a correction | Proposed edit, then acceptance or rejection | Carrier proposes, driver decides | No effect until the driver acts |
| Automatically recorded driving time | Annotation only; minutes stay | Either party may annotate | Not applicable |
| Unassigned driving record | Assignment to a driver or an annotation | The carrier, then the driver | On review of the record |
| Device malfunction | Written notice and reconstructed paper logs | Driver notifies, carrier repairs | Notice in twenty-four hours, repair in eight days |
Malfunctions and the fallback to paper
Section 395.34 sets the procedure when a device fails. The driver notes the malfunction, provides written notice to the carrier within twenty-four hours, reconstructs the record of duty status for the current day and the preceding seven consecutive days unless the records are retrievable from the device, and continues on paper. The carrier must correct, repair, replace or service the device within eight days of discovering the condition, or request an extension from the applicable division administrator.
The distinction between a malfunction and a data diagnostic event matters here. A diagnostic event flags missing or inconsistent data that the driver must resolve; a malfunction means the device is not performing a required function. Only the second triggers the paper fallback and the eight-day repair clock. Treating every diagnostic flag as a malfunction produces weeks of unnecessary paper logs and, with them, weeks of new violations.
Supporting documents and how long records are kept
Section 395.11 requires the driver to submit supporting documents to the carrier within thirteen days of receiving them, and limits the carrier to retaining a stated number of documents per driver per twenty-four-hour period. The categories are defined: bills of lading and dispatch records, dispatch and trip records, expense receipts, fleet management system communications, and payroll records. These exist to test the electronic record, and an investigator reads them alongside the logs rather than after them.
Retention runs six months for records of duty status and supporting documents, along with a back-up copy on a separate device. Where owner-operators are involved, the settlement documents that would corroborate a trip may sit with the equipment owner rather than the carrier, an allocation governed by the required lease terms and chargeback disclosures. Records that survive a roadside stop are also read against the inspection report generated there, described in the inspection levels and the release from an out-of-service order, and the aggregate feeds the safety measurement system.
Points to carry away
- The mandate applies to drivers required to keep records of duty status, not to every driver.
- A driver who keeps records of duty status eight days or fewer in thirty may use paper.
- Automatically recorded driving time may be annotated but may not be shortened or deleted.
- A carrier may propose an edit, and the driver must confirm or reject it before it takes effect.
- Unassigned driving records must be reviewed and either assigned to a driver or annotated.
- A malfunction must be noted, reported to the carrier within twenty-four hours and repaired within eight days.
Questions readers ask
Who may edit a record of duty status?
Both the driver and the carrier may propose edits, and both must be identified in the record. A carrier's proposed edit does not take effect on its own: the driver must affirmatively accept or reject it, and a rejected edit leaves the original entry standing. Every edit requires an annotation explaining it, and the original entry remains retrievable alongside the edited one. The one thing neither party may do is reduce or remove driving time the device captured automatically.
What is an unassigned driving record?
It is driving time the device recorded while no driver was logged in, typically from yard moves, mechanics repositioning equipment, or a driver who forgot to sign on. The carrier must review these records and either assign them to the driver who was operating or annotate them with an explanation of why they are not attributable to any driver. Unassigned miles left unreviewed are among the first things an investigator pulls, because the volume is visible without reading a single log.
Does an exempt driver still need to record hours?
In most cases yes, just not electronically. A driver exempt from the device because he keeps records of duty status eight days or fewer in any thirty-day period still keeps a paper record on those days. A short-haul driver operating within the air-mile radius and released within the stated window keeps no record of duty status at all, but the carrier must keep time records showing the start time, release time and total hours for each day. Exemption from the device is not exemption from the limits.
Sources
- eCFR — 49 CFR 395.8, Driver's Record of Duty StatusThe requirement to use a device, the exceptions to it and the six-month retention period.
- eCFR — 49 CFR 395.30, ELD Record Submissions and EditsWho may edit, the annotation requirement and the bar on altering recorded driving time.
- eCFR — 49 CFR 395.32, Unidentified Driver RecordsThe duty to review unassigned driving time and either assign or annotate it.
- eCFR — 49 CFR 395.34, ELD Malfunctions and Data Diagnostic EventsThe notice, reconstruction and eight-day repair obligations after a malfunction.
- eCFR — 49 CFR 395.11, Supporting DocumentsThe categories of supporting documents and the driver's submission obligation.
- Cornell Legal Information Institute — 49 U.S.C. 31137, Electronic Logging DevicesThe statutory mandate for the devices and the limits Congress placed on their use.
Lawwise is a publication, not a law firm. This article states general rules and cites its sources; it is not advice about any particular case, and the law differs by state and changes over time.
More in Motor Carrier Law
Cargo Loss and Damage Claims Against a Carrier
Under 49 U.S.C. 14706 a receiving carrier is liable for the actual loss or injury to property it transports in interstate commerce. The claimant proves delivery in good condition, arrival short or damaged, and the amount of the loss. The carrier escapes only by proving freedom from negligence and one of five excepted causes. The bill of lading may not allow less than nine months to file a claim, or less than two years to sue after disallowance.
Equipment Leasing and Owner-Operator Protections
A carrier operating equipment it does not own must have a written lease meeting 49 CFR 376.12. The lease must state the compensation, provide payment within fifteen days of submission of the delivery documents, itemize every chargeback and how it is computed, disclose insurance charges, and account for any escrow fund with interest and its return within forty-five days of termination. Violations may be pursued privately under 49 U.S.C. 14704.
Drug and Alcohol Testing Programs and the Clearinghouse
A motor carrier employing drivers who operate vehicles requiring a commercial driver's license must run a testing program under 49 CFR Part 382 using the procedures in 49 CFR Part 40. Six categories of test are required: pre-employment, random, post-accident, reasonable suspicion, return-to-duty and follow-up. A full clearinghouse query precedes employment and a limited query runs at least annually. A driver with a violation is prohibited until the return-to-duty process is complete.