What is the validation process in pharma?
The validation process is the documented evidence that a system, manufacturing process, or piece of equipment consistently produces results meeting predetermined specifications, as required under 21 CFR 211 and EU GMP Annex 15. It covers five disciplines — process, equipment, cleaning, computer system, and analytical method validation — each following a shared structure of risk assessment, protocol development, qualification, and ongoing verification.
Most validation programmes don't fail at IQ, OQ, or PQ. They fail at the word "validation" itself — five distinct disciplines folded into one term.
The Word "Validation" Covers Five Different Disciplines
Before scoping any validation activity, ask "which kind of validation is this" — not "how do we validate this." Conflating process validation with equipment qualification, or cleaning validation with CSV, is the most common root cause of scope creep and protocols that don't survive an inspector's first follow-up question.
| Discipline | What It Confirms | Governing Framework | Typical Qualification Method |
|---|---|---|---|
| Process Validation | The manufacturing process consistently produces product meeting predetermined quality attributes | FDA Process Validation guidance (2011); 21 CFR 211.100 & 211.110; EU GMP Annex 15 | Three-stage lifecycle: process design, process qualification (PPQ batches), continued process verification |
| Equipment Validation | A specific machine or system performs within its designed operating parameters | 21 CFR 211.63 & 211.68; EU GMP Annex 15 | IQ, OQ, PQ at installation and at defined re-qualification triggers |
| Cleaning Validation | Cleaning procedures remove residue, contaminants, and cleaning agents to acceptable carryover limits | 21 CFR 211.67; EU GMP Annex 15, Section 10 | Worst-case product/equipment matrix; swab and rinse sampling against calculated limits |
| Computer System Validation (CSV) | GxP software consistently performs its intended function within defined specifications | 21 CFR Part 11; EU Annex 11; GAMP 5 | GAMP 5 classification; risk-based IQ/OQ/PQ; FDA CSA-aligned documentation |
| Analytical Method Validation | A test method produces accurate, precise, and reproducible results | ICH Q2(R2); USP <1225> | Accuracy, precision, specificity, linearity, range, and robustness testing |
These disciplines are interdependent — a process can't be validated on unqualified equipment, and a batch record system feeding a PPQ run needs its own CSV first. Scoping them in isolation is where timelines quietly double.
What Process Validation Actually Requires
Process validation specifically is the collection and evaluation of data, from process design through commercial production, that establishes scientific evidence a manufacturing process consistently delivers quality product. FDA's 2011 Process Validation guidance replaced the old "three golden batches" mindset with a lifecycle approach.
The batch-count myth: FDA's 2011 guidance never mandates a fixed number of PPQ batches. "Three" is a leftover convention from the 1987 guideline. The correct count is whatever is statistically justified by the process's variability — sometimes fewer, often more.
The Three Stages of Process Validation
- Development and scale-up knowledge formally captured
- Critical process parameters (CPPs) and CQAs identified
- Facility & equipment qualified (IQ/OQ) before any PPQ run
- PPQ batches run under actual production conditions
- Ongoing statistical monitoring of CQAs and CPPs
- Trends feed periodic review and change control
Stage 3 is where most programmes under-invest. A process isn't "done" at PPQ sign-off — it enters years of routine production where Stage 3 monitoring is the only thing catching unnoticed drift.
The Universal Validation Process: Step by Step
Strip away the terminology, and every validation activity — process, equipment, cleaning, or computer system — follows the same eight-step skeleton.
- Classify & Scope: Set the risk tier — GAMP 5 category for systems, criticality tier for processes — before writing any protocol.
- Risk Assessment: Assess impact to patient safety, product quality, and data integrity to determine how much effort is justified.
- Requirements & Protocol Development: Write the URS or protocol with acceptance criteria derived for this system — not copied from a prior one.
- Installation Qualification (IQ): Confirm installation matches specification, with vendor documentation and baseline configuration recorded.
- Operational Qualification (OQ) / Process Qualification: Confirm operation within defined limits — scripted testing for software, or PPQ batches for a process.
- Performance Qualification (PQ) / Continued Verification: Confirm sustained real-world performance — the phase most often under-resourced relative to its risk.
- Report, Release & Traceability: Approve the Validation Summary Report, finalize the RTM, and release the system or process for GxP use.
- Change Control & Periodic Review: Every change is assessed against the validated scope, and validated state is reconfirmed on a set review cycle.
What Experienced Validation Leads Get Right
- Validation is not testing. Testing produces evidence; validation is the documented conclusion drawn from it. "We ran the tests" isn't "we validated it" — thin, evidence-only protocols are exactly what inspectors probe for.
- Rigor should scale to risk, not habit. Uniform rigor everywhere isn't caution — it's a resourcing decision that starves the genuinely high-risk items of attention.
- CSA changed CSV, not process validation. FDA's CSA guidance (Sept. 2025) permits risk-proportionate CSV documentation. It doesn't touch the three-stage process validation model — the two are often confused in both directions.
Where Validation Programmes Fail in Practice
- Validation treated as a one-time event: a report is signed with no continued verification or periodic review plan.
- Copy-pasted acceptance criteria: limits carried over from a similar process without re-derivation for actual risk.
- Change control disconnected from validation state: a system or process is modified without re-triggering the affected qualification steps.
- Manual documentation creating traceability gaps: spreadsheets make it hard to prove which requirement maps to which test evidence at inspection time.
How GoVal Manages the Validation Process
This eight-step skeleton is easy on paper and hard to sustain on spreadsheets across dozens of systems at different lifecycle stages. Most inspection findings trace back to that gap — not a missing step, but nobody able to prove, on demand, that it happened and is still current.
GoVal manages the full validation process for GxP systems in one VLMS: GAMP 5 classification, risk assessment, URS management, IQ/OQ/PQ execution, a live RTM, change control, and periodic review scheduled automatically by risk tier. Every step is a timestamped, audit-trailed record — retrievable in seconds, not reconstructed from folders. GoVal ships pre-validated with 21 CFR Part 11 and EU Annex 11 compliant audit trails and e-signatures. Most regulated teams deploy in 3–6 weeks.
Related Topics
Frequently Asked Questions
What is the validation process in pharma? +
What are the different types of validation in pharma? +
What are the three stages of process validation? +
What is the difference between process validation and equipment validation? +
What is the difference between process validation and computer system validation (CSV)? +
How long does the validation process take? +
How does GoVal support the pharma validation process? +
Run your entire validation process from one platform
GAMP 5 classification, risk assessment, IQ/OQ/PQ execution, live RTM, and periodic review scheduling — all in GoVal.
