Definition · Plain-language
Process validation
Process validation is the collection and evaluation of documented evidence, across the process lifecycle, that a manufacturing process is capable of consistently delivering quality product.
The step most authors miss
Doing CRediT right? Don’t stop at the statement.
A CRediT statement credits you inside one paper. The recognition CRediT was built for happens when those roles are tied to you, persistently. Sign in with your ORCID — free — and claim your CRediT contributions on casrai.org, the home of the standard. They become a verified, portable part of your identity, not a line that disappears into one PDF.
Free: claim your contributions, then export a journal-ready CRediT statement, schema.org structured data, JATS XML, CSV or BibTeX — and preview your public profile. A membership publishes that profile publicly and verifies the journals you serve.
A lifecycle, not a single event
Historically, process validation was often treated as a one-off exercise of making three successful batches. The FDA’s 2011 Process Validation guidance reframed it as a lifecycle spanning the whole commercial life of a process. The aim is continuous assurance that the process remains in a state of control, not a snapshot at launch. This lifecycle view aligns process validation with modern quality concepts such as Quality by Design (ICH Q8) and quality risk management (ICH Q9), where process understanding is built in from development.
The three stages
Stage 1, Process Design, defines the commercial process based on knowledge gained through development and scale-up, establishing a control strategy. Stage 2, Process Qualification, confirms that the designed process, in its actual facility with qualified equipment and trained staff, is capable of reproducible commercial manufacture. Stage 3, Continued Process Verification, provides ongoing assurance during routine production that the process stays in control, using collected data and trends. Each stage builds on the previous one, and findings can feed back to earlier stages.
Why “predetermined” specifications matter
A defining feature of validation is that the acceptance criteria are predetermined — defined before the validation work, based on product and process understanding. This prevents the circular trap of declaring whatever results occur to be acceptable after the fact. By setting specifications in advance and demonstrating the process consistently meets them, process validation provides objective, defensible evidence of capability. Significant changes to a validated process trigger change control and may require revalidation to confirm the state of control is maintained.
Key facts
At a glance
- Definition: documented evidence a process consistently meets predetermined specifications
- FDA framework: 2011 lifecycle guidance (three stages)
- Stage 1: Process Design
- Stage 2: Process Qualification
- Stage 3: Continued Process Verification
- Key principle: acceptance criteria are predetermined, not set after the fact
Common misconceptions
What people often get wrong
Often heard: Process validation means making three successful batches, then you are done.
Actually: The FDA’s 2011 guidance reframes validation as a three-stage lifecycle providing continuous assurance, not a one-off three-batch event. Stage 3, Continued Process Verification, monitors the process for as long as it is in commercial use.
Often heard: Acceptance criteria can be decided after seeing the validation results.
Actually: Specifications must be predetermined — defined in advance from product and process understanding. Setting criteria after the fact is circular and undermines the objective evidence validation is meant to provide.
Often heard: Once validated, a process never needs revalidating.
Actually: Significant changes to a validated process trigger change control and may require revalidation. Continued Process Verification also monitors ongoing performance to confirm the process stays in a state of control.
Going deeper
