This is a ready-to-use decision record for stating, before the PPQ protocol is finalized, what basis the campaign’s acceptance criteria rest on and whether the program intends to rely on concurrent release. Complete it during protocol drafting and attach it as a referenced input to the protocol itself. 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
| Field | Entry |
|---|---|
| Document title | PPQ Acceptance Criteria and Concurrent Release Basis for <<FILL: product / process>> |
| Document number | <<FILL: e.g. DR-PPQ-006>> |
| Version | <<FILL>> |
| Effective date | <<FILL>> |
| Linked PPQ protocol number | <<FILL>> |
| Document owner | <<FILL: e.g. Validation Lead>> |
1. Purpose
This record states, with a documented rationale, whether the PPQ protocol’s acceptance criteria are the commercial release specification and routine in-process limits, or a tighter provisional in-process limit set for the campaign, and whether the program intends to release PPQ batches commercially before the full PPQ report is approved.
2. Scope
| Dimension | Decision |
|---|---|
| Product / process in scope | <<FILL>> |
| Batch count in the campaign | <<FILL>> |
| Applicable flexibility guidance, if any | <<FILL: e.g. FDA CMC flexibilities for cell and gene therapy BLAs, May 2026, docket FDA-2026-D-4692, or not applicable>> |
| Out of scope | <<FILL: e.g. the sampling plan's statistical basis, covered under its own justification>> |
3. Responsibilities
| Role | Responsibility |
|---|---|
| Validation lead | Facilitates the decision, drafts the rationale, links it into the PPQ protocol |
| Manufacturing science / process development | Supplies the Stage 1 capability data supporting the acceptance-criteria basis chosen |
| Statistics | Confirms whether Stage 1 data statistically supports release-specification criteria or whether a tighter provisional limit is warranted |
| Regulatory affairs | Confirms the applicable flexibility guidance, if any, genuinely covers this product and is correctly cited |
| Quality Assurance | Approves the acceptance-criteria basis and the concurrent-release decision, including the hold triggers |
4. Acceptance-criteria basis
| Question | Answer |
|---|---|
| Chosen basis | <<FILL: release specification and routine in-process limits / tighter provisional in-process limits during PPQ>> |
| If release specification: what Stage 1 data demonstrates capability at that limit? | <<FILL>> |
| If tighter provisional limits: what are they, and what is the stated transition plan to routine limits? | <<FILL>> |
| Enhanced sampling plan reference | <<FILL: link to the sampling plan and its statistical basis>> |
5. Concurrent release decision
| Question | Answer |
|---|---|
| Will the program rely on concurrent release of PPQ batches ahead of the full PPQ report? | <<FILL: Yes/No>> |
| If Yes, guidance or policy basis | <<FILL>> |
| Condition required for a batch to release under this basis | <<FILL: e.g. independently meets commercial release specification, no open deviation on that batch>> |
| Hold triggers, campaign-wide | <<FILL: e.g. any deviation, trend, or failing batch anywhere in the campaign>> |
| Who has authority to invoke a hold | <<FILL: e.g. QA release authority>> |
6. Conclusion
| Field | Entry |
|---|---|
| Acceptance-criteria basis finalized and stated in the protocol | <<FILL: Yes/No>> |
| Concurrent release strategy finalized and stated in the protocol | <<FILL: Yes/No, or not applicable>> |
| Approved by (QA, name, date) | <<FILL>> |
7. References
FDA guidance, “Process Validation: General Principles and Practices” (January 2011). FDA guidance, “Chemistry, Manufacturing, and Controls Flexibilities for Developing Human Cellular and Gene Therapy Products for a Biologics License Application” (May 2026, docket FDA-2026-D-4692), where applicable to the product type. 21 CFR 211.22, quality control unit responsibilities.
Confirm the current version and applicability of each reference before issue; the 2026 flexibility guidance applies to human cellular and gene therapy BLAs specifically and should not be cited for a product type outside its stated scope.
8. Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL>> | <<FILL>> | Initial issue. |
9. Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Author (Validation) | <<FILL>> | ||
| Reviewer (Statistics) | <<FILL>> | ||
| Reviewer (Regulatory Affairs) | <<FILL>> | ||
| Approver (QA) | <<FILL>> |
Filled specimen
Extract for an example autologous cell therapy product with a two-batch PPQ campaign. Company and product are illustrative.
Acceptance-criteria basis: release specification and routine in-process limits, chosen because Stage 1 characterization across 8 development-scale runs showed viable cell dose and transduction efficiency consistently within the commercial release specification range across three donor sources, supporting capability at that limit without a tighter provisional threshold. Enhanced sampling plan reference: SP-CT-004, testing every in-process and release attribute at twice the routine post-validation frequency for the two PPQ batches.
Concurrent release decision: Yes. Basis: FDA’s May 2026 CMC flexibility guidance for cell and gene therapy BLAs, applicable because the product is a human cellular therapy with a limited number of qualified commercial-scale lots available at filing. Condition for release: each batch independently meets the full commercial release specification, with no open deviation against that batch at the time of release. Hold triggers: any deviation opened against either PPQ batch, any CQA trend outside the enhanced sampling program’s internal alert limit, or a failing result on either batch, halts commercial release of both batches pending investigation. Authority to invoke a hold: QA release authority, escalated to the validation lead and regulatory affairs immediately upon any trigger.
Conclusion: both the acceptance-criteria basis and the concurrent-release strategy are stated in PPQ protocol PPQ-CT-2026-011 section 11, referencing this decision record by number.
Common inspection findings this decision record prevents
- A PPQ protocol that states acceptance criteria as “per specification” with no traceable rationale connecting the choice to Stage 1 capability data.
- Concurrent release exercised informally once a batch happens to meet spec, with no protocol-stated basis or named hold trigger.
- A flexibility guidance cited for a product type outside its stated scope.
- A hold trigger left undefined, so a deviation on one campaign batch does not automatically prompt a review of sibling batches already released.
How to adapt this decision record
- Complete this record during protocol drafting, not after batch one starts; link it into the PPQ protocol by document number.
- Confirm in section 3 that Stage 1 data genuinely supports the acceptance-criteria basis chosen before defaulting to the release specification.
- If citing a flexibility guidance for concurrent release, confirm in section 5 that the product genuinely falls within its stated scope.
- State the hold triggers specifically enough that a QA release reviewer can apply them without further interpretation.
- Confirm every reference in section 7 against the current published version before issue.