Corrective action: fixing the cause rather than the symptom

A corrective action is a change made so that a problem which has already occurred does not occur again. That definition rules out most of what gets logged under the heading. Replacing the faulty part, refunding the customer, redoing the report — those are corrections. They deal with the instance in front of you and leave the mechanism that produced it entirely intact.

The distinction sounds pedantic until you look at a register where the same issue appears four times in a year, each with a corrective action recorded and closed. What was recorded was the repair, and the repair works exactly once.

Correction, corrective action, preventive action

• Correction: what you do about the affected item — scrap it, rework it, apologise, reissue. Necessary and immediate.
• Corrective action: what you change so the cause stops producing this outcome. Follows an investigation.
• Preventive action: what you change because a problem has not happened yet but plausibly could, usually spotted elsewhere or in a near miss.
• Together the last two are usually called CAPA, and in regulated industries the process is prescribed rather than optional.

Grading matters as much as the distinction. Not every issue deserves a full investigation, and treating all of them alike is how CAPA systems collapse under their own weight. A quick assessment of severity and recurrence decides whether something gets a correction and a note, or the full analysis. Where the action has to be presented to a customer or an auditor, it is written up as a capa report with its effectiveness check.

What a corrective action needs to be worth recording

1. Describe the problem in observable terms: what happened, when, how it was noticed, what it affected.
2. Contain it first — stop the immediate harm before analysing anything.
3. Investigate the cause properly, and be suspicious of the first answer that blames a person.
4. Decide the action, and check that it changes something structural: a step, a check, a system setting, a document.
5. Name one owner and a date. Actions owned by a department are owned by nobody.
6. Implement it, and record what actually changed rather than what was intended.
7. Verify effectiveness later — after enough time and volume for recurrence to have shown up.
8. Close it only after verification, and record the evidence used.

The verification step is the one that gets skipped

Almost every weak CAPA register has the same shape: actions defined, actions implemented, actions closed the same week. Effectiveness verification requires waiting — a month, a quarter, however long it takes for the situation to arise again — and checking whether it did. Without that step the register records intentions, and an auditor reading it learns only that somebody wrote something down.

Verification also catches the common failure where the action was implemented but did not work, or worked and created a new problem somewhere else. That is not rare and it is not embarrassing; discovering it a year later, from a customer, is.

Retraining is usually not a corrective action

When an investigation ends at somebody made a mistake, the action recorded is almost always retraining or a reminder. It is fast, it is cheap and it very rarely works, because the conditions that made the mistake likely — an ambiguous form, two similar part numbers, a step with no confirmation — are unchanged, and the next person will hit the same conditions.

The stronger question is what made the error easy. Answers that change something physical or procedural — a check that catches it, a field that cannot be filled wrongly, a step reordered — survive staff turnover. Training is a supplement to those, not a substitute.

Automotive and aerospace customers usually want the write-up in their own shape. An 8D report walks a team through containment, cause and verification in eight fixed steps, and it is frequently a contractual requirement after a complaint.

Keeping the register

Ettex Records suits this shape: one row per issue with the description, the correction, the cause, the action, the owner, the due date and the verification date, filterable to what is open, what is overdue and what is awaiting verification. That last filter is what makes the process real rather than aspirational — the pending-verification list is the one people otherwise forget.

It is a register rather than a quality system. There is no workflow with approval gates, no electronic signature, no audit trail meeting a regulated standard, no linkage from an action to a controlled document revision, and no effectiveness reminders that fire by themselves. Where a regulator prescribes how CAPA must be managed — pharmaceutical, medical devices, aerospace — that specification governs, and dedicated validated software is usually the right answer rather than a general register.

Separate the repair from the fix, distrust investigations that end at human error, give every action one owner and a date — and never close one before verifying it worked. The investigation behind it is a root cause analysis, and stopping at the first plausible answer is what produces retraining as the only action.