Skip to main content
DOTAudit Academy

Master checklist

DOT New Entrant Audit Document Checklist

An evidence-first checklist for driver, vehicle, HOS, testing, accident, insurance, and company records.

12 minute readPublished Reviewed

Short answer

Direct answer

A useful checklist does more than name documents. It identifies the control being proved, the record owner, the retention location, the relevant period, and the quality check performed before submission.

01

Organize by control and evidence

A useful checklist does more than name documents. It identifies the control being proved, the record owner, the retention location, the relevant period, and the quality check performed before submission.

Source: FMCSA — Safety Audit Resource Guide

02

Core evidence families

Typical review areas include company and authority information, insurance, driver qualification, controlled-substances and alcohol testing, hours of service, vehicle inspection and maintenance, accidents, and operational controls. Your actual request controls the response.

  • Company profile, authority, and insurance evidence
  • Driver roster and qualification files
  • Drug-and-alcohol program and query evidence
  • Logs and supporting records
  • Vehicle list, inspections, repairs, and maintenance
  • Accident register and supporting files
  • Inspection-data review and correction records

Source: FMCSA — New Entrant Safety Assurance Program

03

Quality control before upload

Check names, dates, signatures, vehicle identifiers, legibility, and date ranges. Use a response index and avoid sending unrelated personal information. If a record never existed, do not create a false historical document.

Source: FMCSA — Safety Audit Resource Guide

Primary sources

Verify the current rule

Questions carriers ask

Frequently asked questions

Is there one universal audit checklist?

No. FMCSA guidance establishes review areas, but the verified audit notice and your operation determine the exact request.

Can screenshots be audit evidence?

Sometimes, if they are legible, complete, attributable, and accepted by the request. Native exports are often easier to validate.

Free working tools

Put the guidance to work

Continue this desk

Topic hub