CSV Traceability Matrix: Requirements to Test Evidence in Computer System Validation
Follow intended-use requirements through risk assessment, specifications and verification evidence, with practical checks for gaps, changes and unresolved exceptions.

On this page · 11 sections
- 1What is a CSV traceability matrix?
- 2Regulatory foundations: FDA guidance, Part 11 and Annex 11
- 3Set the boundary by intended use and system dependency
- 4Compare the matrix with neighboring validation records
- 5Build traceability alongside the validation lifecycle
- 6Design the matrix fields and evidence relationships
- 7Worked cases: tolerance testing and coverage calculations
- 8Use the matrix to assess changes and regression scope
- 9Trace interfaces and verify exception recovery
- 10Find false coverage before it becomes a review gap
- 11Review the baseline and retrieve a complete evidence trail
How does CSV Traceability Matrix apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What is a CSV traceability matrix?
A CSV Traceability Matrix is a controlled record that links a computerised system’s intended-use requirements to risk assessments, specifications, verification activities and the resulting evidence. It is also called a requirements traceability matrix, RTM or validation traceability matrix. Here, CSV means computer system validation, not comma-separated values.
Its central question is practical: for a particular requirement and system version, what demonstrates that the intended function or control was adequately verified? A useful matrix lets a reviewer follow that question from the stated need through the verification approach to the recorded result, rather than infer coverage from a folder of test reports.
The matrix contains relationships, usually expressed through stable record identifiers, relevant revisions and concise coverage or status information. A requirement reference points to the user requirements specification; specification references identify how the function is defined; verification references identify the activity and its execution evidence. These links provide a route through the records, not a replacement for them.
Keep the authoritative requirement wording, detailed design, test instructions, acceptance criteria, observations and raw evidence in their respective controlled records. Copying all of that material into every matrix row creates competing versions and makes maintenance harder. The matrix should identify the relevant record precisely enough that a reviewer can retrieve it and understand which requirement it addresses.
This article addresses configured manufacturing applications, laboratory systems, spreadsheets, interfaces and equipment software. It treats the matrix as a documentation practice, not a universal legal definition or prescribed template. Regulatory applicability must be assessed separately for the product, intended use and jurisdiction.
02Regulatory foundations: FDA guidance, Part 11 and Annex 11
Build the regulatory mapping around the system’s product context and jurisdiction, not around a preferred spreadsheet template. Separate binding US regulations from official guidance and the team’s documentation choices. The practical matrix implications below are implementation recommendations, not mandatory column names or a universal matrix format.
| Jurisdiction and product context | Instrument | Legal or guidance status | Supported traceability point | Practical matrix implication |
|---|---|---|---|---|
| US: medical-device software validation | FDA software validation guidance, requirements traceability discussion, page 16 | Official FDA guidance, 2002 | Recommends tracing software requirements to and from system requirements, and to risk analysis results. | Link each software requirement to its parent system requirement and relevant risk analysis result; support navigation in both directions. |
| US: medical-device production and quality-system software | FDA software validation guidance, section 6.1 | Official FDA guidance | Recommends validation effort commensurate with the risk posed by the automated operation. | Record the risk rationale behind evidence depth rather than assigning every requirement the same test burden. |
| EU: medicinal-product GMP applications | Annex 11, section 4.4 | Official EU GMP guidance; distinct from US regulation | User requirements specifications should describe required functions, be based on documented risk assessment and GMP impact, and remain traceable throughout the lifecycle. | Connect user requirements to documented risk and GMP impact, then maintain their evidence relationships through lifecycle changes. |
| US: systems and documentation maintained under Part 11 | 21 CFR 11.1(e) | Binding US regulation | Computer systems, controls and attendant documentation maintained under Part 11 must be readily available for, and subject to, FDA inspection. | Use the matrix as a navigation aid to retrievable records, not as a template attributed to this provision. |
Check applicability before assigning regulatory drivers
- US drug applications: check the current text of 21 CFR 211.68 for scope and applicable equipment requirements. Start from the relevant good manufacturing practice context rather than importing a device-validation rationale unchanged.
- Current US device applications: check current device requirements and the applicable quality-system framework; the QMSR overview provides orientation. Do not treat historical device-rule references in the 2002 guidance as a current regulatory map.
- EU medicinal-product applications: check the current text of Annex 15 for scope and applicable qualification and validation requirements alongside Annex 11.
For electronic records and electronic signatures, document the applicability decision before assigning Part 11 as a requirement’s driver. Keep regulatory drivers separate from internal acceptance criteria so reviewers can distinguish the external obligation or recommendation from the chosen way of demonstrating it.
03Set the boundary by intended use and system dependency
Before creating matrix rows, build an applicability worksheet as part of the GxP impact assessment. Record product category, jurisdiction, intended use, affected records or decisions, system owner and business-process dependency: what relies on the result, and what independent checks exist? Document a rationale for inclusion, exclusion or separate assessment. These are practical scoping decisions; legal applicability remains product- and jurisdiction-specific.
| Example system | Candidate boundary to assess |
|---|---|
| Pharmaceutical dispensing application | Material identity, weighing, balance connection and dispensing records. |
| Device acceptance-test system | Test limits, instrument inputs, pass/fail decisions and result retention. |
| Supplement calculation spreadsheet | Formula version, units, input controls and calculated quantities used in production. |
| Food production interface | Transferred lot identities, quantities, acknowledgements and rejected messages. |
| Chemical manufacturing historian | Tags, timestamps, aggregation and retained trends used for process decisions. |
These examples illustrate dependencies, not a common regulatory regime. Define the system boundary using the configured application version, enabled modules, interfaces, master data, infrastructure dependencies, user roles and relevant operating environment. Identify who controls shared components and where their assessment is recorded.
Use dependency analysis as a practical risk assessment. An unselected menu option does not demonstrate isolation: unused functions may share database tables, permissions, scheduled jobs or computing resources with functions in scope. Assess plausible interactions and record the basis for excluding them or evaluating them separately.
Scale documentation detail to intended-use risk and complexity, including reliance on system outputs, rather than the supplier’s product category alone.
04Compare the matrix with neighboring validation records
In common validation practice, these records answer different questions. A matrix connects them; it does not replace their decisions, instructions or results.
| Record or method | Question answered | Typical contents | Relationship to the matrix |
|---|---|---|---|
| User requirements specification | What must users accomplish? | Intended use, required capabilities, constraints | Provides the requirements to trace |
| Risk assessment | What could fail, with what consequences? | Hazards, impacts, controls, risk rationale | Connects requirements and controls to verification priorities |
| Validation plan | How will validation be organised? | Scope, responsibilities, activities, acceptance strategy | Defines how traceability is established and reviewed |
| Test protocol | How will acceptance be checked? | Preconditions, steps, expected results | Provides planned verification references |
| Executed test record | What actually happened? | Actual results, observations, attachments, deviations | Provides execution-specific evidence references |
| Validation summary report | What conclusion does the evidence support? | Results assessment, unresolved issues, conclusions, approvals | Uses coverage findings to inform the overall conclusion |
Functional or configuration specifications sit between intended-use requirements and verification activities: they describe the behaviour or settings that implement the need. Controlled records can express these relationships without a separate document for every layer. Link the risk assessment to quality risk management, rather than treating a risk rating as a substitute for its rationale.
GAMP is recognised industry guidance that can inform lifecycle organisation and terminology, not binding law.
Software requirements traceability follows assurance relationships: needs, implementation and verification. Batch genealogy follows production and material relationships, such as which input lots contributed to an output batch.
05Build traceability alongside the validation lifecycle
Create traceability as decisions are made, not after testing. The following is a practical working model, adaptable to system complexity and local quality procedures rather than a prescribed organisation chart.
- Establish intended use. The process owner describes the supported activity, users and operating context. The validation lead turns that agreement into a traceability scope and identifies who will maintain it.
- Write identifiable requirements. Use atomic, objectively assessable statements with stable identifiers, revision history, a named owner and measurable acceptance criteria. The process owner confirms that each statement expresses the actual business need.
- Assess risk. Process and technical specialists evaluate failure consequences with the validation lead. Record the rationale connecting each requirement to the depth of verification, rather than assigning every row the same testing effort.
- Map specifications and controls. Technical specialists connect requirements to design, configuration and procedural controls. Hand unresolved design questions back to the requirement owner before treating the mapping as settled.
- Plan verification. Testers define methods and expected results before execution. Where appropriate, allocate checks across installation qualification, operational qualification and performance qualification; use the stages that fit the validation approach.
- Capture execution evidence. Testers attach the executed record, tested version, actual result and exception reference to the relevant requirement. The validation lead checks these handoffs for completeness without replacing technical review.
- Resolve exceptions and establish the reviewed baseline. Assigned owners investigate failures and document corrections, retesting or justified dispositions. Quality reviewers examine the evidence and unresolved risks; authorised humans approve the baseline and any release decision.
For example, split “control access, calculate accurately and report results” into three statements: REQ-101—users with the Viewer role cannot save changes; REQ-102—calculate net mass as gross minus tare within ±0.01 kg over the specified input range; REQ-103—each generated report displays record ID, net mass and unit. These illustrative criteria need system-specific approval.
Review forward from each requirement to its control and executed evidence. Then review backward from evidence to justified scope. Investigate tests with no justified purpose, functionality exercised without a documented requirement, and results attached to the wrong requirement; do not delete unmatched tests without assessment.
A controlled spreadsheet, document-based matrix or relational tool can support this work when its intended use is justified. Select for appropriate access, revision control, stable links and reviewability—not row count alone.
The workflow diagram below shows these handoffs and review loops.
- Define useIdentify scope, intended users and measurable requirements.
- Assess riskConnect failure consequences to controls and verification depth.
- Map specificationsLink requirements to designs, configurations and interface definitions.
- Plan verificationAssign methods, acceptance criteria and coverage relationships.
- Capture executionRecord tested versions, actual results and evidence references.
- Review exceptionsAssess gaps, deviations and evidence suitability.
- Maintain baselinePreserve revisions and reassess relationships after changes.
06Design the matrix fields and evidence relationships
Use the following layout as a practical data model, not a prescribed regulatory template. Keep linked records authoritative; the matrix identifies relationships and summarises their state rather than duplicating protocols or reports.
| Field | Content to retain |
|---|---|
| Requirement ID and revision | Stable identifier and exact requirement revision. |
| Intended-use statement | Function, user and operating context being supported. |
| Risk/control reference | Linked risk assessment and relevant control. |
| Specification reference | Design or configuration record, revision and clause. |
| Verification ID and method | Planned activity; test, documented review or analysis; acceptance basis. |
| Execution ID | Unique occurrence of the verification activity. |
| Tested version | Software build and relevant configuration baseline evaluated. |
| Execution result | Pass, fail, incomplete or not executed. |
| Evidence reference | Record ID, revision, location and relevant page or attachment. |
| Deviation reference and state | Linked deviation ID; open, under investigation or closed. |
| Evidence-review disposition | Pending review, accepted or rejected; reviewer and date. |
A planned verification reference shows intended coverage, not completed work. Populate the execution reference when the activity occurs. Keep execution result, deviation state and evidence-review disposition separate: a passing rerun does not itself close a deviation or establish reviewer acceptance. Avoid collapsing these fields into one green status.
Model many-to-many relationships explicitly. One requirement may need several verification activities; one activity may support several requirements when its acceptance criteria explicitly establish that coverage. Use a linking table or repeated relationship rows rather than hiding multiple executions in an unstructured cell.
Prefer stable identifiers and revision-specific references over filenames alone. A repository address locates evidence; origin, system version and execution context identify what it demonstrates. Preserve who performed the activity, when, in which environment and with which relevant inputs. This supports data integrity and document control of the URS.
Where the requirement and risk justify documented review or analysis, retain the method, acceptance basis and resulting record—not merely a “reviewed” flag.
The following data-model diagram separates requirements, planned activities, executions and evidence records, with explicit links between them.
Requirement
Defines intended behavior and applicability.
- requirement_id
- revision
- requirement_text
- applicability
- owner_id
Risk Control
Connects consequences with mitigation.
- risk_id
- failure_mode
- risk_level
- control_id
Specification
Identifies the implemented solution.
- specification_id
- revision
- configuration_item_id
- requirement_id
Verification
Defines method and acceptance.
- verification_id
- method
- acceptance_criteria
- requirement_id
Execution Evidence
Preserves results and review disposition.
- execution_id
- verification_id
- tested_version
- result
- evidence_uri
- deviation_id
- review_status
07Worked cases: tolerance testing and coverage calculations
Case 1 — Hypothetical dispensing boundary tests
Assume a dispensing requirement with a target mass of 1,000 g, an inclusive tolerance of ±1%, and input resolution of 1 g. The allowance is 1% × 1,000 g = 10 g, producing an acceptable interval of 990–1,010 g. Both endpoints belong inside the weighing tolerance band; the nearest representable inputs outside it are 989 g and 1,011 g.
Use hypothetical configuration CFG-DISP-01: software build DEMO-1, gram inputs, 1 g resolution, and the tolerance settings above. Assume each execution returns its expected response. All identifiers and results below are illustrative, not observed manufacturing outcomes. “Accepted” means permitted to proceed within this dispensing function, not batch release.
| Requirement / risk / specification | Input | Expected response | Verification reference | Execution reference | Assumed test result |
|---|---|---|---|---|---|
| URS-017 / R-04 / FS-08 | 989 g | Blocked | TC-017-01 | EX-017-01 | Pass |
| URS-017 / R-04 / FS-08 | 990 g | Accepted | TC-017-02 | EX-017-02 | Pass |
| URS-017 / R-04 / FS-08 | 1,010 g | Accepted | TC-017-03 | EX-017-03 | Pass |
| URS-017 / R-04 / FS-08 | 1,011 g | Blocked | TC-017-04 | EX-017-04 | Pass |
The verification reference identifies the predefined challenge; the execution reference identifies its particular run against CFG-DISP-01. A negative challenge can produce a passing test when the system correctly blocks the input: “blocked” describes the expected system response, while “pass” describes agreement between actual and expected responses. The execution record would hold the actual response and supporting evidence rather than leaving reviewers to infer them from this summary.
Case 2 — Hypothetical requirement-level coverage
Assume 42 baseline requirements, with two formally excluded from applicability, leaving 40 applicable requirements. All 40 have planned verification links; 36 have complete, accepted evidence. The remaining four comprise two failed requirements, one unexecuted requirement, and one awaiting deviation disposition. Also assume eight applicable high-risk requirements, seven with accepted evidence. These are requirement counts, not test counts: the four boundary tests above still address one requirement.
- Planned-link coverage: 40 ÷ 40 × 100 = 100%.
- Accepted-evidence coverage: 36 ÷ 40 × 100 = 90%.
- High-risk accepted-evidence coverage: 7 ÷ 8 × 100 = 87.5%.
Display each metric beside its denominator, exclusion rationale, evidence-status breakdown and risk grouping. The denominator makes scope visible; exclusion rationale explains why two baseline requirements do not count; evidence status exposes unfinished or unsuccessful work; risk grouping prevents the overall percentage from hiding the high-risk gap. Link the pending disposition to its CSV deviation report.
These illustrative practice definitions are not regulatory thresholds. Here, 100% planned-link coverage means every applicable requirement has a verification route—not that verification succeeded. Count a requirement as accepted only when its defined evidence set is complete and accepted; additional test rows do not increase its weight. The percentages inform human review rather than authorizing release.
08Use the matrix to assess changes and regression scope
Treat matrix maintenance as part of change control, not as a final documentation task. Start with the changed requirement, configuration item, interface, dependency or defect correction. Follow its relationships to affected risks, specifications and verification activities, including tests of functions that consume its outputs.
Do not stop at the requirement named in the change request. A shared calculation service, permission rule or database field may affect otherwise unchanged workflows. Reassess these indirect dependencies before setting the regression scope. Where relationships are missing, investigate the dependency rather than treating an empty link as evidence of no impact.
- Remains applicable: identify retained evidence and explain why its tested configuration, assumptions and acceptance criteria still support the revised baseline.
- Needs review: identify specifications, risk assessments and evidence whose applicability requires a documented decision.
- Needs re-execution: identify affected verification activities and justify the selected regression scope, including exclusions.
Preserve superseded baselines. Connect the change identifier to revised requirements, specification versions, new executions and the resulting matrix revision. Reviewers should be able to distinguish historical results from evidence supporting the current configuration; do not silently carry every previous pass forward.
For computerised systems within EU GMP scope, official guidance in Annex 11, section 10 calls for controlled changes under a defined procedure; section 11 calls for periodic evaluation. As a traceability practice, distinguish event-driven updates after changes from periodic checks for configuration drift, obsolete links and unassessed supplier changes. Set the review frequency according to system risk and change history rather than applying one universal calendar interval.
09Trace interfaces and verify exception recovery
For each system integration, trace interface requirements across both sending and receiving systems: field definitions, units, message and batch identifiers, timestamp meaning and time zone, acknowledgement semantics, and reconciliation ownership. Identify who compares sent records with accepted transactions and who investigates differences. Select controls according to intended use and failure consequences; these are risk-selected engineering practices, not universal requirements for every interface.
Assume a dispensing system sends a 25.0 kg material-consumption transaction to an MES. The MES commits it, but the connection fails before the sender receives acknowledgement. The sender then retries the same transaction identifier. Trace requirements to tests demonstrating:
- Duplicate prevention: retry leaves exactly one consumption entry for 25.0 kg.
- Missing-record detection: comparison of sent identifiers with committed identifiers flags an intentionally omitted transaction.
- Rejected-message visibility: an invalid material identifier produces a visible rejection with an assigned investigation owner.
- Recovery reconciliation: every sent transaction is accounted for as committed, rejected or pending, with unresolved differences identified.
Transport success alone is not business acceptance. Define observable criteria at the receiving process boundary: the correct batch and material, quantity and unit, transaction status, and absence of unintended inventory postings.
Link each exception-handling requirement to its recovery procedure and executed verification evidence. Specify the permitted retry or authorised reprocessing path, including identifier handling. Retain a resolution record connecting the original exception, corrective action, reconciliation result and reviewer decision; route qualifying events through deviation management.
10Find false coverage before it becomes a review gap
Treat these as practical requirements traceability review checks, not independently mandated controls. A populated cell is useful only when its relationship to the requirement survives scrutiny.
| Symptom | Why the link is unreliable | Detection check | Corrective control |
|---|---|---|---|
| Copied test references | Test addresses another requirement. | Compare steps and criteria with each requirement. | Replace unsupported mappings. |
| Wrong configuration | Results concern a different baseline. | Compare execution metadata with target configuration. | Assess differences; justify reuse or retest. |
| Orphan requirements | No evidence relationship exists. | Reconcile approved requirements against matrix entries. | Assign evidence work and an owner. |
| Broken evidence links | Results cannot be retrieved. | Open references using reviewer access. | Restore controlled references; confirm record identity. |
| Unjustified not-applicable dispositions | Exclusion lacks an intended-use basis. | Challenge rationale against actual use. | Document reviewed justification or restore coverage. |
| One broad test linked to many requirements | Acceptance criteria demonstrate only a subset. | Map each criterion to the claimed requirements. | Split mappings; add missing tests. |
Sample complete chains from requirement through risk and specification to executed evidence and disposition. Following risk-based validation, investigate the most consequential gaps first, expanding checks when defects suggest systematic copying or baseline confusion. Before relying on dashboard totals, apply the coverage calculations discussed above only to relationships that withstand these checks.
11Review the baseline and retrieve a complete evidence trail
Before closing the validation summary report, use this practical baseline checklist:
- Scope is approved and requirements have unique identifiers.
- Risk links explain the significance of each requirement.
- Verification methods address the relevant acceptance criteria.
- Evidence matches the assessed system and specification versions.
- Exceptions are resolved or have documented, justified dispositions.
- References work for reviewers, and review decisions are recorded.
For an inspection retrieval exercise, select one consequential requirement. Have a reviewer retrieve its current specification, verification record, execution evidence and exception disposition using only controlled references. Record broken links, ambiguous versions or missing decisions as follow-up actions. The trail should stand without undocumented explanations; this tests retrieval rather than rehearsed answers and supports audit readiness.
Keep electronic-record and signature-control assessments, including applicable Part 11 controls, distinct from requirements coverage. A complete matrix does not prove that all applicable controls are satisfied.
Authorised people make approval and release decisions. Software can organise records and status information, but does not establish site compliance or make the quality decision.
Frequently asked questions
Q.Does a small validation spreadsheet need a separate traceability matrix, or can controlled linked records provide the same visibility?+
For a small validation spreadsheet, controlled linked records can provide traceability without a separate matrix file. As a practical design choice, give each requirement a stable identifier and link it to the applicable formula or configuration, verification evidence and review disposition. A reviewer should be able to navigate both directions and identify missing evidence without reconstructing the relationships. Choose the format around maintaining reliable requirements traceability, not around producing another document.
Q.Can one test support several requirements, and when should a requirement be split into smaller statements?+
Yes—as a traceability practice, one test can support several requirements when its steps and acceptance criteria separately demonstrate each requirement. Link to the relevant step or observation, rather than only the test document. Split a requirement when it combines behaviours that could pass or fail independently, have different risks, or need different verification methods. In the URS, separate access restrictions from audit-trail recording, for example, even if one scenario exercises both.
Q.How should the matrix record a risk control verified by review or analysis rather than a scripted test?+
Record the verification method explicitly as review or analysis, then identify the control, acceptance criteria, evidence location, document revision, reviewer and conclusion. For example, a calculation review might reference an independently checked derivation and its signed assessment. Do not report it as a passed runtime test; a uniquely identified completed review or analysis can still carry its acceptance conclusion and evidence-review disposition. Under a risk-based validation approach, explain why the method addresses the particular failure mode; reviewing a design alone does not demonstrate that an implemented runtime control operates correctly.
Q.When can supplier test evidence support a configured or cloud-hosted system’s intended use?+
Supplier evidence can contribute when a documented assessment establishes its relevance to the intended use, software version, configuration and operating environment. In the EU GMP context, Annex 11, section 3.3 says regulated users should review commercial off-the-shelf documentation to check that user requirements are fulfilled. As practical acceptance criteria, assess test detail, results, unresolved defects and differences from local use. For GxP cloud computing, distinguish provider-tested infrastructure from customer-specific workflows, interfaces and permissions needing additional evidence.
Q.How should withdrawn, replaced or not-applicable requirements affect coverage calculations?+
Define coverage against an approved, versioned set of applicable requirements. Preserve withdrawn and not-applicable entries with reasons and approval references, but exclude them from the active denominator. Link replaced entries to their successors rather than counting both. For example, assume 20 requirements, two withdrawn and three approved as not applicable, with no overlap: 15 remain applicable. If 12 have accepted verification evidence, coverage is 12/15 = 80%. Route scope changes through change control, not informal row deletion.
Q.How should a failed execution and a later successful retest remain connected without overwriting history?+
Keep each execution as a distinct record with its own identifier, date, system baseline and result. Link the failed execution to its CSV deviation report, the corrective action or justified disposition, and the subsequent retest. The matrix can show the current accepted outcome while retaining links to every relevant attempt. Record why the retest scope was sufficient, including any regression checks. A successful rerun should not silently replace the failure or imply that its investigation is closed.
Q.Can two manufacturing sites share a matrix when they use the same application but different configurations or procedures?+
Yes, as a practical document structure, use a shared core with site-specific applicability and evidence mappings. Identify each site's intended use, roles, interfaces, procedures and configuration specification. Shared tests should be credited only where the assessed conditions match; differing workflows or settings need their own verification or a documented justification for reuse. Report coverage by site as well as centrally, so complete evidence at one location cannot conceal a gap at the other.
Q.How should process owners, IT and quality reviewers resolve disagreement about an open traceability gap?+
Make the disagreement specific: identify the requirement, missing evidence, potential consequence and competing interpretations. A practical governance model has the process owner explain intended use, IT assess technical behaviour and dependencies, and quality assess the proposed disposition against the validation plan. Record the decision, rationale, responsible owner and due date in the quality risk register or linked issue record. Escalate unresolved acceptance decisions through designated authority; a coverage percentage or software status must not substitute for human approval.
Primary sources
Want to see how CSV Traceability Matrix could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
