A corrective action plan (CAP) documents a compliance problem, its root cause, the specific fix, who is responsible, the deadline, and how you verified it worked. Carriers use CAPs to respond to audit findings, a conditional safety rating, or recurring violations. A strong CAP shows FMCSA, brokers, and insurers that your operation catches and corrects its own problems.
Auditors and underwriters do not just want to hear that you fixed a violation. They want to see it: what went wrong, why, what you did, and proof it stuck. That is what a corrective action plan is. Done well, it is one of the strongest trust signals a carrier can produce.
When You Need a Corrective Action Plan
- After a compliance review that results in a conditional or unsatisfactory rating
- To respond to specific findings from a DOT audit
- When a driver or the fleet has a recurring violation pattern, such as repeat HOS issues
- As internal documentation whenever you correct any meaningful compliance gap
Note on new entrant audits specifically: if a new carrier fails its new entrant safety audit, FMCSA requires a corrective action plan submitted within 15 days of the failure notice, with corrective action completed within a set window (generally 60 days for most carriers, or 45 days for passenger and placarded hazmat carriers). Rated carriers seeking to upgrade a conditional or unsatisfactory rating follow a separate process under 49 CFR Part 385.
What a Strong CAP Includes
Every corrective action plan should answer six questions in writing:
- The problem. The specific violation or finding, stated plainly.
- The root cause. Why it happened. Not "driver error." The actual reason: no daily log review, no expiration alerts, a dispatch practice, a training gap.
- The corrective action. The specific change you made to fix it.
- Who is responsible. A named person who owns the fix.
- The timeline. When it was corrected and when the new process starts.
- Verification. How you confirmed it worked, and how you will keep it from recurring.
A Simple Template You Can Use
| Field | What to Write |
|---|---|
| Finding / Violation | The specific issue, with date and reference if from an audit |
| Root Cause | The real reason it happened, at the system level |
| Corrective Action | The exact change made |
| Responsible Person | Named owner of the fix |
| Date Corrected | When it was fixed |
| Preventive Measure | The new ongoing process |
| Verification | How you confirmed it, and the follow-up date |
An Example
Finding: Two drivers had expired medical certificates in their files during a review. Root cause: No expiration tracking. Medical cards were only checked at hire. Corrective action: Pulled and filed current certificates for both drivers. Responsible person: Office manager. Preventive measure: Set 60-day expiration alerts on every medical card and MVR in the DQ file system. Verification: Audited all active files, confirmed current, follow-up review scheduled quarterly.
Why This Matters
A weak CAP says "we will do better." A strong CAP shows a system that catches problems. That difference matters to an auditor deciding your rating, to a broker running a safety review, and to an underwriter pricing your renewal. It is also the honest way to actually improve.
Most corrective action plans I see fail for the same reason: they treat the symptom, not the system. A driver got an HOS violation, so the plan says the driver was retrained. Fine. But why did it happen? If the answer is that nobody reviews logs daily, retraining one driver fixes nothing. Write the plan at the level of the system that let it happen, and it becomes proof you actually run a safe operation.
Common Mistakes Carriers Make
(1) Writing "driver error" as the root cause instead of the real system gap. (2) Documenting the fix but no preventive measure. (3) No named owner, so nobody actually does it. (4) No verification, so you never confirm it worked. (5) Filing the CAP and never following up. (6) Vague promises like "we will do better" instead of a specific change.
What Fleet Regulators Helps With
We build corrective action plans that hold up, whether you are responding to a DOT audit finding or fixing a recurring problem before it becomes one. We help identify the real root cause, document the fix and the preventive measure, and verify it stuck. For carriers that want ongoing support, our fractional safety department manages corrective action as part of day-to-day compliance.
Build a Corrective Action Plan That Holds Up
Book a free compliance review. If you are responding to a finding or a recurring problem, we will help you build a plan that actually fixes it.
Book a Free Compliance Review →DOT Audit Help
Fleet Regulators builds corrective action plans for audit findings and recurring violations, and prepares carriers for every stage of a compliance review.
Get Audit Help →Frequently Asked Questions
It is a written document that states a compliance problem, its root cause, the specific corrective action, who is responsible, the timeline, and how you verified it worked and will prevent recurrence.
Commonly after a compliance review that results in a conditional or unsatisfactory rating, to respond to specific audit findings, or when a driver or fleet has a recurring violation. For a failed new entrant safety audit, FMCSA requires a corrective action plan within 15 days of the failure notice.
It addresses the system that allowed the problem, not just the symptom. It names a responsible owner, sets a preventive measure, and includes verification that the fix worked.
Yes. We help identify the real root cause, document the fix and preventive measure, and verify it, whether it is for an audit finding or a recurring internal problem.
