Requirements Traceability Matrix (RTM)

Prove coverage from every requirement to the tests that verify it.
Updated

What It Does

The Requirements Traceability Matrix answers the question every auditor and release manager asks: is every requirement tested, and did the tests really prove it? The platform keeps the links between requirements and tests up to date as you generate tests, then shows the latest run of each test and workflow against the requirement it covers. A green test is not always proof, so the Verified column reads a requirement verdict instead of counting passes: a requirement is verified only when a check grounded in it was evaluated in a run. Requirements with no tests stand out with a red zero, and one covered only by an end-to-end workflow still counts as covered. If you run load tests judged against performance targets, the Under load column records met or missed beside the functional verdict, and the Security column lists open findings with the worst severity. Hover any count to see each test or workflow and its last run, or jump to a single requirement from the assistant or the coverage views. The matrix exports as CSV or PDF, and the rows carry the ticket keys when requirements were imported from a tracker.

A requirements traceability matrix: five requirements are linked to tests T1 to T6 one row at a time, four roll up to Pass with Met under load where a performance target applies, one requirement with no tests is flagged Untested, and the matrix also shows Verified, Workflows and Security columns

Overview

A live Requirements Traceability Matrix links each requirement to the tests and workflows that validate it and to their latest runs, so you can see at any moment which requirements are covered and passing. It goes further than a pass count: the Verified column shows whether a requirement was actually verified, is failing, passed without its tests checking what it asks for ("not really"), or has not run. Every row cites the document and the section, page or row the requirement came from. With the add-ons, the same row shows whether the requirement met its performance target under load and any open security findings. Export the matrix as CSV or PDF, and on Professional, Trial and Enterprise group it by tracker ticket. The matrix is included on every plan, Free included.

Key Capabilities

Links from each requirement to its tests, workflows and their latest results
Verified column: verified, failing, "not really" (passed but never checked) or not run
Every row cites its source document and the section, page or row
Untested requirements stand out; a requirement covered by a workflow counts as covered
Under load and Security columns when you use the performance and security add-ons
Export as CSV or PDF
Group by tracker ticket (epic, story, requirement, tests, result) when requirements come from Jira, Azure DevOps, GitHub or GitLab
Included on every plan, Free included

How It Works

  1. 1

    Open Requirements and select the Traceability tab

  2. 2

    Read each requirement’s source, tests, workflows and their latest runs

  3. 3

    Check the Verified column for the verdict, and hover it for the evidence

  4. 4

    Spot untested requirements, shown with a red zero, and generate tests for them

  5. 5

    With the add-ons, read Under load and Security on the same row

Available on

All Plans

Included in the free trial — no credit card required.

Included in all plans
See pricing →

Built for regulated teams

Teams in regulated industries rely on this capability to ship API changes with an audit trail.

Try Traceability (RTM) Today

Start your 15-day free trial — no credit card required.