# Requirements Traceability Matrix: Template and Example

Editable worksheet. Examples on the website and in the example CSV are fictional and illustrative. Replace their IDs, assumptions, and review decisions with your own verified records.

## Scope and baseline
Feature: [name]
Specification version: [version]
Review owner: [role]

## Field guidance
Keep requirement IDs stable. Source ID identifies the need or decision. Delivery ticket identifies implementation work. Verification method explains how the requirement will be checked. Test ID and evidence reference locate the check and result. Tested version identifies the examined build. A Passed result requires actual evidence.

## Review checklist
- Source and downstream relationships resolve in both directions.
- Each requirement has an appropriate verification method.
- Failure and authorization boundaries are covered.
- Results match the current requirement and examined build.
- Unknown relationships and accepted exceptions have owners.

## Sources checked November 9, 2026
- NASA requirements management — bidirectional relationships — https://www.nasa.gov/reference/6-2-requirements-management/
- NASA verification matrix — identifiers and verification methods — https://www.nasa.gov/reference/appendix-d-requirements-verification-matrix/