Hours of Service Documentation Checklist

Key Takeaways

• Hours-of-service documentation is not only a compliance record. After an incident, it helps establish duty status, driving time, edits, annotations, and whether the log was current.
• Preserve the ELD export, supporting documents, unassigned driving review, and any edits or annotations connected to the incident period.
• Do not rely on screenshots alone. A platform export usually carries more useful metadata than a dashboard image.

Related documentation steps

Fleet safety records work best when policies, coaching, meeting notes, and accident reviews use the same filing and follow-up habits.

fleet safety documentation checklist · driver coaching policy · accident review board basics · FMCSA CSA score basics

What this checklist covers

This checklist is for preserving hours-of-service records after a crash, roadside inspection, cargo dispute, or internal review. It focuses on what the fleet should save, where gaps appear, and how the record connects to the incident file.

Hours-of-service records are compliance records first. In an incident review, they also help establish whether the driver was on duty, how long they had been driving, whether edits were made, and whether supporting documents match the log.

Records to preserve

Preserve the ELD export for the driver and unit covering the incident day and the surrounding period requested by the safety contact, insurer, or legal contact. Include certification status, edit history, annotations, unassigned driving review, and any malfunction notes.

Save supporting documents tied to the trip: bills of lading, fuel receipts, toll records, dispatch messages, scale tickets, delivery receipts, and repair or roadside service documents. These records can help explain duty status and vehicle movement.

Common gaps

Common gaps include missing supporting documents, unreviewed unassigned driving, edits without clear annotations, a driver who had not certified the log, and screenshots saved without the underlying export.

A gap does not always mean a violation occurred. It does mean the safety contact should document what was reviewed, what is missing, and what explanation or substitute record exists.

When HOS records become claim evidence

Hours-of-service records usually enter a claim file when fatigue, duty time, dispatch pressure, or route timing is questioned. The record does not answer those questions alone, but it gives the review a time base.

Pair the ELD export with dispatch messages, load documents, fuel receipts, toll data, and driver notes. Together, those records show how the trip actually unfolded rather than only what the log grid displayed.

Who should handle outside requests

Law enforcement requests, insurer requests, attorney letters, and customer questions should not all be handled the same way. Route each outside request through the company safety or legal contact before producing records beyond ordinary enforcement requirements.

When records are produced, log what was sent, who received it, the date, and the format. Keep the original export and a copy of the production record in the incident file.

How to review edits and annotations

Review edits in order: who made the edit, why it was made, whether the driver accepted it, and whether the annotation explains the change. Edits without a clear reason draw attention during audits and claims.

Unassigned driving should be reviewed before the file is closed. If the movement belongs to the involved unit or driver, document the assignment. If it does not, document the reason it was rejected.