Health November 16, 2026

Move CAPA documentation beyond compliance to meaningful quality improvement

By: Annie Lambert, PharmD, BCSCPSelma Mitiche, PharmD

Key Takeaways

  • Treat CAPA documentation as the record of a full investigation, from root cause analysis through verification of effectiveness, not just a form to close.
  • Separate correction, corrective action, and preventive action. Fix the immediate problem, eliminate its cause, and look for similar risks elsewhere.
  • Set measurable success criteria upfront and trend your CAPAs across the facility to turn corrective and preventive action into lasting quality improvement.
A closed CAPA doesn't always mean a solved problem. When CAPA documentation stops at the immediate fix, pharmacies miss the chance to learn from the event. This article walks through each step of corrective and preventive action, the common mistakes that undermine it, and how to turn required records into meaningful quality improvement.

Every sterile compounding program eventually encounters an event that falls outside an established specification or limit. It may be a temperature excursion, unexpected microbial growth during routine certification, or the discovery that an incorrect ingredient was used in a compounded sterile preparation. These events require investigation, documentation, and an appropriate response. USP <797> also requires pharmacies to maintain a quality assurance program that monitors, evaluates, and improves the processes used to prepare CSPs.

Corrective and Preventive Action, or CAPA, is one of the tools used to manage these events. The issue is investigated, corrective steps are identified, the response is documented, and eventually the CAPA is closed. Closing the CAPA, however, does not necessarily translate into quality improvement. Did the investigation identify why the event occurred? Did the corrective action reduce the likelihood that it will happen again? Did the organization learn anything that can improve other areas of the operation?

CAPA has its greatest value when it functions as part of the pharmacy’s broader quality assurance program. A mature CAPA process provides a disciplined way to identify root causes and contributing factors, verify that corrective actions are effective, and apply what was learned to prevent recurrence. When those steps are missing, CAPA can become little more than required documentation. When they are done well, each CAPA becomes an opportunity to strengthen the pharmacy’s overall quality system.

CAPA documentation fundamentals: 7 actionable steps

A CAPA is a way to document an unexpected finding, and it investigates what happened, what caused it, and how to prevent it from occurring again. The following diagram outlines the general steps of a CAPA plan.

Identify the problem

At a minimum, the CAPA must identify the event, result, or finding that triggered it, including when and how it was discovered, the people, products and environment affected, and any other details that may be relevant to the investigation. At this stage, designate a CAPA owner who will be accountable for overseeing the process through completion.

Risk assessment

The next step is to use a risk-based approach to determine the scope and urgency of the response. How many doses or patients were affected? Which areas of the cleanroom or which personnel were involved? From there, determine the impact, its severity, and any potential risks to future CSPs. This assessment helps identify the immediate steps needed to contain the problem, leading to corrective action.

Correction

At this stage, several USP requirements may come into play, including quarantining affected CSPs, notifying relevant personnel, or recalling specific batches. All applicable USP requirements, regulations, and standard operating procedures (SOPs) must be followed. The immediate goal is to contain the problem and prevent further harm resulting from the triggering event.

Root cause analysis

Once the immediate issue is contained, a root cause analysis can begin. Several tools are available, including fishbone diagrams, the 5 Whys, and Failure Modes and Effects Analysis (FMEA), as well as combinations of these approaches. The appropriate method should be used to identify the factors that contributed to the failure, rather than focusing solely on the incident's immediate cause. By the end of this analysis, there should be a clear understanding of what needs to change to prevent recurrence.

Corrective and preventive action

This is where CAPA becomes more than a response to an isolated event and begins to serve as a tool for continuous quality improvement. The immediate containment (correction) of the problem has already occurred, and further investigation into the root cause should have identified what led to it.

Corrective action is the process of addressing identified issues in systems or processes so that the error does not recur. Preventive action involves assessing beyond the immediate problem to identify whether similar weaknesses exist elsewhere and addressing them to improve quality before a finding occurs. Corrective and preventive action plans should clearly outline the steps to be taken, who is responsible, the required follow-up, and the measurable indicators of success, including how data will be collected and evaluated.

Implementation

Once the plan is established, preventive actions must be implemented and thoroughly documented in the timeline in which they occur. Recording each step and when it was taken ensures that the information remains accessible and retrievable for the final stage: verification of effectiveness.

Verification

During verification, the previously established quality indicators are evaluated to determine whether the root causes have been adequately addressed and whether the actions taken are mitigating the problem. Just as importantly, this process should involve reviewing data for emerging trends before another failure occurs. This includes trending CAPAs related to the same issue, even when they arise elsewhere in the process, to determine whether the changes are contributing to meaningful improvement across the quality system. This step may involve reopening or revising a CAPA if the problem recurs.

Following these steps ensures that the CAPA process does not end with the resolution of an immediate incident. It must demonstrate the logic connecting the problem, root cause, intervention, and evidence that the intervention worked. It uses the event as an opportunity to step back, identify broader vulnerabilities, and strengthen the quality system as a whole, including areas beyond those directly involved in the original incident.

Common CAPA documentation mistakes that undermine quality

Too often, facilities complete a CAPA form without recognizing that they have merely documented an out-of-specification (OOS) finding and the immediate steps taken to address it. The following common pitfalls can prevent CAPA from fulfilling its intended purpose of driving improvements in quality systems overall.

One of the most important distinctions to understand is the difference between correction, corrective action, and preventive action. Take the event of a CSP prepared at the wrong concentration:


Definition Example
Correction Fixing the immediate problem Remaking the CSP, quarantining the incorrect product
Corrective action Addressing the cause of an identified problem so it does not recur Determining why the error occurred and redesigning the workflow, training, technology, or verification process
Preventive action Addressing a potential weakness before it produces another event or compliance failure Reviewing similar processes to determine whether the same vulnerability exists elsewhere

Other common mistakes:


Avoid Instead
Confusing correction, corrective action, and preventive action

Do not treat an immediate fix as the entire CAPA, for example, discarding an affected CSP and stopping there.
Separate the responses. Correct the immediate issue and contain affected CSPs; use corrective action to eliminate the identified cause and prevent recurrence; use preventive measures to address similar risks elsewhere before failures occur.
Opening a CAPA for every OOS or incident, or dismissing minor events as unrelated Use a documented, risk-based assessment to distinguish a one-time event from a recurring or systemic weakness. Not every incident requires a CAPA. Escalate based on severity, recurrence, patient risk, and evidence of a broader process failure.
Assuming a CAPA requires a violation of procedures or processes

Waiting for a USP violation, failed inspection, or out-of-specification result before investigating an undesirable trend
Initiate review when performance signals reveal risk, even if the process appears compliant. Repeated environmental monitoring excursions or unfavorable trends can expose operational vulnerabilities, even if no excursion has occurred. And the root cause might reveal that, although all SOPs were followed, other factors or workflows were contributing to a trend that would eventually lead to a problem.
Blaming the individual instead of examining the process

Concluding that an employee caused the event and closing the CAPA after the employee signs a retraining record
Examine workflow design, staffing, equipment, instructions, environmental conditions, and human factors. Retraining may be appropriate, but only when a knowledge or skill gap is supported by the investigation.
Writing vague action plans

Using instructions such as “retrain staff,” “monitor more closely,” or “reinforce the SOP” without identifying what will change, when, or the follow-up.
Specify the action, accountable owner, due date, evidence of completion, and expected result. For example, revise a sampling procedure, train designated staff on the revision, and audit sampling practices.
Closing CAPAs when actions are completed

Treating an updated SOP, completed training, or signed checklist as proof that the problem has been resolved.
Distinguish implementation from effectiveness. Verify over a meaningful follow-up period that the root cause was addressed and the issue has not recurred; document the evidence before closure.
Defining success too late

Choosing effectiveness measures only after the action plan has been implemented, when baseline data or meaningful comparisons may be unavailable.
Set measurable success criteria at the outset, including the baseline, target, review period, and person responsible. Choose measures that demonstrate improved performance.
Reviewing CAPAs in isolation

Closing individual cases without comparing similar findings across shifts, rooms, processes, or pharmacy locations.
Periodically trend CAPA data across the entire compounding facility. Look for recurring root causes, weak controls, overdue actions, and recurring deviations across locations; use those findings to prioritize system-wide improvements.

Corrective and preventive action builds quality

While it may be tempting to resolve a problem quickly and close out the CAPA, its real value lies in turning individual failures, near misses, and compliance findings into opportunities for organizational learning and continuous quality improvement. Pharmacy leaders who integrate CAPA into their ongoing quality management practices are better positioned to prevent recurring problems, identify emerging risks, and build safer, more reliable systems of care.

Simplifi 797 provides CAPA documentation, giving Designated Persons (DPs) a structured way to document investigations, root causes, corrective actions, and preventive actions related to compounding and USP compliance events. By creating a documented, inspection-ready record of what happened, why it happened, and what was done to address it, organizations can improve compliance oversight without introducing a separate quality management system. This allows DPs to manage the full story of an event, from the initial excursion through investigation and resolution, within a single workflow.

Learn About Simplifi 797
Back To Top