Protocol: Process Performance Qualification (PPQ)

This is a ready-to-use PPQ protocol. Replace every <<FILL: ...>> placeholder with your own specifics, set your document numbers and dates, and route it through your normal document control, review, and approval before any batch runs. A worked filled specimen follows the template so you can see how a completed section reads. Verify each cited regulation against the current source before you rely on it. This is general guidance to adapt, not legal or regulatory advice.

Approval page (execute only after all signatures)

Approval before execution is mandatory. Running any PPQ batch before this page is fully signed is a validation and data-integrity finding.

1. Objective

To demonstrate that the commercial manufacturing process for <<FILL: PRODUCT>>, operated at commercial scale with commercial equipment, materials, personnel, and procedures, reproducibly produces product that meets its predefined quality attributes. This protocol qualifies the process (Stage 2, PPQ); it does not requalify already-qualified facility, utilities, equipment, methods, or cleaning.

2. Scope

In scope: the integrated commercial process for <<FILL: PRODUCT, STRENGTH(S), PRESENTATION(S)>> at <<FILL: site>>, batches <<FILL: batch numbers / range>>. Validation approach: <<FILL: prospective / concurrent (attach justification) / continuous manufacturing per ICH Q13>>. Out of scope: equipment qualification, method validation, cleaning validation, and utilities qualification, which are prerequisites confirmed in section 5.

If a bracketing or matrixing approach is used across strengths or pack sizes, state it here and attach the bracketing rationale: <<FILL: bracketing/matrixing rationale or "not applicable">>.

3. Number-of-batches rationale

There is no regulatory requirement for a fixed number of batches. The number below is a conclusion of a documented risk assessment, not an assumption. Record the basis in the table; attach the full assessment as <<FILL: risk assessment reference>>.

More batches will be run if the executed data shows unexpected variability; the decision and its basis will be recorded.

4. Process description and control strategy

Summarize the process flow, the critical process parameters (CPPs) with their proven acceptable ranges from Stage 1, the critical quality attributes (CQAs), and the in-process controls. Cross-reference the development report <<FILL: ref>> and control-strategy document <<FILL: ref>>.

5. Prerequisites (all must be true and documented before batch 1)

Do not start execution with any prerequisite open.

6. Responsibilities

7. Enhanced sampling plan

PPQ sampling is deliberately denser than routine release sampling (“enhanced sampling”) to demonstrate within-batch uniformity and between-batch consistency. Sampling is targeted at where variability actually lives, not simply “more of the same sample.”

Between-batch design: arrange the batch set so the variability sources in section 3 appear (different material lots, operators, shifts, equipment trains). Record which batch spans which source: <<FILL>>. Sample-size rationale (e.g. ANSI/ASQ Z1.4 attribute scheme or a tolerance-interval variables approach, with stated confidence and coverage): <<FILL>>.

8. Acceptance criteria (set before execution, traceable to source)

Three layers. Every criterion must trace to a source; none may be added, widened, or “clarified” after data is seen.

Note on capability: a small number of PPQ batches is not enough data for a reliable Cpk. This protocol confirms specification compliance with margin and presents preliminary capability or trend only; formal capability is established in continued process verification (CPV).

9. Statistical methods (pre-registered)

State the analysis committed to before execution, so no method is chosen after seeing the data: <<FILL: descriptive statistics; control charts; stratified mean and RSD limits; tolerance intervals; preliminary capability with sample-size caveat>>. Software and version: <<FILL>>.

10. Test cases

Each attribute/parameter is a test case executed against section 8. Complete the actual value, verdict, tester, and date at execution.

11. Deviation and OOS handling

Any deviation or out-of-specification result during execution is raised and investigated through <<FILL: SOP-ID for deviations>> and <<FILL: SOP-ID for OOS>>, and its impact on the PPQ conclusion is assessed and documented. A deviation does not automatically fail PPQ, but this protocol does NOT pre-authorize ignoring any excursion. Every deviation is carried into the report (section 13).

12. Prerequisites for release of PPQ material

Product manufactured under this protocol may be released lot by lot only if it meets all release specifications and batch disposition is approved by QA. The process is not considered validated until the PPQ report concludes successfully. For concurrent validation, attach the pre-approved justification and the enhanced per-lot release controls: <<FILL: reference or "not applicable">>.

13. Summary and conclusion (completed at report stage)

Reference the PPQ report <<FILL: report number>>, which states results against every criterion, all deviations and their impact, the statistical analysis, the conclusion on qualification, and the CPV bridge (monitored parameters, control limits, review cadence).

14. References

FDA Guidance for Industry, Process Validation: General Principles and Practices (January 2011). 21 CFR 211.100, 211.110, 211.192 (production, in-process controls, batch review). EudraLex Volume 4, Annex 15: Qualification and Validation (2015). ICH Q8(R2), Q9(R1), Q10, Q11; ICH Q13 for continuous manufacturing where applicable. ANSI/ASQ Z1.4 and Z1.9 for attribute and variables sampling, referenced by number.

Confirm the current version and clause numbers of each reference before issue.

15. Attachments

Number-of-batches risk assessment; development/control-strategy report; master batch record; method references; sampling diagrams; bracketing rationale (if used); concurrent-validation justification (if used).

16. Revision history

Filled specimen (excerpt)

The following shows the number-of-batches rationale and part of the acceptance-criteria table completed for an illustrative immediate-release tablet. The company, numbers, and lots are illustrative; replace them with your own.

Number-of-batches rationale (illustrative):

Acceptance criteria (illustrative excerpt):

In this example the three batches were arranged so batch 1 used API lot A with operator team 1 (day shift), batch 2 used lot B with operator team 2 (evening shift), and batch 3 used lot A again with a mixed team, spanning the material and operator variability the rationale committed to.

Common inspection findings this protocol prevents

• “Three batches per industry standard” with no risk basis behind the number.
• Acceptance criteria added, widened, or clarified after results are seen.
• All batches run on one shift, one operator, one material lot, then a claim of reproducibility.
• A precise Cpk reported off three lots and treated as established capability.
• A deviation in the batch record that never appears in the report.
• Execution started before the approval page was fully signed.
• The statistical method chosen after seeing the data rather than pre-registered.

How to adapt this protocol

1. Set your protocol number, site, product, and application details in the approval page and scope.
2. Complete the number-of-batches rationale from your real Stage 1 knowledge and risk assessment; attach the assessment.
3. Build the enhanced sampling plan around where your process variability actually lives (blend locations, fill timeline, shelf map, column cycles).
4. Set every acceptance criterion before execution and trace each to a registered spec, a Stage 1 study, or a justified statistical standard.
5. Pre-register the statistical method in section 9.
6. Point the deviation and OOS cross-references to your real procedures.
7. Confirm every regulation in section 14 against the current published version before issue.