CAPA for Protocol Deviations in Clinical Trials: Real-World Case Examples

Understanding Protocol Deviations and Their Regulatory Impact

Protocol deviations are any changes, divergences, or departures from the approved protocol during a clinical trial. These can range from missing a visit window to using incorrect informed consent forms. Regulatory bodies such as the FDA and EMA consider unmanaged deviations a risk to subject safety and data integrity.

Corrective and Preventive Actions (CAPAs) are essential tools for identifying the root cause of deviations, resolving them effectively, and preventing recurrence. In this article, we illustrate CAPA application for protocol deviations using practical case examples from clinical trial settings, highlighting what went wrong, how it was corrected, and what preventive steps were taken.

Case 1: Missed Visit Window in an Oncology Trial

Deviation: A patient visit in a Phase III oncology trial occurred 10 days after the allowed window due to scheduling delays.

Root Cause: Site coordinator was on leave; no backup staff assigned for visit scheduling.

Corrective Action: The sponsor accepted the protocol deviation and submitted a report. The missed data was annotated in the CRF. The site issued a deviation log with rationale and patient safety assessment.

Preventive Action:

• Introduced a cross-coverage schedule for coordinators
• Updated the site’s SOP to mandate delegation for scheduling responsibilities
• Implemented visit tracking reminders within CTMS

This example was later used in a sponsor’s internal training module on deviation prevention and CAPA handling.

Case 2: Use of Outdated Informed Consent Form (ICF)

Deviation: Site used an older version of the ICF for two subjects after a protocol amendment had introduced a revised consent form.

Root Cause: Site did not discard previous ICF versions and overlooked email notification about the updated form.

Corrective Action:

• Re-consented affected subjects using correct version
• Notified sponsor and IRB
• Updated deviation and re-consent documentation in the TMF

Preventive Action:

• Implemented an ICF version control log at site level
• Conducted site training on document control SOPs
• Flagged outdated forms for destruction and documented removal

Regulators later acknowledged the effectiveness of this CAPA during a routine GCP inspection.

Case 3: Dose Administration Out of Sequence

Deviation: A subject was administered investigational product (IP) before lab results confirmed eligibility on Day 1.

Root Cause: Site misinterpreted the protocol flow and assumed screening was already complete.

Corrective Action:

• Stopped dosing until lab results confirmed eligibility
• Documented deviation and medical monitor was consulted
• Subject continued participation with additional safety monitoring

Preventive Action:

• Created protocol-specific dosing checklist
• Re-trained staff on Day 1 visit flow
• Implemented double-verification process before IP administration

More such protocol-specific job aids are available on PharmaValidation.

Case 4: Delayed SAE Reporting

Deviation: Site reported a Serious Adverse Event (SAE) 72 hours after becoming aware of the incident—beyond the 24-hour reporting requirement.

Root Cause: The sub-investigator failed to escalate the event immediately due to misunderstanding of SAE criteria.

Corrective Action:

• Immediate SAE report submitted with explanation
• Deviation documented and explained in safety narrative
• Sponsor performed expedited safety review

Preventive Action:

• Re-education of site team on SAE definitions and timelines
• Distributed laminated SAE criteria cards
• Set escalation protocol with on-call PI contact list

This case is frequently cited in GCP training materials focused on safety management.

Case 5: Incorrect Lab Sample Handling

Deviation: Blood samples meant for PK analysis were not centrifuged and stored at room temperature instead of frozen conditions.

Root Cause: New lab technician unaware of handling requirements stated in lab manual.

Corrective Action:

• Site informed central lab and sponsor
• Subject’s PK data was excluded from primary endpoint
• Deviation documented with QA input

Preventive Action:

• Refresher training on lab manual procedures
• Checklist introduced for sample collection and processing
• Job shadowing protocol implemented for new lab staff

GCP inspectors appreciated proactive handling and thorough documentation of this case.

Lessons Learned from CAPA Application in Deviations

• Always link CAPA to a clear root cause supported by evidence
• Ensure preventive actions are systemic, not individual-focused
• Close the loop by verifying effectiveness (e.g., via audit or absence of recurrence)
• Document CAPAs in TMF with cross-reference to deviation logs

CAPA systems must be designed not only for reactive correction but also for proactive prevention. These examples demonstrate how structured CAPAs enhance trial quality and regulatory confidence.

Conclusion

CAPA is more than a checklist—it is a mindset. Each deviation in a clinical trial presents an opportunity to strengthen processes, educate staff, and reinforce protocol compliance. By applying CAPA with diligence, clarity, and consistency—as illustrated in the above case studies—clinical trial teams can ensure quality, safety, and regulatory alignment at every stage.

References:

• ICH E6(R2): Guideline for Good Clinical Practice
• FDA BIMO Compliance Program Manual
• PharmaSOP: Deviation and CAPA Templates Library