Audit Document Packet

Build a DOT audit document packet with the driver, vehicle, HOS, drug testing, accident, and authority records auditors often request.

Who this is for
Owner-operators, Small fleets, New authorities
Written by
Dale Whitfield
Reviewed by
DOT Audit Prep Editorial Team
Last reviewed
2026-06-16
Source confidence
High

Quick checklist

  • Create one top-level audit folder with a consistent subfolder structure for each record category.
  • Name driver files as: DQ - LastName, FirstName and vehicle files as: Unit - [number] - VIN.
  • Use the same category order as a typical FMCSA request list: carrier profile, driver files (49 CFR 391.51), vehicles and maintenance (49 CFR 396.3, 396.17), HOS records (49 CFR 395.8), drug and alcohol (49 CFR Part 382), accidents (49 CFR 390.15), authority.
  • Keep a missing-items log at the top of the packet — list each gap with who is retrieving it.
  • Add a dated index page as the first document so the auditor can see what is included.
  • Keep an untouched archive copy separate from the working packet to avoid accidental edits.
  • Test that files open correctly and are readable before submitting digital records.

Why this matters

A document packet does not need to look impressive — it needs to be navigable under time pressure. The most common audit difficulty is not missing records but slow retrieval: a driver file that requires searching three folders, a maintenance invoice with no unit number, an ELD export that is six clicks deep in a vendor portal. A packet built before the audit notice arrives means the carrier's response time is measured in minutes, not hours. The folder structure, file naming, and index together eliminate most of the retrieval friction that slows down reviews.

What to prepare

Area Records to gather
Packet tabs
  • Carrier profile: USDOT, authority, insurance, MCS-150, UCR
  • Driver qualification: one subfolder per driver, labeled by name
  • HOS and ELD: exports organized by driver and date range
  • Vehicle maintenance: one subfolder per unit, labeled by unit number
  • Drug and alcohol: enrollment, pre-employment tests, random records, Clearinghouse
  • Accident register and roadside inspection follow-up records
  • Insurance and authority: current filings matching the legal entity name
Packet controls
  • Index document listing each tab and the files within it
  • Version date on the index so it is clear when it was last updated
  • Missing-items log with item description and retrieval owner
  • Vendor and portal contact list
  • Portal login owner list: who has admin access to each system

Common gaps

  • Packet has files but no index — the auditor has to open everything to find what they need.
  • Driver and vehicle files are combined in one folder rather than separated by record type.
  • Screenshots are saved when full ELD or system exports are available.
  • Missing items are noted in a sticky note or email thread rather than in the packet itself.
  • Files sent to the auditor are not saved as copies, making the submitted set hard to reconstruct.

Before / During / After audit

Before

  • Build the folder structure before starting record collection.
  • Complete one full driver file and one full unit file as templates to confirm the structure works.
  • Use the completed examples to identify gaps in other files before the audit.

During

  • Send records in the same packet tab order regardless of the format requested.
  • Update the missing-items log as follow-up requests come in.
  • Keep an untouched archive copy separate from the version actively used for the review.

After

  • Save the final packet with the audit outcome letter or notes.
  • Convert the index into a recurring internal review checklist.
  • Archive old records and expired documents according to the applicable retention period.

FAQ

Does the document packet need to be submitted in a specific format?

FMCSA does not mandate a specific packet format for carriers. The format depends on whether the review is remote (typically uploaded files or email) or onsite (physical folders or on-screen review). For remote audits, using a consistent file naming convention and a folder structure that mirrors the record categories makes review faster and reduces follow-up requests. For onsite reviews, labeled physical folders with a printed index work the same way.

How should a carrier name files in a document packet?

Use names that identify the driver or unit and the document type without needing to open the file. For driver records: DQ-Smith-John-Annual-Review-2026.pdf. For vehicle records: Unit-12-VIN-1234-Annual-Inspection-2026.pdf. Consistent naming means the auditor and the carrier's own staff can locate specific records without scrolling through a folder of generic names like document1.pdf or scan.pdf.

What goes in the index page at the front of the packet?

The index should list every record category included, where it is located in the folder structure, the date range covered, and the number of documents. A separate column for missing items — with a note about retrieval status — lets the examiner see the packet's scope at a glance before pulling individual files. Keep it to one page. The goal is to reduce the examiner's navigation time, not to provide a report. Date the index the day it is assembled so the examiner knows it reflects the packet at submission, not an earlier version.

Download

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

Sources

FMCSA · agency-guide

New Entrant Safety Audit Resources

FMCSA New Entrant resource hub with safety audit, safety regulation, and program materials.

Last checked: 2026-06-16