How to Write a Corrective Action Plan After a Bad Audit

A bad audit result feels like a verdict. It is really a to-do list. If a compliance review left you with a proposed Unsatisfactory or a Conditional rating, a strong corrective action plan is how you show FMCSA that the problems are fixed and will stay fixed.

This guide walks through how to build one that is clear, specific and backed by proof.

When you need a corrective action plan

Carriers usually write a corrective action plan in these situations:

• A proposed Unsatisfactory rating. This is the urgent case. Under 49 CFR 385.13, the rating becomes final after a set period unless it is changed. That window is generally 60 days for property carriers and shorter for passenger carriers and certain hazmat carriers. Check the deadline on your notice.
• A Conditional rating. You can keep operating, but customers and insurers notice. A corrective action plan supports a request to upgrade.
• A failed new entrant safety audit. New carriers usually must submit a corrective action plan within a set time. The process differs from rating upgrades, so follow the instructions in your notice.

The request for a rating change based on corrective action is covered in 49 CFR 385.17. You must make the request in writing and show evidence that you have taken corrective action and that your operation now meets the safety fitness standard.

Start with the findings

Before writing anything, get organized.

1. List every violation from the compliance review report. Focus first on acute violations and patterns of critical violations, since those drove the rating.
2. Group them by factor or area. For example, driver qualification, drug and alcohol testing, hours of service, maintenance.
3. Note how many records were affected. One missing medical certificate and ten missing certificates call for different fixes.

This list becomes the outline of your plan.

Find the root cause for each problem

The most common mistake is fixing the symptom. If an investigator found five drivers with expired medical certificates, getting five new certificates fixes today. It does not fix next month.

For each finding, ask why it happened:

• Was there no system to track the item?
• Was nobody assigned to it?
• Did staff not know the requirement?
• Was there a system, but nobody followed it?

A good plan names the root cause plainly. For example: “We had no process to track medical certificate expiration dates. The office manager relied on drivers to bring in new cards.”

Build each corrective action

For every finding, write a short section with these parts:

• The violation. Quote the regulation and briefly describe the finding.
• The root cause. One or two sentences.
• The immediate fix. What you already did to correct the specific records or situations.
• The system fix. The new process, tool, policy or training that prevents it from happening again.
• The responsible person. A name or job title, not “management.”
• The date completed or scheduled completion date.
• The evidence. A list of the documents attached that prove it.

Here is the difference between weak and strong:

Weak: “We will do better on hours of service.”

Strong: “Root cause: no one reviewed driver logs. Fix: safety manager now reviews all logs weekly against fuel receipts and bills of lading using a written procedure (attached). Drivers with violations receive written coaching (sample attached). Started on the date shown in Exhibit C.”

Gather proof that FMCSA can verify

A plan without proof is just a promise. Attach evidence for every item, such as:

• Updated driver qualification files or a sample of them.
• New medical certificates and the note verifying the medical examiner on the National Registry.
• Proof of enrollment in a drug and alcohol consortium and random selection records.
• Clearinghouse query records.
• Written policies and procedures.
• Training sign-in sheets and materials.
• Maintenance records and periodic inspection reports.
• Log audit reports showing reviews are happening.
• Screenshots or reports from any tracking system you now use.

Organize the attachments by finding, and label them to match the plan. Make it easy for the reviewer to check each item.

Tracking systems are strong evidence because they show a lasting fix. For example, DOT Compliance Watch organizes driver files, testing records, HOS records and maintenance records and sends alerts before documents expire. A report showing upcoming expirations and completed items shows a reviewer that tracking is now built into your operation.

Submit, then follow through

A few practical tips on submission:

• Send it early. For a proposed Unsatisfactory rating, submit well before the deadline, so FMCSA has time to review it.
• Keep it readable. Use headings, numbered findings and short paragraphs.
• Keep copies of everything you send, with the date sent.
• Respond promptly if FMCSA asks for more information.

FMCSA may accept the plan, ask for more, or conduct a follow-up review. Either way, the systems you described must actually run. A future review will check whether they did.

Keep a short monthly checklist:

• Are new tracking processes being followed?
• Are expiring documents renewed before they lapse?
• Are log reviews and coaching documented?
• Is training complete for new staff?

For anything as serious as a proposed Unsatisfactory rating, consider working with a qualified advisor who handles FMCSA matters. The rules and procedures are in Part 385, and our DOT regulations reference is a good starting point.

Turn a bad audit into better systems

A corrective action plan is your chance to prove your operation is safer than the audit showed. Build real systems, back them with records and keep them running. Start a 14-day free trial and put those systems in place today.