/Everyday professional

Corrective Action Report Format

Root cause, correction, and how you know it worked.

Details

corrective action report format
Fills every box with an example you can type over.
Adding a logo, a photo or your signature?

Red highlights mark what is still blank. Click anything on the page to change it. Your draft is kept on this device as you work.

Tap the page to change any words.
[organisation name]
[organisation address]
Date: October 14, 2026
To, [organisation] [address]
Subject: Corrective action report [reference]

Dear Sir / Madam,

Problem: [what went wrong]. Immediate containment: [what stopped the bleeding].

Root cause: [why it happened — the cause, not the symptom]. Corrective action: [what changes so it cannot recur], to be completed by [date].

Verification: [how you will know it worked]. The report stays open until the verification evidence exists, not until the action is marked done.

Yours faithfully, For [organisation name] Authorised Signatory [place]
If the root cause is "human error", keep going. That is a symptom — the cause is whatever made the error easy to make and hard to catch.

What is a Corrective Action Report?

A corrective action report records what went wrong, why it went wrong at root, what was done to fix it, and how you know the fix worked. It matters because correction and corrective action are different things. Replacing the rejected batch solves today; finding out why the wrong material was issued is what stops the same batch being rejected next quarter.

Quality teams raise them after an internal or external audit finding, a customer complaint, a failed inspection or a repeated defect. Operations teams use the same structure after a process failure, a service outage or a near miss. Suppliers are asked to complete one when they cause a problem, and the quality of the answer tells you a great deal about them. The owner should be someone with authority over the process that failed, not the person who found the problem, because the finder rarely has the standing to change how the work is done.

The framework you report under sets the expectations. ISO management system standards require action to eliminate the cause of a nonconformity and a check of effectiveness — read the current clause rather than the version you were trained on, since the wording has changed over editions. Automotive suppliers commonly use the eight-discipline format with its containment and prevention steps. Regulated manufacturers work within a formal CAPA system that regulators inspect: the FDA in the US, national authorities in the EU and UK, CDSCO in India, the TGA in Australia. Confirm which applies before choosing a template.

A corrective action report is not a disciplinary record. The moment it becomes one, people stop reporting problems and you lose the data the system runs on. Write it about the process, not the person. It is also not a containment plan — containment protects the customer while you investigate, and it belongs in the report but is not the corrective action. And closing the report is not the same as fixing the problem: closure without a verified effectiveness check is how the same finding reappears at the next audit with the previous report attached.

What to put in a Corrective Action Report

These are the details this template asks for. Anything left blank is marked in red on the preview so you can see what is still missing.

FieldWhat goes in it
Issuing organisationFor example: Maple Grove Homeowners Association
Organisation addressFor example: 1420 Kinnear Road, Columbus, OH 43212
NCR referenceFor example: NCR-2026-0041
The problemFor example: Fourteen panels from batch 4471 delaminated and reached the customer.
Immediate containmentFor example: Remaining batch quarantined, customer notified, replacements despatched next day.
Root causeFor example: Goods-in checks sample one panel per pallet. Delamination affects the lower layers, which…
Corrective actionFor example: Change the sampling rule to include one panel from the bottom third of every pallet, and…
How you will verify itFor example: Audit twenty goods-in checks after four weeks and confirm the bottom-third sample was…
Due byFree text
Signatory name optionalFor example: K. Srinivasa Rao
Signatory designation optionalFor example: Honorary Secretary
Issued to (full name)For example: James Whitfield
Their addressFor example: 588 Kinnear Road, Columbus, OH 43212

How to write a Corrective Action Report

  1. State the problem in measurable terms

    Write what was observed, where, when, how many and against what requirement. Four of twenty units from batch 2214 failed the leak test on 3 March against spec QS-11. Avoid conclusions in the problem statement — poor operator attention is a theory, not an observation, and putting it here ends the investigation before it starts.

  2. Record immediate containment and who was told

    Say what you did to stop the problem reaching anyone else: batch quarantined, remaining stock held, customer notified, affected shipments recalled. Give the date and the person who authorised it. Containment is judged separately from the root cause, and an investigation that took three weeks is defensible only if containment happened on day one.

  3. Find the root cause, not the first cause

    Keep asking why until you reach something you can change: the seal failed because the tool was worn, the tool was worn because the change interval was based on a machine that has since been replaced. Use whatever method suits — five whys, a cause and effect diagram — and record the evidence, not just the conclusion.

  4. Separate correction from corrective action

    Correction fixes this instance: rework the batch, credit the customer. Corrective action changes the system so it does not recur: revise the tool change interval, add the check to the shift start sheet, retrain and reassess. Write both, with an owner and a due date each. An action with no name against it will not happen.

  5. Verify effectiveness before closing

    Set the evidence in advance: no leak test failures across the next ten batches, the revised check present and completed on four weeks of shift sheets, the audit finding closed by the auditor. Give a verification date, do the check, record the result, then close. If the evidence is not there, the report stays open and the action is revised.

Common mistakes

  • Stopping the investigation at operator error, which names a person instead of a cause and leaves the conditions that made the error likely untouched.
  • Recording the correction as the corrective action, so the batch is reworked, nothing in the process changes, and the same defect returns next month.
  • Closing the report on the day the action is implemented, with no effectiveness check, which is the finding most auditors raise at the following visit.
  • Leaving actions without a named owner and a date, so they sit unstarted until the report is reviewed and everyone assumes someone else had it.
  • Writing the report as a disciplinary record, which teaches staff to stop reporting problems and starves the system of the data it depends on.

Frequently asked questions

What is the difference between correction and corrective action?

Correction deals with the specific problem in front of you — scrap the part, refund the customer, restart the service. Corrective action removes the cause so it does not happen again — change the setting, revise the procedure, alter the check. Auditors look for both, and a report containing only correction is one of the most common findings raised.

What is a CAPA?

CAPA stands for corrective and preventive action, the combined system used in regulated manufacturing and healthcare. Corrective action addresses causes of problems that have occurred; preventive action addresses causes of problems that have not yet occurred but could. In regulated settings the whole system — how issues are raised, investigated, actioned and closed — is itself subject to inspection.

How do I find the root cause?

Start from what you observed and keep asking why until you reach something within your control to change. Five whys works for simple chains; a cause and effect diagram helps where several factors combine. Test the answer: if you fix this, would the problem still be possible? If yes, you have not gone far enough. Record the evidence, not just the conclusion.

How long should a corrective action take?

Containment should be immediate. Investigation and implementation depend on the cause — days for a procedure change, longer for a tooling or design change. Many organisations set a target of thirty days to a documented plan, then track actions to their own dates. If your customer or standard sets a response time, that governs; agree an extension in writing rather than missing it silently.

Who should sign off a corrective action report?

The process owner accountable for the change, plus whoever verified effectiveness — usually quality, and for a customer complaint sometimes the customer. Signing should mean the evidence was seen, not that the paperwork arrived. Record names, roles and dates. If your quality system defines the approval route, follow it, since auditors check that the documented route was the one actually used.

This page explains general practice and is not legal advice. Requirements differ between countries and, in some cases, between states — check what applies where the document will be used.

All templates · Operations templates