CAPA: how to follow up corrective and preventive actions effectively

What is CAPA?

CAPA is a fixed way of following up deviations. Something went wrong or is about to go wrong, for example an incident, a complaint, an audit finding or a failed inspection. CAPA makes sure the cause is dealt with, not just the visible result.

You will meet the term in quality, safety and environmental management systems. Standards such as ISO 9001, ISO 14001 and ISO 45001 all ask you to control deviations and to improve based on the cause. CAPA is a practical way to do that.

Correction, corrective and preventive

Three terms are often mixed up. A correction fixes the immediate result. A corrective action removes the cause of a deviation that has already occurred. A preventive action removes the cause of a deviation that has not happened yet but could.

An example: an employee slips on a wet floor. The correction is drying the floor. The corrective action is repairing the leak that made it wet. The preventive action is checking all similar locations for the same leak.

Root cause analysis: from symptom to cause

The quality of a CAPA stands or falls with the root cause analysis. Stopping at the first explanation, such as "the employee was not paying attention", rarely leads to an action that works. Keep asking until you reach something you can change in the system, the way of working or the environment.

A simple and useful method is the 5 Whys: at every answer you ask again why that was the case. For more complex matters you can use a cause tree or fishbone diagram. Involve the people who do the work, because they know the practice.

A practical example: several complaints come in about wrongly delivered orders. The correction is exchanging the order. The 5 Whys shows that labels are retyped by hand and nobody checks them. The corrective action is printing labels straight from the order file. After three months you check whether this type of complaint has disappeared.

Writing a good action

An action must be feasible and verifiable. "More attention to safety" is not an action, "fit the scaffold with a second guard before 1 November" is. Also consider the hierarchy of controls: eliminate or substitute the hazard first, then engineering controls, and use instruction or personal protective equipment only as a last step.

Record for each action who owns it, what exactly needs to happen and when it must be done. An action without an owner or deadline gets left behind.

• A concrete description of what changes
• An owner with the authority to carry it out
• A realistic deadline
• A description of how you will confirm that it works

Verification and effectiveness

Closing an action is not the same as solving the problem. Verification checks that the action was carried out as intended. The effectiveness check looks later at whether the problem really no longer occurs. Plan that check in advance, for example after three or six months, and decide which measurable data you will look at: the number of reports, the outcome of an inspection or the result of an audit.

If the action turns out not to work, that is valuable information. You reopen the analysis and look for the real cause. That is how CAPA works as a learning cycle.

Common pitfalls

Most CAPA processes do not fail for lack of intent, but because of sloppy follow-up. If you recognise any of the following, it pays to tighten your approach.

• Stopping at a symptom instead of the root cause
• Blaming an individual instead of the system
• Actions without an owner or deadline
• Closing without checking that it works
• Turning every minor deviation into a CAPA so the real ones drown
• Tracking actions scattered across email, spreadsheets and minutes

How to put it into practice

Start with a simple step plan that anyone can follow and that you can apply to every deviation. Keep it light enough to be used on busy days too.

Discuss open CAPAs in a fixed meeting, for example monthly. That keeps owners sharp and shows which actions are stuck and why.

• Record the deviation with facts, date and place
• Take an immediate correction to prevent worse
• Decide based on your criteria whether a CAPA is needed
• Investigate the root cause together with those involved
• Choose actions and assign an owner and deadline to each
• Check the action was carried out and plan the effectiveness check
• Close only when the effect has been shown

Following up CAPA with BrydgeOne

In BrydgeOne, all actions from incidents, inspections, quality and environmental reports, audits, risk assessments and management review come together in the Actions module. Every action has an owner and deadline, and closing one always requires an explanation, with photos or documents as evidence. Signals that do not have an action yet can be turned into one with a single click.

The root cause analysis with 5 Whys, the measures and the effectiveness check are recorded in the source module, for example the incident. The action record shows that information next to the follow-up task. With recurrence and sub-measures you keep repeating checks in view.

Every action can be traced back to the report it came from. That makes it easier to show in an audit or management review that deviations were not only fixed, but also learned from.