This is a ready-to-use governance policy. It is not a restatement of the CAPA management procedure: the SOP sets the numeric due-date defaults for root cause, action completion, and effectiveness checks; this policy defines what happens, and who gets told, once a CAPA passes those dates. Replace every <<FILL: ...>> placeholder with your own specifics and route it through your normal document control, review, and approval. A worked filled specimen follows. Verify each cited regulation against the current source before you rely on it.
Document control header
| Field | Entry |
|---|---|
| Document title | CAPA Aging and Escalation |
| Document number | <<FILL: POL-ID, e.g. POL-QA-006>> |
| Version | <<FILL: version, e.g. 1.0>> |
| Effective date | <<FILL: effective date>> |
| Document owner | <<FILL: role, e.g. Head of Quality Assurance>> |
| Applies to | <<FILL: sites / departments in scope>> |
| Governing SOP | <<FILL: SOP-ID for CAPA management>> |
1. Purpose
This policy defines a graduated escalation ladder for CAPAs that are approaching, at, or past their due date, so that aging is visible to progressively more senior owners the longer it continues, and so that a pattern of aging across the CAPA population is itself reviewed as a quality system signal, not just as a collection of individually late records. An aging CAPA with no escalation path is a known, recurring inspection finding; this policy is the control that prevents it.
2. Scope
This policy applies to every open CAPA at the sites listed in the header, from the date root cause analysis is due through the date the effectiveness check is due. It applies to individual record aging (section 3.2) and to portfolio-level aging trends reviewed at management review (section 3.4). It does not replace the CAPA management procedure <<FILL: SOP-ID>>, which sets the numeric due-date defaults this policy escalates against, or the change control procedure that governs any resourcing or prioritization change made as a result of an escalation.
3. Policy statements
3.1 Aging tiers
Every open CAPA is classified against its current due date (root cause, action completion, or effectiveness check, whichever is the active milestone):
| Tier | Status | Definition |
|---|---|---|
| On track | Green | Due date not yet reached, no reason to expect a miss |
| Approaching due | Yellow | Within <<FILL: 15>> days of the due date, action not yet complete |
| Overdue | Amber | Past the due date, no approved extension on record |
| Significantly overdue | Orange | More than <<FILL: 60>> days past the due date, or a second unjustified extension |
| Chronically overdue | Red | More than <<FILL: 120>> days past the due date, or a third extension of any kind |
A CAPA classified Critical or expedited under the triage risk assessment moves through this ladder on a compressed timeline: <<FILL: e.g. half the day counts above>>, because the underlying risk is higher.
3.2 Escalation ladder
| Tier reached | Who is notified | Required action |
|---|---|---|
| Approaching due | CAPA owner and action owners (system-generated reminder) | Confirm on track or request an extension per the governing SOP before the due date passes |
| Overdue | Area management, in addition to the owner | Area management confirms a resourcing or prioritization blocker is not the cause, or clears it |
| Significantly overdue | Quality head, briefed individually outside the routine cycle | Quality head reviews the record directly and either directs a corrective path or accepts a documented, justified extension |
| Chronically overdue | Mandatory agenda item at <<FILL: quality governance board / management review>>, with a named executive sponsor assigned | The board can reassign the CAPA owner, reallocate resources, or direct that the aging itself be investigated as a quality event under section 3.3 |
Escalation notifications are automatic where the CAPA is tracked in an electronic quality management system; where tracked manually, <<FILL: role>> runs the aging report at least <<FILL: weekly>> and issues the notifications by hand.
3.3 Aging as its own quality event
A CAPA that reaches Chronically overdue, or that accumulates <<FILL: three or more>> extensions regardless of elapsed time, triggers a documented review of why the organization’s own process failed to close it. This is separate from the CAPA’s original root cause. It asks a different question: what about resourcing, prioritization, ownership clarity, or competing workload allowed this record to age past the point the escalation ladder was designed to prevent. The output is a short assessment, not a full CAPA, unless the review itself surfaces a systemic gap warranting one.
3.4 No silent extensions
An extension is never a quiet change to a due date. Every extension requires a documented, QA-approved justification and a revised date, entered before the original date passes wherever possible. An extension requested after the due date has already passed is itself logged as a miss against this policy, separate from the extension being granted.
3.5 Portfolio-level review
At every <<FILL: management review cycle>>, Quality Assurance presents the aggregate aging distribution across all open CAPAs (count by tier, trend over the prior <<FILL: 3>> cycles) and the count of CAPAs that triggered section 3.3. A rising aging trend, even with no single record individually escalated to Chronically overdue, is itself a finding that triggers a review of CAPA program resourcing independent of any one record’s cause.
4. Roles
| Role | Responsibility under this policy |
|---|---|
| CAPA owner | Keeps the record current, requests extensions before due dates pass, responds to escalation contact |
| Action owner | Delivers assigned actions by their due date or flags a blocker early enough for an extension to be requested in time |
| Area management | First escalation point at Overdue; resolves resourcing or prioritization blockers within their authority |
| Quality head | Escalation point at Significantly overdue; approves or directs correction of the aging pattern |
| Quality governance board / management review | Escalation point at Chronically overdue; holds authority to reassign ownership, reallocate resources, and direct a section 3.3 review |
| Quality Assurance | Runs the aging tracking, issues notifications, approves extensions, presents the portfolio trend |
5. Compliance and exceptions
Any deviation from this policy’s tiers or timelines (for example, a locally justified longer “approaching due” window for a specific product line) requires a documented, QA-approved exception on file, referencing this policy number. A pattern of individual non-compliance by a specific owner (repeated missed due dates, repeated late extension requests) is addressed through the organization’s existing performance management process; this policy governs the record and the escalation, not the personnel conversation.
6. References
ICH Q10, Pharmaceutical Quality System (management review of the CAPA system). 21 CFR 820.100 (corrective and preventive action; for devices now read through the Quality Management System Regulation incorporating ISO 13485:2016). 21 CFR 211.192 (investigation of discrepancies and failures, drugs).
Confirm the current version and clause numbers of each reference before issue.
Record generated: escalation log entry
| Field | Entry |
|---|---|
| CAPA number | <<FILL>> |
| Aging tier reached and date | <<FILL>> |
| Escalation contact made (name, role, date) | <<FILL>> |
| Action taken as a result | <<FILL>> |
| Section 3.3 review triggered? | Yes / No |
Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL: date>> | <<FILL: author>> | Initial issue. |
Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Author | <<FILL>> | ||
| Reviewer (QA) | <<FILL>> | ||
| Approver (Quality Head) | <<FILL>> |
Filled specimen
The following shows a CAPA’s escalation history under this policy, so you can see how the ladder plays out over time. The company, system, and numbers are illustrative; replace them with your own.
CAPA-2026-0091 (a corrective action for a recurring environmental monitoring excursion) had an action-completion due date of 15 April 2026.
- 01 April 2026, Approaching due: system reminder sent to the CAPA owner and the two action owners. One action owner flagged that a required equipment upgrade was delayed by a vendor lead time.
- 16 April 2026, Overdue: area management notified per section 3.2. Area management confirmed the vendor delay was outside the team’s control and approved requesting a documented extension.
- 17 April 2026: extension approved by QA to 15 May 2026, with the vendor delay as the justification, logged per section 3.4 before the extension took effect.
- 20 May 2026, Overdue again: the vendor delivered late a second time. A second extension was requested, moving the tier to Significantly overdue territory ahead of schedule because of the repeat extension.
- 21 May 2026: Quality head briefed directly per section 3.2. Quality head directed the CAPA owner to identify an alternate equipment source rather than approve a third extension against the same vendor cause.
- 10 June 2026: equipment installed through the alternate source, action completed and verified.
- Section 3.3 review: not triggered. Two extensions were logged with clear, non-repeating external cause (vendor performance), and the quality head’s intervention resolved it before a third extension or the Chronically overdue tier was reached.
The record shows the ladder doing its job: escalation happened automatically, the second extension pulled in the quality head early rather than waiting for a fixed day count, and the intervention (change the sourcing approach, not just extend again) prevented the record from ever reaching the governance board.
Common inspection findings this policy prevents
- A CAPA open for a year or more with a due date that has slid repeatedly, with no evidence anyone above the CAPA owner was ever aware.
- Extensions logged with no justification, or a justification added after the fact to match how long the CAPA actually took.
- A CAPA program with no aggregate aging metric presented at management review, so a systemic resourcing problem is invisible until an inspector finds it in the raw log.
- Escalation existing only as an informal, undocumented habit that varies by manager, rather than a consistent, auditable ladder.
- Chronic aging treated as a fact of life rather than as a signal that triggers its own review.
How to adapt this policy
- Set your document number, owner, and effective date in the header.
- Set the day-count thresholds in section 3.1 to match your own CAPA volume and risk profile; a smaller program may compress the ladder, a larger one may need finer tiers.
- Name the actual governance body in section 3.2 (a dedicated quality governance board, or the existing management review forum) rather than inventing a new committee if one already exists.
- If you run CAPA in an electronic quality management system, configure the tiers and notifications in section 3.2 as system rules rather than a manual weekly report.
- Confirm every regulation in section 6 against the current published version before issue.