Bluelabel RTM · Requirements Traceability · 13 Oct 2026

How the RTM works

How a requirement moves from the RFP or SOW through allocation, design, delivery and validation, what the RTM app already covers, where it falls short of a commercial tool such as Visure Requirements ALM, and the release train that closes the gaps.

From RFP to validated requirement

Live in the RTM app todayPartial done outside the app or by handGap planned in the release train

Requirement lifecycle: from review to delivery

How the RTM app is used day to day: requirements reviewed and decomposed, allocated to the systems and covered by one end-to-end design; review sessions with the stakeholders whose notes are actioned and closed, moving each requirement through its status; then planned, built, tested and reported. Each name opens its tab.

  1. 1Review and decompose

    Each requirement is read, numbered and checked: one need, clear and testable (the SMART check). A compound one is split into its parts, and two that say the same thing are merged into one.

    Sufficiently decomposed?

    Requirement Status:

    • As Imported
    • Under Review
    • Accepted
    • Invalid
    • Obsolete

    In the app: Requirements · Split proposals · Data checks · Deferral log · Glossary

  2. 2Allocate to systems

    Each subsystem's lead says whether it supports the requirement and how. Supported or Partly supported adds the subsystem to the requirement's Systems.

    Every requirement allocated to a system?

    A subsystem's answer:

    • Supported
    • Partly supported
    • Not supported

    In the app: Allocate subsystem

  3. 3End-to-end design

    Programme epics, functional specs, user stories and business rules; business processes, interaction diagrams and ICDs that join the systems end to end, drawn in draw.io (a PDF becomes an editable diagram); test cases written against the design.

    One cohesive design that covers every requirement?

    In the app: Epic & Functional Spec Mapping · Add Functional Spec · Add Business Process · Add Document · Find a design · Journey Maps · User story · Business Rules · Use cases · Test

  4. 4Review sessions

    Stakeholders review the requirements, the design and the test cases in a session, from slides built from an epic and its features; the notes taken become comments and actions, which are actioned and closed, and the outcome moves the requirement through its status. Once Accepted, its text changes only with a reason, a source and a Change Order number, and it goes back to Under Review.

    All actions closed and the requirement Approved?

    Review disposition:

    • New
    • Ready for Review
    • Action
    • Rework
    • Approved

    A note or action:

    • Open
    • Accepted
    • Not accepted
    • Done

    In the app: Reviews · Slides · My comments

  5. 5Plan

    The epics, features, user stories or requirements are allocated to sprints, and releases are planned against the PIs on the PI calendar, with each requirement's Planned Deployment and Workstreams Affected.

    Committed to a sprint and a release?

    A planned item:

    • Planned
    • In Dev
    • In Test
    • Ready
    • Released

    In the app: Plan (timeline, PI board, backlog, PI planning, Gantt, metrics; Planning (classic) in its sidebar) · RTM Manager

  6. 6Implement

    PRs and change requests are fed into the requirements: each requirement shows the change that built it and the release version that shipped it.

    Every requirement in the release built?

    In the app: Implementation

  7. 7Test

    The test cases reviewed in design are run, and each result updates the requirement's test status, last run date and coverage. Each case's steps sit beside their expected results; Reports › Validation tracks coverage, execution over time and the age of results. The master test workbook is shown in place on the Test Matrix, against the requirements its tests name.

    Passed?

    A test case:

    • Not run
    • Passed
    • Failed
    • Blocked

    In the app: Test (Standard and Advanced: the Test Matrix)

  • ↺ Not decomposed enough: split it and review the parts again
  • ↩ Design gap: a requirement no design covers, or a system missing, goes back to allocation
  • ↩ Rework: the requirement goes back to be rewritten or split
  • ↩ Failed: back to Implement, then the case is run again
  1. Review and decomposedecomposition · SMART · splits
  2. Allocate to systemssystems coverage
  3. End-to-end designdesign coverage · gaps
  4. Review sessionsstatus · open actions
  5. Plansprint · release · PI commitments
  6. ImplementPRs · release versions
  7. Testtest results · coverage · execution · age
Reports · track the whole delivery, from the first review to the tested release

Each step, and where the RTM app stands

Create

  1. 1

    RFP / SOW received

    A statement of work or RTM workbook is uploaded with the upload button and kept in the Library, typed and searchable. The DDD register entry is still filed by hand.

    Live
  2. 2

    Break down into requirements

    Each “shall” or “must” sentence of an imported SOW becomes a draft requirement linked to its page. Drafts already in the RTM are flagged, and a reviewer accepts each one, keeping the SOW's clause number or taking one from the RTM numbering rule. AI extraction comes in R6.

    Live

Manage

  1. 3

    Classify and number

    Requirement number, section, PI, type and attributes, numbered by the RTM numbering rule when the source has none. Add, edit in place, merge, search (with * as a wildcard) and export in a layout an Admin sets work in the app; an export imports back as it is, every change is in the change log, and the database is the master. A Deferred requirement needs a reason, picked from a list or typed (up to 100 characters); each deferral becomes a numbered change request (CR-0001 …) on Manage › Deferral log, emailed to the RTM Managers and Project Managers.

    Live

Design

  1. 4

    Associate to subsystems

    Each requirement has Systems: the subsystems that deliver it (website, mobile app, COMBO Web API, Tolls API, SMS, Email, Toll Calculator, CBOS). On Allocate subsystem each workstream lead records whether their subsystem supports it, how, and what it depends on. A Non Functional requirement records the process that resolves it instead.

    Live
  2. 5

    Link to design

    Requirement → programme epic → functional spec → user story → business rule, plus business processes, designs, document references and Jira tickets. Business rules are database records with their appendices, use cases and journey maps are linked to requirements, and the Capability Map shows the RTM by capability. Requirements are dragged onto features and epics on Epic & Functional Spec Mapping, and search by epic or feature drills down to linked RTMs.

    Live

Review

  1. 6

    Review and approve

    Requirements and their design are walked through with the client in a review session (Review › Reviews): agenda, slides, dispositions, minutes and actions, with comments on every item and each action followed up from Home and My comments. Library documents go through approval on the Documents tab, and splitting or merging an Accepted requirement is a change request an RTM Manager approves first. There is no electronic sign-off of the requirements yet.

    PartialR5

Plan

  1. 7

    Plan delivery

    The Plan holds the backlog, its breakdown, the program board, PI planning, the PI board, the program schedule and metrics; PIs and sprints, the release train by subsystem, milestones, and each requirement's PI, owner and target date are planned in the app.

    Live

Implement

  1. 8

    Build

    Every website change request carries a trace tag; the app syncs release notes every 15 minutes and shows the build against each RTM and rule. Each requirement has a release field per subsystem, and the Implement page shows the release each subsystem deployed it in.

    Live

Validate

  1. 9

    Verify

    Live test cases on Validate › Standard cover requirements: each step beside its expected result, test phase, tool, estimated time to run, status and last run date, searched and filtered by phase. Reports › Validation shows requirements coverage by test cases, status by phase, % automation, execution over time and the age of results; the Test Matrix shows the master test workbook. Only each case's latest run is kept: run history and a verification matrix come in R4.

    PartialR4
  2. 10

    Validate with the client

    UAT confirms the delivered behaviour meets the RFP intent. No UAT record or sign-off in the app yet.

    GapR5
  3. 11

    Baseline and accept

    Manage › Baselines takes a numbered, read-only baseline of the whole RTM with its trace links, compares it with the live RTM or another baseline, and exports it. The client's acceptance sign-off on a baseline comes in R5.

    PartialR5
  1. ↺

    Change request loop

    An Accepted requirement's text changes only with a reason, a source and a Change Order number, and goes back to Under Review. Splitting or merging an Accepted requirement raises a change request that is approved first, and every deferral is logged as a CR and emailed. Flagging each linked story, rule and test as suspect, with an impact view before approval, is still to come.

    PartialR3

Capability gaps against Visure

CapabilityRTM app todayPriorityRelease
Single sign-on, roles, audit trailEmail sign-in with Google Authenticator MFA, an invite email to each new person, a role per person with what each role sees and changes on Admin › Roles, client access per person and an audit log; no single sign-on yetCriticalR1
Version history per requirementChange log per requirement: who, when, old and new value, and the reason for a change to Accepted textCriticalR1
AI assistant and MCP serverSMART check with Claude (optional); no MCP serverHigh valueR1 read-only, R6
Single repository (backlog and rules in the DB)Backlog, rules and plan held in the database; the RTM workbook is exported from it with a Revision History and imports back as it isHighR2
Baselines and baseline diffNumbered read-only baselines, compared with the live RTM or each other, exported to ExcelHighR3
Change impact and suspect linksA reason, source and Change Order number before an Accepted requirement's text changes; no suspect linksHighR3
Test cases, runs and verification matrixLive test cases with steps and expected results, phase, tool, time to run, last result and coverage, and the master test workbook on the Test Matrix; only the latest run is keptHighR4
Coverage dashboardsData checks on Manage, key metrics on Home, and Reports with tabs and movable charts: requirements coverage by test cases, test execution over time, age of results and the requirements change rateHighR4
Reviews and electronic sign-offReview sessions, slides, dispositions, comments and actions; Library documents and change requests approved in the app; no sign-off of the requirementsMed–highR5
Jira and other tool integrationJira tickets copied and linked to the requirements they name (one way); the website release-notes feedMediumR5
Word / Excel compliance documentsExcel, PDF and Word export in a layout an Admin sets; Excel import; review minutes in ExcelMediumR2
NotificationsIn-app, email and Microsoft Teams: change notifications, imports, releases and review actionsMediumR5
Reuse and variants (web and mobile)NoneMediumR6
Risk analysisNoneLow–medLater
Safety-standard templates (ISO 26262, DO-178C)Not needed for the client—Not planned

Release train

PI 3 runs 20 Oct – 28 Dec 2026 in two-week sprints.

S120 Oct – 2 Nov
S23 – 16 Nov
S317 – 30 Nov
S41 – 14 Dec
S515 – 28 Dec
R1
PI 3 · S1–S2

Trust

  • Entra ID single sign-on; viewer, editor and approver roles
  • Audit trail and version history on every requirement
  • Retire instead of delete
  • Read-only MCP server so Claude sessions query the RTM directly
R2
PI 3 · S2–S4

Single source of truth

  • Backlog, web rules and subsystem allocation held in the database
  • Master workbook generated from the database, not edited by hand
  • DDD register entry written automatically on each export
R3
PI 3 · S4–S5

Baselines and change control

  • Named baselines per release, with diff and export
  • Suspect flags on linked stories, rules and tests when a requirement changes
  • Impact view for each change request
R4
PI 4 · S1–S3

Verification

  • Verification method per requirement; test cases and runs
  • Verification matrix and coverage dashboard by subsystem and PI
R5
PI 4 · S3–S5

Review and integrate

  • The client review workflow with comments and sign-off on baselines
  • Two-way Jira sync; notifications
R6
PI 5

Intelligence

  • AI extraction of requirements from an RFP or SOW
  • Suggested trace links, quality checks and stale-rule detection
  • Reuse of requirements across web and mobile

Build or buy

Keep building. The RTM app already holds the traceability the client relies on most (requirement to story, rule and website build), it is fed automatically by the website pipeline, and the gaps above are a known, bounded list. A Visure licence would add verification, baselines and reviews sooner, but would mean migrating the trace data and rebuilding the website feed. Revisit after R3 if the client requires a certified tool for acceptance.