Why quality issues keep coming back — and how to stop them for good

Recurring quality issues can feel like ghosts. You close a corrective and preventive action (CAPA), but then a few months later, the issue returns.

While closing a CAPA proves the team completed a response, it doesn’t necessarily prove that the root cause was identified, the corrective action was implemented consistently, or that the change worked over time.

And to really prevent quality issues from coming back, all three of those things need to happen.

“Closed” and “fixed” answer different questions

When you close a record, it tells you that the required steps were completed. An effective corrective action tells you that the condition that caused the problem has been removed or at least controlled.

But those things don’t always have the same outcome.

That’s because recurring issues generally trace back to one of three breakdowns:

• The investigation stopped at the immediate failure point rather than reaching the underlying cause
• The root cause was identified, but findings or updated requirements were lost during manual handoffs
• The corrective action was documented, but the new process was not followed, nor was its effectiveness ever confirmed.

A stronger CAPA process needs to address each of these points. The goal is not only to respond to the event, but to make the next occurrence less likely.

Root-cause investigations need room for honest answers

Teams can use fishbone diagrams, 5 Whys, and other investigation methods correctly but still reach the wrong conclusion.

These tools are only as useful as the information people are able and willing to provide.

In a blame-first environment, employees may focus on protecting themselves or their colleagues. Investigations can then stop at an individual mistake:

• The operator selected the wrong setting.
• The employee missed a step.
• The reviewer approved the wrong version.
• The technician entered the wrong value.

Those observations may describe what happened, but they do not always explain why the process allowed it.

A more useful investigation asks:

• Was the correct procedure easy to find and follow?
• Were responsibilities clear?
• Did the system prevent or detect the error?
• Was the employee working with complete and current information?
• Have similar conditions appeared elsewhere?
• What needs to change to make recurrence less likely?

This does not mean removing accountability. Deliberate violations of safety or quality requirements still require an appropriate response.

But it does mean distinguishing misconduct from ordinary human error, unclear processes, and weak controls. The purpose of a root-cause investigation is to improve the system, not to find the fastest person to blame. Asking the right questions about processes and controls can help shift the blame away from people and make them more willing to answer questions.

A finding only helps if the organization can reuse it

Suppose the team identifies the correct root cause. The next question is whether that finding becomes part of the organization’s shared quality knowledge.

This is where manual processes often break down.

For example:

• An employee is pulled into another issue before updating the final record.
• Revised documentation remains in an email inbox.
• A file is saved in the wrong shared folder.
• Someone updates an obsolete version of a procedure.
• Investigation notes remain on a laptop or a sheet of paper.
• Another site experiences the same issue but cannot find the earlier CAPA.

Each is a predictable risk when the process depends on people remembering a series of disconnected steps. The problem becomes more serious when teams cannot search across deviations, complaints, and CAPAs to see whether an issue has happened before.

The cost of quality issues isn’t limited to the additional investigation. Recurring issues can contribute to rework, lost output, additional labor, excess inventory, warranty exposure, customer complaints, and recalls.

As much as finding the root cause matters, making that knowledge available for the next decision matters just as much.

Make the correct process easier to follow

Manual processes become harder to follow as an organization adds sites, products, systems, and employees.

Every manual handoff creates another opportunity for information to be delayed, copied incorrectly, or stored where the next person cannot find it. And when people retire, that knowledge goes with them.

A modern quality management system can reduce that dependence on memory by helping teams:

• Route investigations, reviews, and approvals through a defined workflow
• Maintain current document versions and change histories
• Apply common fields, definitions, and classifications
• Connect deviations, complaints, audits, and CAPAs
• Search for similar events across sites
• Record effectiveness checks and follow-up work
• Report on recurring issues from a shared source

A QMS will not determine the correct root cause for the team, but it can help surface similar past issues using AI. It also can’t guarantee that employees will follow a weak or impractical process.

What it can do is make the approved process easier to follow, make missing steps more visible, and give teams a better chance of recognizing a recurring pattern before it becomes another major event.

What quality leaders can do now

Organizations do not need to complete a full technology implementation before improving how they manage recurring issues. They can start with a few practical steps.

• Define what effective closure means. Do not treat approval of the CAPA as the final proof that the action worked. Establish when and how effectiveness will be reviewed.
• Standardize important terms. Use consistent definitions and tags for root causes, defects, products, suppliers, and sites so similar events can be found and compared.
• Create a searchable source of quality history. Give teams one governed place to find deviations, complaints, CAPAs, and supporting evidence.
• Review manual handoffs. Identify where employees must copy, email, reconcile or re-enter information and determine which steps are most likely to fail.
• Look for recurrence across the organization. Review events by root cause and contributing condition, not only by document number or local site.
• Confirm that process changes reached daily work. Updated documentation has little value if employees cannot find it, understand it or apply it.

The takeaway

The objective of solving quality issues is not merely to close the record faster. It’s to give the problem fewer places to hide.

A QMS makes it easier to manage best practices at scale, but whether you use one or not, the discipline to follow them still matters.

When an organization can trace what happened, preserve what it learned and confirm that the corrective action changed the process, recurring quality issues can finally be resolved and stop feeling like ghosts.

Speaking of putting recurring quality issues to bed, we’ve created a short guide to help you turn root cause analysis findings into executive decisions. Get your copy here.

David Isaacson is an executive director of portfolio marketing at Octave.

This content is sponsored by Octave. The views and opinions expressed are those of the sponsor and do not necessarily reflect those of the Regulatory Affairs Professionals Society.