A requirements traceability matrix (RTM) maps requirements to the artifacts used to implement and verify them, such as design documents, test cases, test results, and defects. It helps teams answer three questions: What needs to be validated? Which checks cover it? What does the evidence show?
For example, a requirement that users can reset their passwords might link to cases for valid requests, expired links, and invalid tokens. The RTM connects those cases to their execution results and any defects, making gaps easier to identify before release.
An RTM can be a spreadsheet, a report, or a connected view across requirements and test management tools. This guide explains what to include, how to build one, and how TestRail supports requirements traceability as your project evolves.
Key takeaways
- An RTM connects requirements to related artifacts and verification evidence.
- Forward traceability follows requirements into implementation and verification; backward traceability follows artifacts back to their originating requirements.
- A linked test case indicates documented coverage, not successful validation. Execution results and acceptance decisions provide additional evidence.
- A useful RTM includes stable requirement IDs, linked checks, current results, defects, ownership, and release context.
- TestRail supports RTM workflows through requirement references, coverage reports, Jira integration, and consolidated manual and automated results.
What is a requirements traceability matrix?

Source – https://www.testkarts.com/manual-testing/traceability-matrix
A requirements traceability matrix is a structured mapping between requirements and the work or evidence associated with them. In software testing, it commonly connects requirements to test cases, execution results, and defects.
Broader traceability may also include business objectives, design components, implementation artifacts, and other verification methods, such as reviews or analysis.
The RTM makes these relationships visible throughout the software development life cycle (SDLC). Teams can use it to identify requirements without planned checks, review unsuccessful or incomplete testing, and investigate which assets may need updating after a change.
An RTM does not automatically establish complete coverage or product quality. Its usefulness depends on accurate requirements, meaningful checks, current links, and evidence from the relevant version of the product.
RTM vs. test plan: what is the difference?
| Document | Main purpose | Typical contents |
| Requirements traceability matrix | Connect requirements to implementation and verification evidence | Requirement IDs, linked tests, results, defects, and verification status |
| Test plan | Define how testing will be organized and performed | Scope, approach, roles, environments, schedule, risks, and exit criteria |
The test plan describes the testing approach. The RTM helps the team assess how that approach addresses the agreed requirements.
Why is requirements traceability important?

Requirements traceability improves visibility into scope, coverage, and testing evidence. Its main benefits are practical:
Identify coverage gaps
Compare the complete list of in-scope requirements with the checks linked to them. Requirements with no associated verification method need attention, while requirements with linked cases may still need a review of their acceptance criteria and edge conditions.
Support change impact analysis
When a requirement changes, its links help the team find related tests, design elements, and implementation work. Use those relationships to guide updates and regression testing, alongside engineering knowledge and dependency analysis.
Make release decisions easier to assess
A requirement with a passing happy-path test and an unresolved security defect presents a different release risk from one with all required checks passed. Traceability makes that distinction visible when results, defects, and decision context are recorded together.
Improve collaboration and review
Product owners, business analysts, developers, and testers can review the same requirement-to-evidence relationships. This helps resolve unclear expectations and gives stakeholders a basis for discussing gaps and residual risk.
Organize evidence for audits
An RTM can help reviewers follow the relationship between requirements and verification evidence. In governed environments, preserve the relevant versions, approvals, and execution records according to your process. Traceability supports evidence review; the matrix alone does not establish compliance.
Types of requirements traceability

Forward, backward, and bidirectional traceability describe the direction in which you follow relationships. They do not necessarily require separate documents.
| Type | Direction | Question it helps answer | Example |
| Forward traceability | Requirement to downstream artifacts | How was this requirement implemented and verified? | Password-reset requirement linked to a design, endpoint, and tests |
| Backward traceability | Artifact to its originating requirement or other justified source | Why does this artifact or check exist? | Expired-token test traced back to a password-reset acceptance criterion |
| Bidirectional traceability | Both directions | Can we follow the relationship from requirement to evidence and back? | A requirement links to a test, and the test identifies the requirement it verifies |
Backward traceability can surface tests or features that need explanation. An unlinked test is not automatically unnecessary: it may address a technical risk, a previous defect, or a security concern. Review its purpose and record the appropriate source.
What should an RTM include?

Choose fields that support your decisions without creating unnecessary maintenance work.
| Field | Purpose |
| Requirement ID | Provide a stable, unique reference |
| Requirement description | Summarize the behavior or constraint |
| Source and version | Identify the authoritative requirement and applicable revision |
| Priority or risk | Highlight business impact and testing importance |
| Verification method | Identify testing, review, analysis, or another agreed method |
| Linked test case IDs | Connect the requirement to reusable checks |
| Execution context | Identify the release, build, run, environment, and configuration |
| Test results | Show the relevant execution outcomes |
| Linked defects | Connect failures or unresolved concerns to issue records |
| Verification status | Summarize progress using the team’s agreed rules |
| Owner and notes | Assign follow-up and capture decisions or exceptions |
Add design or implementation links when they are needed for your traceability scope. Keep detailed requirement text and test instructions in their authoritative systems, with links from the matrix.
Requirements traceability matrix example
The following example shows a testing-focused RTM for an event-registration application. IDs and results are illustrative.
| Requirement ID | Requirement | Linked test cases | Results for build 2.4.0 | Defect | Verification status |
| REG-101 | Users can register with valid details | C101: Valid registration; C102: Confirmation email | C101 passed; C102 failed | BUG-42: Confirmation email not sent | Failed check; follow-up required |
| REG-102 | Duplicate registrations are rejected | C103: Existing email; C104: Repeated submission | C103 passed; C104 not run | None recorded | Partially executed |
| AUTH-101 | Registered users can log in | C105: Valid credentials; C106: Invalid password | Both passed | None recorded | Required checks passed |
| AUTH-102 | Password-reset links expire after the specified interval | No cases linked | Not run | None recorded | Coverage gap |
| ACCESS-101 | Registration is operable by keyboard | C107: Keyboard navigation and submission | Blocked by environment issue | BUG-43: Test environment unavailable | Blocked |
This example separates three different situations: a missing test, an existing test that has not run, and an executed test that failed. Each requires a different follow-up.
One requirement can link to multiple tests, and one test can address multiple requirements. If a spreadsheet becomes difficult to filter, use one row per requirement–test relationship and preserve requirements with no links as explicit gap rows.
How to create a requirements traceability matrix

1. Define the scope and purpose
Decide which release, feature set, or project the RTM will cover. Identify whether you need requirement-to-test mapping, broader design and implementation traceability, or evidence for a formal review.
Define the applicable builds and environments so results from an older release are not mistaken for current verification evidence.
2. Gather the complete requirement baseline
Collect the authoritative in-scope requirements from your requirements system, Jira issues, specifications, or other approved sources.
Review them with the appropriate stakeholders. Resolve ambiguous acceptance criteria and identify requirements that need verification through methods other than test execution.
Preserve the full requirement list, including items without tests. A matrix built only from already-linked cases cannot reveal requirements that were never linked.
3. Assign stable IDs and ownership
Use unique IDs that remain stable as descriptions change. Track revisions separately rather than renaming every requirement and breaking existing links.
Test IDs do not need to mirror requirement IDs. Maintain explicit relationships so many-to-many mappings remain understandable.
Assign a coordinator for RTM maintenance and identify who owns requirement changes, test updates, and verification decisions.
4. Map requirements to verification methods and cases
Link each requirement to the tests, reviews, or analyses used to evaluate it. Review whether the linked checks address the important acceptance criteria, conditions, and risks.
For a password-reset requirement, one successful-request test may be insufficient. Depending on scope, checks may also need to address invalid tokens, expiration, reuse, permissions, and information disclosure.
For help choosing the right documentation detail, read test scenario vs. test case.
5. Add execution results and defects
Record results for the relevant build and configuration. Distinguish passed, failed, blocked, and unexecuted tests, and attach or link supporting evidence where needed.
Connect defects to affected results. A repaired defect still needs the appropriate retesting before the matrix reflects successful verification.
6. Define requirement-level status rules
Agree on how test outcomes contribute to verification status. For example, a requirement might be considered verified only when all mandatory checks have passed for the target build and no disqualifying defects remain.
Record exceptions and approvals explicitly. Keep development status, such as “implemented,” separate from testing status, such as “verification incomplete.”
7. Review gaps and maintain the matrix
Review the RTM during planning, after requirement changes, and before release decisions. Check for missing mappings, outdated cases, obsolete results, and unresolved defects.
Preserve a dated snapshot when you need to retain the evidence behind a decision. A current view and a historical release record serve different purposes.
How to measure RTM coverage

Use metrics that distinguish documentation coverage from execution evidence.
Requirement-to-test mapping coverage = requirements with at least one linked test ÷ in-scope requirements intended for test verification × 100.
For example, if 18 of 20 requirements intended for testing have linked cases, mapping coverage is 90%. That does not mean 90% of the requirements passed or that every acceptance criterion is adequately covered.
| Metric | What it tells you |
| Requirement-to-test mapping coverage | How many testable requirements have at least one linked case |
| Test execution progress | How many planned checks have been executed in the selected scope |
| Requirement verification progress | How many requirements meet the team’s verification rules |
| Defects by requirement | Where recorded defects affect requirement-related testing |
In the event-registration example, four of five requirements have linked cases, giving 80% mapping coverage. Only AUTH-101 has all its listed checks passed. Even then, final acceptance depends on the team’s agreed verification and defect criteria.
Review link quality alongside percentages. A loosely related case can make a coverage metric look better without providing meaningful evidence.
Excel or a test management tool: which should you use?

Excel and Google Sheets can work well for a small RTM with limited scope and a clear maintenance owner. They are also useful for sharing a fixed review snapshot.
As requirements and tests change more frequently, manual synchronization becomes harder. Teams may need to reconcile requirement revisions, multiple execution configurations, and defect updates across several systems.
| Approach | Useful when | Maintenance consideration |
| Spreadsheet RTM | Scope is small and updates are infrequent | Assign ownership and reconcile links and results regularly |
| Connected requirements and test tools | Multiple teams, releases, or configurations share testing assets | Configure integrations and review data quality and report scope |
| Exported report snapshot | Stakeholders need a dated review or release record | Label the generation date, filters, build, and requirement baseline |
Choose an approach that keeps the relationships reliable. Tools can reduce manual effort, but they still need correct mappings and agreed status rules.
How TestRail supports requirements traceability

TestRail connects reusable cases, execution results, and defects to external requirement references. Requirements can remain in Jira or another authoritative system while TestRail maintains the associated testing records.
Link cases to requirements with References
Add the relevant requirement IDs to the References field on your test cases. With the appropriate reference integration, those IDs can link back to their source records.
Use the separate defect linkage for bugs identified during execution. This preserves the distinction between the requirement a case evaluates and the issue discovered while running it.
Learn how to configure reference and defect integrations.
Choose the report that answers your question
| Report | Use it to |
| Coverage for References (Cases) | Review case mappings for the specified requirements and identify cases without references |
| Comparison for References (Results) | Compare execution results grouped by reference across selected runs and configurations |
| Summary for References (Defects) | Review recorded defects associated with requirement-linked testing |
For coverage-gap analysis, supply the complete in-scope reference list. Selecting only references already present in cases can omit requirements with no links and create a misleading view of coverage.
Read the Coverage for References report guide and reporting overview for setup and report selection.
Check Jira coverage for a sprint, fix version, or epic
TestRail’s Jira Coverage Check helps identify Jira items with and without associated test cases or results. It requires an active Jira Requirements integration.
From the Test Cases page or a specific test run, select Jira Coverage, choose the relevant sprint, fix version, or epic, apply any issue-type filters, and generate the report. You can review linked cases, open Jira items, and export the coverage results as CSV.
The report reflects reference relationships when it is generated. A covered item has an associated case or result; that designation does not mean every required check passed.
See the Jira Coverage Check guide.
Keep Jira and TestRail information connected
The configured Jira integration lets teams link work items as requirements or defects and create Jira issues from within TestRail. The TestRail Integration for Jira add-on provides visibility into linked testing artifacts from Jira issues.
Define which system owns each field and verify the configured behavior before relying on automated updates. Linking a result does not, by itself, mean a Jira requirement’s workflow status will change.
Explore TestRail’s Jira integration setup.
Consolidate automated results and maintain references with the CLI
The TestRail CLI supports uploading automated test results into TestRail. Configure result-to-case matching so automated executions connect to the intended reusable cases and their references.
Current CLI functionality also includes commands to add, remove, and replace references across cases. These commands can support controlled updates when requirement mappings change. Review replacement operations carefully so valid existing links are retained where needed.
See the TestRail CLI command reference.
Use AI-assisted authoring without losing traceability
TestRail Cloud’s AI Test Case Generation can help draft cases from requirements. Review generated checks against acceptance criteria and risks, and confirm their requirement references before relying on them in coverage reporting.
AI Test Prioritization can help rank tests within a run using execution history and other signals. Use that ranking alongside requirement coverage and risk review; unexecuted checks remain unexecuted even when a prioritized subset passes.
For AI-powered features, the AI Evaluation template supports quality ratings across multiple dimensions. Link those cases to requirements and define the evaluation criteria that count as acceptable evidence.
Learn more about AI test-case generation, AI Test Prioritization, and the AI Evaluation template.
RTM best practices and common mistakes

- Start from the full requirement baseline. Already-linked cases cannot reveal every missing requirement.
- Keep IDs stable. Track revisions separately and update affected relationships deliberately.
- Review mapping quality. A link is useful only when the check meaningfully addresses the requirement.
- Separate mapped, executed, and verified. These describe different stages of evidence.
- Record release context. Include the relevant build, environment, configuration, and report date.
- Review unlinked tests. Investigate their purpose rather than automatically deleting them.
- Assign maintenance responsibilities. Requirement owners, test owners, and a coordinator should know when updates are expected.
- Preserve decisions and exceptions. Record accepted risks, approvals, and follow-up actions where your process requires them.
Build traceability you can use before release
An effective requirements traceability matrix makes the relationship between expectations and evidence easy to inspect. Start with clear requirements, connect them to meaningful checks, and keep results and defects current for the release being evaluated.
TestRail helps teams organize those relationships through references, coverage reports, Jira integration, and manual and automated execution records—giving stakeholders a clearer view of coverage gaps and verification progress.
Start your free TestRail trial.
Requirements traceability matrix FAQs
What is an RTM in software testing?
An RTM maps requirements to related test cases and verification evidence. It can also include design links, implementation artifacts, execution results, and defects to support coverage review and change impact analysis.
What should a requirements traceability matrix include?
Include stable requirement IDs, descriptions or source links, verification methods, linked test cases, relevant results, defects, and status. Add ownership, requirement revisions, and release context to make the information maintainable and useful for decisions.
Who creates and maintains the RTM?
Ownership varies. A QA lead, business analyst, or project manager may coordinate it, while requirement owners and testers maintain their respective information. Clear update responsibilities matter more than a particular job title.
What is the difference between forward and backward traceability?
Forward traceability follows a requirement into implementation and verification artifacts. Backward traceability follows an artifact back to its originating requirement or justified source. Bidirectional traceability supports both views.
Does 100% requirement coverage mean testing is complete?
No. If coverage measures links, 100% means every in-scope requirement has an associated check. It does not establish that all acceptance criteria are addressed, the checks were executed successfully, or unresolved defects are acceptable.
Can you create an RTM in Excel?
Yes. A spreadsheet can work for small projects with clear maintenance ownership. As scope and execution data grow, connected requirements and test management tools can reduce manual reconciliation and improve visibility.
How does TestRail help create a requirements traceability matrix?
TestRail uses References to link cases to requirements and provides reports for case coverage, execution results, and defects. Jira Coverage Check supports coverage reviews for selected Jira entities, while CLI workflows can help maintain references and consolidate automated results.




