DOT Audit Prep

Corrective Action Plan After a DOT Audit

A corrective action tracker for assigning owners, due dates, proof files, and follow-up notes after audit findings.

Who this is for
Motor carriers, Safety contacts, Small fleets
Written by
Dale Whitfield
Reviewed by
DOT Audit Prep Editorial Team
Last reviewed
2026-06-16
Source confidence
Medium

Quick checklist

  • Copy every finding or requested correction from the audit into one action tracker — not separate emails or notes.
  • Assign a single named owner for each corrective action item.
  • Set a due date and name the specific proof document needed to close each item.
  • Separate one-time file fixes from process changes — they need different owners and timelines.
  • Save the final correspondence and proof of completion with the original audit packet.
  • After closing one-time fixes, check whether the same gap exists in other driver or unit files.
  • Schedule a 30-day and 90-day check to confirm that process changes are holding.

Why this matters

After an audit, the standard response is to fix the sample file that was flagged. That closes the citation but leaves the same gap in every other file the auditor did not review. A corrective action plan is useful when it addresses both the immediate finding and the system that allowed the gap to occur. Carriers that see the same findings at every audit typically treat each review as a one-time records problem rather than a recurring process problem. The carriers that improve their ratings between audits address both the file and the workflow.

What to prepare

Area Records to gather
Action tracker fields per finding
  • Finding description as written by the examiner
  • Record category: DQ file, maintenance, HOS, drug and alcohol, or other
  • One named owner responsible for closing the item
  • Due date with buffer before any response deadline
  • Specific proof document required to close the item
  • Status: open, in progress, or closed with proof
Process change items
  • What process created the gap that allowed the finding
  • Revised procedure to prevent recurrence
  • Person responsible for the new process going forward
  • How the new process will be verified over time
  • Date the change went into effect
Review schedule
  • 7 days: confirm all owners understand their items and have started work
  • 30 days: confirm new processes are in place and documented
  • Quarterly: pull a sample from each record category to check for recurrence

Common gaps

  • The carrier corrects the flagged sample file but not the same issue in the other files that were not reviewed.
  • No documented proof that a correction was made — the action was described verbally but not written down.
  • Vendor-dependent items have no follow-up confirmation step — the carrier assumes the TPA or ELD provider handled it.
  • The action tracker is not connected to future internal reviews, so the same findings recur.
  • Process changes are announced in a meeting but not assigned to a specific person or written into a checklist.

Before / During / After audit

Before

  • Set up a blank action tracker template before the audit starts so it can be filled in during the review.

During

  • Record findings and follow-up requests exactly as the examiner phrases them.
  • Ask what proof format is expected for each item when the finding does not specify.

After

  • Close each action item with documented proof, not a verbal update.
  • Review whether the same gap exists in other files beyond those that were sampled.
  • Keep the completed tracker with the full audit packet for reference at the next review.

FAQ

Is a written corrective action plan required after a DOT compliance review?

For compliance reviews that result in a proposed safety rating, the carrier may submit evidence of corrective action to request a rating upgrade under 49 CFR 385.17. The submission must address the specific violations that led to the rating. Even when a written plan is not formally required, documenting corrective actions in writing protects the carrier if the same issue comes up in a follow-up review.

What is the difference between a one-time file fix and a process correction?

A one-time fix is adding a missing document to a specific file — for example, adding an annual MVR review note to a driver's DQ file. A process correction is changing how future records are created — for example, adding a calendar reminder so the annual MVR review happens on time for every driver every year. Most audit findings require both: fix the flagged item and change the process so the same gap does not recur in other files or in the next review period.

How should a carrier document that corrective actions were completed?

Each action item should have a named proof document — the actual updated file, the vendor confirmation email, the training sign-in sheet, or the new calendar reminder with a screenshot. Verbal confirmation or a note that says 'completed' without supporting documentation does not constitute proof if the issue is revisited. Save the proof alongside the action item in the audit folder.

Download

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

Sources

Related resources

After a DOT AuditA post-audit closeout guide for result notices, record storage, rating follow-up, and process updates.Safety Ratings and CSA BasicsA plain explanation of FMCSA safety ratings, CSA BASICs, and why audit findings can matter after the document review.Missing Documents Before an AuditA practical action list for trucking companies that discover missing documents shortly before a DOT audit.