Requirements Traceability Matrix
Template Library
Requirements Traceability Matrix Template
Connect requirements to source evidence, stakeholders, use cases, verification methods, and downstream engineering impact.
ES-102
Traceability
Evidence Chain
Template purpose
Use this template to preserve the evidence chain from vision to requirements and from requirements to downstream engineering work.
Traceability helps reviewers understand why requirements exist, who they serve, how they will be verified, and where they affect planning, architecture, design, testing, release, operations, and governance.
Project
<Project name>
Document control
| Field |
Value |
| Artifact owner |
<owner> |
| Primary reviewers |
<reviewers> |
| Status |
<draft / in review / accepted / revised> |
| Last updated |
<YYYY-MM-DD> |
| Related Engineering Stage |
ES-102 — Requirements and Constraints |
| Project workspace target |
docs/project-workspace/requirements/traceability_matrix.md |
Requirement traceability matrix
| Requirement ID |
Requirement Summary |
Source Evidence |
Stakeholder / Need |
Use Case |
Verification Method |
Downstream Impact |
Status |
| FR-001 |
<summary> |
<source> |
<stakeholder / need> |
<UC-ID> |
<test / review / inspection / analysis> |
<planning / architecture / design / testing / governance / operations> |
<draft / reviewed / accepted> |
Source coverage matrix
| Source Evidence |
Related Requirement IDs |
Coverage Notes |
docs/project-workspace/vision/problem_statement.md |
<FR/NFR/C IDs> |
<notes> |
docs/project-workspace/vision/vision_statement.md |
<FR/NFR/C IDs> |
<notes> |
docs/project-workspace/vision/stakeholders.md |
<FR/NFR/C IDs> |
<notes> |
docs/project-workspace/vision/scope.md |
<FR/NFR/C IDs> |
<notes> |
docs/project-workspace/vision/assumptions.md |
<FR/NFR/C IDs> |
<notes> |
docs/project-workspace/vision/success_metrics.md |
<FR/NFR/C IDs> |
<notes> |
Verification coverage matrix
| Requirement ID |
Verification Method |
Evidence Expected Later |
Owner |
<FR/NFR/C ID> |
<test / review / inspection / monitoring / analysis / audit> |
<test result, review record, monitoring signal, audit evidence> |
<owner> |
Downstream impact matrix
| Requirement ID |
Planning Impact |
Architecture / Design Impact |
Testing Impact |
Release / Operations Impact |
<FR/NFR/C ID> |
<impact> |
<impact> |
<impact> |
<impact> |
Requirements without source evidence
| Requirement ID |
Issue |
Action |
<requirement ID> |
<issue> |
<action> |
Requirements without verification approach
| Requirement ID |
Issue |
Action |
<requirement ID> |
<issue> |
<action> |
Requirements with unresolved AI, data, or governance implications
| Requirement ID |
Concern |
Follow-up Needed |
<requirement ID> |
<concern> |
<follow-up> |
Traceability review notes
Review checklist
- [ ] Requirements trace to source evidence.
- [ ] Requirements trace to stakeholders or needs.
- [ ] Use cases are linked where relevant.
- [ ] Verification methods are identified.
- [ ] Downstream impact is visible.
- [ ] Untraced requirements are listed.
- [ ] Requirements without verification are listed.
- [ ] AI, data, and governance traceability gaps are visible.
Continue to Requirements Review
Review the requirements package for clarity, traceability, testability, scope alignment, and readiness.
Open Requirements Review →