SOP-703

Corrective and Preventive Action (CAPA)

Number
SOP-703
Category
Quality Assurance
Edition
Reference Edition 1.3
Approx. pages
6

[YELLOW] the site fills in. [DEFAULT: green] a value the site may keep or change.

On this page

1. Purpose

This SOP describes how [SITE NAME] identifies the cause of quality problems, plans and completes corrective and preventive actions, checks that the actions worked, and tracks CAPAs to closure.

2. Scope

This SOP applies to quality problems from any source, in any study or site process, at every location. Sources include:

  • protocol deviations and noncompliance (SOP-308 Protocol Deviations and Noncompliance)
  • internal QC and audit findings (SOP-700 Internal Quality Control and Quality Assurance Audits)
  • sponsor monitoring findings (SOP-600 Sponsor Monitoring Visits)
  • sponsor and IRB audit findings (SOP-701 Sponsor and IRB Audits)
  • FDA inspection observations and RRA observations (SOP-702 FDA Inspections and Remote Regulatory Assessments)
  • complaints from participants, staff, sponsors, IRBs or vendors
  • privacy incidents (SOP-400), temperature excursions (SOP-304), system failures (SOP-401) and continuity events (SOP-705)
  • trends in quality metrics (SOP-700)

This SOP does not replace the reporting steps in other SOPs. A deviation is still reported under SOP-308 and a privacy incident under SOP-400. This SOP covers what the site does to fix the cause.

Where a sponsor, IRB or FDA sets a stricter requirement or deadline for a CAPA, follow it.

3. Responsibilities

RoleResponsibilities
Quality LeadOwns this SOP and F-703-01. Decides whether a CAPA is needed, sets the depth of root cause analysis, assigns owners, tracks due dates, approves effectiveness checks and approves closure. Reports CAPA status and trends at management review.
Site DirectorProvides resources, approves CAPAs that need budget or staffing changes, receives escalation of overdue CAPAs, and approves closure of any CAPA where the Quality Lead owns an action. Where the Site Director is also the Quality Lead, the PI or the independent reviewer named under the SOP-102 5.3 Site decision does these (5.5.3, 5.7.2).
Principal Investigator (PI)Takes part in root cause analysis for study-related problems, approves CAPAs that affect study conduct or participant safety, and decides whether CAPA information must be reported to the sponsor or IRB.
CAPA owner (any staff member assigned)Completes assigned actions by the due date and provides evidence of completion.
All Research StaffReport problems and complaints promptly, take part in root cause discussions honestly, and carry out the actions assigned to them.

4. Definitions

TermDefinition
CorrectionImmediate action to fix the specific problem (for example, re-consenting a participant on the current form, completing a missing log entry). A correction does not address why the problem happened.
Corrective actionAction to remove the cause of a problem that has occurred, so it does not happen again.
Preventive actionAction to remove the cause of a potential problem, or to stop an identified problem from occurring in other studies, staff or locations.
Corrective and Preventive Action (CAPA)The documented process of correction, root cause analysis, corrective action, preventive action and effectiveness check, recorded on F-703-01.
Root causeThe most basic cause that, if removed, would prevent recurrence.
Root cause analysis (RCA)A structured method to find the root cause.
Effectiveness checkA planned, measurable check, done after the actions are complete, that shows whether the problem has stopped recurring.
Critical, major and minorSeverity classes defined in SOP-700 Internal Quality Control and Quality Assurance Audits, section 4.

5. Procedure

5.1 Deciding whether a CAPA is needed

5.1.1
Any staff member who identifies or receives a quality problem or complaint reports it to the Quality Lead within [DEFAULT: 1 business day]. Problems that affect participant safety are reported to the PI immediately, before anything else. Consent errors are reported to the PI the same day (SOP-301 5.12.2).
5.1.2
The Quality Lead reviews the problem within [DEFAULT: 5 business days of report], assigns a severity, and opens a CAPA on F-703-01 CAPA Record when any of the following applies:
  • a critical finding or event
  • a major finding or event
  • an important protocol deviation, or a deviation that harmed a participant (SOP-308, 5.6.2)
  • any FDA 483 observation, RRA observation or Warning Letter
  • a sponsor or IRB audit finding graded major or critical
  • a repeat of the same minor problem [DEFAULT: 3 or more times in a rolling 6 months, in one study or across studies, matching SOP-308], including trends found in the SOP-700 quarterly metrics review
  • a privacy incident with a systemic cause (SOP-400)
  • a substantiated complaint about participant treatment, consent or privacy
  • a sponsor, IRB or management review request
5.1.2.1
This list is the site's single set of CAPA triggers. SOP-400, SOP-700, SOP-701 and SOP-702 point to it. Minor sponsor or IRB audit findings that are not part of a trend are corrected, given a one-line cause in the audit response (SOP-701), and counted in the quality metrics (SOP-700); they do not need an F-703-01 entry.
5.1.3
For minor problems that do not meet section 5.1.2, the record owner makes the correction and the Quality Lead captures the problem in the quality metrics (SOP-700). No F-703-01 entry is needed unless a trend develops.
5.1.4
The Quality Lead records the CAPA number on related records (for example, the deviation log entry, audit response or complaint record) so the records link to each other.

5.2 Immediate correction and containment

5.2.1
Before the root cause is known, the PI and Quality Lead decide what must happen now to protect participants and data. Examples:
  • pausing a task by a staff member until retrained
  • quarantining IP after a temperature excursion (SOP-304)
  • re-consenting affected participants on the correct version (SOP-301)
  • checking all other participants in the study, or other studies, for the same problem
5.2.2
The CAPA owner records each correction and containment action, with date and evidence, on F-703-01.

5.3 Root cause analysis scaled to severity

5.3.1
The Quality Lead sets the RCA depth:
  • Minor (trend-triggered): the record owner and Quality Lead complete a 5 whys analysis.
  • Major: the Quality Lead leads a 5 whys analysis with the staff involved and the Lead CRC. A fishbone diagram is used where more than one cause is likely.
  • Critical, FDA observations and repeat major findings: the Quality Lead leads a team analysis with the PI, Site Director and staff involved, using a fishbone diagram and 5 whys for each main branch, and reviews related records across all affected studies.
5.3.2
5 whys. The team states the problem as a fact (what, where, when, how many), then asks "why did this happen?" and answers with evidence, repeating until it reaches a cause the site can control and that would prevent recurrence if removed. This usually takes three to five steps.
5.3.3
Fishbone (cause and effect) diagram. The team lists possible causes under standard categories, then tests each against the evidence:
  • People (training, workload, experience, handoffs)
  • Procedures (SOP unclear, missing, conflicting with protocol or sponsor instructions)
  • Protocol and sponsor tools (complex schedule, unclear CRF guidance, system design)
  • Equipment and systems (EHR, EDC, IxRS, temperature monitors, alarms)
  • Environment (space, interruptions, location, after-hours work)
  • Communication (between staff, with sponsor, with IRB, with participants)
5.3.4
RCA rules:
  • "Human error" or "staff did not follow the SOP" is not a root cause by itself. The team asks why the error was possible or likely (for example, no checklist, conflicting instructions, workload, unclear form).
  • The analysis looks at the process, not at blame. Staff are expected to describe what happened honestly. Suspected deliberate misconduct is handled under SOP-704 Research Misconduct and Fraud Reporting, not here.
  • The team records the analysis, the evidence used, and the root cause statement on F-703-01.
5.3.5
RCA is completed within [DEFAULT: 15 business days of CAPA opening for major, 10 business days for critical], or sooner where an external deadline applies (for example, the 15 business day response window for a Form FDA 483 under SOP-702).

5.4 CAPA plan

5.4.1
The Quality Lead and CAPA owner write the CAPA plan on F-703-01. For each action the plan states:
  • what will be done
  • whether it is corrective or preventive
  • the owner (a named person, not a role)
  • the due date
  • the evidence that will show it is complete (for example, revised form, approved SOP, training record, system change record)
5.4.2
Actions address the root cause. Retraining alone is acceptable only when the root cause is a knowledge gap. Where the cause is a process or tool problem, the plan changes the process or tool (for example, adds a checklist step, changes a form, adds a system alert, adjusts workload).
5.4.3
Preventive actions consider whether the same cause exists in other studies, staff or locations, and extend the action there.
5.4.4
If the plan changes an SOP or form, the change goes through SOP-100 Writing, Approving and Controlling SOPs. If it requires training, training is recorded on F-103-01 Staff Training Log (SOP-103).
5.4.5
The PI approves CAPA plans that affect study conduct. The Site Director approves plans that need budget, staffing or vendor changes. The Quality Lead approves all plans.
5.4.6
Where the CAPA arises from a sponsor finding, an IRB finding or an FDA observation, the CAPA plan is the basis of the site's written response (SOP-701, SOP-702). The PI decides with the Quality Lead whether the CAPA itself must be reported to the sponsor or IRB under SOP-308 or SOP-502.

5.5 Tracking

5.5.1
The Quality Lead keeps F-703-02 CAPA Log as the register of all CAPAs, adds each CAPA on the day it is opened on F-703-01, and updates its status at each review. The Quality Lead reviews open CAPAs at least [DEFAULT: every 2 weeks] and follows up on actions that are due.
5.5.2
An owner who cannot meet a due date asks the Quality Lead for an extension before the date, with a reason. The Quality Lead records the new date and reason on F-703-01. Extensions on CAPAs promised to FDA, a sponsor or an IRB are communicated to them before the original date.
5.5.3
Overdue CAPAs are escalated to the Site Director. Where the Site Director is also the Quality Lead, overdue CAPAs are escalated to the PI or the independent reviewer named under the SOP-102 5.3 Site decision.

5.6 Effectiveness check

5.6.1
Each CAPA plan defines an effectiveness check with:
  • the measure (for example, consent QC error rate, number of late SAE reports, deviations of the same type)
  • the target (for example, zero recurrences, or error rate below a stated level)
  • the period or sample [DEFAULT: the later of 3 months or the next 10 occurrences of the activity; for rare activities, the next 3 occurrences or 12 months, whichever comes first]
  • the person who performs the check, who should not be the CAPA owner
5.6.2
After all actions are complete and the period has passed, the reviewer performs the check and records the result and evidence on F-703-01.
5.6.3
If the target is not met, the Quality Lead reopens the RCA, revises the plan, and sets a new effectiveness check. The CAPA stays open.

5.7 Closure

5.7.1
The Quality Lead approves closure on F-703-01 when:
  • all actions are complete with evidence
  • the effectiveness check met its target
  • any commitments to FDA, sponsor or IRB are fulfilled and communicated
5.7.2
If the Quality Lead owned any action or performed the effectiveness check, the Site Director approves closure instead. In that case, where the Site Director is also the Quality Lead, the PI or the independent reviewer named under the SOP-102 5.3 Site decision approves closure.
5.7.3
Closed CAPA records are kept in the quality file and, where they relate to a study, a copy or reference is filed in the ISF. Records of noncompliance and CAPA are essential records (ICH E6(R3) Appendix C) and are retained under SOP-402 Record Retention, Archiving and Destruction.
5.8.1
As part of the quarterly metrics review in SOP-700 5.7.1, the Quality Lead reviews F-703-02 for:
  • number of CAPAs opened and closed, by source and severity
  • overdue CAPAs
  • CAPAs that failed an effectiveness check
  • repeated root causes across CAPAs (for example, workload, unclear sponsor instructions, a particular system)
5.8.2
Repeated root causes across CAPAs trigger a new site-level CAPA. Trends and CAPA status go to the management review under SOP-700.
  • F-703-02 CAPA Log
  • F-703-01 CAPA Record
  • F-700-01 Internal QC Review Checklist
  • F-308-01 Protocol Deviation Log
  • F-103-01 Staff Training Log
  • SOP-100 Writing, Approving and Controlling SOPs
  • SOP-102 Site Organization, Roles and Staff Responsibilities
  • SOP-103 Staff Qualification, Training and Training Records
  • SOP-301 Informed Consent Process and Documentation
  • SOP-304 Investigational Product Management
  • SOP-308 Protocol Deviations and Noncompliance
  • SOP-400 Participant Privacy and HIPAA in Research
  • SOP-401 Computerized Systems and Electronic Records
  • SOP-402 Record Retention, Archiving and Destruction
  • SOP-502 Unanticipated Problems and Reportable New Information
  • SOP-600 Sponsor Monitoring Visits
  • SOP-700 Internal Quality Control and Quality Assurance Audits
  • SOP-701 Sponsor and IRB Audits
  • SOP-702 FDA Inspections and Remote Regulatory Assessments
  • SOP-704 Research Misconduct and Fraud Reporting
  • SOP-705 Business Continuity and Emergency Preparedness
  • F-900-01 Local Addendum to a Network SOP (Model N only)
  • SOP-900 Network Governance, SOP Hierarchy and Local Addenda (Model N only)
  • SOP-903 Network Oversight of Member Sites (Metrics, Central QA, Escalation) (Model N only)
  • Appendix B Central and Site Responsibility Matrix (Model N only)

7. References

ReferenceTitle
21 CFR 312.60General responsibilities of investigators
21 CFR 812.100General responsibilities of investigators (devices)
ICH E6(R3) Principles 6 and 7Quality built into trial design and conduct; risk-proportionate processes
ICH E6(R3) Annex 1, 2.5Compliance with Protocol
ICH E6(R3) Annex 1, 3.12Noncompliance (root cause analysis and CAPA expectation)
ICH E6(R3) Appendix CEssential Records (records of noncompliance and corrective and preventive actions)
FDA Compliance Program 7348.811Bioresearch Monitoring: Clinical Investigators and Sponsor-Investigators
ISO 14155 (current edition)Clinical investigation of medical devices for human subjects: Good clinical practice (device studies)

Independent Site SOP Library. Licensed CC BY-NC 4.0 by the American Institute for Medical Research (AIMR), with added permission for any site's internal use (license terms). Not legal advice: each adopting site confirms state law, IRB and sponsor requirements with its own counsel and owns every step it approves.