Requalification vs Revalidation in Pharma: When You Must Repeat Proof of Performance
Definition
Requalification is the repeat (full or partial) execution of qualification activities—typically IQ, OQ, and/or PQ—to confirm that equipment, utilities, or systems still perform as intended after time, maintenance, relocation, or change. Revalidation is the repeat (full or partial) execution of validation activities to confirm that a process, method, cleaning program, or computerized system still consistently meets predefined requirements after change or evidence of drift. In practical terms: requalification is often associated with equipment/systems, while revalidation is often associated with processes and validated programs—but both exist to maintain the validated state.
Why This Difference Matters
Teams often use these terms interchangeably, and that’s where audit trouble starts. The difference matters because it affects:
- What you re-test (installation checks vs performance evidence)
- How deep you go (partial vs full repeat)
- How you justify decisions in change control
- How you document ongoing compliance and validated state maintenance
Auditors don’t care about your terminology as much as they care about whether your decision is logical, risk-based, and supported by evidence.
Requalification vs Revalidation (Clear Comparison)
| Aspect | Requalification | Revalidation |
|---|---|---|
| Main focus | Confirm equipment/system/utility still meets qualification requirements | Confirm process/method/cleaning/system still meets validation requirements consistently |
| Typical documents | IQ/OQ/PQ protocols and reports (repeat/partial) | Validation protocols and reports (repeat/partial) |
| Common targets | Equipment, utilities, facility systems, instruments | Manufacturing process, cleaning program, analytical method, CSV scope |
| Main trigger types | Relocation, major maintenance, replacement of critical components, periodic schedule | Process changes, repeated failures, new product introduction, trend drift, major software/config changes |
| Typical question answered | Does it still operate correctly within defined limits? | Does it still consistently produce compliant outcomes? |
When Requalification Is Typically Triggered
Requalification is often triggered when there’s a reasonable chance that installation, configuration, or operational performance may have changed. Typical triggers include:
- Relocation: moving equipment or systems to a different room/site
- Major maintenance: replacing critical parts (motors, controllers, sensors)
- Utility modifications: changes in HVAC zones, PW loops, compressed air systems
- Control system changes: PLC/SCADA updates affecting alarms or sequences
- Periodic schedule: planned requalification based on risk and history
- Repeated issues: recurring alarms, drift, unexplained excursions
Requalification can be partial. For example, you may repeat a subset of OQ tests focusing on modified functions rather than repeating the entire qualification suite.
When Revalidation Is Typically Triggered
Revalidation is triggered when process consistency or validation assumptions may no longer hold. Typical triggers include:
- Process changes: parameter range changes, recipe changes, scale changes
- Material changes: new API source, excipient grade change, supplier change with different properties
- Equipment changes affecting process: new blender design, new filter type, different dryer model
- Repeated deviations / OOS / OOT: trending signals indicating drift
- Cleaning changes: new product, new worst case, new equipment surfaces, new detergent
- Computer system changes: major upgrades/configuration changes impacting GMP functions and records
- Regulatory or knowledge changes: new risk understanding requiring updated controls
Like requalification, revalidation can be partial if a risk-based impact assessment proves only certain areas are affected.
Periodic Requalification vs Event-Driven Requalification
Requalification is often managed in two ways:
- Periodic: performed at defined intervals based on risk, history, and criticality.
- Event-driven: performed after changes, repairs, relocations, failures, or trends.
A risk-based program usually uses both: scheduled reviews for stability plus event-based triggers for control.
How Change Control Decides Whether You Need Requalification or Revalidation
Change control impact assessment is the decision engine. A strong impact assessment asks:
- Does the change affect any critical requirements, alarms, controls, or performance features?
- Does it change a parameter range, material attribute, or process endpoint that influences CQAs?
- Is the change reversible? Is the risk detectable before product impact?
- What evidence (data/trends/history) supports reduced or increased testing?
Then it assigns the required action: no action, partial requalification, partial revalidation, or full repeat.
Mini Examples (Realistic Scenarios)
Example 1: Requalification Trigger
A tablet press load cell is replaced and the press is recalibrated. Because measurement and control functions can shift, you may perform partial OQ (sensor calibration verification, alarm verification, challenge checks) and confirm key IPC performance under controlled conditions.
Example 2: Revalidation Trigger
You change the API supplier and the new API has a different particle size distribution. If this affects blend uniformity or dissolution, revalidation (or at least targeted PPQ/verification batches) may be needed to confirm the process still consistently meets quality outcomes.
Example 3: Both Needed
You replace a granulator with a different model and update its control system. You may need requalification for the equipment functions and revalidation for the process performance because both installation/operation and product outcomes are impacted.
Common Mistakes (Audit Traps)
- Using the terms loosely: calling everything “revalidation” without defining what was repeated and why.
- No impact assessment: decisions made without a documented risk-based rationale.
- Over-retesting: repeating full IQ/OQ/PQ unnecessarily (wastes time, still doesn’t guarantee better control).
- Under-retesting: major changes justified as “minor” with no evidence.
- Ignoring trends: repeated excursions or OOT signals not triggering re-evaluation.
- Poor documentation linkage: no clear connection between change control and requalification/revalidation scope.
Audit-Ready Talking Points
- Requalification confirms equipment/systems still meet qualified performance after change/time/events
- Revalidation confirms continued consistent compliance of processes or validated programs after change/drift
- Decisions are based on documented change impact assessment and risk
- Scope is proportional: partial repeat where justified, full repeat where needed
- Outputs are documented with clear pass/fail conclusions and evidence attachments
FAQs
Is requalification the same as revalidation?
No. Requalification usually focuses on equipment/system qualification performance, while revalidation focuses on continued consistent compliance of processes or validated programs. Both maintain the validated state and may overlap depending on the change.
Do you always need full IQ/OQ/PQ again?
Not always. A risk-based impact assessment may justify partial requalification limited to affected functions or critical tests.
What triggers revalidation most often?
Process/material changes, repeated OOS/OOT trends, major equipment changes affecting process performance, and significant computerized system upgrades impacting GMP functions and records.
Can periodic review trigger requalification or revalidation?
Yes. Periodic review can reveal drift, recurring failures, or uncontrolled changes that require partial or full repeat activities to restore confidence in the validated state.
What is the most common audit issue here?
Decisions not supported by evidence—either re-testing is skipped after significant changes or full re-testing is done without a clear, risk-based justification.