ELD Compliance Audits: What Carriers Should Expect

Key takeaways:

• An “ELD compliance audit” is not a separate inspection category in the Federal Motor Carrier Safety Regulations. FMCSA and State partners may examine ELD and hours-of-service records during an offsite, onsite focused, or onsite comprehensive investigation.
• A roadside inspection is different from a carrier investigation. At roadside, an authorized safety official may ask the driver to display and transfer hours-of-service records and produce supporting documents already in the driver’s possession.
• Using an ELD does not by itself establish compliance. Drivers and carriers remain responsible for accurate records of duty status (RODS), applicable hours-of-service limits, supporting documents, account controls, edits, certification, record retention, and malfunction procedures.
• ELD requirements apply only when the driver is required to prepare RODS and no ELD exception applies. Short-haul time records, occasional paper RODS, driveaway-towaway operations, and certain older vehicles must be evaluated under the specific rules.
• No checklist can guarantee an investigation outcome. Findings and enforcement depend on the facts, the regulations involved, and the applicable FMCSA or State process.

What Is an ELD Compliance Audit?

The phrase ELD compliance audit is commonly used for a review of a carrier’s electronic logs and related hours-of-service controls. FMCSA more broadly describes three types of carrier safety investigations: offsite, onsite focused, and onsite comprehensive investigations. An offsite investigation reviews requested records remotely. An onsite focused investigation examines identified safety or compliance problems at the carrier’s place of business. An onsite comprehensive investigation reviews the carrier’s overall safety operation.

Part 395 records may be part of any of those investigations, but the scope can also include driver qualification, controlled-substances testing, vehicle inspection and maintenance, crashes, financial responsibility, or other applicable requirements. A new-entrant safety audit is another distinct process and should not be confused with an ELD-specific review.

Roadside Inspection vs. Carrier Investigation

At a roadside inspection, the immediate focus is the driver, vehicle, and records available for the trip. Under 49 CFR 395.24(d), a driver must produce and transfer the driver’s hours-of-service records from the ELD when an authorized safety official requests them. The driver must also make any supporting documents in the driver’s possession available for review under 49 CFR 395.11(g).

A carrier investigation is broader. A safety investigator may request records for selected drivers and periods, compare RODS with supporting documents and source data, review company controls, interview personnel, or examine other safety-management areas. An offsite investigation may be expanded or converted when the available information calls for a broader review.

Roadside findings can contribute to a carrier’s safety data and may prompt further attention, but a roadside inspection is not the same event as an offsite or onsite investigation.

Who Must Use an ELD?

The ELD rule does not apply to every commercial vehicle or every truck driver. The starting question is whether the driver must prepare RODS under Part 395. A motor carrier generally must require an ELD when RODS are required, unless an exception in 49 CFR 395.8(a)(1)(ii) or another applicable provision permits manual records or another recordkeeping method.

For a detailed applicability review, including short-haul time records, the rolling eight-days-in-30 exception, driveaway-towaway operations, and older-vehicle rules, see Are ELDs Mandatory in the USA? A carrier should document why each driver is using an ELD, paper RODS, or a short-haul time record instead of assuming one rule applies fleet-wide.

Records an Investigator May Examine

RODS and applicable hours-of-service limits

An ELD records duty status; it does not decide every legal question or prevent a driver from violating an hours-of-service limit. The underlying limits depend on the operation and any exception being used. For example, property-carrying drivers subject to 49 CFR 395.3 generally may drive up to 11 hours after 10 consecutive hours off duty, may not drive beyond the 14-hour window, and, unless a listed short-haul exception applies, need a 30-minute interruption after more than eight cumulative hours of driving without such an interruption. Passenger-carrier rules and regulatory exceptions differ.

Reviewers may compare duty-status changes, locations, vehicle and trailer identifiers, shipping-document information, annotations, special driving categories, and unidentified-driving records with other evidence. A carrier should investigate discrepancies rather than treating an ELD alert as proof of a violation or assuming the absence of an alert proves compliance.

Driver certification and log edits

Under 49 CFR 395.30, both the driver and motor carrier are responsible for accurate ELD records. Drivers must review and certify their records. If a record is edited after submission, the driver must recertify it. Carrier-proposed edits do not take effect unless the driver confirms them, and each change or addition must be annotated. Original ELD information and source data cannot be erased or altered.

Supporting documents

49 CFR 395.11 identifies supporting-document categories such as trip or dispatch records, qualifying expense receipts, fleet-management communications, and payroll or settlement records. Drivers generally submit supporting documents within 13 days. Carriers generally need not retain more than eight supporting documents for a driver’s 24-hour period, but when more than eight exist, the retained set must include the earliest and latest time indications. The records must be linkable to the corresponding RODS.

RODS and required supporting documents must be retained for at least six months from receipt under 49 CFR 395.8(k). Supporting documents must not be obscured, destroyed, defaced, mutilated, or altered. The rule is more specific than simply saving every fuel receipt or bill of lading, so a retention process should follow the listed categories and data elements.

ELD registration, accounts, and carrier controls

A carrier required to use ELDs must use devices listed on FMCSA’s registered ELD list. Registration is based on provider self-certification; it should not be described as FMCSA approval or certification of the device. Carriers must manage ELD accounts, assign unique usernames, require proper login, maintain and calibrate devices according to provider specifications, and ensure a portable ELD is fixed and visible to the driver while the vehicle is operating.

The carrier should also review unidentified-driving records, inactive accounts, team-driver assignments, personal-conveyance and yard-move settings, and any support-personnel access used to propose edits. Policies and driver instruction help implement these controls, but software and training do not transfer the carrier’s regulatory responsibility to the vendor.

Onboard ELD information

Current 49 CFR 395.22(h) requires the carrier to ensure that drivers possess an onboard information packet containing:

• Instructions describing the ELD’s supported data-transfer mechanisms and how to produce and transfer HOS records to an authorized safety official.
• Instructions describing malfunction reporting and recordkeeping procedures.
• Enough blank RODS graph grids to record at least eight days.

The carrier must also retain a backup copy of ELD records for six months on a device separate from the original storage system and protect driver privacy using sound business practices.

ELD malfunctions and diagnostic events

A malfunction does not suspend HOS or recordkeeping duties. Under 49 CFR 395.34, the driver must note the malfunction and provide written notice to the carrier within 24 hours. If needed, the driver must reconstruct the current 24-hour period and the previous seven consecutive days unless those records are already possessed or retrievable, then continue compliant manual RODS until the ELD is back in service.

The carrier must act to correct, repair, replace, or service the ELD within eight days of discovering the condition or receiving the driver’s notice, whichever occurs first. A carrier needing more time must submit a qualifying extension request to the appropriate FMCSA Division Administrator within five days after the driver’s notice. An extension is not automatic.

Common Gaps to Find Before an Investigation

• Drivers who should use ELDs are assigned paper logs or short-haul time records without a valid basis.
• The device is no longer on FMCSA’s registered list, or the carrier has not documented a provider revocation notice and transition plan.
• RODS are missing certifications, required data, annotations, vehicle assignments, or supporting records.
• Carrier edits were accepted without driver confirmation, or original data was altered or deleted.
• Unidentified-driving time is not reviewed and assigned or annotated appropriately.
• Supporting documents cannot be matched to the driver and RODS or were not retained for the required period.
• Drivers cannot produce or transfer records at roadside using the ELD’s supported method.
• The required onboard transfer instructions, malfunction instructions, or blank graph grids are missing.
• Malfunctions were not reported, documented, repaired, or escalated within the regulatory timeframes.
• ELD data is reviewed without checking the operation-specific HOS rule or exception.

How to Prepare for an ELD and HOS Investigation

1. Map the applicable rule. Identify which drivers must prepare RODS, which must use an ELD, which use a short-haul time record, and which exception supports any alternative method.
2. Confirm device status. Compare every ELD model and software version in service with FMCSA’s registered and revoked-device information. Keep vendor notices and replacement records.
3. Sample records. Review selected drivers and days across terminals, dispatchers, vehicle types, and operating patterns. Compare RODS with supporting documents, location and engine data, payroll, dispatch, and maintenance records when relevant.
4. Review edits and unidentified driving. Confirm that annotations, driver acceptance or rejection, recertification, and retained originals follow 49 CFR 395.30.
5. Test roadside readiness. Have drivers practice displaying and transferring records using the actual ELD instructions without changing a record. Geosavi’s ELD roadside inspection checklist covers that separate workflow.
6. Test malfunction procedures. Verify the 24-hour driver notice process, record reconstruction, manual RODS, eight-day repair deadline, and extension-request escalation.
7. Organize production. Designate a knowledgeable point of contact, preserve the original request, track what is produced and when, and keep a copy of each response.
8. Correct prospectively and preserve history. Fix procedures and accurate records through permitted edits and annotations. Do not erase original ELD data, alter supporting documents, or create records that did not exist.

Internal reviews can identify gaps, but they do not guarantee a satisfactory result or prevent enforcement. A carrier facing a formal investigation, notice, or disputed legal issue should consider advice from qualified transportation counsel.

What to Do During an FMCSA Investigation

• Confirm the investigator’s identity, the type and scope of the investigation, the records requested, the covered drivers and dates, and the response deadline.
• Provide responsive, accurate records through the requested secure method. Ask for clarification when a request is ambiguous.
• Keep a production log showing what was submitted, by whom, and when.
• Answer factual questions accurately. Do not guess, alter records, or make unsupported explanations.
• Escalate potential violations, legal questions, or data-quality disputes to appropriate management or counsel.
• Review any findings and required response carefully. FMCSA follow-on actions can include a cooperative safety plan, a Notice of Violation seeking corrective action, or a Notice of Claim asserting civil penalties. Those outcomes are not automatic consequences of every ELD issue.

Prepare the Process, Not Just the Device

Investigation readiness comes from accurate records and repeatable carrier controls, not simply installing an ELD. The carrier must know which rules apply, retain and reconcile the required evidence, support drivers at roadside, address malfunctions promptly, and correct problems without erasing the audit trail.

Geosavi can help carriers evaluate ELD configuration, data-transfer readiness, driver workflows, and record-review procedures. Contact Geosavi to discuss the technical side of ELD and HOS preparation. Geosavi does not guarantee an audit result or provide legal advice.