DOT Audit Prep

HOS Record Gap Checker

A gap checker for finding missing HOS logs, ELD exports, support documents, and annotations before an audit.

Who this is for
Safety managers, ELD admins, Drivers
Written by
Dale Whitfield
Reviewed by
DOT Audit Prep Editorial Team
Last reviewed
2026-06-16
Source confidence
High

Quick checklist

  • Pull driver logs for the full requested date range from the ELD system — records of duty status must be retained for six months under 49 CFR 395.8.
  • Run an exception report showing uncertified logs, unassigned driving, and edits.
  • Flag any day that has driving time but no certified log entry.
  • Review all unassigned driving segments and assign or annotate each one.
  • Check that edits have specific notes — not just "corrected" or "fixed log."
  • Gather supporting documents for any sampled dates the auditor may review.
  • Document short-haul exception days with the time, starting point, and return point — the exemption conditions appear at 49 CFR 395.1(e) and require time records even when daily logs are not required.

Why this matters

HOS log gaps are the most common finding in routine DOT audits because they are easy to generate and easy to miss. A driver who ends a long day without certifying, or a dispatcher who never reviewed the unassigned driving queue, creates a gap that looks like a compliance failure even if the hours were legal. Before an audit, the goal is not to make the records perfect — it is to know what is missing and have a clear, documented explanation for each gap already in the system before the auditor asks.

What to prepare

Area Records to gather
Log gap checks
  • Missing log day — days with CMV movement but no log
  • Uncertified log — driver did not certify by end of shift
  • Unassigned driving — ELD recorded motion but no driver was logged in
  • Edit without a clear note — change is visible in the audit trail but reason is vague
  • Missing support document for a sampled day
Exception documentation
  • Short-haul exception: start time, return time, and location documented
  • Adverse driving conditions: weather or traffic event noted in annotation
  • 16-hour exception: driver's home terminal departure and return documented
  • ELD exemption basis noted for drivers not subject to ELD rules
Review notes per gap
  • Driver contacted and response noted in the system
  • Annotation added in the ELD where the gap appears
  • Supporting document located and filed near the log date
  • Exception basis documented if applicable
  • Manager review date and name recorded

Common gaps

  • Unassigned driving segments remain in the admin queue with no action taken.
  • Drivers did not certify off-duty days or days with short personal moves.
  • Log edits show in the audit trail with notes like "fixed" or "corrected" but no explanation of what changed.
  • Short-haul exceptions are claimed but no time records or trip details support the exemption.
  • Supporting documents are kept in a stack in the truck cab but not organized by driver and date.

Before / During / After audit

Before

  • Run exception reports covering the most recent 90 days as a baseline check.
  • Start with the most recent month and work backward when reviewing gaps.
  • Pull supporting documents for any date flagged in the exception report.

During

  • Use the ELD system as the primary source; support documents confirm on-duty time.
  • Keep supporting documents organized and available by driver and date.

After

  • Add a weekly HOS exception review to the safety coordinator routine.
  • Train drivers on daily certification and how to annotate edits with clear notes.
  • Document any pattern of recurring gaps with coaching records for each driver.

FAQ

Does a driver need to submit a log on days when there was no driving?

Every 24-hour period during which a driver is subject to HOS recordkeeping requires a certified log entry, including days with no driving at all. An ELD system may generate an automatic off-duty entry for days with no recorded movement, but the driver still has to certify it. What shows up as a gap in an audit is usually a string of uncertified days, or days that are entirely blank in the record — the driver was on duty doing dispatch, pre-trip, or maintenance work but never recorded it. The gap is not about the driving; it is about the on-duty time that was not logged.

What is unassigned driving and why does it matter?

Unassigned driving is ELD-recorded vehicle movement that has no driver logged in. This can happen when a vehicle is moved in a yard, during a test drive, or when a driver forgets to log in. Under the ELD rule, the carrier must review unassigned driving and either assign it to a driver or note why it cannot be assigned. Unreviewed unassigned driving left in the admin queue is a compliance gap.

How do auditors use HOS records during a safety audit?

Auditors typically pull a sample of driver logs from the requested period and check for certifications, edit history, unassigned driving, and supporting document availability. They may also compare on-duty time in the logs against CMV activity records or fuel receipts to look for time that was not logged. The review is not exhaustive for every driver, but it covers enough of a sample to identify systemic problems.

Download

Use the print button to create a paper or PDF copy from your browser. No account or upload is needed.

Sources

Related resources

Hours of Service Records ChecklistA checklist for preparing HOS records, logs, supporting documents, and review notes before a trucking audit.ELD Records ChecklistA practical checklist for exporting and reviewing ELD records before a DOT or FMCSA audit.Audit Readiness Score ToolA private, browser-only audit readiness score tool for checking the main DOT audit record categories before a review.