Wrong Cause, Same Problem

September 2026 · 4 min read · By ASOW Suite GRC

You closed the CAPA. Three months later, the same problem is back. The record says solved. Reality says otherwise.

A closed corrective action is not a solved problem. When a nonconformity returns, it's telling you something plainly: the root cause was never correctly found, never actually removed, or the effectiveness check was too weak to notice it survived. Recurrence isn't bad luck — it's a signal to look deeper.

What recurrence really means

The same issue coming back usually points to one of five failures in how it was handled:

• The problem was defined wrong — you solved a narrower, more convenient version of it.
• A symptom was mistaken for a cause — the fix hit what was visible, not what produced it.
• The action doesn't touch the real cause — it's real and completed, but the mechanism is left intact.
• The effectiveness check came too early — closed before enough cycles ran for recurrence to show.
• A local fix for a systemic problem — one line fixed while the same condition stays everywhere else.

None of these are failures of effort. Work was done, a record was created, a box was ticked. The failure is in the reasoning — which is exactly why it's easy to repeat.

Use 5 Whys correctly

You probably already own a root cause analysis method. The problem is how it's used. The 5 Whys isn't a form to fill in — it's a discipline for getting from an event to the condition that allowed it:

• Every "why" rests on evidence, not opinion. No record to back it? The chain has become guesswork.
• Don't stop at "human error." That's where a real analysis starts. Why was the mistake possible? Why did nothing catch it?
• Go until you reach the system — the condition in the process or control that let the error happen. That's the only level where a fix prevents recurrence.

When the real problem is the CAPA process

One recurring problem is a signal about one analysis. A pattern of them is a signal about the corrective action process itself. Audit that process — not the latest defect — when you see:

• Root causes repeatedly landing on symptoms or people — the method is being applied as a formality.
• CAPAs closed on "action completed" (training delivered, procedure updated) instead of evidence the cause is controlled.
• Recurrence never reopening the analysis — the same issue gets a fresh CAPA, and the link to the "solved" case is never made.

Weak check vs. meaningful check

The difference between a CAPA that holds and one that quietly reopens lives in the effectiveness check:

The left column can all be true while the problem is still fully alive. Only the right column proves the cause is under control. CAPA effectiveness isn't a status field — it's a claim that has to survive contact with evidence.

What a purposeful audit asks

When recurrence sends you to the process, a purposeful internal audit doesn't re-check the paperwork. It works backward from the recurrence with six questions:

The last two are the ones most audits skip — and the ones that matter most. They interrogate the effectiveness check itself and refuse to accept a closed record as proof. It's the same evidence-first standard a good ISO 9001 audit applies everywhere else.

The point

Most CAPAs fail quietly because the pieces live in different places — a finding in one log, a root cause in a meeting note, an effectiveness check in someone's memory. ASOW Suite holds the chain together in one place:

finding → root cause → corrective action → responsibility → due date → effectiveness check → recurrence → management review

Because each step links to the next, a returning problem reopens the reasoning instead of starting a fresh, disconnected record — and the effectiveness check is a real step with an expected result and a review period, not a closing signature. That's the whole idea behind the positioning: from requirement to evidence.