What is corrective action?

    Short answer

    Corrective action is the action taken to eliminate the root cause of a problem that has already happened, such as a defect, nonconformity, incident or audit finding, so that it does not happen again. Corrective actions differ from a correction, which only fixes the immediate instance, and from preventive actions, which remove a potential cause before anything goes wrong.

    Last updated · TeamAssurance

    Key facts

    • Definition: ISO 9000 defines corrective action as action to eliminate the cause of a nonconformity and to prevent recurrence.
    • Triggered by: customer complaints, internal defects, audit findings, incidents and near misses, repeat breakdowns and supplier problems.
    • Required by: ISO 9001, ISO 14001 and ISO 45001 (all clause 10.2), IATF 16949 in automotive and ISO 13485 in medical devices.
    • Outputs: a confirmed root cause, an action with an owner and due date, updated standards and evidence that the problem has stopped.
    • Part of: CAPA, corrective and preventive action, the system that manages both kinds of action through to verified closure.

    What does corrective action mean?

    Corrective action means fixing the cause of a problem, not only the problem itself. The ISO 9000:2015 definition of corrective action is "action to eliminate the cause of a nonconformity and to prevent recurrence". In plain words, a corrective action changes something about the process, equipment, standard or system so that a problem that has already happened cannot happen again for the same reason.

    Three parts of the definition matter in practice:

    • It acts on the cause, not the symptom. Reworking a faulty batch or repairing a damaged barrier is a correction. The corrective action is what stops the next batch or the next collision.
    • It follows a real problem. A nonconformity, defect, incident, complaint or audit finding has already occurred. Acting on a problem that has not happened yet is preventive action.
    • It must prevent recurrence. An action only counts as corrective once there is evidence the problem has stopped.

    In the plural, corrective actions are the individual actions raised to fix one problem, each with its own owner and due date. A single audit finding can need several, for example a changed setting, an updated standard and a new check. The types of corrective actions, ranked from strongest to weakest, and how a corrective action request (CAR) tracks them are set out on the corrective actions page.

    What is the difference between correction, corrective action and preventive action?

    A correction deals with the instance, a corrective action removes the cause of a problem that has happened, and a preventive action removes a potential cause before any failure.

    Correction fixes the symptom, corrective action removes the root cause, preventive action stops a potential cause before it fails.

    CorrectionCorrective actionPreventive action
    Acts onThe symptomThe root causeA potential cause
    WhenImmediatelyAfter the cause is confirmedBefore any failure
    ExampleSort and rework the faulty batchFix the drifting setting and update the standardApply the fix to sister lines that have not failed yet

    Most operations are good at corrections and weak at the other two, which is why the same problems keep coming back.

    What are the steps in the corrective action process?

    The corrective action process runs from a factual problem description to verified closure, in seven steps:

    1. Describe the problem with facts: what, where, when and how much, with a number in it. "Line 3 rejected 4.2% of cases for skewed labels on Tuesday night shift" is a problem statement; "labelling issues" is not.
    2. Contain it. Protect the customer and people now: quarantine suspect stock, stop the task, add a temporary check. Containment is a correction, not the corrective action.
    3. Find the root cause with root cause analysis: 5 whys, a fishbone diagram or an A3. Confirm each cause with evidence and go past the first plausible explanation.
    4. Define the corrective action that removes the cause, with one owner, a due date and the measure that will show it worked. Where the fix crosses departments, a RACI chart settles who does the work and who signs it off. Prefer actions that design the error out, such as poka-yoke, over reminders and retraining.
    5. Implement it, including the updated standard, work instruction or checklist, and train the people affected.
    6. Verify effectiveness after enough time or volume has passed: the measure back at target, the defect absent, the audit passing. Ideally someone other than the owner checks.
    7. Close and share the lesson with similar lines, sites and suppliers, so the same cause is removed everywhere (yokoten).

    Automotive and aerospace suppliers often run the same logic as an 8D report, which adds team formation and recognition as explicit steps.

    What are examples of corrective actions?

    Good examples of corrective actions name the problem, the correction, the confirmed root cause and the change that stopped it coming back:

    • Manufacturing defect: a labeller jams weekly. Correction: clear the jam. Root cause: label roll tension drifts after changeover. Corrective action: a marked tension setting and a tension check added to the changeover standard; jams stopped over the next six weeks.
    • Skipped quality check: operators miss a torque check. Correction: re-brief the shift. Corrective action: the torque tool now logs each tightening and the step cannot be signed off without the record.
    • Safety incident: a forklift clips a pedestrian walkway barrier at a Melbourne distribution centre. Correction: repair the barrier. Root cause: the racking layout forces forklifts to cross the walkway at a blind corner. Corrective action: re-route the walkway and add a marked crossing and a convex mirror, chosen using the hierarchy of controls.
    • Audit finding: an internal audit finds expired calibration on three gauges. Correction: calibrate them. Root cause: calibration dates lived in a spreadsheet nobody reviewed. Corrective action: calibration due dates scheduled as tasks with an owner and escalation when overdue.
    • Supplier problem: incoming resin is out of specification twice in a quarter. The supplier receives a supplier corrective action request (SCAR) and must show their root cause and verified fix.

    What should a corrective action plan include?

    A corrective action plan records the problem, containment, root cause, actions, owners, due dates and the verification evidence in one place. The corrective action plan template has these fields ready to fill in; a non-conformance report usually comes first and raises the need for action. At minimum the plan should show:

    • The problem statement and where it was found.
    • Containment taken and when.
    • The root cause and the evidence that confirms it.
    • Each action, its owner and its due date.
    • How effectiveness will be checked, by whom and when.
    • The standards, risk assessments and training records that were updated.

    What does ISO 9001 require for corrective action?

    ISO 9001 clause 10.2 requires an organisation, when a nonconformity occurs, to react to it and contain it, evaluate whether action is needed to eliminate the cause, implement the action, review its effectiveness, update risks and opportunities, and change the management system where needed. Documented information must be kept on the nonconformity, the actions taken and the results. ISO 45001 adds that corrective actions for safety follow the hierarchy of controls and management of change, with workers involved in the investigation.

    Why do corrective actions fail?

    • They are closed when the action is done rather than when the result is verified.
    • The "root cause" is a symptom, or a person ("operator error").
    • Retraining is the default action, so nothing about the process changes.
    • The standard is not updated, so the old way returns.
    • Actions have no single owner or due date and drift.
    • Lessons are not shared, so the same cause produces the same problem on the next line.

    Sources and further reading

    How TeamAssurance helps

    In TeamAssurance, a defect, hazard or audit finding becomes a tracked action with an owner and due date; repeating issues are visible as a pattern and move into structured root cause work in the continuous improvement capability; the corrective action carries a verification step against the measure before closure; and the changed standard is scheduled as a checklist and trained through the skills matrix.

    Frequently asked questions

    What is the difference between corrective action and CAPA?

    CAPA, corrective and preventive action, is the system that manages both kinds of action from identification to verified closure. Corrective action is the half that responds to problems that have already occurred.

    How do you verify a corrective action worked?

    Define in advance what evidence will show it: the measure back at target, the audit passing, the defect absent over a set period. Check that evidence after the action, by someone other than the person who implemented it, and only then close.

    What is a corrective action request?

    A corrective action request (CAR) is a formal request, often to a supplier or another department, to investigate a problem and implement a corrective action, with a response due by a set date. Supplier corrective action requests (SCARs) are common in quality systems.

    Is retraining a corrective action?

    Only when the root cause really is missing knowledge, and even then the standard or training material should change too. If people were already trained and the error still happened, retraining is a correction; the corrective action is to change the process so the error is hard to make.

    What are the types of corrective actions?

    Corrective actions are usually ranked by how well they stop a repeat: eliminating or designing out the cause is strongest, then engineering or automating a control, then changing the standard or procedure, and weakest is training or reminding people. Aim as high as is reasonably practicable.

    How long should a corrective action take?

    Many quality systems expect containment within 24 hours, a confirmed root cause and action plan within about 30 days, and verification once enough time or volume has passed to prove the fix. Customer and supplier agreements often set their own deadlines.