Prospective / Concurrent vs Retrospective
Validate before, during, or after routine production — and when each is allowed.
What a comparison is not
A comparison is SPEQ’s reading of how two published documents differ. Neither is the right answer, it is not a determination of which applies to you, and neither is summarised in a way that replaces reading it.
Process validation can be timed three ways. Prospective validation completes before the product is released for routine sale. Concurrent validation releases batches while validation is ongoing, justified for specific situations. Retrospective validation relied on accumulated historical data — an approach now largely obsolete under the lifecycle model. The timing you may use is tightly constrained by regulation and risk.
| ASPECT | PROSPECTIVE / CONCURRENT | RETROSPECTIVE |
|---|---|---|
| When it happens | Prospective: before routine supply · Concurrent: during, batch by batch | Retrospective: after the fact, from history |
| Default expectation | Prospective is the norm | Retrospective is discouraged / no longer accepted for new processes |
| Release timing | Prospective: release after validation · Concurrent: release as you validate, with justification | Product already made and often released |
| When concurrent is justified | Rare products, low volume, urgent medical need — with strong rationale and enhanced monitoring | N/A |
| Evidence basis | Designed PPQ runs with pre-defined criteria | Statistical review of historical batch data |
| Lifecycle fit | Aligns with the 3-stage lifecycle | Predates it; superseded by CPV |
Use prospective validation as the default — validate before routine supply. Use concurrent validation only in specific, justified cases (e.g., low-volume or medically urgent products) with a documented rationale and heightened monitoring.
Retrospective validation is essentially historical: it is not an acceptable strategy for validating new or changed processes today. Ongoing confidence now comes from continued process verification (Stage 3), not a retrospective data review.
Prospective is the norm, concurrent is the justified exception, and retrospective is effectively obsolete. The lifecycle model replaced "validate once, then review history" with "design it, qualify it, then continuously verify it." If someone proposes retrospective validation for a new process, that is a red flag; concurrent release must carry a documented justification and extra monitoring.
Prospective / Concurrent vs Retrospective: frequently asked questions
Common questions on how Prospective / Concurrent and Retrospective differ and when each applies.
Is retrospective validation still allowed?
It is no longer an accepted approach for validating new or changed processes. The lifecycle model (process design, qualification, continued process verification) replaced retrospective validation; historical data now supports continued process verification, not initial validation.
When can I use concurrent validation?
Concurrent validation — releasing batches while validation is still in progress — is reserved for specific, justified situations such as low-volume products, products made infrequently, or urgent medical need. It requires a strong documented rationale and enhanced monitoring, and quality-unit approval.
What is prospective validation?
Validating the process and completing the process performance qualification before the product is released for routine commercial supply. It is the default expectation for a new or changed process.
How does this relate to the three stages of process validation?
Prospective validation aligns with completing Stage 2 (process qualification) before routine supply, followed by Stage 3 (continued process verification). Concurrent validation overlaps Stage 2 with routine release under justification. Retrospective validation predates and is superseded by this model.