What is CAPA? Corrective and preventive action in production

What CAPA means in practice

At ten o'clock the fill weight check on line 2 shows that batch 88213 is filling light. The operator adjusts the filler and the light bottles are set aside. That is a correction: the immediate problem is solved. But if nobody finds out why the filler drifted, the same deviation will be back in the log next month.

CAPA is the step after that. You investigate the cause, take an action that removes it and check later that the problem has really gone. ISO 9001 calls this corrective action, and in GMP environments and under food safety standards such as BRCGS and IFS an auditor expects to see a working CAPA process.

A CAPA usually goes through these steps:

• Report: record the deviation with what, where, when and which batch
• Contain: act at once, such as blocking product or adjusting the machine
• Investigate: find the root cause, not just the symptom
• Choose an action: one with an owner and a deadline
• Carry it out: do the action and record that it was done
• Verify: after an agreed period, check that the deviation stays away
• Close: close the CAPA with evidence, so the record is complete

Correction, corrective and preventive: the difference

A correction repairs the effect: rejecting the light bottles, resetting the filler. It has to happen straight away, but it prevents nothing.

A corrective action tackles the cause of a deviation that has already happened. If the filler drifted because a wear part was never replaced, that part goes into the maintenance schedule.

A preventive action tackles a problem that has not happened yet. If line 3 has the same filler, you add the wear part to its schedule too, before it goes wrong. Since the 2015 version, ISO 9001 no longer has a separate requirement for preventive action; it now falls under risk based thinking. In practice and in GMP the term CAPA is still in everyday use.

Why a CAPA log in Excel breaks down

Many companies track deviations and actions in an Excel file, with email alongside. It works for the first entry and then stalls:

• The report is separate from the batch, order and machine, so the investigation starts with searching
• Actions have no clear owner or deadline and are left lying
• Nobody gets a reminder when an action is overdue
• The effectiveness check is forgotten, so a CAPA is closed without knowing whether it works
• After the first few rows, nobody keeps the file up to date
• During an audit or complaint it takes hours to find the history of a single problem

How to set up CAPA without separate lists

It starts with one place where every deviation is reported, straight from the work. A check outside the limit, a stop or an operator's remark should become a report in a few taps, with the context already attached.

For each CAPA, record at least this:

Keep the investigation light. For most deviations a short root cause analysis is enough; save heavy methods such as an 8D report for repeated or serious problems. A process people actually follow is worth more than a thorough form that stays empty.

• What went wrong, with a photo and the measured value
• Batch, order, line or machine and the time
• The immediate correction and who carried it out
• The cause, with the reasoning that led to it
• The action, with owner, deadline and task list
• When and how effectiveness will be checked

An example: from deviation to closed CAPA

Batch 88213 is filling light. Using five whys, the quality officer gets to the cause:

The corrective action is therefore to put the seal in the maintenance schedule for line 2, owned by the maintenance team. The preventive action is to do the same for the other lines with the same pump.

After ten batches, quality checks whether fill weights stay within the limit. If they do, the CAPA is closed with the checks as evidence. If the deviation comes back, it was not the right cause and the investigation continues.

• Why light? The dosing pump delivered too little.
• Why? The pump seal was leaking.
• Why? The seal was worn.
• Why? It had never been replaced.
• Why? It was not in the maintenance schedule.

Where Frontlink fits

In Frontlink you record a deviation from what happens on the floor: a check outside the limit, a stop or an operator's report. The deviation carries the batch, order, machine and time, with a photo, cause and action, and an owner, deadline and task list. It stays visible until it is resolved, and after a set number of days or batches Frontlink prompts for the effectiveness check.

A Frontlink engineer builds it at your site, on your own data and ERP. You start with one process, which is usually running within a few weeks.