Internal DOT Compliance Audits: What Motor Carriers Should Review

An internal DOT compliance audit is a carrier-organized review of applicable requirements, operational practices, and supporting records. Its purpose is to identify where actual operations and documented controls do not align. Apparently complete files can contain expired qualifications, inconsistent timestamps, inaccessible vendor records, or unsupported completion statements.

A useful review covers carrier status, driver qualification, testing programs, hours of service, vehicle maintenance, and accident and inspection records. It tests what the evidence establishes, identifies gaps, and follows corrective actions through verification.

This guide explains how to scope that work and document defensible findings. An internal review does not replace an official agency audit or guarantee its outcome.

How an Internal Review Differs From an Official DOT Audit

“DOT audit” is broad terminology. Clarify which process is involved before choosing a checklist or interpreting results. A carrier-organized review and an official FMCSA safety audit serve different purposes.

49 CFR Part 385 distinguishes safety audits from compliance reviews. Official processes do not all have the same scope, timetable, or rating consequences. An internal reviewer should identify deficiencies clearly without presenting internal conclusions as agency determinations.

Define the Scope and Select Records for Review

Confirm Which Requirements Apply

Start with an operational profile: interstate or intrastate movements, vehicle weights and configurations, passenger capacity, cargo, and driver licensing requirements. Consider the transportation involved, rather than assuming a trip is intrastate solely because the vehicle stayed within one state.

Commercial driver’s license (CDL), passenger-carrier, and hazardous-material requirements can change the review substantially. Identify the FMCSA Requirements that apply to the operation before selecting records. State requirements also need separate examination for intrastate operations. Use the applicable regulatory definitions, including those in 49 CFR §390.5, as a starting point.

Record claimed exceptions and the facts supporting them. A label such as “short-haul” is not sufficient evidence.

Define the review period, locations, responsible reviewer, and authorized access to records. Separate regulatory criteria from company procedures so an internal policy failure is not automatically described as a federal violation.

For staff building foundational knowledge, US Compliance Institute’s DOT Compliance course can support their understanding of the regulatory framework.

Document Your Sample and When to Expand It

Build the population before selecting records. List relevant drivers, vehicles, trips, and record categories, including former drivers and disposed vehicles whose records remain within applicable retention periods.

Combine routine selections with higher-risk cases: recent hires, recurring exceptions, changed operations, and vendor-held records. Record identifiers, dates, selection reasons, exclusions, and limitations.

Expand the sample when findings suggest a pattern. Several missing annual reviews may justify examining the affected terminal or hiring group rather than treating each file as an isolated issue.

Sampling is an internal management method. There is no universal federal percentage for this self-review, and a clean sample does not establish compliance across unexamined records. Sampling also does not replace mandatory ongoing checks.

Internal DOT Audit Checklist: Records and Controls to Test

Use this DOT compliance checklist as a starting matrix for your internal review. Adapt each test to the operation and review period.

Carrier Information, Authority, and Insurance

Match the legal entity, USDOT number, addresses, and operating information across official records and internal documents. Determine which authority, insurance, process-agent, and other filings actually apply. Every carrier does not need an MC number or identical insurance documentation.

Compare carrier information in SAFER with applicable Licensing and Insurance records and policy documents. FMCSA’s operating-authority status instructions identify current status and authority-history checks.

Examine historical operating dates as well as today’s status. Possessing an authority certificate or insurance document does not establish that the required status or coverage was effective throughout the reviewed period.

Driver Qualification and Medical Status

A driver qualification file, or DQ file, contains the applicable evidence supporting a driver’s qualifications. Check applications, initial inquiries, annual motor vehicle records (MVRs), documented reviews, and road-test evidence or permitted equivalents against §391.51 file requirements. Apply relevant exceptions and record-specific retention provisions.

Compare the first assignment and later operating dates with qualification evidence. A currently valid record does not resolve an earlier lapse. Check initial investigations under §391.23 and annual inquiry and review under §391.25. The annual driver-submitted violation list was removed; annual MVR inquiry and review obligations remain where applicable.

Medical evidence depends on driver category. For applicable CDL drivers, examine the licensing-state Commercial Driver’s License Information System record; non-CDL drivers generally require the medical examiner’s certificate and related verification. Do not apply paper-card assumptions universally. Check current NRII implementation and exemption information, including any geographically limited relief, against the driver and operating dates. Restrict access to sensitive records.

Drug and Alcohol Program Records

First establish coverage under 49 CFR Part 382, generally involving drivers operating vehicles requiring a CDL, subject to specified exceptions.

For covered drivers, examine pre-employment drug-test results or a documented qualifying exception, random selections and completions, and applicable post-accident, reasonable-suspicion, return-to-duty, and follow-up records. Pre-employment alcohol testing is not universally required, and not every accident triggers DOT testing.

Reconcile the active driver roster with consortium records. Check required pre-employment and annual Clearinghouse queries, appropriate consent, reporting, and responses to prohibited status. Clearinghouse query guidance helps distinguish query types and consent evidence. Enrollment alone does not prove completion.

Keep testing information under controlled access, with applicable retention and disclosure restrictions. Do not distribute sensitive results through ordinary personnel folders or an unrestricted findings log.

Hours of Service and ELD Records

Hours of service (HOS) rules govern driving and duty limits. An electronic logging device (ELD) records relevant duty-status information, but its presence does not establish compliance.

Under 49 CFR Part 395, review applicable duty records, supporting documents, unidentified driving, edits, annotations, missing periods, and malfunction records. Test retrieval and examine evidence supporting claimed exceptions.

Compare selected records with dispatch, fuel, delivery, and other supporting information. Normalize time zones and identify what each timestamp represents. Personal conveyance is not a blanket HOS exemption.

Classify discrepancies carefully. An unexplained mismatch warrants investigation; a missing required record may establish a recordkeeping issue; a substantive violation needs evidence supporting the applicable elements.

Vehicle Inspections, Maintenance, and Repairs

Match vehicle identifiers across periodic inspections, maintenance history, driver vehicle inspection reports (DVIRs), repair orders, and roadside findings. Under 49 CFR Part 396, trace a reported defect through assessment, required correction, certification, and subsequent operation. Examine out-of-service restrictions and follow-up evidence.

Avoid outdated property-versus-passenger assumptions: current federal §396.11 does not require no-defect DVIRs for either category when no defect or deficiency was discovered or reported. Check applicable exceptions, state requirements, and company procedures separately.

A repair invoice must relate to the correct vehicle and condition. Paperwork alone does not establish safe operating condition or authorize operation. Confirm that the sequence supports required correction before further use.

Accident Records and Roadside Findings

Reconcile the accident register with incident reports, insurer records, towing invoices, and dispatch interruptions. Apply the regulatory accident definition rather than the company’s incident label. For example, a collision recorded internally as “minor” may qualify because disabling damage required towing.

Section 390.15 requires the applicable accident register and associated reports to be maintained for three years after each accident.

Use recurring roadside findings to select further tests. FMCSA’s Compliance, Safety, Accountability program uses Safety Measurement System information to support oversight. The term CSA scores is commonly used informally, but carriers do not have one universal CSA score. SMS information and safety ratings are distinct and should be interpreted separately.

Additional Requirements for Your Operations

Add targeted checks for hazardous materials, passenger services, and other specialist work. For hazmat operations, examine applicable shipping, handling, security, and function-specific training requirements. Passenger operations may require different operating-limit and equipment checks. Assign specialist review where the reviewer lacks the necessary expertise.

Record Findings and Set Corrective Actions

Describe what the evidence shows precisely. Distinguish:

• Missing evidence: A required or expected record cannot be located.

• Expired evidence: Validity ended before the relevant activity.

• Inconsistent evidence: Sources conflict on a material fact.

• Inaccessible evidence: A record reportedly exists but cannot be retrieved.

• Substantiated failure: Evidence establishes that an applicable requirement was not met.

Missing records can themselves establish a recordkeeping issue. They do not automatically prove the same underlying operational violation. Conversely, a document’s existence does not prove the activity complied.

Use this findings-log structure:

Finding ID | Requirement or criterion | Evidence reference | Finding | Immediate response | Owner | Due date | Closure evidence

Identify the affected driver, vehicle, date, and sample. State the regulatory provision or company criterion, preserve source evidence, and explain the limitation. “Annual review note unavailable for Driver 17” is more useful than “DQ files incomplete.”

Assess urgency before assigning routine follow-up. A potential restriction on current operations requires prompt evaluation and appropriate action. Internal target dates do not extend regulatory or agency deadlines.

Investigate whether the cause involves knowledge, scheduling, access, or a failed control. Training may address a demonstrated knowledge gap, but attendance alone cannot close the finding. Never backdate records or silently reconstruct missing evidence.

Worked Example: Investigating an HOS Record Discrepancy

Hypothetical example: Dispatch shows a 6:15 a.m. departure, while the assigned driver’s ELD shows off-duty status until 7:00 a.m.

The reviewer confirms the driver, tractor, date, and time zone, then checks what “departure” means in the dispatch system. Gate records, location information, delivery documents, and the dispatcher’s explanation show that 6:15 was the planned departure. The actual departure occurred after 7:00.

The evidence supports an administrative discrepancy in dispatch, not a finding of unrecorded driving. The reviewer preserves the original entry and explanation, assigns correction of the misleading field, and checks other trips using the same workflow.

If supporting evidence instead showed earlier vehicle movement, further investigation would determine who drove, whether the duty record was deficient, and whether an operating-limit violation occurred. Those are separate questions.

No one changes the ELD record merely to match dispatch. Any justified amendment must follow applicable requirements and preserve required history. Follow-up testing checks whether dispatch now distinguishes planned and actual events consistently.

Verify Corrections and Plan the Next Review

Define acceptable closure evidence when assigning the action. A completed task statement is insufficient if it does not demonstrate that the underlying problem was addressed.

For a retrieval failure, test access to usable records. For a missed review, examine the completed review and test the revised scheduling control. For a qualification gap, verify current eligibility and separately document what happened during the affected period.

Record the verifier, date, evidence examined, and conclusion. Where practical, use someone other than the action owner to verify closure. Reopen findings when support is inadequate or subsequent testing shows recurrence.

Correction can resolve an ongoing problem without erasing a historical failure. Preserve that distinction in the findings log.

Adjust the next motor carrier internal audit to operational changes, repeat findings, new systems, and risk. Periodic self-reviews are a management practice, not a universal federal annual internal-audit mandate. Mandatory checks under individual regulations continue independently of the internal review calendar.