Free template

Free requirements traceability matrix template (CSV)

A ready-to-fill RTM that maps each requirement to its tests, their latest results and open defects, with a coverage summary at the bottom.

By the TestPlum teamChecked

Short answer

A requirements traceability matrix template is a table with one row per requirement and linked test: requirement ID, requirement, priority, test ID, test title, last result, last run date, defect and status. This CSV comes filled with a checkout example that shows forward tracing, backward tracing and a coverage summary.

What this RTM template is for

A requirements traceability matrix (RTM) answers two questions before a release: is every requirement tested, and is every tested requirement passing? It also shows the reverse: tests that are not linked to any requirement.

This page is about the template itself. For the background, including how to derive each requirement's status, read the guide to the requirements traceability matrix.

To fill it in, start from your list of requirements or user stories and give each a stable ID. Add one row for every test that proves it, copying the test ID and title from your test cases. After each test run, update Last result, Last run and Defect, then set each requirement's Status. Finally, list every test that has no requirement at the bottom, so nothing hides.

Every column explained

The CSV has one row per requirement and test pair. A requirement with three tests has three rows, which keeps the file easy to filter and sort.

The columns of the requirements traceability matrix template
ColumnWhat to writeExample
Requirement IDThe stable key of the requirement or story.REQ-13
RequirementWhat was promised, in one sentence.A declined payment shows a clear error and keeps the cart
PriorityThe requirement's priority.Critical
Test IDA test that proves it. Empty means not covered.CHK-2
Test titleThe test's title, so the row reads on its own.Declined card shows an error and keeps the cart
Last resultThe most recent result: Passed, Failed, Blocked or Not run.Failed
Last runThe date of that result.2026-11-18
DefectAn open bug found by this test.BUG-41
StatusThe requirement's status, the same on all of its rows.Failing

A filled example with forward and backward tracing

The download traces five checkout requirements. Read it forward, from requirement to test to result, to find what is untested or failing. Read it backward, from test to requirement, to find tests that prove nothing.

Example rows from the requirements traceability matrix template
RequirementTestLast resultDefectStatus
REQ-12 Pay with a saved cardCHK-1, CHK-5Passed, PassedPassing
REQ-13 Declined payment keeps the cartCHK-2, CHK-8Failed, PassedBUG-41Failing
REQ-14 Discount code reduces subtotalCHK-3, CHK-6Passed, Not runPartial
REQ-15 Guests must give an emailCHK-4PassedPassing
REQ-16 Pay with a gift cardnoneNot covered
(no requirement)CHK-7 Page loads in under 2 secondsPassedOrphan test

The coverage summary

The bottom of the CSV adds up the matrix. In the example, 4 of 5 requirements have at least one linked test, so coverage is 80%. But only 2 are passing, 1 is failing, 1 is partly tested and 1 has no test at all. Coverage tells you what is tested; status tells you whether it works. Report both, side by side.

The summary also counts orphan tests (CHK-7 here) and the defects that block requirements (BUG-41). Both are worth a look before every release.

Use these status rules so two people get the same answer: Not covered when no test is linked, Failing when any linked test's latest result is failed or blocked, Passing when every linked test passed, and Partial when some passed and the rest have not run yet.

Good and weak RTMs, and common mistakes

  • Counting a requirement as covered when its only test was never run. Covered means linked; it does not mean verified.
  • Keeping old results. Use the latest result. A test that failed last week and passes today counts as passing.
  • Updating the matrix once, before an audit. It is out of date the moment someone records a new result.
Weak RTM habits next to better ones
WeakBetterWhy
“Tested: yes” per requirementThe test IDs and their latest resultsShows which tests, and whether they pass today.
Status typed by handStatus derived from the latest results with fixed rulesTwo people get the same answer.
Requirements onlyEvery test listed, including tests with no requirementBackward tracing finds tests that verify nothing.
Requirement titles as keysStable IDs that match your trackerTitles change; IDs let you match rows to tickets.

Keep it in a spreadsheet or in Git

In a spreadsheet, filter by Status to list failing and not-covered requirements, and use a pivot table on Requirement ID to count tests per requirement. Recompute the summary with formulas so it cannot drift from the rows.

In Git, keep the CSV next to your requirements or release notes, and update it in the same pull request that changes a requirement. The diff then shows exactly which traces changed. Either way, someone has to copy results in by hand after every run, which is the weak point.

When a spreadsheet RTM stops scaling

Once you have more than a few dozen requirements, or results arrive from CI every day, a hand-kept matrix is always behind. That is when it pays to generate it from the results instead.

In TestPlum, you link tests to requirements once, and each requirement's status is worked out from the latest recorded results: passing, failing, partly passing, not run yet or not covered. The traceability matrix goes from requirement to test to result to open bug, and the summary counts tests with no requirement too. Requirements verified is one of the checks in the release verdict. Tests can come in from a CSV, TestRail, Xray or Zephyr Scale; see migrating to TestPlum.

Download

Frequently asked questions

What columns should a requirements traceability matrix have?

At least the requirement ID, the requirement, the linked test IDs, the latest result of each test, any open defect and the requirement's status. Priority, test titles and the date of the last run make it easier to read and act on.

What is forward and backward traceability?

Forward traceability follows a requirement to its tests and results, which proves it was verified and shows requirements with no tests. Backward traceability follows a test back to its requirement, which shows tests that are not linked to anything.

How do I calculate requirements coverage?

Divide the number of requirements with at least one linked test by the total number of requirements. In the template's example, 4 of 5 requirements have a test, so coverage is 80%.

What status should a requirement have if one of its tests fails?

Failing. A requirement passes only when all of its linked tests pass on their latest result. If some pass and the rest have not run, it is partly verified.

Why does the template use one row per test instead of one row per requirement?

So each test keeps its own result, date and defect in separate cells. You can still read it per requirement by sorting or filtering on Requirement ID, and the status column is the same on all of a requirement's rows.

Can I generate a traceability matrix automatically?

Yes, if your tests and requirements are linked in a tool that records results. In TestPlum the matrix and each requirement's status are worked out from the latest results, so nobody copies results into a spreadsheet.

Find out whether your next release is ready

Create a workspace, import your tests or write a few, and record a run. Everything on this site is in the product today.