Question 13 of 20 Intermediate Troubleshooting
A CAPA closed on time but the same issue reappears months later. What would you examine?
Short answer
Check whether the recurrence really is the same failure, then test each link: was the root cause right, did the action address it, was it implemented and sustained, and was the effectiveness check sensitive enough to detect failure? Recurrence usually means one of those links was weak.
Why
A recurrence is useful evidence because it tests the original reasoning. First confirm it is the same failure mode, not just the same symptom. A second particle complaint might come from a different source.
If it is the same, work through the chain. Was the root cause supported by evidence, or was it the most plausible story? EU GMP Chapter 1 allows addressing the most likely causes when the true cause cannot be found, but then a recurrence suggests the likely cause was wrong.
Did the action target that cause, or a symptom? Was it fully implemented and is it still in place, since temporary fixes, revised SOPs that nobody reads, and equipment settings that drift back are common? Was the effectiveness check able to fail?
A three-month window for an event that happens twice a year proves very little. Critiques of root cause analysis describe weak actions and low implementation rates as common reasons lessons are not learned. Also ask what changed between closure and recurrence, such as new staff, new suppliers or higher volume, which might have reopened a gap the action had covered.
The outcome decides whether to reopen the original CAPA, if its conclusion was wrong, or open a new one linked to it, if a new cause appeared.
How to work it through
- Confirm the new event is the same failure mode by comparing evidence, not just the description.
- Review the original root cause evidence and what alternatives were ruled out.
- Verify the actions were implemented and are still in place on the floor.
- Assess whether the effectiveness check had the power to detect recurrence.
- Look for changes since closure that could have reopened the gap.
- Decide whether to reopen the original CAPA or open a linked new one, and record the reasoning.
An example
A CAPA for missing batch record pages closed after a form redesign and three clean months. Seven months later two records again miss a page. Comparison shows the same page, the sampling log, is missing.
On the floor, a new shift supervisor has been printing the old form version from a local drive. The action worked where implemented, but document control never removed old copies. The original CAPA is reopened because its implementation was incomplete, and an action is added to remove uncontrolled forms and audit for them monthly.
Where the answer stops holding
A low-frequency event may recur by chance even after a partial fix, so one recurrence is not proof the whole CAPA failed. Without good original documentation, it can be impossible to tell which link broke. Recurrence across sites may need a broader investigation than one CAPA.
A strong answer covers
- Confirm same failure mode
- Test root cause evidence
- Verify implementation and sustainment on the floor
- Check sensitivity of the effectiveness check
- Look for changes since closure
Common mistakes
- Opening a new unrelated CAPA without reviewing why the first one failed.
- Assuming the action was implemented because the record says complete.
- Accepting a short clean period as proof for a rare event.
The interviewer might ask next
How would you set the observation window so the next effectiveness check can actually fail?