Free resource · CSV
A requirements traceability matrix you can actually use.
Connect a requirement to the work that implements it and the tests that check it. Use this template to identify gaps and keep a record of release evidence.
A blank template. A worked example.
Generic UTF-8 planning templates, not Yetea importer files. REQ-001, WORK-001 and CASE-001 are fictional template references, not Yetea-generated identifiers.
| Requirement ID | Requirement | Source reference | Task reference | Test Case reference | Test Case revision | Test Run reference | Result | Owner | Evidence note |
|---|---|---|---|---|---|---|---|---|---|
| REQ-001 | A password-reset link can be used only once. | Reset requirements, section 2 | WORK-001 | CASE-001 | 1 | RUN-001 | Passed | QA owner | Sample: second use was rejected. |
| REQ-002 | Expired reset links explain how to request a new link. | Reset requirements, section 3 | WORK-002 | Not recorded | Not recorded | Not recorded | No coverage | Product owner | Sample gap: define and link a Test Case before review. |
How to maintain it.
Identify the requirement and its source.
Use Requirement ID and Requirement for a stable reference and the intended behavior. Source reference points to the precise rule, section or decision.
Connect work and coverage.
Task reference identifies implementation. Test Case reference identifies verification; leave it empty when coverage is missing rather than inventing a pass.
Record the execution.
Test Case revision, Test Run reference and Result describe which instructions ran and what happened. A linked test alone is coverage, not a passing result.
Assign responsibility and explain exceptions.
Owner identifies who follows up. Evidence note records the observation or gap. Review the row after requirement changes, case edits and new runs.
A manually maintained matrix is not automatic verification, a certification or proof that software is defect-free.
Keep these links beside the work.
Yetea connects exact sources, implementation tasks and Test Cases, with execution evidence beside the task.
Explore connected traceability