Mock DOT Audit Services

A mock DOT audit is an independent review of a carrier’s records, safety controls and operating practices before FMCSA, a state partner, an insurer or a customer asks difficult questions. It is not an official audit and it does not create a safety rating. Its purpose is to find weak records, missed deadlines and unsafe processes early enough for the carrier to correct them.

When a mock DOT audit is worth doing

A carrier does not need to wait for an investigation letter. The best time to review records is before the pressure starts. A mock audit is useful when a company has grown quickly, changed staff, added CDL drivers, bought another carrier, received poor roadside inspections, had a serious crash, is preparing for a new entrant safety audit or wants to improve adverse SMS/BASIC or roadside inspection and crash performance.

Mock audit, safety audit and compliance review are not the same

The words are often used loosely, but the difference matters. An official new entrant safety audit, an official compliance review and a private mock audit have different consequences. A provider should be clear about which one it is preparing you for.

A mock audit should never be sold as a guarantee that FMCSA will pass the carrier, avoid enforcement or issue a particular rating. A new entrant safety audit itself produces an adequate or inadequate basic-safety-management-control determination, not a safety fitness determination or safety rating. The mock review should produce a practical work list and evidence trail so the carrier knows what to fix.

What a proper mock DOT audit should check

The review should follow the real operating risk. A small property carrier with CDL drivers needs a different review from a hazmat carrier, passenger carrier, owner-operator adding drivers or fleet with a conditional rating. The provider should scope the review before asking for records.

• company registration, USDOT profile details, operating authority and insurance evidence where applicable;
• driver qualification files, applications, MVRs, road tests or accepted equivalents, annual reviews, medical qualification records, and previous-employer safety-performance-history investigation records kept under controlled access;
• Clearinghouse pre-employment full queries, annual queries at least once every 12 months, limited-query consent, electronic full-query consent, limited-hit follow-up within 24 hours and prohibited-driver handling for employees subject to Part 382;
• DOT drug and alcohol testing program, random-selection pool, testing records, policy and required training records for covered CDL drivers where Part 382 applies;
• hours-of-service records, ELD records, supporting documents and unidentified driving controls;
• vehicle maintenance files, annual inspections, DVIRs where required and repair evidence;
• 49 CFR 390.15 accident register for federally defined accidents, retained three years, plus copies of accident reports required by state agencies, other governmental entities or insurers;
• applicable Hazardous Materials Regulations records where the operation is subject to the HMRs, with placarding, PHMSA registration, security plan and hazardous materials safety permit thresholds treated separately;
• specific required training and acknowledgement records where applicable, such as 49 CFR 382.601 driver receipt, 382.603 supervisor training and 172.704 hazmat training; and
• prior violations, roadside inspection data, out-of-service trends and corrective actions.

The report should rank problems by operational risk

A useful mock-audit report does not bury the carrier in a long spreadsheet with no priorities. It should separate urgent safety issues, missing records, stale records, process gaps and housekeeping items. A missing annual review note is not the same as using an unqualified driver or allowing a prohibited driver to perform safety-sensitive work.

Records to prepare before a mock DOT audit

The provider should tell the carrier what to gather before the review starts. The list does not need to be complicated, but it should match the carrier’s actual operation.

1. Carrier snapshot. USDOT number, operating authority, states served, vehicle list, driver list, commodities and insurance evidence where applicable.
2. Driver records. DQ files, driver license evidence where it serves as a road-test equivalent, medical qualification evidence, MVRs, annual reviews, road test records and driver investigation-history records.
3. Drug and alcohol records. Part 382 program records, random-selection pool records, test records, policy records, supervisor training and Clearinghouse workflow evidence where covered-driver rules apply.
4. Hours-of-service records. ELD account access, logs, supporting documents, edits, unassigned driving and malfunction records.
5. Vehicle files. Maintenance schedule, repairs, annual inspections, DVIRs where required and out-of-service correction evidence.
6. Accident and violation records. The 49 CFR 390.15 accident register where the federal definition is met, required accident reports, roadside inspections, citations and corrective actions.

What a provider should not claim

The review should stay honest. A provider should not claim that a mock audit makes the carrier immune from FMCSA action, guarantees a satisfactory outcome, removes roadside inspection history or creates an official safety rating. It should also avoid hiding uncertain records behind broad statements such as “file complete” when the evidence has not been checked. The value is in the specifics: which driver file is missing an annual review, which vehicle inspection evidence is stale, which ELD process is uncontrolled and which corrective action still needs proof.

What happens after the mock audit?

The carrier should leave with a clear fix list, not vague advice. For each finding, there should be an owner, target date and evidence requirement. Some issues can be corrected by obtaining a missing document. Others require a process change, such as how drivers are onboarded, how annual MVRs are scheduled, how ELD edits are reviewed or how maintenance defects are closed.

For carriers with serious findings, the provider may recommend a staged plan: remove immediate safety risks first, repair core driver and vehicle records next, then build calendar controls so the same issue does not return. A mock audit that only creates a file once and leaves no maintenance system behind has limited value.

How mock audits connect to ratings, CSA and future reviews

A mock audit does not change FMCSA data, erase violations or create a safety rating. It can, however, show the carrier whether the records behind its safety program are strong enough to support correction work. If a carrier has adverse SMS/BASIC measures, poor roadside trends, unresolved DataQs or a rating problem, the mock audit may help identify which internal controls need attention before a formal submission or review.

For new carriers, the mock audit is usually about proving that basic safety-management controls exist. For established carriers, it may be about confirming that the controls still work after growth, staff changes or repeated roadside issues.