Governance DocsGovernance Docs
Browse Toolkits

CART

No products in the cart.

Skip to content

Traceability Matrix: A Clear 5-Link Guide for CSV

traceability matrix: Traceability Matrix for CSV

A traceability matrix is the one validation document an inspector can test in thirty seconds: pick a requirement, ask where its test is, and see whether the matrix answers. In computer system validation, the matrix links each user requirement to the specification that builds it, the risk call that sets its rigor, the test that proves it and the result that closed it. If a link is missing, so is the evidence. This post covers what the matrix must hold, what the EU texts say about it, and the gaps it exposes.

The matrix is one piece of a wider set of record and validation duties; our 21 CFR Part 11 requirements guide covers the rest of Part 11.

What a Traceability Matrix Does in Computer System Validation

Validation proves that a system does what you rely on it to do. The matrix proves that you tested the right things. It runs one line per requirement, left to right:

  1. User requirement. What the regulated user has automated and relies on.
  2. Specification. The functional or design specification, and the configuration specification, that deliver it.
  3. Risk. The documented risk assessment of that requirement, which sets how much testing it gets.
  4. Test. The test case or script that challenges it.
  5. Result. The executed outcome, plus any deviation raised against it.

Read forward, the chain shows that every requirement is built and tested. Read backward, it shows that every test and every piece of specified functionality serves a requirement someone approved. Both directions matter.

What the EU Texts Say About Traceability

Start with what is in force. EU GMP Annex 11 (January 2011), clause 4.4, says a user requirements specification must describe what the system has to do, rest on a written risk assessment and GMP impact, and stay traceable through the whole life cycle. It does not name a matrix, and it does not say how to build one. The duty is traceability; the matrix is the usual tool.

The July 2025 draft revision of Annex 11 is a consultation draft. It is not adopted, and no adoption date has been announced. It is more explicit, which makes it a useful guide to where expectations may be heading. The draft expects the following:

  • 6.5, Traceability. Documented links between individual requirements, the design specifications beneath them and the matching qualification and validation test cases, established and maintained. It encourages effective tools to hold requirements and support traceability.
  • 9.5, Traceability of tests. Test cases should trace to individual requirements or specifications, for example through a requirements traceability matrix. Test cases that cannot be traced to a requirement or applicable specification do not meet the draft’s expectations for qualification and validation.
  • 9.2, Quality risk management. How much qualification and validation each function gets is decided from a justified, written risk assessment at requirement level (and at specification level where relevant).
  • 6.4, Update. Requirements are kept current through the life cycle and form the basis for qualification and validation.

Note the phrase in 9.5: the matrix is given as an example (“for example”), not mandated by name. The firm obligation is that every test can be traced. A spreadsheet matrix, a requirements tool or linked identifiers can all do it if they stay current.

For the primary text, see the EU consultation page for the Annex 11 and Annex 22 drafts, and read the in-force text on the EudraLex Volume 4 pages.

Why Untraceable Tests Do Not Count

The draft’s logic in 9.5 is blunt. A test that points to no requirement shows that something was tested, not that anything you rely on was tested. Picture a thick binder of passed scripts with no way to say which requirement each covers, or which requirements none covers. Passing tests give false comfort when the scope of what they prove is unknown.

There is also a risk logic. Since the draft ties test depth to risk assessment of individual requirements (9.2), a test with no requirement has no risk rating to justify its depth. You cannot show it was proportionate. The same applies in reverse: a high-risk requirement with a thin test cannot be defended if the matrix shows the risk but not the depth.

The guidance from FDA for device software points the same way. Its CSA guidance recommends using requirement traceability tools and automated traceability where possible, and says scripted testing for higher-risk functions may call for detailed repeatability and traceability. See CSV vs CSA for how that guidance scales the effort.

A Worked Traceability Matrix Extract

Build the matrix at the level of individual requirements, not documents. A row that says “URS section 5 maps to OQ protocol” proves nothing; a row per requirement lets a reviewer see exactly which test answers which need, and the draft’s wording in both 6.5 and 9.5 is about individual requirements.

Here is a short extract for an imaginary chromatography data system. The identifiers are examples. Your numbering scheme will differ.

Requirement Specification Risk Test Result
URS-012: peak integration changes are recorded with reason FS-4.3 audit trail; CFG-17 reason prompt enabled High: data integrity OQ-031, OQ-032 Pass; OQ-032 raised DEV-004, closed
URS-019: only trained analysts can approve results FS-6.1 role matrix; CFG-22 roles High: access control OQ-040 Pass
URS-027: report shows system suitability result FS-8.2 report template Medium: calculation PQ-012 Pass
URS-031: export to the LIMS runs without manual re-entry FS-9.1 interface High: data transfer None Gap

The fourth row is the point of the exercise. A high-risk requirement with no test cannot be signed off until it has one.

Gaps a Traceability Matrix Exposes

A matrix built from the live documents, not drawn up after the fact, shows problems that reviews of single documents miss:

  • Requirements with no test. The row above. Either add a test or document why the requirement is covered another way, such as vendor evidence you have reviewed.
  • Tests with no requirement. Under draft 9.5 these do not count. Either a requirement is missing from the URS, which means the URS is incomplete, or the test is not needed.
  • Requirements with no risk rating. Nobody can justify the test depth.
  • Specified functions with no requirement. Functionality built or configured that nobody asked for. The draft’s principle 2.5 expects requirements to reflect the implemented system, so unrequested functionality is a documentation gap too.
  • Configuration not in the specification. The draft’s 6.6 expects the chosen configuration to be documented in a controlled configuration specification.
  • Failed or deviated tests with no follow-through. A result column that says “pass” next to a deviation that is still open.
  • Stale requirements. The system changed, the requirement did not (draft 6.4), and the tests now prove the old behavior.
  • Vendor specifications adopted unreviewed. If the supplier wrote the requirements specification, draft 6.3 expects the regulated user to review, approve and own it for the implemented version.

Keeping the Traceability Matrix Alive

The matrix is most likely to drift after go-live. Three habits keep it honest.

Tie it to change control. Every change request should name the requirements it touches and prompt a matrix update. Without that step, the matrix becomes a snapshot of the validation, not of the system.

Use stable identifiers. Requirement numbers should survive document revisions. If a requirement is split or retired, record that. Renumbering silently breaks every link that referred to it.

Review it at periodic review. Check a sample of live requirements against current test evidence. Our post on IQ, OQ and PQ explains where each test sits in the qualification sequence, and the validation master plan should say who owns the matrix and when it is reviewed.

To start from a working layout, the 21 CFR Part 11 Toolkit includes a Requirements Traceability Matrix, a User Requirements Workbook, a User Requirements Specification and a Test Script and Execution Record. It holds 105 templates (68 Word and 37 Excel) for $99. They are templates to adapt to your own system, and using them does not make a system compliant.

21 CFR Part 11 Toolkit sample page: GDL-CSV-026 - User Requirements Specification
21 CFR Part 11 Toolkit sample page: GDL-CSV-048 - Test Script and Execution Record
21 CFR Part 11 Toolkit sample page: GDL-CSV-047 - Performance Qualification Protocol and Report

Traceability Matrix FAQ

Is a traceability matrix mandatory?

The in-force Annex 11 (2011), clause 4.4, requires that user requirements be traceable throughout the life cycle but does not name a matrix. The draft revision cites a matrix as an example of how to trace tests to requirements. The draft is not adopted, so treat it as direction, not law.

Can I use a requirements tool instead of a spreadsheet?

Yes. The draft encourages effective tools for holding requirements and supporting traceability. Whatever you use must be controlled, show the links in both directions, and be available when an inspector asks.

Do commercial off-the-shelf systems need a matrix?

If you rely on the system for GMP work, you still need requirements and tests for what you rely on. The draft says its requirements principle applies whether a system is built in-house, bought off the shelf or provided as a service. Vendor evidence may cover some rows, if you have reviewed it and it covers your version.

Does the matrix replace the validation report?

No. It shows coverage. The validation summary still states what was done, what failed, what was resolved and whether the system may be used.

Who should own it?

The regulated user. A supplier may provide parts, but under the draft the regulated user remains responsible for reviewing, approving and keeping the requirements and evidence for the implemented version.

When a standard changes, know first

One email a month: edition changes, new deadlines, and what they mean for documentation you already have. No sales sequence.

We don’t spam! Read our privacy policy for more info.