ELD and hours-of-service compliance is more than installing a device. A motor carrier needs the right logging method for each driver, accurate accounts and vehicle connections, routine log review, supporting documents, a malfunction plan and action when FMCSA revokes a device.
Start by deciding who must use an ELD
Part 395 generally requires a motor carrier to obtain a record of duty status for each covered driver’s 24-hour period. A driver who must prepare RODS generally must use an ELD, but the rule identifies exceptions. Those include a driver who uses paper RODS on no more than eight days in any 30-day period, specified driveaway-towaway operations and a vehicle with a pre-2000 VIN model year, or a vehicle with an engine predating model year 2000 where the carrier retains supporting engine-change records.
Short-haul treatment is different. A driver who meets the 150 air-mile exception in 49 CFR 395.1(e)(1) is exempt from RODS and ELD requirements, but the carrier must keep accurate time records showing reporting time, total on-duty hours, release time and, when applicable, the prior seven days. Those records must be retained for six months. A provider should test the actual operation against the exception instead of treating local work as automatically exempt.
Hours-of-service limits depend on the operation
The ELD records time, but it does not decide whether a trip plan is lawful. Dispatch, driver availability, exceptions and supporting records still need human review.
| Rule area | Property-carrying CMV | Passenger-carrying CMV |
|---|---|---|
| Off-duty period | 10 consecutive hours before driving | 8 consecutive hours before driving |
| Driving limit | Up to 11 hours within the permitted duty window | No more than 10 hours following 8 consecutive hours off duty |
| Duty window | No driving after the 14th consecutive hour after coming on duty | No driving after 15 hours on duty following 8 consecutive hours off duty |
| Cycle limit | 60 hours in 7 days or 70 hours in 8 days, based on the carrier’s operation | 60 hours in 7 days or 70 hours in 8 days, based on the carrier’s operation |
| Driving interruption | When applicable, 30 consecutive minutes after no more than 8 cumulative hours of driving without an interruption | The property-carrier 30-minute interruption rule does not apply |
Exceptions and special operations can change these results. Alaska, adverse driving, sleeper-berth, agricultural, oilfield, emergency and other provisions need fact-specific review against current Part 395.
What a practical ELD compliance review should cover
Device and account controls
Confirm current FMCSA registration, engine synchronization, required driver account and license information, unique user accounts, support-user permissions, device configuration and fixed mounting of portable ELDs while the vehicle is in operation.
Log exceptions and patterns
Review potential 11, 14, 60 or 70-hour issues, missing certifications, location gaps, diagnostic events, repeated edits and conflicts with dispatch or payroll data.
Unidentified driving
Assign driving to the correct driver or annotate why it remains unassigned. Retain unidentified driving records and make them available with the corresponding ELD data.
Malfunctions and transfer
Test roadside transfer methods, keep the required ELD instruction sheets in the vehicle, maintain enough blank graph-grid logs for at least eight days, and document driver notification, reconstruction and repair steps.
Log edits need an audit trail
Under 49 CFR 395.30, drivers and motor carriers must ensure ELD records are accurate. Drivers review, correct and certify their records. A carrier may propose an edit after the driver submits the record, but the driver must confirm or reject the proposed change and recertify when an edit is accepted. Edits must not overwrite the original recorded information, and the ELD must retain the required edit history.
A useful review therefore looks beyond a dashboard’s red flags. It compares driving events, duty changes, annotations and edits with the work actually performed. Personal conveyance, yard move and sleeper-berth use should follow the carrier’s written policy and the facts of each movement. Software settings cannot turn an inaccurate status into a compliant record.
Supporting documents should agree with the log
Part 395 identifies five normal-course categories used to verify on-duty not-driving time: trip or shipping documents, dispatch records, expense receipts, fleet-management communications and payroll or settlement records. Required documents generally need a link to the driver, a date, a location and a time that can be converted to local time.
A sensible carrier review cycle
- Check missing logs, certifications, unidentified driving and malfunction events promptly.
- Compare selected logs with dispatch, fuel, toll, payroll, shipping and location records.
- Document coaching and corrective action for repeated causes, not only individual exceptions.
- Retain RODS and required supporting documents for at least six months.
- Keep a separate six-month backup of ELD records and be able to produce electronic records when requested.
A carrier generally need not retain more than eight supporting documents for one driver’s 24-hour period under 49 CFR 395.11. When more than eight exist, the retained set must include the earliest and latest time indications. The rule includes additional detail, so the document policy should be checked against the carrier’s operation.
Responding to an ELD malfunction
- Driver notice. The driver notes the malfunction and gives the motor carrier written notice within 24 hours.
- Reconstruct records. The driver reconstructs the current day and previous seven days on compliant graph-grid logs unless those records are already held or retrievable from the ELD.
- Continue manual RODS. Paper records continue until the device is serviced and brought back into compliance.
- Repair or replace. The motor carrier must act to correct the malfunction within eight days of discovery or driver notice, whichever comes first.
- Request more time when necessary. A motor carrier seeking an extension must submit the request within five days after the driver notifies the carrier to the FMCSA Division Administrator for the State of the carrier’s principal place of business, with the information required by 49 CFR 395.34.
Revoked ELDs require a dated response plan
FMCSA maintains separate registered and revoked device lists and publishes replacement instructions when devices are removed. Those notices are time-sensitive. On August 6, 2026, FMCSA listed five more revoked devices and gave affected carriers until October 6, 2026 to replace them with registered ELDs. For the ten devices removed on July 9, 2026, the September 8 transition period has ended. Continued use on or after September 8 violates the record-of-duty-status requirement and can result in the driver being placed out of service. Other 2026 revocations had different dates, and enforcement had already begun for some earlier removals.
Check the live list rather than relying on an old vendor document or a static article. Preserve accessible records, follow the specific FMCSA notice, move to the permitted interim recording method, choose a registered replacement, test data transfer and document driver training. Continued use after the applicable transition date can be treated as operating without a required ELD.
What outsourced ELD and HOS support should deliver
The provider should define which drivers and vehicles are reviewed, how often exceptions are checked, who proposes edits, how urgent issues are escalated and how records are returned to the carrier. Reports should distinguish a potential system alert from a confirmed violation and should never hide original events or coach a driver to certify an inaccurate log.
This platform can connect motor carriers with providers offering ELD setup, log auditing, driver training and hours-of-service support. The carrier remains responsible for its drivers, dispatch decisions, records and compliance.
Build an exception map before configuring the ELD platform
The carrier’s written malfunction process should identify who receives the driver’s notice, how paper logs are supplied, who contacts the ELD provider and how the repair or replacement deadline is tracked. Save the driver’s reconstructed records and the support ticket. A device banner or vendor email is not a complete carrier record.
Review data that sits outside the driver’s grid
- Unassigned driving and rejected or pending edits.
- Personal conveyance and yard-move use.
- Missing location, engine synchronization or unidentified diagnostic events.
- Supporting documents that conflict with the recorded duty status.