This is a ready-to-use plan for the process performance and product quality monitoring program that ICH Q10 names as element 1: the ongoing collection and trending that demonstrates a state of control rather than a single passing batch. 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 | Process Performance and Product Quality Monitoring Program, <<FILL: PRODUCT / SITE>> |
| Document number | <<FILL: PLAN-ID, e.g. MON-PLAN-001>> |
| Version | <<FILL: version, e.g. 1.0>> |
| Effective date | <<FILL: effective date>> |
| Program owner | <<FILL: role, e.g. Head of Quality / Process Owner>> |
| Applies to | <<FILL: product(s), process(es), and site(s) in scope>> |
1. Scope and objective
This plan defines how <<FILL: COMPANY NAME>> collects, trends, and acts on process performance and product quality data for <<FILL: PRODUCT / PROCESS>>, across <<FILL: commercial manufacturing / applicable lifecycle stage>>, so that the process is shown to stay within its defined parameters and the product within specification on an ongoing basis, not only at batch release. This program is the operational engine behind ICH Q10 element 1 and the Stage 3 continued process verification (CPV) commitment made in the process validation lifecycle. See continued process verification.
2. Approach and risk basis
Parameters and attributes monitored under this plan are selected from the process control strategy and the associated ICH Q9(R1) risk assessment, not chosen by convenience of what a historian happens to log. Every parameter or attribute in section 3 traces to a criticality rationale: a critical process parameter (CPP) or critical quality attribute (CQA) identified in development or technology transfer, or a key parameter whose drift has a documented link to a quality outcome. Non-critical parameters may still be monitored for process understanding, but they do not carry the same escalation weight.
3. What is monitored
| Parameter / attribute | Criticality | Data source | Sampling / frequency | Statistical tool |
|---|---|---|---|---|
<<FILL: e.g. fill weight>> | <<FILL: CQA / CPP / key>> | <<FILL: e.g. check-weigher, batch record>> | <<FILL: e.g. every unit, in-process>> | <<FILL: e.g. X-bar/R chart, Cpk>> |
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
<<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> | <<FILL>> |
Also include, at minimum: batch release results, in-process control results, stability trend data, environmental monitoring results (where applicable), complaint rate, and recurring deviation themes tied to this process. See statistics in quality (Cpk and control charts) for the statistical methods referenced above.
4. Alert and action limits
- Set alert and action limits inside the registered specification, derived from process capability, not set equal to the specification. An alert limit signals an investigation-worthy trend; an action limit requires a documented response before the next batch or lot proceeds.
- Document the derivation of each limit (statistical basis, number of batches used, and the review that approved it) so the limit itself is defensible, not arbitrary.
- Re-derive limits when the process changes materially or on the periodic review cycle in section 8; do not silently widen a limit because it is frequently exceeded.
5. Review cadence and escalation
| Trigger | Review | Owner | Escalation |
|---|---|---|---|
| Each batch | In-process and release data reviewed against alert limits | <<FILL: role>> | Alert crossed twice consecutively, or once at action limit, opens a deviation |
| Monthly | Trend review across all monitored parameters | <<FILL: role, e.g. Process Owner>> | Adverse trend routed to CAPA per <<FILL: SOP-ID>> |
| Quarterly | Consolidated trend package | Quality management review | Systemic issues escalated with a resourcing request |
| Annual | Full-year capability review feeding the annual product review | <<FILL: role>> | Feeds annual product review |
An alert or action limit crossing that generates no documented action is treated as a program failure in its own right, independent of whether the underlying batch passed.
6. Roles and responsibilities
| Role | Responsibility |
|---|---|
| Process owner | Defines and maintains the monitored parameter list and limits; reviews monthly trends |
| Quality Assurance | Confirms the program links to deviation, CAPA, and change control; approves limit changes |
| Statistics / quality systems | Maintains the trending tools and control charts; supports capability derivation |
| Site leadership | Reviews the quarterly and annual package in management review and resources corrective action |
7. Deliverables
| Deliverable | Reference | Owner |
|---|---|---|
| Monitored parameter and limit list | <<FILL>> | Process owner |
| Monthly trend report | <<FILL>> | Process owner |
| Quarterly management review package | <<FILL>> | Quality Assurance |
| Annual capability summary feeding the PQR | <<FILL>> | Quality Assurance |
8. Program review cycle
This plan and the limits it governs are reviewed at least <<FILL: e.g. annually>> and on any change that could affect the control strategy (process change, specification change, significant equipment change). The review is documented and confirms the monitored list still reflects current criticality.
9. Acceptance criteria
- Every monitored parameter traces to a documented criticality rationale.
- Alert and action limits are derived from capability, documented, and tighter than the registered specification.
- Reviews occur on the defined cadence with a named owner, and every limit crossing generates a documented, traceable action.
- Trend output is a direct input to management review and to the annual product review, not a parallel record nobody reads.
- Adverse trends are traceable into deviations or CAPA per section 5.
10. References
21 CFR 211.180(e) (annual review of records to evaluate quality standards). FDA, Process Validation: General Principles and Practices (2011), Stage 3 continued process verification. ICH Q8(R2) (Pharmaceutical Development) for the control strategy basis. ICH Q9(R1) (Quality Risk Management) for parameter criticality. ICH Q10 (Pharmaceutical Quality System), element 1.
Confirm the current version of each reference before issue.
11. Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL: date>> | <<FILL: author>> | Initial issue. |
12. Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Author | <<FILL>> | ||
| Reviewer (Process Owner) | <<FILL>> | ||
| Approver (Quality Head) | <<FILL>> |
Filled specimen
The following shows the monitored-parameter table and a trend outcome completed for an illustrative sterile fill-finish line, so you can see the level of detail expected. The company, product, and numbers are illustrative; replace them with your own.
| Parameter / attribute | Criticality | Data source | Sampling / frequency | Statistical tool |
|---|---|---|---|---|
| Fill weight | CQA | In-line check-weigher | Every unit, in-process | X-bar/R chart, Cpk monthly |
| Headspace oxygen | CPP-linked CQA | At-line analyzer | Every 30 minutes during fill | Individuals/moving-range chart |
| Bioburden, pre-filtration | CPP | QC microbiology | Per batch | Trend chart, alert at 2x historical mean |
Trend outcome: over the third quarter, fill weight Cpk held at 2.1, comfortably in control. Headspace oxygen showed a slow upward drift across four consecutive batches, crossing the alert limit on the fourth. The process owner opened a deviation the same week, traced the cause to a partially worn stopper seating tool, and a CAPA replaced the tooling and added a tooling wear check to the preventive maintenance plan. The quarterly trend package presented to management review showed the drift, the action taken, and the return to baseline over the next six batches, which is the kind of closed loop an inspector wants to see.
Common inspection findings this plan prevents
- A monitoring program exists and charts are produced, but no alert or action limit is defined, so a trend can drift indefinitely with no trigger for action.
- Limits are set equal to the registered specification, so “in control” and “passing” become indistinguishable.
- Monitored parameters were chosen historically and never reconciled against the current control strategy or risk assessment.
- Trend data is collected but never reaches management review in a form leadership can act on.
- An adverse trend is noted in a report but never opened as a deviation or CAPA.
How to adapt this plan
- Populate section 3 from your actual control strategy and Q9(R1) risk assessment, not from whatever the historian already logs.
- Set your review cadence and escalation thresholds to match your process risk and batch frequency.
- Point the cross-references in sections 5 and 6 to your real deviation, CAPA, and management review procedures.
- Confirm the statistical methods in use are validated (spreadsheet or software) per your CSV program.
- Confirm every regulation in section 10 against the current published version before issue.