Question 8 of 20 Fundamentals Concept
How do prospective, concurrent and retrospective validation differ?
Short answer
Prospective validation is completed before any batch is released. Concurrent validation releases batches while validation is still running, which EU Annex 15 allows only in exceptional, justified cases. Retrospective validation, built from historical batch data, is no longer acceptable under Annex 15.
Why
Prospective validation is the default. Annex 15 says processes using the traditional approach should undergo prospective validation, wherever possible, before the product is certified. The FDA's 2011 guidance similarly expects PPQ to be completed successfully before commercial distribution.
Concurrent validation means routine production starts before the validation program is complete. Annex 15 permits it only in exceptional circumstances with a strong benefit-risk ratio for patients, such as a medicine in short supply. The decision must be justified, recorded in the validation master plan and approved, and each batch must have enough data to show it is uniform and meets criteria before the QP certifies it.
The FDA guidance calls this concurrent release of PPQ batches and gives examples such as infrequently made products or very short-lived products, again with careful oversight. Retrospective validation used historical production data to argue that a process already in use was validated. Annex 15 states plainly that it is no longer an acceptable approach, because past data were not collected under a plan designed to detect variability.
For example, a legacy product with ten years of passing batches still needs prospective work if it moves site. Historical data remain useful for setting the validation strategy and for the hybrid approach, but not as the validation itself.
A strong answer covers
- Prospective as the default before release
- Concurrent only in exceptional, justified cases
- Each concurrent batch assessed before certification
- Retrospective no longer acceptable in Annex 15
- Historical data still informs strategy
Common mistakes
- Treating concurrent validation as a routine way to save time.
- Claiming years of passing batches validate a process retrospectively.
- Releasing concurrent batches before the batch-level data have been evaluated.
The interviewer might ask next
What conditions would you set before agreeing to concurrent release of a PPQ batch?