Guides

The safety audit: records and retention

An audit asks three plain questions: do the records exist, are they complete, and do they match each other? This guide puts every keeping period that matters in one place.

← All guides

Early in its operating life, a new entrant motor carrier gets a safety audit under 49 CFR Part 385, Subpart D. New carriers often picture something dramatic — inspectors under trucks, a week of grilling. The truth is quieter and, for the unprepared, harder: the audit is a paperwork exam. It is pass or fail on whether the records exist, whether they are complete, and whether they match each other and match the road the trucks actually travelled.

That framing is good news. Paperwork can be put in order long before anyone asks for it, and the rules say exactly which records to keep and for how long. This guide stays records-focused on purpose: the table of keeping periods first, then the principle underneath all of them — matching — then the ELD-specific readiness points that auditors read closely.

The rule

A new entrant safety audit is held under 49 CFR Part 385, Subpart D. The records it examines are kept under their own rules: logs and supporting documents under 49 CFR 395.8(k) and 395.11, ELD backup under 395.22(i), driver qualification files under 391.51, and vehicle records under 396.3, 396.9, and 396.11.

The retention table: what to keep, and for how long

Keep this list where the filing happens. Each line is one kind of record, its keeping period, and the rule it comes from.

  • Records of duty status (logs): at least 6 months from receipt — 49 CFR 395.8(k)(1).
  • Supporting documents: kept with the logs under the same 6-month rule — 49 CFR 395.8(k)(1) and 395.11. The categories under 395.11(c) are bills of lading and itineraries showing origin and destination; dispatch and trip records; expense receipts tied to on-duty-not-driving time; electronic mobile communication records; and payroll records and settlement sheets.
  • ELD records backup: a back-up copy kept for 6 months, on a device separate from where the originals are stored — 49 CFR 395.22(i)(1).
  • Unidentified driving records: at least 6 months from receipt — 49 CFR 395.32(c)(2).
  • Driver qualification files: for as long as the driver is employed, and for 3 years after — 49 CFR 391.51(c).
  • Vehicle maintenance records: 1 year where the vehicle is housed or maintained, and 6 months after the vehicle leaves the carrier's control — 49 CFR 396.3(b)–(c).
  • Driver vehicle inspection reports: at least 3 months — 49 CFR 396.11.
  • Roadside inspection reports: 12 months — 49 CFR 396.9.
  • Accident register: accidents recorded on a register kept for 3 years — 49 CFR 390.15.

Two of those lines deserve a slower read, because offices get them wrong in opposite directions.

Supporting documents have a shape, not just a period. They are kept so they can be tied to the driver's record, under 49 CFR 395.11(e) — a receipt that cannot be matched to a driver and a day does its job poorly. A carrier need not keep more than 8 supporting documents per driver per 24-hour period; if it has more, it keeps the earliest and latest among the set it retains, under 49 CFR 395.11(d). And the flow starts with the driver: drivers submit supporting documents within 13 days, under 49 CFR 395.11(b). An office that waits for drivers to hand papers in “sometime” will always be filing against an audit clock it cannot see. A set day for papers to come in, every week, keeps the 13-day duty easy.

Driver and vehicle files are built, not gathered. A driver qualification file has set contents under 49 CFR 391.51(b): the application, the road-test certificate, motor vehicle records, annual review notes, and the medical certificate, among the listed items. A vehicle maintenance record under 49 CFR 396.3 carries the vehicle's identification, the schedule of inspections and maintenance due, and the record of inspections, repairs, and maintenance for that vehicle. Neither file can be assembled the week before an audit, because both are histories: they are the paper trail of decisions made across the year. The time to start them is the day the driver is hired and the day the truck enters service.

The ELD backup: separate means separate

One line in the table hides a trap in a single word. The back-up copy of ELD records must be kept on a device separate from where the originals are stored, under 49 CFR 395.22(i)(1). A second folder on the same machine is not a backup in the rule's sense; it fails on the same day the machine does. Separate means a failure that takes the originals leaves the copy standing — a different device, so the records survive the accident that created the need for them. Six months of logs is a small amount of data. There is no practical reason for this line to be the one an audit catches, and yet it catches carriers who treated “backup” as a word instead of a place.

The matching principle: where audits are actually lost

Periods tell you how long to keep records. Matching tells you what the auditor does with them once you hand them over. Auditors cross-check. The log is read against the bill of lading. The dispatch record is read against the fuel receipt. A delivery time in one document is held up beside a duty status in another.

Records that disagree with each other are where audits are lost. Not missing periods — outright contradictions: driving shown where a receipt places the driver somewhere else, a trip in the dispatch records that the log never mentions, hours that cannot have happened in the order the papers claim. A carrier can keep every record for exactly the right period and still fail on records that tell two different stories about the same day.

The defence is built during the week, not before the audit. When a supporting document and a log disagree, the time to notice is when the papers come in — while the driver remembers the day and an honest correction, annotated in the open, can still be made under the editing rules. The keeping periods above are minimums, and “we threw it away” is not a defence inside them. But a kept record that contradicts three others is its own kind of problem. Keep records long enough, and keep them in agreement; the audit tests both.

ELD-specific readiness

Two areas of the ELD record draw a close read, because both show whether the office watches its own system week by week or only when asked.

Unidentified driving records, handled. Under 49 CFR 395.32, unidentified records must be reviewed, and either assigned to the right driver or annotated with why the time is unassigned. A short, handled list reads as supervision. A long, untouched pile reads as its opposite, and it is a finding by itself. The full drill is in our guide to unidentified driving records.

Edits, annotated, with originals intact. Under 49 CFR 395.30, edits carry annotations and the original record is preserved. Auditors read edits for exactly that shape: a change, a reason, and the original standing beside it. An edit that follows it reads as a correction kept in the open, which is what the rule is built to produce. How the editing rules work, including the driver's right to confirm or reject office-proposed changes, is in our guide to editing your logs.

And when a device fails inside the audit window, the malfunction paper matters too: the driver's written notice, the reconstructed week, and the paper record kept until the device was fixed, under 49 CFR 395.34. That drill is covered in When the ELD breaks.

A small office system that passes

Nothing above requires a records department. It requires a rhythm. Papers come in from drivers on a set day, inside their 13 days. Someone matches them against the logs that week, while memories are fresh, and asks about disagreements the same week. Unidentified records are reviewed and cleared as they appear, not in a quarterly panic. The backup is copied to its separate device and spot-checked — actually opened, once in a while, to prove it reads. Files for drivers and vehicles are opened on day one and added to as events happen: a repair, a review, a roadside inspection, each filed while it is a single sheet rather than a season's worth.

A carrier running that rhythm does not prepare for an audit so much as live in a state the audit simply confirms. The records exist, they are complete, and they match — because someone made them match every week, when matching was cheap. That is the whole secret the table of periods is pointing at: retention is a clock, but readiness is a habit.

Rules checked October 2026. Rule sources: 49 CFR 395.8(k); 49 CFR 395.11; 49 CFR 391.51; 49 CFR 396.3.

Keep reading

Related guides

Unidentified driving records

Where driving with nobody logged in comes from, and the only two ways the office can clear it.

Editing your logs: what can change, what can't

What a driver can correct with an annotation, what can never change, and why the office needs the driver to confirm.

When the ELD breaks: the malfunction drill

Note it, tell the carrier in writing within 24 hours, rebuild the week on paper, and start the 8-day repair clock.

A question the guide didn't answer?

Rules are general; your week is specific. Call us and we'll talk it through with you — or write, if you'd rather.