Continued Process Verification (CPV) Plan

This is a ready-to-use continued process verification (CPV) plan, Stage 3 of the FDA three-stage process validation lifecycle. It defines what is monitored after PPQ, how, how often, and what triggers action, so a process stays in a demonstrated state of control across its commercial life. 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 reference against the current source before you rely on it.

Document control header

1. Purpose

This plan defines the ongoing monitoring program for <<FILL: product / process>> after PPQ, so the process is verified, with data, to remain in a state of control through commercial manufacturing, not merely assumed to remain valid because it once passed qualification.

2. Scope

3. Roles and responsibilities

4. Parameter selection rationale

Select CPV parameters from three sources: every CPP and CQA carried forward from PPQ, any parameter identified in process characterization as sensitive but not classified critical, and any parameter tied to a recurring deviation or complaint theme. Document why each selected parameter matters and, as importantly, why a parameter was excluded; “not selected” needs a reason on record, not silence.

5. Data sources

State how data moves from the source system into the statistical tool, manually or by validated interface, and who confirms the extract is complete and unaltered before analysis.

6. Statistical methods

Apply a control chart matched to the data’s own structure, not a default. Most CPV parameters produce a single result per batch, an assay, a yield, a pH, which calls for an individuals and moving range (I-MR) chart; a parameter read as several values from a constant-size subgroup within a batch calls for Xbar-R or Xbar-S instead, because averaging the subgroup separates within-batch noise from between-batch shift in a way I-MR cannot; count or rate data, defect counts, particulate counts, calls for a c, u, np, or p chart rather than either. State which applies to each parameter in the table below and why. Report process capability (Cp, Cpk, or Ppk once enough data points exist, typically <<FILL: minimum n, e.g. 20 to 30 batches>>) alongside the chart, and favor Ppk over Cpk once the data set spans enough batches to show batch-to-batch drift, since Ppk uses total variation and will not hide a wandering mean the way a within-subgroup Cpk can. State the control rules used (for example a point beyond three sigma, a run of points trending or on one side of the mean) and the capability target, for example <<FILL: Cpk >= 1.33>>, with the basis for that target.

7. Review cadence

8. Escalation triggers

A trigger firing does not itself mean the process failed; it means an investigation is owed and due within the stated timeframe. An alert with no logged response is a program gap, not a quiet pass.

9. APR/PQR linkage

CPV data feeds the annual product review (APR) or product quality review (PQR) required under <<FILL: 21 CFR 211.180(e) or EU GMP chapter 1, as applicable>>. This plan provides the trend data and capability results; it does not replace the APR/PQR’s broader scope (complaints, recalls, stability, change control). State the data handoff: <<FILL: format, system, and the review that consumes it>>.

10. Program health acceptance criteria

The CPV program is in an acceptable state when every parameter in section 4 has current data within its review cadence, every fired trigger has a logged, closed or open-with-owner investigation, and the annual program review in section 7 has confirmed the parameter list and limits still reflect the process. A program with silent gaps in data or unactioned triggers is not a functioning CPV program regardless of how the charts look.

11. References

FDA guidance, “Process Validation: General Principles and Practices” (January 2011), Stage 3. ICH Q10, Pharmaceutical Quality System. ICH Q12, Lifecycle Management. 21 CFR 211.180(e), Annual Product Review. PDA Technical Report No. 60 (Revised 2026), Process Validation: A Lifecycle Approach.

Confirm the current version of each reference before issue.

12. Revision history

13. Approvals

Filled specimen

Extract for an example oral solid dose product in its first year of commercial CPV. Company, product, and numbers are illustrative.

After 24 commercial batches, the hardness chart showed a run of 7 consecutive points above the historical mean, meeting the alert rule. The process owner investigated and traced it to a new granulation raw material supplier approved under change control CC-2026-071; hardness remained within the 6 to 10 kp acceptance range throughout, and Cpk stayed at 1.51. Disposition: no CAPA required, but the parameter’s control limits were reviewed and confirmed still appropriate at the annual program review, and the finding was included in that year’s APR.

The specimen shows what the plan exists to produce: a real signal, caught by the chart rather than by a complaint, investigated to a specific cause, and closed with data rather than a shrug, feeding directly into the APR.

Common inspection findings this plan prevents

• CPV data collected but never charted or reviewed against a defined rule.
• Parameters selected with no documented rationale, or PPQ-critical parameters quietly dropped from monitoring.
• A control chart alert with no logged investigation or response.
• Capability claimed from too few data points to be statistically meaningful.
• A chart type mismatched to the data’s structure, for example forcing arbitrary readings into an Xbar-R subgroup where no real subgroup exists, or applying an I-MR chart to count data that needs a c, u, np, or p chart instead.
• CPV run as a standalone exercise with no connection to the APR/PQR it is supposed to feed.

How to adapt this plan

1. Set your document number, product, site, and linked PPQ report in the header.
2. Build the parameter list in section 4 from your actual PPQ CPPs/CQAs plus any sensitive or complaint-driven additions, with a stated rationale for each.
3. Set real control rules and capability targets in section 6, with the basis for the target, not just “Cpk >= 1.33” by default.
4. Set review cadences and escalation timeframes in sections 7 and 8 that your team can actually sustain.
5. Confirm the APR/PQR data handoff in section 9 matches how your quality system actually consumes the trend data.
6. Confirm every reference in section 11 against the current published version before issue.