Skip to main content
Reqorra
Free · No sign-up

Build a traceability matrix that shows you the gaps

Paste your BRD or requirements list. Every requirement gets a row, traced down to the stories that deliver it and the test cases that verify it — with uncovered rows flagged.

Paste the BRD or requirements list you need traced. Every requirement in it becomes a row. Upload a file or paste the text.

Drop your BRD or requirements doc here, or browse

PDF, Word (.docx), or plain text — up to 4 MB.

or paste it below

Nothing to hand? — a real requirements workshop, so you can see what comes out before you paste your own.

No account needed. Usually under a minute.

How it works

Every requirement becomes a row

Paste the BRD or requirements list. Each requirement is pulled out, numbered, and given its own row — functional and non-functional alike.

Traced down both sides

Each row is traced to the user stories that deliver it and the test cases that verify it. A matrix that only lists requirements is a list; the tracing is the matrix.

Gaps called out, not hidden

A requirement with no story or no test is marked as a gap in amber rather than left as an empty cell. Finding those rows is the entire reason the document exists.

Questions

What is a requirements traceability matrix for?
To answer one question quickly: is anything about to ship untested or unbuilt? It lays every requirement against the work that delivers it and the tests that prove it, so an uncovered row is obvious instead of being discovered in UAT.
What are the columns?
Requirement ID, the requirement, its type and MoSCoW priority, the user stories delivering it, the test cases verifying it, and a coverage cell. The CSV download carries the same columns for Excel or Google Sheets.
Does it fabricate coverage to make the matrix look complete?
It writes a story and a test case for each requirement it can, and marks the row as a gap when it cannot. A matrix where everything is green by construction tells you nothing — the value is entirely in the rows that are not.
My requirements change every week. Does the matrix go stale?
This page produces a snapshot, so yes. Saved into a project it stops being a snapshot: the coverage is computed from the real stories and test cases, requirements added in later meetings appear as new rows on their own, and a requirement that gets revised flags the artifacts under it for review.
Is it free, and do I need an account?
Free, with no account. Signing up is only needed to keep the matrix live rather than exporting a point-in-time copy.

What comes next

Or save any of it into a project, where all of this connects up on its own — see every tool.