CAPA on the Manufacturing Floor: From Detection to Verified Fix

Corrective and preventive action (CAPA) is the process manufacturing teams use to investigate a quality problem, remove its cause, and confirm that it doesn't return. It starts with a nonconformance, which is any product or process that doesn't meet a defined requirement. It ends only when evidence shows the fix worked.

Why Does CAPA Go Beyond Fixing the Defect?

A repair gets the line running again, but a problem that comes back creates more scrap, rework, and downtime. CAPA adds the steps that keep it from returning, including root-cause investigation, process changes, and verification.

To illustrate the process, this article follows one nonconformance on a packaging line from the operator's first failed check to a verified fix. Along the way, you'll see who owns each stage, what evidence each stage needs, which metrics show whether your process works, and how Redzone's Connected Workforce System follows the CAPA process.

{{callout1}}

What Happens When an Operator Finds a Quality Problem?

When an operator finds a quality problem, the first job is to record it while the evidence is still on the line. A thorough nonconformance record gives everyone who follows the same information. For background on the system behind that record, read Redzone's guide to what QMS software is.

Suppose your plant packages snack foods, and you run the bag filler on production Line 3 during second shift. At a scheduled line-side check, three bags in a row weigh less than the minimum on the specification. You log the event in Redzone Compliance using a mobile device at the line, noting the product, production order, line, shift, filler, specification, measured weights, and a photo of the scale reading. A configurable trigger escalates the failed check to the line leader and quality assurance (QA) right away, so they can decide what happens to the bags already made.

How Should Your Team Contain and Escalate the Issue?

Containment means holding the affected product so that it can't reach the next process or a customer. It comes before investigation because other underweight bags may be moving toward packing and shipping.

Your line leader sets a boundary based on the last acceptable check — which was two hours ago — and every bag produced after that goes on hold until QA decides whether it can ship. Before regular production resumes, an authorized person has to approve the line's condition.

Redzone Compliance lets you log, assign, and track each nonconformance from detection to resolution, so open items stay visible to the whole team. With the bags on hold, the team has to decide which other responses the problem needs.

What's the Difference Between Containment, Correction, Corrective Action, and Preventive Action?

These four terms describe different responses to the same problem. When a team treats a correction as the corrective action, the record can close while the cause is still in place.

Containment Controls the Product

In the underweight-bag example, the hold covers every bag made after the last acceptable check. Containment ends when QA decides what happens to the held product, but it never explains why the problem happened.

Correction Fixes the Condition

Correction fixes the immediate problem or the affected product. For example, a maintenance technician recalibrates the filler to run within specification, and the team reworks or scraps the underweight bags.

Corrective Action Removes the Cause

Corrective action changes the process that allowed the filler problem. But your team can't choose that change until it knows why the filler drifted. That requires root cause analysis, as explained in the next section.

Preventive Action Protects Other Lines

Preventive action mitigates the same risk before it causes a failure somewhere else. In this example, the question is whether the two other fillers of the same model could fail the same way. 

Both corrective and preventive actions depend on one answer the investigation still has to find.

{{callout2}}

How Do You Find the Root Cause?

Teams find the root cause by testing each possible explanation against production data, direct observation, and the knowledge of the people who run the line. Finding the systemic cause is often the hardest part of CAPA. A drifted filler explains the underweight bags, but it doesn't explain why the drift went unnoticed for two hours.

The investigation team includes the operator who found the problem, maintenance, and quality. The operator knows what changed on the line that shift, and maintenance knows the filler's service history. ChampionAI, the AI built into Redzone, adds recommendations and can start approved workflows based on your plant's historical data, while decisions are left to experienced employees.

Your team can use 5 Whys root-cause analysis to test each cause-and-effect link. Redzone Compliance guides that work with structured CAPA, 5 Whys, and fishbone diagram workflows. Despite its name, the 5 Whys method may take fewer or more than five questions, and complex problems may need maintenance records, data analysis, or a controlled trial.

Your team finds that the filler drifted after a product changeover earlier in the shift. The changeover standard work had no weight check, and the next scheduled check came two hours later. That finding tells the team what process to change.

How Do Corrective Action and Updated Standard Work Prevent Recurrence?

Corrective action prevents recurrence by changing the process that allowed the problem. Updated standard work then makes that change part of every shift.

To fix the gap, the process owner adds a check-weigh to the changeover standard work. The operator now confirms bag weight before production restarts. The team also shortens the check interval after each changeover, because that's when this drift occurred.

A new step only works if everyone who runs the filler knows about and follows it. When standard work changes, training must reach operators on every shift and there must be a record of who completed the training. Redzone Learning, the platform's training module, delivers training and tracks completion.

The root cause also answers the preventive action question. Plant leadership adds the same changeover check to the two other fillers to prevent the same failure on another line.

These actions can be finished in a day. Knowing whether they worked takes longer.

How Do You Verify That the Fix Worked?

You verify a corrective action by setting success criteria before the change and checking production results against them afterward. A completed task shows that someone did the work, but results show that the cause is under control.

In this example, the team requires three full production runs within specification, zero related holds, and no underweight bags across the next two scheduled changeovers. The criteria include changeovers because that's where the failure started.

Verification should test the root-cause conclusion, not only the defect rate. Supervisors should confirm that operators ran the new check-weigh at each changeover and that the training records are complete.

The person who completed the action shouldn't be the one who verifies it; QA should examine the results before closing the CAPA. Redzone Compliance time-stamps every step and ties it to the location, product, and shift, so every reviewer sees the full record.

When Can You Close a CAPA?

You can close a CAPA when every required action is complete, the verification evidence meets the success criteria, and an authorized reviewer has approved the record. If your plant is certified to ISO 9001:2015, clause 10.2, covers the same steps, from reacting to the nonconformity to reviewing whether the action was effective.

The table below summarizes who owns each stage of the underweight-bag example and what evidence moves it forward.

One closed CAPA tells you about one problem. To see whether your whole process is working, track the following metrics.

Which Metrics Show Whether Your CAPA Process Works?

Five metrics show whether your plant finds problems quickly and whether defect reduction lasts. QA should review them regularly.

How Do You Calculate First-Pass Yield?

First-pass yield is the percentage of units that meet requirements without rework, repair, or retesting. To calculate it, divide the conforming units produced on the first attempt by all units entering the process. 

If 9,600 of 10,000 bags pass without rework, the result is 0.96, so your first-pass yield is 96%.

How Should You Read These Metrics Together?

Don't judge any one metric alone, because a fast closure time looks good until the recurrence rate shows the same problem coming back. These metrics are easier to track when every check, hold, action, and approval are recorded in one connected workforce system.

Why Redzone for Quality Management on the Factory Floor?

Redzone is the #1 connected workforce solution for manufacturers, trusted by more than 2,000 factories with 600,000+ users across 39 countries. Its Productivity, Compliance, Reliability, Learning, and Scheduling modules share real-time data, so a quality issue like the underweight bags stays connected from the first check to closure.

Redzone coaches work with your team during rollout to help build the new workflow into daily huddles. Multilingual support allows your full workforce to take part, and Redzone integrates with your ERP and MES instead of replacing them.