Requirements Traceability Workflows

01 / Requirements & changes

Preserve the reason behind the requirement.

Capture requirements in a structured hierarchy, link related records and compare what changed between baselines.

Use requirement IDs, attributes, modules and parent–child relationships.
Trace requirements with typed links and review suspect relationships.
Review and approve requirements, then record controlled content changes through approved change requests.
Compare baselines and export the differences.

Role permissions govern available actions. Administrators have additional authority, and the audit record retains the changes.

RTM hierarchy of source and derived engineering requirements — Selected requirement hierarchy: organise the source and derived records before following dependencies and changes.

Start with a template. Adapt it to your project.

Built-in attribute templates give you a starting structure. Add typed fields — text, integer, enum, boolean or date — and identify attributes required before approval.

Import or export the attribute schema as CSV, and use bulk fill to apply consistent values. A template supplies structure; your contract defines the actual requirements.

RTM built-in attribute templates — Built-in attribute templates in RTM. Choose the structure relevant to the project and adapt the fields.

Keep the before and after of a change.

Compare baselines to see changed statements. Approved change requests retain the decision and rationale; affected trace links can be marked suspect for engineering review.

RTM baseline comparison showing the earlier and changed requirement statements — Selected baseline comparison: two changed requirements. “Suspect” trace links identify relationships to review after a change.

02 / Supplier Response Exchange

Keep each supplier conversation attached to its requirements.

A revised answer can introduce a condition, a clarification or a formal exception. RTM records each round and its outcomes so the accepted position can be followed.

IssueSelect requirements and export an RFI package.
ImportBring the supplier’s response CSV into its round.
ClarifyRecord questions, answers and outcomes.
DecideAccept responses or decide deviations and waivers.
CloseClose the round when responses have been resolved.

Supplier exchange dashboard with supplier-specific rounds, answers and exception counts — Supplier response overview. Counters include recorded outcomes across the example rounds.

Retain the clarification and its outcome.

Questions and answers stay with the supplier response. Deviation and waiver decisions can retain rationale and conditions.

Suppliers use exchange files to reply; they do not need to run RTM for that reply.

An accepted supplier response records an agreed position. Executed verification and its supporting evidence remain a separate engineering responsibility.

RTM accepted third-round supplier response — Selected third-round supplier response: the 100 ms position is accepted. Earlier replies and their exception decisions remain in the project record.

03 / Verification & evidence

See the coverage. Investigate the gaps.

Link requirements to tests and supporting documents. Review what is covered, what remains untested and what needs further evidence.

Manage test methods, criteria, actual results and evidence references.
View requirement coverage alongside test status.
Register evidence documents and their revisions.
Use evidence checks to identify missing or unapproved supporting documents.

RTM test cases with results and evidence references — Selected test list: PASS, FAIL, BLOCKED and NOT_RUN are distinct recorded states.

Notice when the supporting file changes.

RTM records a registered file’s SHA-256 hash and can identify a changed or missing file. The team can flag related trace links for review.

Document revisions can supersede earlier records while preserving their relationship.

RTM document register flagging a changed evidence file — A changed registered file is flagged for review.

Evidence checks flag missing or unapproved supporting documents. Integrity checks identify file changes; they do not certify the document’s contents. Evidence reports support review preparation and do not guarantee customer or contract acceptance.

Governance & audit

Control access. Keep the decision trail.

A recorded audit history records the user, time, action and detail. Filter by user, action keyword or date, then export the records to CSV for review.

Combine the operation log with role permissions, requirement versions, review outcomes and change requests to follow the engineering decision trail.

The audit trail supports accountability and review. Your project still defines approval responsibilities and acceptance criteria.

RTM audit log filtered by user — RTM audit log with user, action and date filters, record details and CSV export.

04 / Reports & exchange

Share a readable engineering record.

Choose from 24 Reports & Exports menu options, covering reporting, checks and file exchange. The Programme Pack brings eight connected project files together: requirements, compliance, verification, risks, suppliers, SOW, supplier requirements and a milestone report.

Requirements and traceability matrices.
Supplier traceability and deviation/waiver records.
Verification status and change request audit reports.
CSV and ReqIF exchange within the supported format scope.

ReqIF exchange supports the documented mappings. Review the scope below when planning a transfer between tools.

Read the deployment and exchange FAQ →

RTM supplier traceability report excerpt — Selected supplier traceability report: follow issued requirements, replies and linked engineering records.

ReqIF import scope
Supported within documented mappings	Not retained as original content
Requirements, hierarchy and supported relations	Attachments, images and baselines are not imported
Mapped fields; preview identifies unmapped or adjusted values	Rich XHTML becomes plain text

Also included

Roles and permissions

Viewer, Analyst, Engineer and Admin roles control what each account can do.

Audit history

Changes are recorded with who made them and when, alongside requirement history and the change request audit log.

Review records

Record review decisions and comments against requirements.

Tender clauses

Record tender entries and link them to the requirements that respond to them.

Suppliers and SOW items

Record suppliers, statement-of-work items and supplier requirements alongside your own.

Risk register

Record risks by likelihood and impact and relate them to requirements.

Milestones and baselines

Track progress against milestones and take baselines for later comparison.

Custom attributes and modules

Add project-specific attributes and organise requirements into modules.

Reports and exports

Built-in reports, plus CSV, ReqIF, HTML and ZIP pack exchange within the documented scope.

Make the workflow concrete

See the workflow behind your engineering question.

Choose a supplier reply, a baseline change or a verification record for a focused demonstration.

Book a Guided Demo Get the Free Radar Case Pack ↓

Prefer to explore first? Follow supplier decisions, controlled changes and evidence checks in the free 10-page radar case, with a review checklist and Excel / CSV references.