Yes, a single CAPA can address multiple related NCRs from different programs if the NCRs share a substantiated root cause and the corrective actions can be applied and verified across each affected program. The CAPA should not replace the individual NCR records. Each NCR still needs its own containment, disposition, traceability, approvals, and closure evidence as required by the applicable customer, contract, procedure, or quality system.
When one CAPA is appropriate
A shared CAPA is usually appropriate when the issue is systemic rather than isolated. Examples include a common work instruction defect, a training gap, an inspection method problem, a calibration control weakness, an ERP or MES routing error, or a supplier process issue affecting multiple part numbers or programs.
The key condition is evidence. The organization should be able to show why the NCRs are related, how the root cause was determined, and why the selected corrective actions address the failure mode across all affected programs. A superficial similarity, such as the same defect code or department, is not enough.
What must remain separate
Even when one CAPA is used, the underlying NCRs normally remain separate quality records. They may involve different parts, serial numbers, lots, customers, engineering authorities, contractual requirements, or delivery impacts.
Each NCR should retain its own record of containment, material disposition, rework or repair authority, use-as-is approval where applicable, customer notification where required, and verification of completion. The CAPA can link these records, but it should not blur them together.
Where this can fail
A single CAPA becomes risky when it is used to simplify administration rather than reflect the actual quality problem. Common failure modes include:
- Forcing unrelated NCRs under one root cause to reduce CAPA count.
- Ignoring program-specific customer requirements or delegated authority limits.
- Closing the CAPA before all affected programs have implemented and verified the actions.
- Applying a global corrective action without confirming that the same process, tooling, data, or work instruction is actually used across programs.
- Losing traceability between each NCR, its disposition, and the CAPA effectiveness check.
Program and customer constraints matter
Some customers or contracts may require separate CAPAs, separate notifications, or specific formats such as 8D or RCCA. Some programs may also have export control, configuration management, or customer portal requirements that affect how records can be linked or shared. A combined CAPA is only acceptable if it does not conflict with those obligations.
In aerospace-grade and similarly regulated environments, the safer approach is often to use one parent or systemic CAPA with linked NCRs, plus program-specific child actions or verification tasks where needed. This keeps the systemic investigation together while preserving program-level accountability.
System implications
In brownfield environments, this depends heavily on how the QMS, MES, ERP, PLM, and customer quality portals are integrated. Many plants can link NCRs to a CAPA in the QMS, but the related production orders, routings, part revisions, inspection records, and dispositions may live in other systems.
If those links are manual, the procedure should define who maintains them and what evidence is required. If links are automated, they still need validation, change control, and periodic review. Integration alone does not prove that the CAPA scope is correct.
Practical rule
Use one CAPA when the problem is genuinely systemic and the organization can prove traceability from each NCR to the shared root cause, corrective action, and effectiveness check. Use separate CAPAs when the root causes, authorities, customer requirements, or verification methods differ materially.