Independent and not affiliated with the FDA, MHRA, ISPE, PDA, or any agency. Get the appgoutham@madhadi.com
madhadi.comData Integrity & GxP Quality
Browse all topics → Articles Templates & Procedures Learning paths GlossaryScenariosToolsRegulatory ReferencesLearning PathsTopics About Start here
Matrix Plug-and-play starting point Equipment Qualification

Matrix: Requirements Traceability for Commissioning and Qualification (URS to Test to Reuse)

A plug-and-play requirements traceability matrix mapping each URS requirement through FS and DS to the FAT, SAT, IQ, or OQ test that verifies it, with the reuse justification that lets FAT/SAT evidence reduce IQ and OQ. Includes a filled specimen.

Document type: Matrix

Read and copy the template below into your own quality system. It is a generic starting point for your own internal use, provided as is, with no warranty; see the Terms and License. Adopting it does not by itself create compliance.

This is a ready-to-use requirements traceability matrix (RTM) for a commissioning and qualification effort. It maps every user requirement to the single lowest sensible test that verifies it, and records the justification for reusing FAT or SAT evidence into IQ or OQ so you test once instead of three times. Build it before FAT, not after. Replace every <<FILL: ...>> placeholder. A filled specimen follows. This is educational reference content, not regulatory advice.

Why this matrix earns its place

Reuse of FAT/SAT evidence into qualification is a privilege earned with documentation, and the RTM is the document that makes it defensible. It shows an inspector, at a glance, that every URS line is covered exactly once, where it is verified, and why a FAT result can stand in for an IQ or OQ test. Without it, coverage gaps and duplications are invisible and the reuse argument collapses. See factory and site acceptance testing and commissioning and qualification under ASTM E2500.

FieldEntry
Matrix number<<FILL: RTM-ID>>
Equipment / system<<FILL>>
Related URS / FS / DS<<FILL: document numbers>>
C&Q plan / VMP reference<<FILL>>
Owner<<FILL: C&Q engineer>>

Column definitions

ColumnMeaning
Req IDUnique requirement identifier from the URS
RequirementThe testable requirement text
Risk / critical aspectIs this a critical aspect (impacts product quality, patient safety, or data integrity)?
FS / DS refWhere the design satisfies it
Verified atThe lowest sensible test event: FAT / SAT / IQ / OQ / PQ
Reused inThe qualification stage that references the evidence instead of repeating it
Reuse justificationWhy the evidence is valid and transport/installation-safe (the Annex 15 condition)
StatusOpen / Verified

Matrix

Req IDRequirementCritical?FS / DS refVerified atReused inReuse justificationStatus
<<FILL>><<FILL>>Y/N<<FILL>><<FILL>><<FILL>><<FILL>>Open

Coverage check

CheckResult
Every URS requirement mapped to at least one test<<FILL: Yes / gaps listed>>
No critical requirement verified only by unwitnessed vendor testing<<FILL>>
Each reused FAT result has a transport-sensitive SAT re-test or a documented rationale<<FILL>>
Supplier assessment on file supporting reliance on vendor data<<FILL: reference>>

Sign-off

RoleNameSignatureDate
Author (C&Q)<<FILL>>
Reviewer (QA)<<FILL>>

Filled specimen

Example rows for a bioreactor skid.

Req IDRequirementCritical?FS / DS refVerified atReused inReuse justificationStatus
URS-041Product-contact parts 316L, Ra <= 0.5 umYDS-3.2FAT (material certs + inspection)IQMaterial cannot change in transit; cert-based, stableVerified
URS-052All I/O points correctly mappedYFS-5.1FAT (full I/O check, QA witnessed)OQ (component)Executed under approved protocol; re-confirmed by SAT functional runVerified
URS-060High-temperature interlock de-energizes heater within 2 sYFS-6.4FAT then SAT re-testOQTransport-sensitive; SAT re-test shows unaffected by shippingVerified
URS-071Audit trail records changes with user ID and timestampYFS-8.2FAT (software test, QA + IT witnessed)OQ / Part 11 evidenceSoftware config frozen; version verified identical at SATVerified
URS-088Compressed air dew point within ISO 8573-1 class per URSYDS-4.1SAT (real utility)IQCannot be tested at vendor; site-utility specificVerified
URS-096HMI displays temperature in CNFS-8.1FAT (screen verification)OQConfig verified; low risk; SAT confirms display unchangedVerified

The payoff is visible in the “Reused in” column: instead of re-running the I/O check and the interlock test a third time during OQ, OQ references the controlled FAT execution plus the SAT confirmation, and spends its effort on what genuinely needs site execution. Each reuse carries its own justification tied to the Annex 15 condition, so the argument survives an inspection.

Common inspection findings this matrix prevents

  • No one can show which requirement each test covers, so gaps and duplications are invisible.
  • FAT evidence reused into OQ with no recorded justification and no transport-sensitivity check.
  • A critical requirement covered only by an unwitnessed, uncontrolled vendor test.
  • Reuse claimed without a supplier assessment supporting reliance on vendor data.

How to adapt this matrix

  1. Import your URS requirements as rows before FAT, and assign each to its lowest sensible test event.
  2. Mark critical aspects; those get witnessing and the tightest reuse justification.
  3. For every reused FAT result, name the transport-sensitive SAT re-test or the rationale for stability.
  4. Run the coverage check at the end and resolve any gap before you rely on reuse.
Use madhadi.com as an app Full screen, works offline, one tap from your home screen.