Free tool · No signup · Runs in your browser

Free Requirements Traceability Matrix Generator

Paste your requirements and test cases (or upload CSVs), click cells to map coverage, and get a traceability matrix with automatic gap detection. Export as CSV or Markdown, or print to PDF.

Requirements

One per line: ID, Title - or just the title (IDs are auto-numbered). Max 300.

0 requirements

Test cases

Same format. Export from Jira, a spreadsheet, or type them in.

0 test cases
Add at least one requirement and one test case to build the matrix - or load the sample data to see how it works.

How it works

Step 1

Add requirements and test cases

Paste them one per line, upload CSV exports from Jira or a spreadsheet, or load the sample data to see the matrix in action.

Step 2

Click to map coverage

Each cell links a test case to a requirement. Coverage counts, GAP flags, and orphaned test cases update instantly as you click.

Step 3

Export the matrix

Download CSV for Excel or Sheets, Markdown for Confluence or your wiki, or print the color-coded matrix to PDF for an audit pack.

What a requirements traceability matrix tells you

A requirements traceability matrix (RTM) maps every requirement to the test cases that verify it. Reading it answers the two questions every release decision hangs on: which requirements have no test at all (coverage gaps), and which tests verify nothing anyone asked for (orphans).

Auditors ask for an RTM because it is evidence of intent: proof that testing was driven by the requirements rather than by whatever the team happened to check. Regulated industries require one for every release; everyone else discovers they needed one the first time a "done" feature ships untested.

The honest limitation of any spreadsheet RTM - including the one this tool generates - is that it is a snapshot. It is accurate the moment you export it and starts drifting the moment requirements change or a new test is added. This tool runs entirely in your browser (nothing is uploaded), and it is perfect for an audit pack or a one-off gap check. For a matrix that stays current, traceability needs to live where the work happens.

Requirements Traceability Matrix: the full guide

Frequently asked questions

Is this RTM generator free?

Yes - free, no signup, no limits. Everything runs in your browser and your requirements and test cases are never uploaded anywhere. It is built by the team behind BesTest, a test management app for Jira.

What format do the CSV uploads need?

Two columns: an ID and a title, with or without a header row. Exports from Jira, Excel, or Google Sheets work as-is. You can also paste plain lines of text - IDs are auto-numbered when missing.

What is a coverage gap and what is an orphaned test case?

A coverage gap is a requirement with no linked test case - it will reach production unverified. An orphaned test case is one not linked to any requirement, which usually means either undocumented scope or wasted test effort. The matrix flags both automatically.

Does one linked test case mean a requirement is covered?

In a simple matrix, yes - and that is its main blind spot. A complex, high-risk requirement with a single happy-path test is technically "covered" but practically untested. Weighting coverage by a requirement's significance is exactly what dedicated traceability tooling adds over a spreadsheet.

This matrix is a snapshot. Your requirements are not.

Every spreadsheet RTM is out of date by the next sprint. BesTest keeps requirements, test cases, and executions linked live inside Jira - coverage is calculated from each requirement's significance, gaps surface as they appear, and the matrix your auditor wants is always one click away instead of one afternoon away.

Free for teams up to 10 users. All features included.