What Is a Requirements Traceability Matrix (RTM)? With Template

May 27, 2026

A Requirements Traceability Matrix (RTM) is a table that links every approved requirement to its design, its test cases, and its current status. It is how a business analyst proves that nothing requested was forgotten and nothing built was unrequested.

Why you need one On any project larger than a handful of requirements, things slip. A requirement gets approved but never tested. A feature gets built that nobody asked for. An RTM catches both. When a stakeholder asks "did we cover the refund scenario?", you answer in seconds, not days.

The essential columns A practical RTM does not need to be complicated. These columns cover most projects:

Requirement ID — a unique reference like REQ-001. Description — the requirement in plain language. Source — who requested it (links back to the BRD). Priority — Must, Should, Could (from MoSCoW). Design Reference — where it is addressed in the design. Test Case ID — the test that verifies it. Status — Not Started, In Progress, Complete, Verified.

How to keep it useful The RTM fails when it becomes a document nobody updates. Three rules keep it alive. Update it during development, not at the end. Keep it in a shared tool like a spreadsheet or Jira, not buried in email. Review it at every milestone so gaps surface early.

Forward and backward tracing Forward tracing follows a requirement to its test case, confirming it was built and verified. Backward tracing starts from a feature and confirms a requirement justified it. A good RTM supports both directions, which is how you catch scope creep and missing coverage at the same time.

Our BA Starter Kit includes a ready-to-use RTM template alongside a BRD, stakeholder register, and use case specification.