The lifecycle approach replaced a fixed number of validation batches with a requirement to understand and maintain the process. Many organizations adopted the vocabulary without changing the practice.
Stage 1: the work that makes Stage 2 straightforward
Process design should produce a documented control strategy: which parameters matter, what ranges were studied, and what evidence supports the limits. When this exists, qualification becomes confirmation. When it does not, qualification becomes discovery — usually at the worst time.
Stage 2: qualification with a defensible rationale
The number of batches must be justified by process understanding and variability, not selected by convention. The justification belongs in the protocol, written before execution.
Stage 3: continued process verification
Ongoing monitoring should be designed to detect drift, with defined statistical approaches and defined responses. A trending program that produces charts nobody acts on is not verification.
Change is the test of a validation program
A mature program can state, for any proposed change, what needs to be re-evaluated and why. If every change triggers either full revalidation or no assessment at all, the underlying process understanding is thin.