Skip to main content

GuidelinesGMP2026.10.09

KGMP CAPA Responses: Connect Causes, Actions and Effectiveness With Evidence

A revised procedure and training attendance alone may not show that a finding’s cause was resolved. Link observations, impact, investigation and recurrence-prevention evidence in the response.

Separate the finding from interpretation

Retain the original finding and distinguish the requirement, objective observation and the company’s interpretation. “Poor record control” can obscure which record in which process failed which criterion. Identify the site, product, document version and observations under each finding number.

State verified facts without minimizing or overextending them. If interpretation differs, explain the evidence and additional checks. Use the KGMP preparation guide for context, while keeping this response focused on the particular finding.

Establish immediate action and affected scope

Determine whether a missing record is an isolated case. Investigate defined periods, forms, operators, equipment and product families where the same issue may exist. If shipped-device safety or quality may be affected, evaluate and act through the relevant procedures.

Correction fixes the detected nonconformity; corrective action addresses its cause. Handling a missing record differs from changing a release process that allowed the omission. Do not reconstruct a record as if it had existed at the original time. Distinguish verifiable historical facts from current actions.

Make the cause testable against evidence

“Operator error” or “insufficient training” may start an investigation but is not automatically its root cause. Check whether instructions were unclear, forms lacked essential fields or review controls failed. Consider both the cause of occurrence and the reason it escaped detection.

Compare interviews with actual records, procedural changes and work conditions. Document supporting evidence and reasons other explanations were rejected. Review whether the issue affects other processes or products in the risk-management file.

Distinguish planned work from completed evidence

This is a practical response structure, not a statutory form. Follow the format and deadline in the relevant reviewing body’s notice.

Element Response content
Observation Specific condition inconsistent with the requirement
Impact Investigation scope, products/lots and results
Cause Evidence; occurrence and non-detection causes
Correction/action Work, owner, changed documents and implementation date
Implementation evidence Identified approvals, actual records and verification
Effectiveness Measures, sampling/time rationale, criteria and assessor

“Revision planned” and “approved and implemented” are different statuses. Identify which claim each attachment supports, not just its filename. A short traceable path to source evidence is more useful than a long narrative.

Evaluate recurrence prevention, not merely attendance

Training signatures establish attendance, not all aspects of sustained operation. For missing records, examine actual post-change records and release checks. Justify the number of production instances or observation period from frequency and risk rather than imposing one number on every case.

Also consider unintended effects. Automated entry or approval blocks can duplicate incorrect values or obstruct necessary work. If effectiveness is inadequate, revisit the cause and action. Keep incomplete checks open with an owner and planned completion conditions.

Maintain the closure decision after submission

Sending the response is not identical to concluding that actions are effective. Link inquiries, replies, submission versions, additional work and closure under the finding identifier. Consider related suppliers, processes and post-market complaints and involve affected functions.

Bring the finding, procedures, actual records and current action plan to a KGMP corrective-action review. Identify missing links between facts, causes, actions and effectiveness before adding documents. Submission timing and conformity decisions depend on the particular review procedure.


Sources checked: 2026-09-28. The tables and preparation steps are practical suggestions; confirm the legal submission scope and applicable standards for the particular product.

Frequently asked questions

Q. Are a revised procedure and training record enough?
Show that the action addresses the cause and was implemented. Training can be appropriate, but may not be sufficient for a procedural, design or system cause.
Q. What is the difference between correction and corrective action?
Correction addresses the detected nonconformity; corrective action removes its cause to prevent recurrence. Plan both according to impact and risk.
Q. Can we claim completion before effectiveness is checked?
Separate completed actions from ongoing effectiveness evaluation. Present the method, criteria, owner and planned timing without portraying future results as evidence already obtained.

Just send the product details.
We do the reviewing.

We pre-review device class, required pathway, and data readiness free of charge, and reply within 1 business day. No sign-up.