Common Triggers
Revalidation is typically triggered by a change with genuine potential to affect a previously validated process, method, or system's performance, including a formulation change, a significant equipment change or replacement, a manufacturing site transfer, a raw material source change with potential to affect process behavior, or a sustained adverse trend identified through ongoing continued process verification data suggesting the process may no longer be performing within its originally validated envelope. Not every change warrants full revalidation, and the genuine trigger determination requires risk-based assessment of the specific change's actual potential impact on previously validated performance rather than a simple, mechanical rule automatically requiring revalidation for any change whatsoever, however minor.
Risk Assessment Approach
Determining whether a specific change warrants revalidation, and if so what scope of revalidation is genuinely needed, should follow a formal risk assessment considering the change's nature, its relationship to previously identified critical process parameters or critical quality attributes, and available supporting data such as similar changes previously evaluated for comparable processes. This risk assessment should be documented within the change control record for the specific triggering change, discussed in the related change control article, ensuring the revalidation decision is transparently connected to and traceable from the specific change that prompted it.
Scope of Revalidation
Where revalidation is warranted, its scope should be proportionate to the actual change and its assessed potential impact, ranging from full revalidation addressing every aspect of the original validation program for a significant change with broad potential impact, to partial revalidation targeting specifically the process elements or quality attributes plausibly affected by a more limited, narrowly scoped change. A change affecting only a single, well-isolated process step generally does not warrant full revalidation of the entire manufacturing process, provided the risk assessment genuinely confirms the change's impact is indeed limited to that specific isolated step without broader, less obvious downstream implications.
Documentation
The revalidation determination, including the underlying risk assessment reasoning and the resulting scope decision, should be documented as part of the associated change control record, providing clear, traceable justification for both the decision to revalidate, or conversely the decision that revalidation was not warranted, and, where revalidation is pursued, the specific scope selected. This documentation becomes particularly important during regulatory inspection, where inspectors routinely examine whether significant changes were appropriately evaluated for revalidation need and whether that evaluation's conclusion is adequately justified by genuine, documented reasoning.
Distinguishing Revalidation From Routine Continued Verification
Revalidation, a discrete, triggered activity responding to a specific identified change or concern, should be distinguished from Stage 3 continued process verification, discussed in the related process validation lifecycle article, which is an ongoing, routine monitoring activity occurring continuously throughout commercial production regardless of whether any specific triggering change or concern has occurred. A sustained adverse trend identified through continued verification monitoring can itself become a revalidation trigger, connecting these two distinct concepts, but continued verification's ongoing routine monitoring function should not be confused with the more discrete, triggered nature of revalidation itself.
Revalidation for Analytical Methods and Computer Systems
Revalidation triggers apply not only to manufacturing processes but equally to analytical methods, where a significant method modification may warrant partial or full revalidation depending on which validated parameters the modification could plausibly affect, and computer systems, where a significant software update or configuration change similarly warrants revalidation assessment following the same fundamental risk-based principles applied to process revalidation.
Avoiding Both Over- and Under-Triggering
A mature revalidation trigger framework avoids both extremes: reflexively triggering full revalidation for every change regardless of genuine risk, which wastes resources and can create validation program fatigue undermining its own credibility and rigor over time, and, conversely, under-triggering revalidation by failing to recognize when a change genuinely does warrant reassessment, which risks continued reliance on a validated status no longer genuinely representative of the actual current process, method, or system as changed.
Building Institutional Trigger Criteria Over Time
Facilities benefit from documenting and refining their own institutional revalidation trigger criteria over time, informed by accumulated experience regarding which specific change types have historically proven genuinely consequential for their own particular processes and systems, allowing progressively faster, more consistent revalidation determinations for change types with an already well-established track record rather than treating every individual change determination as an entirely novel assessment starting completely from scratch.
Leave your rating