This is a ready-to-use companion form to the CAPA record. It targets one specific, recurring weakness: a CAPA whose action plan never rises above a procedural control or a training refresher. Complete it whenever the highest-tier action in a CAPA’s plan is tier 4 (procedural) or tier 5 (training/awareness). Replace every <<FILL: ...>> placeholder, and route it alongside the CAPA record it belongs to. A filled specimen follows. Verify each cited regulation against the current source before you rely on it.
Form control header
| Field | Entry |
|---|---|
| Form title | CAPA Corrective Action Hierarchy Justification |
| Form number | <<FILL: FORM-ID, e.g. FORM-QA-020-02>> |
| Version | <<FILL: version, e.g. 1.0>> |
| Effective date | <<FILL: effective date>> |
| Governing SOP | <<FILL: SOP-ID for CAPA management>> |
| Trigger for use | Complete this form when no action in the CAPA’s plan reaches tier 1, 2, or 3 of the hierarchy below |
Section A: Identification
| Field | Entry |
|---|---|
| CAPA number | <<FILL: CAPA-ID>> |
| CAPA owner | <<FILL>> |
| Root cause (summary) | <<FILL>> |
| Date this form completed | <<FILL>> |
Section B: The hierarchy, restated
| Tier | Type of action | Reliability | Why it ranks here |
|---|---|---|---|
| 1 | Eliminate / design out | Highest | Removes the possibility of the failure entirely; nothing is left for a person or a downstream control to catch |
| 2 | Engineering / system control | High | The system itself prevents the unsafe state or requires a second party to change it |
| 3 | Automated detection | Medium-high | The failure can still occur but is caught automatically, close to real time |
| 4 | Procedural control | Medium | Relies on a person following a written step correctly, every time |
| 5 | Training / awareness | Lowest | Relies on a person remembering, with no system check behind it |
Section C: Action plan tier summary
List every action in the CAPA’s plan and its tier. This form is triggered when the highest tier reached is 4 or 5.
| # | Action | Tier (1 to 5) |
|---|---|---|
| 1 | <<FILL>> | <<FILL>> |
| 2 | <<FILL>> | <<FILL>> |
| 3 | <<FILL>> | <<FILL>> |
Highest tier reached across all actions: <<FILL: 4 or 5>>
Section D: Mandatory justification
Answer each question. “Not considered” is not an acceptable answer on its own; if a higher tier was not considered, explain why it was out of scope for this event.
| Question | Answer |
|---|---|
| Was elimination or design-out (tier 1) considered? What would it have required, and why was it not selected? | <<FILL>> |
| Was an engineering or system control (tier 2) considered? What would it have required, and why was it not selected? | <<FILL>> |
| Was automated detection (tier 3) considered? What would it have required, and why was it not selected? | <<FILL>> |
| What specific constraint drove the decision to rely on tier 4 or 5 instead (cost, technical feasibility, system architecture, timeline, vendor limitation, other)? | <<FILL>> |
| Is this a permanent position, or an interim measure pending a planned higher-tier action? | <<FILL: permanent / interim>> |
| If interim, what is the planned higher-tier action and its target date? | <<FILL or N/A>> |
| What compensating measure offsets the lower reliability of a tier 4 or 5 action alone (for example, a second independent check, a shortened effectiveness check window, increased review frequency)? | <<FILL>> |
Section E: Review and decision
| Field | Entry |
|---|---|
| Reviewer assessment | Justification accepted / Justification rejected, higher-tier action required |
| If rejected, required next step | <<FILL: return to CAPA owner to redesign the action plan, with a new due date>> |
| Reviewer (name, role, date) | <<FILL>> |
| QA approval (name, signature, date) | <<FILL>> |
Section F: Recurrence trigger
If this same root cause category recurs in a future event, a tier 4 or 5 justification that was accepted here does not automatically carry forward. Record the linkage so a repeat event is evaluated against the fact that a lower-tier fix already failed to prevent recurrence once.
| Field | Entry |
|---|---|
| This root cause category logged for future recurrence check | <<FILL: category label>> |
| If this category recurs, the next CAPA must reassess tiers 1 to 3 before accepting tier 4 or 5 again | Yes (standing rule) |
References
21 CFR 820.100(a) (corrective and preventive action procedures). ICH Q10, Pharmaceutical Quality System (CAPA effectiveness). 21 CFR 211.192 (investigation of discrepancies and failures, drugs).
Confirm the current version and clause numbers of each reference before issue.
Filled specimen
The following shows the form completed for an example event where the corrective action landed on a procedural control, so you can see the level of detail expected. The company, system, and numbers are illustrative; replace them with your own.
Section A. CAPA-2026-0187. Owner: M. Reyes, Lab Operations. Root cause: a manual sample login step allows an analyst to select the wrong test method from a dropdown list with no system validation against the sample type. Date: 02 July 2026.
Section C.
| # | Action | Tier |
|---|---|---|
| 1 | Revise the sample login work instruction to add a mandatory method-versus-sample-type cross-check step | 4 |
| 2 | Retrain all laboratory analysts on the revised work instruction | 5 |
Highest tier reached: 4.
Section D. Elimination considered: yes, removing the manual method selection entirely by auto-populating the method from the sample type field in the LIMS. Not selected for this CAPA because the LIMS configuration change requires a separate change control and validation cycle estimated at 90 days, longer than the risk justifies leaving the gap fully open. Engineering or system control considered: yes, a LIMS configuration rule that blocks submission when the selected method does not match the registered sample type. Not selected immediately for the same reason (requires the same change control cycle); adopted as the planned interim-to-permanent path below. Automated detection considered: yes, a daily exception report cross-checking method against sample type; deferred in favor of the permanent LIMS fix rather than building an interim reporting tool. Constraint driving the tier 4 choice: the higher-tier fix requires a validated LIMS configuration change that cannot be completed inside the CAPA’s standard timeline without leaving the gap open in the interim. Position: interim. Planned higher-tier action: LIMS configuration rule (tier 2), change control CC-2026-311, target date 30 September 2026. Compensating measure: a second-person verification of method selection added to the login step until the LIMS change is validated.
Section E. Justification accepted, on the condition that the tier 2 LIMS action is tracked to its 30 September 2026 date as a linked action, not treated as optional. Reviewer: A. Patel, 05 July 2026. QA approval: R. Gomez, 05 July 2026.
Section F. Root cause category logged: “manual selection from a system dropdown with no validation against a related field.” Standing rule applies.
Common inspection findings this form prevents
- A CAPA closes on a procedural or training fix with no record that a higher-tier control was ever considered.
- The same category of failure recurs a year later with an identical retraining action, because no one flagged that training already failed to prevent it once.
- An interim procedural fix quietly becomes permanent because nothing tracked the planned higher-tier action to completion.
- “Cost” or “timeline” cited as the reason for a lower-tier fix with no specifics, so the justification cannot be evaluated by a reviewer or an inspector.
How to adapt this form
- Set your form number and governing SOP in the header.
- If your CAPA record already has a tier column (see the companion CAPA Record form), trigger this form automatically whenever the highest tier logged there is 4 or 5, rather than relying on someone to remember.
- Decide locally whether Section E’s rejection path returns the CAPA to the owner automatically or requires a QA meeting; either is acceptable if it is consistent.
- If you run CAPA in an electronic quality management system, make the tier field and this justification a required gate before an action can be marked complete, not an optional attachment.
- Confirm every regulation in the references against the current published version before issue.