Corrective Action Request (CAR): What It Is, How the Process Works, and a Free Form

I’ve reviewed a lot of corrective action files over the years, and most of them have the same problem. The paperwork is complete. The problem isn’t solved.

The CAR got issued, somebody wrote “operator error, operator retrained” in the root cause box, the customer accepted the response, and the file got closed. Then the same nonconformance showed up four months later wearing a different job number. That’s not a corrective action system. That’s a filing system for recurring problems.

This article covers what a corrective action request actually is, when to issue one, how the process works when it’s done right, and how to build a CAR system that stops repeat problems instead of documenting them. There’s a free CAR form at the bottom you can use today.

What Is a Corrective Action Request?

A corrective action request (CAR) is a formal document that identifies a nonconformance in a product, process, or service and requires the responsible party to investigate the root cause, correct the problem, and prevent it from recurring.

The key word is request, but don’t let it fool you. In most quality management systems, a CAR isn’t optional. It creates an obligation: acknowledge the problem, contain it, find out why it happened, fix the why, and prove the fix worked.

A CAR can be issued internally (one department to another), to a supplier (more on that below), or arrive from your customer, in which case your response speaks for your entire quality system.

Corrective Action vs. Preventive Action (CAPA)

You’ll see CAR inside a bigger acronym: CAPA, corrective and preventive action. The distinction matters.

Corrective action responds to a problem that already happened. The defect exists, the customer complained, the audit finding is written. You’re fixing the cause of a real event.

Preventive action addresses a problem that hasn’t happened yet. You spotted a trend, a near miss, a risk, and you’re acting before it becomes a nonconformance.

A mature quality system does both, and the bridge between them is the last step of every good corrective action: asking “where else could this same failure happen?” That question turns one corrective action into several preventive ones, and it’s the single most skipped step I see.

When Should a Corrective Action Request Be Issued?

Not every defect needs a CAR. Issuing one for every minor slip buries your team in paperwork and teaches everyone the process is theater. The common triggers that genuinely warrant one:

– A customer complaint or return tied to product quality
– An audit finding (internal, customer, or certification body) that identifies a systemic gap
– A recurring internal nonconformance is the same defect, short shipment, or documentation error showing up again after a routine fix
– A supplier-caused defect that reached your floor or your customer
– A significant one-time failure where the cost or safety impact demands a documented investigation

The pattern in that list: a CAR is for problems where the cause needs to be hunted down and killed, not just the symptom cleaned up. If a quick containment fully resolves it and it never recurs, the full process would have been overhead.

The Corrective Action Request Process

Six steps. The order matters, and so does not skipping the uncomfortable ones in the middle.

1. Identify and Document the Nonconformance

Describe what happened in specific, measurable terms. “Parts out of spec” is not a problem statement. “14 of 300 parts from lot 4471 measured below the 0.500 minimum wall thickness at final inspection” is. A vague problem statement guarantees a vague investigation.

2. Contain the Problem

Before any root cause work: stop the bleeding. Quarantine suspect product, check what already shipped, protect the customer. Containment is not the corrective action, and confusing the two is one of the most common failures. Sorting good parts from bad fixes today’s shipment. It fixes nothing about tomorrow’s.

3. Investigate the Root Cause

This is where most CARs go to die, because the surface-level answer is always available and always wrong. “Operator error” is where the investigation starts, not where it ends. Why did the error happen? Was the work instruction current? Was the fixture worn? Was the training real or a signature on a form?

For internal nonconformances, a 5 Whys analysis is usually the right size. For customer-facing or complex failures, the more rigorous 8D problem-solving process is worth the discipline — it forces a team, formal containment, and verified root cause before anyone writes a fix. In my teaching sessions, I frame failure points three ways: equipment, system, or human. Real root causes are overwhelmingly the first two. When your CAR file says “human error” more than occasionally, your system is blaming people for what the process made likely.

4. Plan the Corrective Action

The action has to attack the root cause you found, not the symptom you started with. If the root cause is a work instruction that doesn’t match how the job actually runs, the corrective action is fixing the instruction and the mismatch, not re-briefing the operator on a document everyone knows is wrong.

5. Implement

Assign an owner and a due date, and make them real. A corrective action without a name and a deadline is a suggestion.

6. Verify Effectiveness, Then Close

Closing the paperwork is not the finish line. The finish line is evidence the problem stopped recurring: follow-up inspection data, audit of the changed process, tracking the defect rate over the next 30, 60, 90 days. If the nonconformance comes back, the CAR wasn’t effective, and it reopens.

And there’s a harder version of this step that almost nobody runs. Confirming the fix was implemented is administration. Confirming it actually works means testing it, which sometimes means reintroducing the failure on purpose to see whether your new control catches it. I’ve written about that separately, including the time we did exactly that and nobody caught it: how do you know your corrective action actually worked. If you only read one thing after this article, read that one. It’s the step that separates a corrective action system from a correspondence system.

Building a Corrective Action Request System

A single well-run CAR is good. A CAR system is where the compounding value is, and it’s what auditors and sophisticated customers actually look for. The pieces:

A log, not a pile. Every CAR in one place with status, owner, due date, and root cause category. If you can’t answer “how many are open and how old is the oldest” in thirty seconds, you don’t have a system yet.

Ownership and escalation. Someone owns the log, chases the due dates, and escalates the stalled ones. Without this, CARs age quietly until an audit finds them.

Trend review. Quarterly at minimum, look across closed CARs by cause category. Three unrelated-looking CARs that all trace back to changeover handoffs are not three problems. They’re one problem with three symptoms, and it’s probably worth a proper improvement project through your continuous improvement cycle.

Feed the QMS. CAR trends should drive updates to your quality control processes and standard work, so the system learns instead of just responding.

Keep the tooling simple. A spreadsheet, a shared log, or any offline form your team will actually keep up beats a quality module nobody opens. There’s also a free option inside our Operations Workbench: the root cause analysis engine works as the front end of a CAR, so the investigation, the owners, and the history all live in one searchable place instead of scattered across files. I’m biased about which one I’d pick, but the honest answer is that any of these works. What matters is the habit underneath: prove the process manually before you automate any of it. The tool should support a habit you already have, not substitute for one you don’t.

Supplier Corrective Action Requests (SCARs)

When the nonconformance originates with a vendor, the same document becomes a supplier corrective action request. Two things make SCARs effective:

Send evidence, not accusations. Photos, measurements, lot numbers, receiving records. Make it easy for the supplier’s quality team to reproduce the problem and hard for them to deflect it.

Read the response like an auditor. If a supplier’s root cause is “operator error, operator retrained,” that’s your early warning about their quality system, not a closed issue. Push back once. How a supplier handles a SCAR tells you more about future performance than any scorecard metric.

Free Corrective Action Request Form

You can download the CAR form I use with clients here: Corrective Action Request Form (PDF). It covers the full loop: nonconformance description, containment, root cause, corrective action, effectiveness verification, and sign-off. Use it as-is or as the starting point for your own.

Why Corrective Action Requests Fail

The failure modes are consistent enough to list:

– Root cause stops at the first answer. “Operator error” and “training” appear in the file; the process that produced the error is untouched. The problem returns, because defects are one of the 8 wastes that never eliminate themselves.
– Containment gets recorded as correction. The bad parts were sorted, so the CAR closes. Nothing changed upstream.
– No effectiveness check. Closed on the promise of a fix, never on evidence the fix worked.
– Blame lands on people. If your corrective actions keep concluding a person failed, look harder. What looks like a people problem is almost always a system problem, and CARs that punish people teach your floor to hide defects, which is the most expensive outcome of all.
– Everything gets a CAR. The process becomes paperwork theater, and the team stops taking any of it seriously.

Final Thoughts

A corrective action request is one of the highest-leverage documents in your quality system, but only when it’s treated as a problem-solving process with paperwork attached, not paperwork with a problem attached.

Get the problem statement specific. Contain first, then dig. Refuse to close on a surface-level root cause. Verify the fix with evidence. Review the trends. Do that consistently and your CAR log stops being a record of what went wrong and becomes a roadmap of where your operation got stronger.

If quality escapes and repeat problems are eating your team’s time, the free Operations Diagnostic will show you in about ten minutes where the biggest leaks are and what to work on first.

That’s it for today.

See you all again next week!

Dave