SystemTrucking Fleets

DOT Compliance Audit

A DOT compliance audit run on the fleet's own records before the investigator arrives, with every finding tied to its section and its record.

See the demo Book a demo

Watch the mock review rated factor by factor ↓

Watch with transcript →

The problem

Driving records stuck in recruiting, trailers past their annual inspection

When the notice arrives, the safety team pulls driver files, daily logs, testing, maintenance and crash records from five or six systems, plus boxes scanned from a terminal that closed. If a mock audit happens at all, someone works a checklist over a handful of files, too few to show what the investigator's sample will.

The rating is arithmetic the fleet rarely does ahead of time: which findings make a pattern, which count double, which records it actually holds somewhere else. Driving records saved in recruiting never reach the driver file, and trailers miss their annual inspection after a move. These gaps surface in the investigator's report, when a proposed Unsatisfactory already has a clock on it.

Built forSafety directorsCompliance specialistsFleet owners and CEOsMaintenance managers

The Problem Today

A safety investigator samples a few dozen files and rates the fleet by a fixed table, and most fleets see that arithmetic first in the report.

61st day: after a proposed Unsatisfactory, interstate operation stops published
10%: of records examined, with more than one violation, is a pattern published

Gathered by hand before a visit

Drivers
Daily logs
Trailers
Crash files

Records filed in recruitingThe driver file never receives them
Patterns misjudgedHours violations count double, measured against daily logs

The Solution

Sampled as an investigator wouldDriver files, logs, vehicles and crashes drawn across terminals
Each factor rated by the tableSection, share of records and the pattern line on every check
A challenger recounts the draftRead as the investigator would, the agents' own errors included
Records filed with true datesFound elsewhere, opened by the VP, never backdated

Built-in controls

Nothing backdated; the VP files each record
Corrective plan signed by the VP and the CEO
Outside free text waits for a named person

What You Get

The fleet meets the investigator knowing its proposed rating, which gaps are patterns and who owns each fix.

Investigator choices rehearsedMore files, a closed terminal or rejected records, each rated
A plan with owners and datesEvery gap assigned before the visit and signed twice
Rulings turned into checksApplied only after the VP of compliance approves

Features

DOT compliance audit features, from the sample draw to the signed plan

The safety and compliance specialist runs the mock review, and the VP of compliance files records and signs the plan, three weeks before an onsite investigation.

demoThe fleet, its staff, drivers, trailers, files and counts shown here are a sample.

01Sample draw
A mock DOT audit drawn the way an investigator samples, steered mid-run
- A sample drawn across every terminal. Driver files, daily logs, vehicle files and the crash register are pulled at random, as a safety investigator pulls them.
- Steering in plain words. Asking for more driver files, a closed terminal's drivers or longer logs changes the draw before the readers start, and the steer is logged.
- Each agent's step in view. The plan, the record being read and who it hands to sit above the board while the review runs.
02Rating board
DOT compliance audit rating board with six factors worked by the rule's table
- Each check against the pattern line. Critical and acute checks show their section, the share of records and the line, so the team sees which gaps would count.
- The rating table worked in view. Factor ratings run through the fixed table to an overall result, with the working printed beside it.
- Labeled as the mock review's proposal. The rating is never presented as the agency's own; the investigator decides.
03Investigator's read
FMCSA compliance review rehearsed by a challenger that reads the agents' draft
- Points in the investigator's voice. Each says what would be asked for first, where the sample would widen and what would not be accepted.
- Errors the agents made in their draft. A ratio worked on the wrong denominator is recounted the investigator's way before the fleet relies on the rating.
- Answered by an agent or a named person. Records settle what they can; a sampling choice goes to the VP of compliance.
04Driver factor
Driver qualification checks file by file, dated from the recruiting system
- Every sampled file opened. Pre-employment record, medical certificate and testing checks are read for each driver, never marked present unopened.
- Original dates from the source system. A record found in recruiting shows its upload date from that system's audit trail and its distance from the first day.
- Gaps that cannot close, named. A file holding only an annual record is marked not found, because an annual record cannot stand in for the pre-employment one.
05Filing
Misfiled records filed with their original dates once the VP opens each one
- Proposed by the specialist, filed by the VP. The specialist cannot file what they proposed, and the VP must open each record before approval is enabled.
- Nothing backdated. Each record is filed today showing the date it really arrived, read from the recruiting system's audit trail.
- A signature with its meaning. The reason code, the VP's own words and what the signature attests go into the audit trail together.
06Rerated
Driver factor rerated below the pattern line once the records are filed
- The board recomputes after filing. Files still lacking the record fall under the line, and the proposed rating moves with them.
- Real patterns stay on the board. Factors with gaps that filing cannot close stay rated, so the corrective plan starts from what is truly missing.
- The condition stated. The board says the proposal holds only if the investigator accepts the records with their original dates.
07Vehicle factor
Annual vehicle inspection gaps traced trailer by trailer to the loads pulled
- Roadside out-of-service rate first. The factor starts from the roadside rate against the rule's threshold, then file findings lower it.
- Loads counted after each lapse. Each trailer's loads with no inspection in the year before them are counted, so maintenance sees the exposure.
- Out of service only by maintenance. Agents ask the vendor for the report; taking a trailer off the road stays the maintenance manager's call.
08Rehearsal
Investigator choices rehearsed as rated scenarios before the visit
- Scenarios rated by the same table. Fewer files, a closed terminal's drivers or rejected recruiting records each get a full rating.
- Assumptions editable and labeled. Each assumption stays labeled until an analyst confirms it, and nothing in the rehearsal changes a record.
- Where the rating turns. The fleet sees which single choice by the investigator would move it from one rating to another.
09Corrective plan
Corrective action plan with owners and due dates, signed by the VP and the CEO
- Each gap with an owner, fix and date. Each gap the review found goes to a named person with a fix and a due date before the investigator arrives.
- Two signatures in order. The VP signs after reading every item; the CEO co-signs and cannot sign first.
- Nothing sent to the agency by signing. Sending the plan or any admission is a separate decision, with a named person, a reason and a second person.

The specialist runs the mock DOT audit and the VP answers for the rating

Four people at the carrier act on the review; each sees the same board and owns a different part.

VPs of compliance

Own the proposed rating, file records found elsewhere and sign the corrective plan

Each found record opened before it is filed
The table's working on one screen
Rulings applied only after their approval

Safety and compliance specialists

Run the mock review, steer the sample and answer the challenger's points

The investigator's arithmetic before the visit
Misfiled records found with their real dates
Scenarios rated before choosing a fix

Fleet owners and CEOs

Co-sign the corrective plan and weigh shipper and insurer exposure

A plan read in full before co-signing
No admission sent without a second person
A rating proposal with its conditions stated

Maintenance managers

Hold vehicle files and decide when a lapsed trailer leaves service

Loads pulled after each lapse, counted
Vendor reports asked for in fixed fields
Free-text vendor notes held for their reading

Five signatures on one mock review, each after opening the record behind it

Each person signs their own part, and a signature from the wrong person is not offered.

Safety and compliance specialist

Sees: The board, the challenger's points and the records found in other systems
Signs: The proposal to file each record, with a reason

VP of compliance

Sees: Every proposed record, opened one by one with its audit-trail date
Signs: The filing, the sampling answers, new lessons and the corrective plan

CEO and owner

Sees: The full corrective plan, after the VP has signed
Signs: The co-signature on the plan

HR and recruiting manager

Sees: The recruiting system's export and its audit log
Signs: The attestation of where each record came from

Maintenance manager

Sees: Lapsed trailers and the vendor's inspection reports
Signs: Taking a trailer out of service and accepting a vendor report

More screens

The run log, the work queue and the record room behind the rating board

Where the review's steps, the leftover work and every artifact the agents read are kept.

The run: sampler, driver file reader, hours reader, vehicle and accident reader, rating agent and the investigator's read, each with sources — **The run**Each agent's step with what it read, its conclusion, its certainty and who it handed to, timed from the redraw to the corrected rating.

Work queue: records found on time outside the sample, files with no record anywhere, crash files missing copies, lapsed trailers — **Work queue**Leftover work by count, owner, due date and clock: records to sign, files with nothing found, report copies to request.

Record room grouped by notice and rule, driver files, hours of service, testing, vehicles and crashes, and outside requests — **Record room**The notice, the rule text, driver files, recruiting uploads, the HR attestation and inspection reports, each marked when opened.

Lessons: an annual record never stands in, original dates only, two new lessons waiting for approval and one rejected — **Lessons from rulings**Two lessons applied, two waiting for the VP, one rejected with its reason. A lesson becomes a check only after approval.

Audit trail: the VP signing the corrective plan, filing four records, opening each one, and the specialist's proposal with its reason — **Audit trail**The plan signature, the filing, each record opened by the VP and the specialist's proposal, with what each signature meant.

demoSample data, from the working solution.

A wrong hours divisor, records in recruiting and trailers past their annual

Four things the mock review found that a checklist over a handful of files would not.

The agents' own hours ratio

The draft counted 7 of 30 drivers over 11 hours. The investigator divides by daily logs: 9 of 900, 1.0%, no pattern.

Records sitting in recruiting

6 of 50 driver files lacked the pre-employment driving record. 4 were found in the recruiting system, uploaded on time; 2 are not found anywhere.

Trailers from a closed terminal

3 of 25 vehicle files, 12.0%: trailers that pulled 22 loads in all after their annual inspection lapsed.

Crash files without report copies

6 of 46 crash register entries lacked the police or insurer report copies, 13.0%, which keeps the General factor Conditional.

demoSample data, from the working solution.

What safety leaders ask before a DOT compliance audit

What is a DOT compliance audit?

A DOT compliance audit, a compliance investigation in the agency's terms, is when a safety investigator samples a carrier's records and rates six factors under the rule's Appendix B. DOT Compliance Audit runs that review first on the fleet's own records, labeled as a mock review, so the fleet sees its proposed rating before the visit.

Is this a DOT audit checklist?

It does the work a checklist points at. It opens the sampled driver files, daily logs, vehicle files and the crash register, ties each check to its section and its records, and works the result through the rating table.

How is a pattern counted in an FMCSA compliance review?

Appendix B counts a pattern as more than one violation reaching at least ten percent of the records examined, and an hours-of-service pattern counts two points. The board works this check by check, and the challenger confirms the right records are the denominator.

Is the rating on screen the agency's rating?

No. Every rating is labeled as proposed by the mock review. The investigator decides, and the board states the conditions its proposal rests on, such as the investigator accepting records with their original dates.

Can a record found in another system count?

Only with its original date, read from that system's own audit trail and inside the rule's window. The specialist proposes the filing, the VP opens each record and signs, and nothing is backdated. The rehearsal shows the rating if the investigator rejects them.

Does signing the corrective action plan send anything to the agency?

No. The VP signs and the CEO co-signs the plan inside the company. Sending it, or any admission, is a separate decision with a named person, a reason and a second person.

Trucking Fleets