PPQ Protocol Skeleton

This is a ready-to-use process performance qualification (PPQ) protocol skeleton, Stage 2 of the FDA three-stage process validation lifecycle. 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 execution. A worked filled specimen follows. Verify each cited reference against the current source before you rely on it.

Document control header

1. Purpose

This protocol defines the prerequisites, batch matrix, critical parameters, sampling, and analysis needed to demonstrate that the commercial manufacturing process for <<FILL: product>> performs consistently and delivers product meeting predetermined quality attributes, per FDA Stage 2 process validation. A successful PPQ campaign, executed under this protocol, is the basis for releasing the process to commercial distribution.

2. Scope

3. Responsibilities

4. Prerequisites

Do not start PPQ execution until every prerequisite below is confirmed true, with evidence referenced.

5. Batch matrix

State the statistical or risk-based rationale for the batch count in section 2; three is common but is not a rule, and a defensible rationale traces the number to Stage 1 variability and product risk, not to convention, with a higher-risk or more variable process needing more.

6. Critical process parameters (CPPs)

Every CPP range here traces to the process characterization referenced in section 4; a range invented for this protocol with no upstream basis is not defensible.

7. Critical quality attributes (CQAs)

8. Sampling plan

Sample enough to characterize within-batch variability, not only to confirm a single average result. State for every point whether the acceptance logic is an attribute plan, pass or fail against a defined criterion, or a tolerance-interval plan, a confidence-and-coverage claim about the population; a statistically weak or mismatched sampling plan cannot support a strong conclusion, regardless of how the batches perform.

9. Deviation handling during PPQ

Any excursion outside a CPP range, any Fail against a CQA acceptance criterion, or any departure from this protocol or the master batch record is recorded as a deviation per <<FILL: deviation SOP-ID>> at the point it is found. Each deviation states the affected parameter or attribute, root cause where determinable, and an impact assessment on the batch’s fitness to support the PPQ conclusion. A deviation does not automatically fail the batch, but an unassessed or unexplained deviation blocks the report conclusion. Do not restart or discard a PPQ batch without a documented, QA-approved rationale.

10. Data analysis plan

State in advance, before batches execute, how the data will be analyzed: descriptive statistics and trend plots for each CPP and CQA, process capability where enough data points exist, and an explicit pass/fail call against each acceptance criterion in sections 6 and 7. Fixing the analysis method after seeing the data, or dropping a batch with no documented, QA-approved reason, invalidates the conclusion.

11. Acceptance criteria for the campaign

PPQ succeeds only when every batch in the matrix is manufactured per the master batch record and this protocol, every CPP stayed within its acceptable range or a deviation demonstrates the excursion did not affect quality, every CQA met its acceptance criterion, and no open deviation remains unresolved. A single unexplained CQA failure is not eligible for a passing conclusion regardless of the other batches’ performance. State explicitly whether the CQA acceptance criteria above are the commercial release specification or a tighter provisional in-process limit, and whether the campaign relies on concurrent release ahead of the full PPQ report; the paired PPQ Acceptance Criteria and Concurrent Release Basis decision record is where that basis and any hold triggers are documented and should be referenced here by number.

12. Report commitments

The validation lead issues a PPQ summary report on completion, covering: batch-by-batch results against every CPP and CQA, all deviations and their resolution, the statistical analysis from section 10, an explicit conclusion on whether the process is validated for commercial use, and the transition plan into continued process verification (Stage 3). QA approves the report before commercial release of PPQ-derived batches, where applicable.

13. References

FDA guidance, “Process Validation: General Principles and Practices” (January 2011). ICH Q8(R2), Pharmaceutical Development. ICH Q9, Quality Risk Management. EU GMP Annex 15, Qualification and Validation.

Confirm the current version of each reference before issue.

14. Revision history

15. Approvals

Filled specimen

Extract for an example oral solid dose product, three-batch PPQ campaign. Company, product, and numbers are illustrative.

Results: all three batches stayed within the compression force range; PPQ-2 showed a brief excursion to 14.3 kN for four minutes during a raw-material lot changeover, logged as DEV-2026-0088. Impact assessment: hardness results bracketing the excursion remained within 6 to 10 kp, so the deviation was closed with no impact on the CQA. All CQAs met acceptance criteria across all three batches. Conclusion: process validated; transitioned into continued process verification per the linked CPV plan.

The specimen shows what a reviewer checks for: a real excursion, not a clean fiction, assessed against the CQA it could plausibly affect, closed with data rather than assertion, before the conclusion was written.

Common inspection findings this protocol prevents

• CPP ranges invented for the PPQ protocol with no traceable basis in process characterization data.
• A batch count set by convention with no risk or statistical rationale documented.
• The data analysis method decided after the results were seen.
• A CQA failure explained away with no root cause or impact assessment.
• A PPQ report that concludes “validated” while a deviation remains open.
• Sampling sized to confirm an average result with no view of within-batch variability.
• A sampling plan with no stated attribute-versus-tolerance-interval basis, so the sample size cannot be tied to any actual confidence or coverage claim.

How to adapt this protocol

1. Set your document number, product, site, and linked Stage 1 and transfer references in the header.
2. Populate the CPP and CQA tables in sections 6 and 7 directly from your process characterization data, not from a generic list.
3. Set the batch count and matrix in section 5 from a documented risk or statistical rationale.
4. Size the sampling plan in section 8 to characterize variability, and lock the analysis method in section 10 before execution starts.
5. Point section 9 to your real deviation SOP, and confirm every reference in section 13 against the current published version before issue.