This is a ready-to-use record for documenting a CAPA effectiveness check: the metric that will demonstrate the failure mode stopped, the observation window, the accountable owner, and the actual result, so “closed” means the failure mode stopped recurring, not only that the corrective action was implemented. Open one record per CAPA at the time the CAPA is approved, and close it only after the observation window has run. Replace every <<FILL: ...>> placeholder with your own specifics. A filled specimen follows.
Field definitions
| Field | Format | Required | Who completes it | When |
|---|---|---|---|---|
| CAPA ID | <<FILL: reference>> | Yes | CAPA owner | At CAPA approval |
| Related deviation ID(s) | <<FILL: one or more references>> | Yes | CAPA owner | At CAPA approval |
| CDMO / site | <<FILL>> | Yes | CAPA owner | At CAPA approval |
| Corrective action implemented | Free text, dated | Yes | CAPA owner | At implementation |
| Effectiveness metric | Free text, must be a measurable, named metric, not a narrative assurance | Yes | CAPA owner, confirmed by sponsor reviewer | At CAPA approval, before implementation |
| Observation window | <<FILL: batches or months, long enough for the failure mode to plausibly recur>> | Yes | CAPA owner, confirmed by sponsor reviewer | At CAPA approval |
| Accountable owner for running the check | Named individual, by role | Yes | CAPA owner | At CAPA approval |
| Result | Pass / Fail, with the underlying data | Yes | Accountable owner | At the end of the observation window |
| If Fail, disposition | Free text: CAPA reopened, root cause revisited | Required if Result is Fail | Accountable owner, confirmed by sponsor reviewer | Immediately on a Fail result |
Instructions for use
- Open this record at the time the CAPA is approved, not after implementation. The effectiveness metric, observation window, and accountable owner are commitments made before the outcome is known.
- The effectiveness metric has to be something that would actually fail if the root cause was not really fixed: a recurrence count of zero over the window, a specification-margin trend holding inside a stated band, or an equivalent measurable criterion. “No further issues reported” is not a metric; it is the absence of a metric dressed as one.
- Set the observation window from how often the failure mode could plausibly recur, not from a fixed default. A failure mode tied to a rare raw material lot needs a longer window than one tied to every batch.
- At the end of the window, the accountable owner records Pass or Fail against the stated metric, with the underlying data referenced, not summarized as an opinion.
- A Fail result reopens the CAPA and revisits the root cause. It does not extend the observation window on the same corrective action, and it does not get buried under a new, unrelated CAPA number.
- Reference this record’s CAPA ID in the CDMO Quality System Drift Scorecard’s root cause code repetition metric and in the Network Change Control Master Record where a CAPA’s corrective action itself constituted a change.
Common inspection findings this record prevents
- A CAPA closed on its implementation date with no effectiveness metric, window, or owner ever defined.
- An effectiveness claim with no underlying data, “monitored, no issues,” standing in for an actual measured result.
- A failed effectiveness check followed by a new CAPA number opened for the same failure mode rather than reopening the original.
- No observation window stated, so “effective” is asserted before the failure mode had any real chance to recur.
How to adapt this record
- Open one record per CAPA; do not batch multiple CAPAs onto one record even if they share a root cause category.
- Set the effectiveness metric and observation window at approval, confirmed by the sponsor reviewer, before implementation begins.
- Record the result at the end of the window from actual data, not a status update.
- On a Fail, reopen the CAPA in the source system and cross-reference that reopening here rather than closing this record as if the check had passed.
Filled specimen
CAPA-2026-0447, opened by CMO Alpha following a raw material out-of-specification event on the ATX-330 excipient lot.
| Field | Entry |
|---|---|
| CAPA ID | CAPA-2026-0447 |
| Related deviation ID(s) | DEV-2026-1188 |
| CDMO / site | CMO Alpha |
| Corrective action implemented | Incoming material sampling plan revised from n=3 to n=13 per ANSI/ASQ Z1.9 for this excipient grade, effective the date of the next receipt |
| Effectiveness metric | Zero incoming-material OOS results for this excipient grade |
| Observation window | Next 6 receipts or 4 months, whichever is longer |
| Accountable owner for running the check | CMO Alpha Incoming QC Supervisor, confirmed by Acme Supply Chain Quality |
| Result | Pass. Six receipts over 4 months, all within specification; sampling plan revision referenced in each receiving record |
| If Fail, disposition | Not applicable |
The window was set to six receipts rather than a fixed calendar period alone because this excipient’s receiving frequency is irregular; a pure four-month window could have closed with only two receipts actually tested against the revised plan, which would not have been enough data to call the corrective action demonstrated.