Requirements Traceability Matrix (RTM)
A complete toolkit for mapping business objectives to technical deliverables, ensuring comprehensive verification and validation across the project lifecycle.
§1 Understanding the RTM
A Requirements Traceability Matrix forms the backbone of quality assurance, ensuring that every identified requirement maps cleanly through to final delivery and verification.
By establishing rigorous traceability from initial business objectives down to functional components, teams mitigate the risk of scope creep and prevent missed requirements. This document provides standard formats for both primary traceability (from requirement to test) and inter-requirements traceability (from high-level business goals to detailed technical specifications).
§2 Blank Template Structure
The standard KEVOS® RTM categorises requirement attributes into clear, logical groupings: Information, Relationship, and Traceability. This allows project managers to immediately identify orphaned requirements or unverified deliverables.
| Requirement Information | Relationship | Traceability | ||||||
|---|---|---|---|---|---|---|---|---|
| ID | Requirement | Source | Priority | Category | Business Objective | Deliverable | Verification | Validation |
| [ID] | [Clear statement of need] | [Originator] | [MoSCoW] | [Type] | [Goal Alignment] | [System Component] | [Test Case/Audit] | [Sponsor Sign-off] |
§3 Worked Example: Website Project
The following table demonstrates a completed RTM for a fictional project: Mary's Consulting - New Company Website. It illustrates how business, stakeholder, functional, non-functional, and transition requirements are documented and traced through to validation.
| Requirement Information | Relationship | Traceability | ||||||
|---|---|---|---|---|---|---|---|---|
| ID | Requirement | Source | Priority | Category | Business Objective | Deliverable | Verification | Validation |
| B-01 | Increase qualified inbound leads (MQLs) by 25% within 12 months of launch. | Mary (Sponsor) | Must | Business | Grow Fortune 500 client base | Live website + analytics dashboard | Analytics review | Quarterly benefits review with sponsor |
| B-02 | Reduce content-update cycle time from ~10 days to < 1 day. | Marketing Lead | Must | Business | Modernise digital footprint | CMS with editor workflow | Demo + 30-day usage data | Marketing Lead sign-off |
| B-03 | Position the brand credibly for Fortune 500 buyers. | Mary (Sponsor) | Must | Business | Grow Fortune 500 client base | Brand-aligned website | Buyer survey | Sponsor + Marketing review |
| S-01 | Marketing must be able to publish content without engineering involvement. | Marketing Lead | Must | Stakeholder | Reduce content cycle time | CMS editor role | User acceptance test | Marketing UAT |
| S-02 | Sales must receive new web-form leads in the CRM within 5 minutes of submission. | Sales Lead | Must | Stakeholder | Increase qualified leads | CRM integration | Integration test | Sales Lead sign-off |
| S-03 | Consultants must be able to submit/update their bio and case studies through a self-service form. | Consultant Community | Should | Stakeholder | Modernise digital footprint | Consultant submission form | Pilot with 10 consultants | Pilot feedback |
| F-01 F-02 F-03 |
1. Provide a Contact / Request-for-Proposal form capturing name, work email, company, role, and message. 2. Display a searchable case-study library filterable by industry, service, and region. 3. Provide a consultant directory searchable by industry, region, and language. |
Marketing Lead | Must Must Should |
Functional | Increase qualified leads Position brand for F500 Modernise digital footprint |
Contact/RFP form Case-study module Consultant directory |
Functional test Functional test Functional test |
UAT UAT UAT |
| F-04 | Provide a blog with categories, tags, author pages, and RSS feed. | Marketing Lead | Should | Functional | Position brand for F500 | Blog module | Functional test | UAT |
| F-05 | Integrate the contact and RFP forms with the company CRM via documented API. | Sales Lead | Must | Functional | Increase qualified leads | CRM integration | Integration test | UAT |
| N-01 | All public pages must load in < 3 seconds on standard broadband (LCP < 2.5s). | Mary (Sponsor) | Must | Non-functional | Grow F500 client base | Optimised site | Performance test (Lighthouse/WebPageTest) | Performance audit |
| N-02 | Site must achieve WCAG 2.1 AA accessibility compliance. | Legal / Compliance | Must | Non-functional | Compliance | Accessibility report | Third-party accessibility audit | Audit sign-off |
| N-03 | Site must be responsive across desktop, tablet, and mobile (≥320px width). | Bill (UX) | Must | Non-functional | Modernise digital footprint | Responsive design | Visual/responsive test | QA review |
| N-04 | Site must remain available with 99.5% uptime SLA (monthly). | IT/Hosting Ops | Should | Non-functional | Reliability | Hosting contract + monitoring | SLA review | Operations review |
| N-05 | Site must comply with GDPR data privacy requirements. | Legal / Compliance | Must | Non-functional | Compliance | Privacy implementation | Legal review | Legal sign-off |
| T-01 | Migrate existing case-study content from the legacy site to the new CMS. | Marketing Lead | Must | Transition | Modernise digital footprint | Migrated content | Content audit | Marketing sign-off |
| T-02 | Train Marketing team to use the new CMS. | Marketing Lead | Should | Transition | Reduce content cycle time | Training materials | Training records | Marketing Lead sign-off |
§4 Inter-Requirements Traceability Matrix
While a standard RTM traces requirements through to verification and deployment, an Inter-Requirements Traceability Matrix maps broad, high-level business objectives to the specific technical, functional, or transition requirements that satisfy them. This provides an audit trail confirming that every technical deliverable serves a defined business purpose.
| Business / Stakeholder Requirement | Technical / Functional Requirement | ||||||
|---|---|---|---|---|---|---|---|
| ID | Business Requirement | Priority | Source | ID | Technical Requirement | Priority | Source |
| B-01 | Increase qualified inbound leads (MQLs) by 25% within 12 months of launch. | Must | Mary (Sponsor) | F-01 F-05 |
Contact/RFP forms CRM integration API |
Must Must |
Marketing Lead Sales Lead |
| B-02 | Reduce content-update cycle time from ~10 days to < 1 day. | Must | Marketing Lead | F-03 N-03 T-01 |
Consultant directory Responsive design Migrate existing content |
Should Must Must |
Marketing Lead Bill (UX) Marketing Lead |
| B-03 | Position the brand credibly for Fortune 500 buyers. | Must | Mary (Sponsor) | F-02 F-04 N-01 N-02 |
Case-study library Blog module Sub 3s page load WCAG AA compliance |
Must Should Must Must |
Marketing Lead Marketing Lead Sponsor Legal |
| S-01 | Marketing must be able to publish content without engineering involvement. | Must | Marketing Lead | T-02 | Train Marketing team to use the new CMS. | Should | Marketing Lead |
| S-02 | Sales must receive new web-form leads in the CRM within 5 minutes of submission. | Must | Sales Lead | F-01 F-05 |
Provide RFP form Integrate forms with CRM API |
Must Must |
Marketing Lead Sales Lead |
| S-03 | Consultants must be able to submit/update their bio and case studies through a self-service form. | Should | Consultant Community | F-03 N-03 T-01 |
Consultant directory Responsive UI Content Migration |
Should Must Must |
Marketing Lead Bill (UX) Marketing Lead |
§5 Quick Reference
Distinct Assessment Objectives
Verification asks: "Did we build the system right?" (Internal specifications tests). Validation asks: "Did we build the right system?" (External sponsor acceptance).
Living Traceability
An RTM requires strict version control. Always include the "Date Prepared" and link changes directly to formally approved Project Change Requests (PCRs) to avoid unapproved scope deviations.
Scaling Matrix Data
While spreadsheets are sufficient for small engagements, complex or enterprise-level programmes should rely on dedicated application lifecycle management (ALM) platforms to automate mapping.