What are the types of corrective actions?
Corrective actions are best sorted by how well they stop a repeat, because that is what decides whether the problem comes back. The stronger the action, the less it depends on people remembering.
| Strength | Type | What it does | Example |
|---|---|---|---|
| Strongest | Eliminate or design out | Removes the chance of the error | Change the part so it can only be fitted one way |
| Strong | Engineer or automate | Builds a control into the equipment or system | Torque tool that logs each tightening and blocks sign-off without it |
| Medium | Change the standard | Updates the procedure, checklist, layout or schedule | Add a tension check to the changeover standard |
| Weak | Train or remind | Relies on people remembering | Re-brief the shift, toolbox talk, new sign |
Containment, such as quarantining stock or stopping a task, is a correction rather than a corrective action. It protects people and customers today but leaves the cause in place. For safety, the same ranking appears as the hierarchy of control: aim as high as is reasonably practicable and record the level.
What is the corrective action process?
The process has six steps, and each one is a place where actions go wrong if it is skipped.
- Contain. Protect people and customers now, and check what else is at risk.
- Find the root cause. Use 5 whys, a fishbone or data, with the people who run the process, and confirm it with evidence.
- Choose the action. One or more actions per cause, as high up the strength table as you can manage.
- Assign an owner and a date. One named person per action and a real due date.
- Verify the result. Check the agreed measure after enough time or volume has passed, ideally by someone other than the owner.
- Standardise and share. Update the procedure or checklist and apply the fix to similar lines and sites.
The full definition, with the difference between correction, corrective action and preventive action, is on the corrective action glossary page. To record one problem end to end, use the corrective action plan template.
What are examples of corrective actions?
| Source | Problem | Weak action | Stronger corrective action |
|---|---|---|---|
| Audit finding | Gauges found out of calibration | Remind the team to check dates | Calibration due dates scheduled as tasks with an owner and escalation when overdue |
| Customer complaint | Wrong label on a delivered pack | Re-brief the packing line | Label scanned against the order before the carton can close |
| Safety incident | Forklift clips a walkway barrier at a blind corner | New "slow down" sign | Re-route the walkway, add a marked crossing and a convex mirror |
| Near miss | Guard left open during cleaning | Toolbox talk on guarding | Interlock that stops the machine when the guard is open |
| Repeat breakdown | Bearing fails every eight weeks | Replace the bearing again | Fix the misalignment and add the check to the maintenance standard |
| Supplier failure | Incoming resin out of specification twice | Reject the load | Supplier corrective action request with their root cause and verified fix |
| Environmental | Repeated small oil leaks to drain | Clean up each time | Bunding at the transfer point and a leak check on the shift checklist |
How do you write a corrective action?
Write each action as a specific change, with the owner and date, tied to the cause it addresses.
| Weak | Better |
|---|---|
| Operators to be more careful | Add a go/no-go gauge at station 4 so a short part cannot pass (maintenance supervisor, 20 Nov) |
| Retrain the night shift | Put the new setting on the changeover checklist and check it at the 6 am huddle (shift leader, 14 Nov) |
| Improve communication | Show open maintenance requests on the Tier 1 board each morning (team leader, 7 Nov) |
An action that matches no listed root cause is a guess. An action with "ASAP" for a date has no date.
How do you track corrective actions?
Keep one log for all sources, so a repeat cause is visible across audits, incidents and complaints. A working log needs these columns: number, source and date raised, problem, root cause, action, strength (design out, engineer, standard, train), owner, due date, status, verification date, result and date closed.
Review it where the work is reviewed. The Tier 1 huddle sees actions due that day, the Tier 2 meeting reviews overdue actions and those waiting for verification, and repeat causes go up to Tier 3 as improvement projects. Three numbers show whether the system works: actions overdue, actions closed without a verification check, and problems that return within 90 days.
Why do corrective actions fail?
- Actions are closed when the work is done, not when the result is verified.
- The root cause is a symptom, or a person.
- Training is the default action, so the process itself never changes.
- Standards are not updated, so the old way returns.
- Actions sit in a spreadsheet that nobody reviews.
- The lesson stays on one line, so the same cause produces the same problem next door.
Step by step
- Contain the problem. Protect people and customers now and check whether other lines, shifts or sites are at risk.
- Find the root cause. Use 5 whys, a fishbone diagram or data with the people who run the process, and confirm the cause with evidence.
- Choose the action. Pick one or more actions per cause, as high up the strength ranking as you reasonably can: design out, engineer, change the standard, then train.
- Assign an owner and a date. One named person per action and a real due date, with the measure that will show it worked.
- Verify the result. Check the measure after enough time or volume has passed, preferably by someone other than the owner.
- Standardise and share. Update the procedure or checklist and apply the fix to similar lines and sites before closing.
A worked example
A packaging plant logged corrective actions from audits, customer complaints and incidents in three different places, and most were closed by retraining. It moved them into one log reviewed on the tier boards and added a strength column. Over a quarter the team converted eleven training actions into changes to equipment or standards, put every overdue action on the Tuesday Tier 2 agenda, and reopened two actions whose verification checks failed. The wrong-label complaint, raised four times in the previous year, did not return.