Quick checklist
- Confirm the ELD provider is registered if ELD rules apply.
- Test record transfer and export steps before the audit.
- Review unassigned driving, edits, annotations, and malfunctions.
- Save driver instructions and malfunction process notes.
- Keep support documents near the related log dates.
Why this matters
An ELD system is useful only if the carrier can access and explain the records. Audits become slower when nobody knows the admin portal or transfer process.
What to prepare
| Area | Records to gather |
|---|---|
| Portal access |
|
| Record review |
|
Common gaps
- The carrier relies on a dispatcher login that no longer works.
- Drivers have uncertified logs.
- Malfunctions are not documented.
- Only screenshots are saved when exportable data is available.
Before / During / After audit
Before
- Run a test export.
- Review one driver's full week.
- Save provider instructions in the audit packet.
During
- Use the requested transfer method.
- Keep login access available during the call.
- Explain edits using notes in the system.
After
- Add ELD review to the weekly safety routine.
- Remove inactive users.
- Document provider support tickets if records were unavailable.
Download
Use the print button to create a paper or PDF copy from your browser. No account or upload is needed.
Sources
eCFR · regulation
49 CFR Part 395 Subpart B - Electronic Logging Devices
ELD requirements, supporting documents, malfunction procedures, and transfer expectations.
Last checked: 2026-05-12
FMCSA · official
Electronic Logging Devices
FMCSA ELD information hub.
Last checked: 2026-05-12
eCFR · regulation
49 CFR 395.8 - Driver's record of duty status
Record of duty status requirements.
Last checked: 2026-05-12