This is a ready-to-use trigger matrix. A validated conclusion is a statement about the state of a process, a piece of equipment, a computerized system, or a method at the time it was tested. Use this matrix to decide, for any event that comes along afterward, whether that statement still holds, needs a targeted retest, or needs a full requalification or revalidation. Replace every <<FILL: ...>> placeholder with your own specifics. A worked filled specimen follows the template. Verify each cited regulation against the current source before you rely on it.
Document control header
| Field | Entry |
|---|---|
| Document title | Revalidation and Requalification Trigger Matrix |
| Document number | <<FILL: MTX-ID, e.g. MTX-VAL-009>> |
| Version | <<FILL: version, e.g. 1.0>> |
| Effective date | <<FILL: effective date>> |
| Document owner | <<FILL: role, e.g. Head of Validation>> |
| Applies to | <<FILL: sites / systems / processes in scope>> |
| Linked documents | Validation Master Plan <<FILL: VMP-ID>>, change control <<FILL: SOP-ID>>, periodic review <<FILL: SOP-ID>> |
Purpose
Most validation failures found at inspection are not a missing IQ or OQ from years ago. They are a change, an excursion, or a stretch of time that came after a system was already validated, and that nobody assessed against the original conclusion. This matrix gives a single, consistent reference for spotting those triggers before an inspector does, and for deciding how much work each one actually warrants, so effort goes where the risk is real instead of being applied evenly to everything or skipped everywhere.
Scope
This matrix covers triggers arising after initial validation or qualification is complete and the item is in routine GxP use: manufacturing processes, equipment and utilities, computerized systems, and analytical methods. It does not cover the initial validation project itself, which is planned under <<FILL: validation plan SOP-ID>>, and it does not replace the individual change control assessment for a specific event; it is the reference that assessment points to when deciding scope and depth.
Responsibilities
| Role | Responsibility |
|---|---|
| System / process / equipment owner | Notices the event, raises it in change control or periodic review, and proposes the trigger category. |
| Validation / CSV function | Confirms the trigger category, assesses scope against this matrix, and defines the requalification or revalidation activity. |
| Subject matter expert | Confirms which functions, parameters, or requirements the event could plausibly touch. |
| Quality Assurance | Confirms or overrides the tier assigned, approves the assessment, and tracks the resulting activity to closure. |
Definitions
- Revalidation: repeating validation activity, in whole or in part, to confirm a process, system, or method still meets its requirements after a change or after time has passed.
- Requalification: the equipment or facility equivalent of revalidation, confirming installation, operation, or performance still holds.
- Trigger: an event or the passage of a defined time interval that requires the question “is this still validated?” to be asked and answered, with evidence.
- Soft trigger: an event that is easy to miss because no one files a change request for it, such as a slow drift, an extended idle period, or a change made by a supplier rather than by the site itself.
- Tier: the depth of assessment or retest a trigger warrants, defined in the scale below.
Tiering scale
| Tier | Meaning | Typical activity |
|---|---|---|
| Tier 0, document only | The event does not touch a validated function, a critical parameter, or a tested requirement. | A written assessment recording why no retest is needed, filed against the item’s inventory record. |
| Tier 1, targeted verification | The affected scope is narrow and well understood. | Retest of the specific function, parameter, or requirement affected, with a stated rationale for what was excluded. |
| Tier 2, full requalification or revalidation | The event reaches multiple functions, a release-critical parameter, or the basis of the original risk assessment. | Repeat of the relevant qualification or validation phases (IQ/OQ/PQ, PPQ, method validation, or the CSV equivalent), with its own report. |
The tier in the matrix below is a default starting point, not an automatic answer. The assessor states the actual tier assigned and the reasoning, because two events in the same category can land in different tiers depending on what they actually touch.
The matrix
| # | Trigger category | Example event | Applies to | Assessment route | Default tier | Typical evidence |
|---|---|---|---|---|---|---|
| 1 | Planned process change | A parameter, formulation, or process step changes through an approved change request. | Process | Compare the change against the process validation report and the continued process verification baseline. | Tier 1 or 2, by scope | Change record, impact assessment, updated CPV trend |
| 2 | Planned equipment change | New equipment, relocation, a major component swap, or a control system upgrade. | Equipment | Re-assess the affected DQ/IQ/OQ/PQ elements against the new configuration. | Tier 1 or 2, by scope | Change record, requalification protocol and report |
| 3 | Computerized system change | A patch, version upgrade, configuration change, data migration, or interface change. | Computerized System | CSV impact assessment against the requirements and risk assessment that supported the original release. | Tier 1 or 2, by scope | Change record, regression test evidence, updated traceability |
| 4 | Analytical method change | A reagent, column, instrument platform, or acceptance criterion changes. | Method | Method validation or verification impact assessment against the original validation report. | Tier 1 or 2, by scope | Change record, comparability or bridging data |
| 5 | Facility or utility change | Room reclassification, HVAC rework, a water system modification, or a facility move. | Process, Equipment | Requalify the facility or utility, then reassess any process or method that depends on it. | Tier 2 for the facility element; Tier 1 or 2 for dependent processes | Requalification report, dependent-process impact assessment |
| 6 | Scheduled periodic review interval elapsed | The interval set in the validation master plan or inventory arrives. | Process, Equipment, Computerized System, Method | Periodic review confirms documentation is current, changes since the last review were controlled, and performance remains in control. | Tier 0, unless the review itself finds an issue | Periodic review record |
| 7 | Performance signal | A continued process verification trend, a cluster of deviations or out-of-specification results, or a control chart signal. | Process, Method, Computerized System | Risk-based investigation into whether the signal reflects a change in the underlying validated state. | Tier 1 or 2, depending on investigation findings | Investigation record, trend data |
| 8 | Unplanned event or excursion | A utility failure, a power loss, an environmental excursion past the alert or action level, or an extended shutdown. | Equipment, Process | Impact assessment of what the event could have affected during and after its duration. | Tier 1 or 2, by duration and scope | Excursion record, impact assessment |
| 9 | Supplier-initiated change | A SaaS vendor’s platform upgrade, a raw material supplier’s process change, or an instrument’s automatic firmware update. | Computerized System, Method, Equipment | Review the supplier’s change notification, assess against your own requirements and risk assessment; this is the trigger category most often missed because no internal change request was ever filed. | Tier 1 or 2, by scope | Supplier notification, impact assessment |
| 10 | Organizational or administrative change | A site relocation, a change in the accountable owner, or a role reassignment affecting operation. | Process, Equipment, Computerized System, Method | Reassess accountability and operating controls; targeted requalification only where a technical scope also changed. | Tier 0 or 1 | Handover record, updated inventory entry |
| 11 | Return to use after decommissioning or an extended idle period | Equipment or a system returns to service after storage, an idle period beyond the defined limit, or planned decommissioning was reversed. | Equipment, Computerized System | Requalify before return to service; depth depends on idle duration, storage conditions, and whether the environment changed while idle. | Tier 1 or 2, by idle duration | Requalification protocol and report |
How to use this matrix for a decision
- Identify the category the event best fits from column 2. Where an event fits more than one row (a facility move that also involves an equipment relocation), assess both.
- State, in writing, which validated functions, critical parameters, or tested requirements the event could plausibly touch, and which it clearly cannot.
- Assign a tier from the scale above, using the default in column 6 as a starting point and adjusting with a documented reason.
- Define the specific verification or requalification activity for a Tier 1 or Tier 2 assignment, referencing the original validation deliverable it revisits.
- File the assessment against the item’s entry in the validation or equipment inventory so the full history is visible from one place, not scattered across separate change records.
Acceptance criteria
A trigger assessment made against this matrix is acceptable when all of the following hold:
- The assessment is documented at or near the time of the triggering event, not reconstructed afterward once someone else noticed.
- The tier assigned carries a stated reason, not just the category default copied across.
- For Tier 1, the excluded scope is stated explicitly, not left as a silent assumption.
- For Tier 2, the requalification or revalidation activity references the specific original deliverable it revisits and produces its own dated report.
- The outcome is filed against the item’s inventory entry, and Quality Assurance has confirmed or overridden the tier.
References
21 CFR 211.100 (written procedures) and 21 CFR 211.68 (automatic, mechanical, and electronic equipment). EU GMP Annex 15 (Qualification and Validation), 2015 revision, on the need to assess the impact of change and to requalify or revalidate where warranted. EU GMP Annex 11 (Computerised Systems), on controlled change to validated computerized systems. ICH Q9, Quality Risk Management, for the risk basis of the tiering scale. ICH Q10, Pharmaceutical Quality System, for the change management and periodic review linkage. FDA, Process Validation: General Principles and Practices (2011), for continued process verification as an ongoing trigger for revalidation. ISPE GAMP 5, Second Edition, for the risk-based approach to assessing changes to computerized systems.
Confirm the current version and clause numbers of each reference before issue.
Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL: date>> | <<FILL: author>> | Initial issue. |
Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Author (Validation) | <<FILL>> | ||
| Reviewer (System / process owner) | <<FILL>> | ||
| Approver (QA) | <<FILL>> |
Filled specimen
The following shows the matrix applied to two events at an illustrative biologics fill-finish site, so you can see how the assessment reads. The site, systems, and numbers are illustrative.
| # | Trigger | Event | Applies to | Assessment | Tier assigned | Evidence |
|---|---|---|---|---|---|---|
| 5 | Facility change | The fill line moved eight meters to a renovated suite; the filling machine itself did not change. | Process, Equipment | Room classification, airflow pattern, and gowning path all changed, so the facility qualification is repeated for the new location and the aseptic process simulation is re-run before commercial fills resume. The filler’s own OQ from 2024 is still valid because the trigger was the room, not the machine, and that reasoning is recorded rather than assumed. | Tier 2 for the facility and aseptic process simulation; Tier 0 for the filler OQ | Facility requalification report FRQ-2026-011, media fill report MF-2026-014, documented rationale for the OQ exclusion |
| 9 | Supplier-initiated change | The building management system vendor pushed a platform upgrade to the hosted instance with two weeks’ notice. | Computerized System | The upgrade notice was reviewed against the URS and the original risk assessment; the alarm-delay configuration and audit trail behavior were the only GxP-relevant functions the vendor’s release notes flagged as changed. Those two functions were retested in the vendor’s staging environment before the upgrade went live in production. | Tier 1 | Vendor release notes, impact assessment IA-2026-033, retest record TR-2026-019 |
Quality Assurance review: R. Gomez, 14 September 2026. Both assessments were reviewed and accepted; the facility event correctly separated what changed (the room) from what did not (the filler), and the supplier-initiated upgrade was caught from the vendor’s own notice rather than discovered afterward in an audit trail review. That is the behavior this matrix exists to produce, an assessment made before the fact, not reconstructed after it.
Common inspection findings this matrix prevents
- A facility move or equipment relocation treated as routine housekeeping, with no requalification of the dependent process.
- A vendor-pushed software update discovered only when an audit trail review turns up unfamiliar behavior, with no impact assessment on file.
- Periodic review confirming documentation is current while a performance trend that should have triggered an earlier revalidation sat unassessed.
- An extended shutdown or idle period ending with a return to routine use and no requalification, because no one filed a change request for time passing.
- A tier assigned by copying the category default with no stated reason, so a reviewer cannot tell whether the assessor actually thought about the specific event.
How to adapt this matrix
- Set your document number, owner, and scope in the header, and link it from your validation master plan.
- Add or split rows to match categories your own change control and periodic review procedures already use, keeping the link between trigger, assessment route, and tier.
- Set your own idle-period and excursion-duration thresholds for rows 8 and 11 from your risk assessment, rather than adopting a number from elsewhere untested.
- Train system, process, and equipment owners on the soft-trigger categories (rows 9, 10, and 11) specifically, since these are the ones most often missed.
- Confirm every regulation in the references against the current published version before issue.