Key takeaways
- This seven-point ELD pre-trip checklist is a practical fleet routine, not a federally prescribed form or sequence.
- Before driving, the driver must be satisfied the vehicle is safe and review the previous DVIR when required. A new written DVIR is not automatically required before every defect-free property-carrying trip.
- Use the correct ELD account, vehicle and trailer details, duty status, and available HOS records. Review any unidentified driving assigned to the vehicle.
- A diagnostic event, a malfunction, and a failed roadside transfer are different issues. Follow the procedure that applies to the actual condition.
- An ELD records and displays data; it does not guarantee that a trip complies with all HOS and vehicle-safety rules.
A few minutes of careful review can catch records or equipment problems before a trip. These seven checks separate federal requirements from sensible operating habits, using current ELD rules and vehicle-inspection rules as the reference points.
1. Confirm the vehicle is safe to operate
Under 49 CFR 396.13, the driver must be satisfied the vehicle is in safe operating condition before driving. Review the previous driver vehicle inspection report (DVIR) when the rule requires one, including the repair certification and acknowledgment when applicable. Check the vehicle and trailer for safety concerns under the carrier’s inspection procedure, and report defects for correction before operation.
Do not confuse that pre-drive responsibility with a mandatory new written DVIR at the start of every trip. For most property-carrying operations, 49 CFR 396.11 calls for a report at the completion of the day’s work when a safety-affecting or breakdown-related defect is discovered or reported; no-defect reports are generally not required. Passenger and intermodal operations have distinct provisions, and a carrier may choose a stricter checklist.
2. Log in under the correct driver and vehicle
Before moving, use your own ELD credentials and confirm the selected power unit, trailer number, and shipping-document number when applicable. For a team operation, each driver should use the proper account and verify who will be driving. 49 CFR 395.22(e) requires carriers to ensure proper ELD login; 49 CFR 395.24 requires drivers to enter or verify prompted vehicle and shipment details.
Check the displayed date, duty status, and current vehicle assignment. This is especially useful when switching trucks or devices. An incorrect profile or unit can make later review harder, but it does not make every mile an automatic violation.
3. Review unidentified driving and prior records
When a driver logs in, 49 CFR 395.32(b) requires review of prompted unassigned driving: accept time that belongs to you or indicate that it does not. The carrier must review unidentified records and either explain why they remain unassigned or assign them to the right driver. The rule does not impose the article’s former universal eight-day assignment deadline.
Review available recent records and correct missing or inaccurate entries using the ELD’s supported edit and annotation process. 49 CFR 395.30 requires the driver to review and certify accurate records, and to recertify after applicable edits. Automatically recorded driving time cannot simply be erased. A limited team-driver reassignment procedure applies when the regulation’s conditions are met.
4. Check ELD status and address alerts
Confirm the ELD is powered, connected to the vehicle as designed, and showing the expected vehicle and engine data. An alert deserves attention, but an engine-synchronization data diagnostic is not automatically an engine-synchronization compliance malfunction. Follow the carrier’s and provider’s guidance for a diagnostic event; do not erase or misclassify the underlying driving record. FMCSA explains the distinction.
If there is an actual ELD malfunction, 49 CFR 395.34 requires the driver to note it and give the carrier written notice within 24 hours. Reconstruct the current day and previous seven days on compliant graph-grid logs unless those records are already possessed or retrievable, and manually record duty status until the ELD is compliant. The carrier generally has eight days from discovery or notice, whichever comes first, to correct the malfunction, subject to an FMCSA extension.
The carrier should also confirm that its model remains on the FMCSA registered ELD list and follow any model-specific revocation notice. Registration checks are prudent fleet practice, not a federally prescribed daily driver checklist. Do not assume every revocation has the same deadline or enforcement outcome.
5. Check duty status and available HOS time
Select the duty status that reflects the work actually being performed. A vehicle inspection is generally on-duty, not driving time. Review the current-day record and the previous seven days that the ELD makes available, along with any applicable carrier information and annotations. If an exemption or special driving category applies, use it only when the operation qualifies.
Displayed remaining time is a planning aid, not a legal guarantee. The driver and carrier remain responsible for accurate records and applicable HOS limits under 49 CFR 395.3 and related exceptions. A correct ELD calculation cannot make an unsafe vehicle or an otherwise noncompliant trip compliant. Our local-driver ELD guide discusses one common exception.
6. Confirm the required in-cab ELD information
For an ELD-covered trip, the carrier must ensure the driver has an information packet with: (1) an instruction sheet for the device’s supported data-transfer method and the steps to produce records; (2) an instruction sheet for malfunction reporting and recordkeeping; and (3) enough blank graph-grid logs for at least eight days. These are the current items in 49 CFR 395.22(h). A printed ELD user manual is no longer a required packet item, though it may still be useful.
Confirm the sheets describe the installed device rather than an old model. The blank grids are a malfunction contingency, not a requirement to keep duplicate completed paper logs during normal ELD operation.
7. Know how to present and transfer records
At an inspection, 49 CFR 395.24(d) requires the driver to produce and transfer HOS records as instructed. A compliant ELD supports one complete transfer option: telematics through web services and email, or local transfer through USB 2.0 and Bluetooth. It need not support all four methods. Learn the method shown on your device’s instruction sheet and how to display or print records when an official requests a physical view. See FMCSA’s transfer guidance.
A failed transfer attempt alone does not establish a malfunction, missing RODS, or an automatic fine. Follow the officer’s instructions, use the available display or printout, and work with the carrier and provider to diagnose the problem. A fleet practice transfer can be useful, but the regulation does not prescribe a test before every departure.
What this checklist does and does not do
These seven checks help drivers leave with a safe vehicle and usable records. They do not replace the carrier’s maintenance program, the driver’s HOS judgment, or the applicable federal and state rules. They are a recommended operating procedure, not an FMCSA-issued seven-step mandate. For device-specific setup or support, use the instructions for your installed ELD or contact Geosavi support. Verify model registration and transfer capabilities from the current device documentation instead of assuming one configuration fits every truck.
ELD pre-trip checklist FAQs
Is a seven-point ELD pre-trip checklist required by FMCSA?
No. FMCSA does not mandate this named checklist or a fixed seven-step sequence. Drivers and carriers must meet the applicable vehicle-safety, ELD, recordkeeping, and HOS rules; a checklist is one way to organize that work.
Does a driver need a new written DVIR before every trip?
Not generally for a defect-free property-carrying trip. The driver must be satisfied the vehicle is safe before driving and review a previous DVIR when required. Under 49 CFR 396.11, a written report is generally prepared at the end of the workday when a relevant defect is discovered or reported. Passenger and intermodal rules differ.
What should a driver check after switching trucks?
Use the correct ELD account and vehicle assignment, verify the power-unit and applicable trailer or shipping details, review any prompted unidentified driving, and confirm the device is recording the expected vehicle data.
What if the ELD shows driving time that is not mine?
Do not accept a record that is not yours. Indicate that it is not attributable to you when prompted and notify the carrier for review. Accept time that you actually drove, using the ELD’s supported correction process.
Is a data diagnostic event an ELD malfunction?
Not necessarily. A diagnostic flags a data inconsistency that the driver should address under carrier and provider instructions. A malfunction means a required ELD function has failed and triggers the separate 49 CFR 395.34 procedures.
What must a driver do after an ELD malfunction?
Note the malfunction, give the carrier written notice within 24 hours, reconstruct any required records that are not otherwise available, and manually record duty status until the device is compliant. The carrier generally has eight days to correct the malfunction unless FMCSA grants an extension.
What ELD materials must be in the cab?
The current packet includes device-specific data-transfer instructions, malfunction and recordkeeping instructions, and enough blank graph-grid logs for at least eight days. A printed user manual is no longer required by 49 CFR 395.22(h).
Must an ELD support Bluetooth, USB, email, and web services?
No. It must support either the complete telematics option (web services and email) or the complete local option (USB 2.0 and Bluetooth). Use the installed device’s instructions to identify its supported method.
Does an ELD’s remaining-hours display guarantee HOS compliance?
No. The display helps with planning, but the driver and carrier must ensure records and operations meet the actual HOS rules and applicable exceptions.
Does a failed roadside transfer always mean an out-of-service order?
No. The result depends on the device, available records, the facts found by the inspector, and applicable criteria. A single failed transfer is not the same thing as an ELD malfunction or a missing record of duty status.
Before the first mile
Check the vehicle, confirm your ELD account and records, resolve alerts correctly, and keep the required instructions available. That preparation makes an inspection easier without promising a particular enforcement outcome. Contact Geosavi for help with your installed ELD workflow.