thebench.bio #1 Ecosystem for the Bio-Tech Industry
All CAPA questions

Question 17 of 20 Advanced Scenario

What evidence would justify extending a CAPA to another site or product family?

Short answer

Extend it when the other site or product shares the mechanism that caused the failure: the same equipment design, material, procedure, software or organizational condition. Check for that mechanism with data rather than copying actions, and adapt actions where local conditions differ.

Why

A CAPA fixes a mechanism, not just a location. If the mechanism exists elsewhere, the same failure is waiting there. ICH Q10 says CAPA should consider other products that might be impacted, and its knowledge management enabler exists so that what one site learns reaches the others.

US regulation already requires investigations to extend to other products that may be associated with a failure. The evidence question is whether the mechanism is present. Suppose a filling line had particle complaints traced to a specific stopper bowl design that abrades stoppers.

Other sites with the same bowl model and the same stopper type share the mechanism, even if they have no complaints yet, because detection may lag. Sites with a different bowl do not. Useful evidence includes equipment lists, supplier and material lots, shared SOPs or software versions, and trend data for early signs.

Copying the action blindly is risky. A training fix that worked at a site with experienced staff may not suit a new site, and an equipment change may need its own validation at each site through local change control. Where the mechanism is uncertain, a time-limited assessment at each candidate site is a sensible first step.

Deciding not to extend should also be documented, with the reason, so a later failure elsewhere cannot be blamed on a silent gap.

A strong answer covers

  • Extend where the mechanism is shared
  • Evidence from equipment, materials, procedures and software
  • Absence of complaints is not absence of risk
  • Adapt and validate actions locally
  • Document decisions not to extend

Common mistakes

  • Copying actions to every site without checking whether the mechanism exists there.
  • Waiting for the failure to appear at the other site before acting.
  • Skipping local change control because the change was approved at another site.