Usage Examples
- PPQ closed out clean, but we still owe a continued process verification plan before the first commercial release.
- The validation protocol and its acceptance criteria were approved before a single batch ran.
- Three PPQ batches is our starting position; the blend uniformity spread may force a fourth.
What is Process Validation (PV)?
Process validation is the documented, lifecycle-long demonstration that a commercial manufacturing process reliably yields conforming product, distinguished from equipment qualification by proving the process itself, not the machinery, performs within defined limits.
Process validation exists because you cannot test quality into a batch after the fact. Sampling a handful of units from a lot of hundreds of thousands will not detect a defect rate that still harms patients, and destructive tests consume the very units they judge. Process validation moves the burden of proof upstream: the process is shown capable, so the release test confirms rather than discovers.
Process validation covers the commercial manufacturing process for drug products and drug substances, from design through routine production. Its boundary is narrower than most teams assume. Equipment and utility qualification, analytical method validation, cleaning validation, and computer system validation each run under their own protocols and acceptance criteria. Process validation consumes their outputs as prerequisites; it does not absorb them or substitute for them.
Process validation is executed protocol-first: acceptance criteria are approved before any qualification batch runs, execution is documented as it happens rather than reconstructed later, every deviation is recorded and justified, and in-process controls are applied to samples from each batch. Process validation then continues past the qualification report, because the same in-process controls and specification limits govern routine commercial production indefinitely.
Not to be confused with
- Equipment qualification (IQ/OQ/PQ)
- qualification proves one asset was installed and operates as specified. Process validation proves the process running on that asset yields conforming product batch after batch. Qualified equipment is an input to validation, not evidence of it.
- Process verification
- verification confirms a batch already made met its specifications. Validation establishes confidence that the next batch will. Passing release testing on three lots is verification and does not discharge the validation obligation.
- Cleaning validation
- a separate exercise proving residues are removed between products. It shares the protocol machinery but has different acceptance criteria and a different failure mode: cross-contamination rather than non-conformance.
- Computer system validation (CSV)
- CSV proves the software controlling or recording the process behaves as intended. It is scoped to the system. A validated MES does not validate the process the MES runs.
There is no single "process validation" section in Part 211. The enforceable obligations sit in the production and process control subpart.
What you must do
- 1Follow the approved written production and process control procedures during execution, and document performance at the time of performance rather than afterwards21 CFR 211.100(b)
- 2Record and justify any deviation from a written production or process control procedure21 CFR 211.100(b)
- 3Establish and follow written procedures describing the in-process controls, tests, or examinations conducted on appropriate samples of in-process materials from each batch21 CFR 211.110(a)
- 4Include, where appropriate, controls for tablet or capsule weight variation, disintegration time, adequacy of mixing, dissolution time and rate, clarity or completeness or pH of solutions, and bioburden21 CFR 211.110(a)
- 5Derive in-process specifications from previous acceptable process average and process variability estimates, applying suitable statistical procedures where appropriate21 CFR 211.110(b)
Common mistakes
Treating three PPQ batches as the legal requirement
no section of Part 211 names a batch count. 211.110(b) ties in-process specifications to prior process average and variability estimates using suitable statistical procedures. Running three lots on a high-variability process buys a signed report and a rejected commercial batch later.
Documenting execution after the campaign ends
211.100(b) requires performance to be documented at the time of performance. Back-filled batch records convert a technically sound validation into a data-integrity finding, and the underlying batches become unusable evidence regardless of how the process actually performed.
Closing validation as a project once the report is signed
211.110(a) requires in-process controls on appropriate samples of each batch, not only the qualification lots. A process that drifts after PPQ is out of control today, and the clean validation report is the reason nobody noticed.
When This Matters
- PPQ closed out clean, but we still owe a continued process verification plan before the first commercial release.
- The validation protocol and its acceptance criteria were approved before a single batch ran.
- Three PPQ batches is our starting position; the blend uniformity spread may force a fourth.
Frequently Asked Questions
FDA's January 2011 process validation guidance splits the work into Stage 1 Process Design, Stage 2 Process Qualification, and Stage 3 Continued Process Verification. Stage 1 builds process knowledge from development data, Stage 2 demonstrates the commercial-scale process is reproducible, and Stage 3 monitors the process for the rest of its commercial life.
Related Use Cases
- Pharma Use Cases
Cut NDA and sNDA prep time by 60% with AI-assisted drafting and automated readiness checks
- Biotech Use Cases
Compress IND prep from 8-12 weeks to under 3 weeks with AI-assisted drafting and validation
- CMC Workflows
Track ICH quality guidelines automatically and get alerts when changes impact your products
- Quality/QA Workflows
Track GxP regulation changes and enforcement trends
