PPQ Deviation Criticality Pre-Classification Plan

Document type	Plan
Topic area	Process Validation
Level	Advanced
Updated	September 2026

This is a ready-to-use plan for agreeing, before PPQ batch one, what class a deviation arising during the campaign falls into and what that classification does to the affected batch and to the campaign’s concurrent-release hold trigger. Complete it during protocol drafting so the classification criteria exist before anyone is deciding under schedule pressure with a real deviation and a batch sitting in the warehouse. Replace every <<FILL: ...>> placeholder with your own specifics and route it through your normal document control, review, and approval. A worked filled specimen follows.

Document control header

Field	Entry
Document title	PPQ Deviation Criticality Pre-Classification Plan for `<<FILL: product / process>>`
Document number	`<<FILL: e.g. PLN-DEV-005>>`
Version	`<<FILL>>`
Effective date	`<<FILL>>`
Linked PPQ protocol number	`<<FILL>>`
Linked acceptance-criteria and concurrent-release basis	`<<FILL: ref, or not applicable>>`
Document owner	`<<FILL: e.g. Quality Assurance>>`

1. Purpose

This plan states, with pre-agreed criteria, how a deviation arising during the PPQ campaign is classified, and what that classification does to the affected batch’s disposition and to any campaign-wide concurrent-release hold trigger. The goal is a classification decided in advance, applied consistently, not argued case by case once a real deviation exists.

2. Scope

Dimension	Decision
Product / process / campaign in scope	`<<FILL>>`
Batch count in the campaign	`<<FILL>>`
Does the campaign rely on concurrent release?	`<<FILL: Yes/No; if Yes, link the concurrent-release basis document>>`
Out of scope	`<<FILL: e.g. deviation investigation methodology itself, covered under the site's deviation SOP>>`

3. Responsibilities

Role	Responsibility
Validation lead	Drafts this plan and links it into the PPQ protocol before batch one
Quality Assurance	Owns the real-time classification decision for any deviation arising during the campaign, applying the criteria below rather than a fresh judgment call each time
Manufacturing / site operations	Reports a deviation as soon as it is identified, without pre-judging its classification
Regulatory affairs	Confirms the classification framework is consistent with how the campaign’s concurrent-release or batch-count flexibility basis, if any, is described in the filing

4. Classification criteria

Set the criteria below before batch one. During the campaign, classify each deviation against these written criteria; where a deviation is genuinely uncertain between two classes, apply the higher class until the investigation resolves it.

Class	Definition	Example patterns for this process	Effect on the affected batch	Effect on sibling batches
Critical	Directly implicates a CQA, the sterility or potency assurance chain, or a condition the acceptance criteria assume held	`<<FILL: e.g. an environmental monitoring excursion on the fill line, a CQA result trending toward its limit>>`	Hold pending investigation	Hold every batch in the campaign per the concurrent-release trigger, if applicable
Major	Affects a documented, non-CQA process parameter or a control excursion outside its normal range, with no CQA linkage established yet	`<<FILL: e.g. a hold-time limit exceeded by a small margin with no observed CQA impact>>`	Hold pending investigation	No automatic hold, unless the investigation later implicates a shared cause
Minor	A documentation or procedural gap with no plausible product-quality impact	`<<FILL: e.g. a late timestamp on an unaffected step>>`	No hold; logged	No effect

5. Escalation and documentation

Step	Requirement
Initial classification	Made by `<<FILL: e.g. QA on shift>>` within `<<FILL: timeframe, e.g. same business day>>`, citing the specific criterion matched
Reclassification	Requires written justification citing new information; a downgrade from Critical to Major or Minor requires QA management approval
Record	Each deviation’s classification, citation, and disposition recorded in `<<FILL: deviation log / eQMS reference>>`, cross-referenced to the PPQ batch record

6. Conclusion

Field	Entry
Classification criteria finalized and stated in the protocol	`<<FILL: Yes/No>>`
Approved by (QA, name, date)	`<<FILL>>`

7. References

See the paired article, PPQ readiness: the prerequisites that decide success before batch one, for the reasoning behind pre-classifying deviation criticality and how it connects to the concurrent-release hold trigger. The paired PPQ acceptance criteria and concurrent release basis form, where the campaign relies on concurrent release, for the hold trigger this plan’s classification feeds. 21 CFR 211.192, review and investigation of an unexplained discrepancy.

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 (Manufacturing)	`<<FILL>>`
Approver (QA)	`<<FILL>>`

Filled specimen

Extract for an example three-batch PPQ campaign for a monoclonal antibody drug substance, relying on the release-specification acceptance basis with no concurrent-release strategy in use.

Class	Example patterns for this process	Effect on the affected batch	Effect on sibling batches
Critical	A bioburden or endotoxin result trending toward its action limit; a chromatography step run outside its proven acceptable range with no data showing the resulting pool still meets specification	Hold pending investigation	N/A, campaign does not rely on concurrent release; full PPQ report still gates all commercial release
Major	A hold-time limit exceeded by less than 10 percent with the affected in-process CQA result within specification	Hold pending investigation	No automatic hold
Minor	A batch record entry corrected same-shift for a transcription error with no process impact	No hold; logged	No effect

A deviation arose during batch two: a chromatography column’s proven acceptable range for conductivity was exceeded by 3 percent for approximately four minutes during equilibration, before returning to range for the loading step. QA classified it Major, not Critical, citing that the excursion occurred during equilibration rather than loading or elution, and that in-process pool testing showed the resulting CQAs within specification with no trend toward the limit; the classification and its basis were recorded the same shift. Because the campaign did not rely on concurrent release, batch three was not automatically held, but the investigation’s root cause, a flow controller calibration drift, triggered a proactive calibration check on the equipment used for batch three before it started.

Common inspection findings this plan prevents

A deviation classified in the moment specifically to avoid a campaign-wide hold, with no written criterion cited for the decision.
A concurrent-release hold trigger that exists on paper but has no defined process for deciding, in real time, which deviations actually meet it.
A downgraded classification with no documented justification or management approval behind the change.
Deviation classification left as an informal norm nobody wrote down until the first real deviation of the campaign forces the question.

How to adapt this plan

Set the classification criteria in section 4 to match this specific process’s actual CQAs and known failure modes, not a generic list copied from another product.
If the campaign relies on concurrent release, link this plan explicitly to the hold-trigger language in that decision record, so the two documents describe the same mechanism consistently.
Confirm section 5’s escalation timeframe and record location match how your site’s deviation system actually operates.
Route this plan for approval during protocol drafting, not after the first deviation of the campaign has already happened.