Your RTM.
Done tonight.

A requirements traceability template that works the way you actually work, in a spreadsheet. Free download. Nothing leaves your machine.

Download Template (.xlsx) Learn more ↓
Covers: AS9100 ISO 13485 DO-178C IEC 62304 ISO 26262 ASPICE
Need standalone risk management or SOUP templates? Free FMEA, hazard log, SOUP, and BOM templates →

How to make audits not suck

Four tabs. One schema.

User Needs, Requirements, Tests, Risks. The relationships that every audit cares about, in a structure your team already knows how to use.

Generate an RTM.

Check your audit status: just drag & drop the file onto RTMify Trace. Get a full analysis and your RTM.

.docx .pdf .md

Live traceability updates.

Using RTMify Live: whenever anyone touches a cell in the sheet, every row gets a realtime status update. Gaps surface before the auditor does.

OK NO_TEST_LINKED MISSING_ID

How it works

  1. 1

    Download the template

    Free .xlsx file. No account, no email, no friction.

  2. 2

    Fill in your requirements, tests, risks

    Use the four tabs: User Needs, Requirements, Tests, Risks. Add your IDs, descriptions, and cross-references.

  3. 3

    Drop the file on RTMify Trace

    Runs on your machine. No need to call IT, your data always stays local.

  4. 4

    Get an RTM as a PDF / Word Doc / Markdown

    Full traceability matrix from requirements to tests to risks. Print it. Email it. Put it in your technical file. Dazzle your friends.

Traceability doesn't need to cost six figures.

Used by quality engineers at medical device, aerospace, and automotive companies. Built by people who've written RTMs at 11pm the night before an audit.

RTMify Live · MCP

"I'm literally talking to my requirements. Jama, Polarion... nobody has this feature."

— RTMify Live user, via Claude Code

Your RTM isn't a static document you update before audits. With RTMify Live, it's a live knowledge graph you can talk to.

See RTMify Live →
Claude Code — ~/Projects/security-system
❯ Which user needs have no requirements?
⏺ rtmify-live · get_rtm (MCP)
⏺ Only UN-010 has no requirements linked to it:
"The system shall provide an audible alarm > 85dB at 3 meters."
Priority: High · Source: Safety
⚠ High priority Safety need — worth addressing soon.
❯ I know you don't have enough context to get why, but I have goosebumps. I'm literally talking to my requirements. Jama, Polarion... nobody has this feature. This is game changing.
⏺ That's the whole point of rtmify — your RTM isn't a static document
you query with a form. It's a live knowledge graph you can just talk to.
 
You can ask things like:
· "What's the impact if UN-002 changes?"
· "Who last touched the code linked to REQ-001?"
· "Which requirements have no code implementation yet?"
 
No form. No export. No pivot table. Just ask.

Standard-specific guidance

The template covers all six standards. Each standards page explains exactly what the standard requires, what the template covers, and where teams typically miss.

AS9100

AS9100 RTM Template

Aerospace quality management. §8.3 design controls, traceability, and configuration management.
ISO 13485

ISO 13485 RTM Template

Medical device QMS. §7.3 design inputs, outputs, V&V, and risk per ISO 14971.
DO-178C

DO-178C RTM Template

Airborne software. HLR/LLR traceability, DAL annotation, bidirectional coverage.
IEC 62304

IEC 62304 RTM Template

Medical device software lifecycle. §5.2–5.7, safety class, SOUP tracking.
ISO 26262

ISO 26262 RTM Template

Automotive functional safety. HARA, ASIL assignment, V-model traceability.
ASPICE

ASPICE RTM Template

Automotive SPICE. SYS.2/SWE.1–6 bidirectional traceability and capability evidence.

Download the template

Free. No account. No email. Works in Excel and Google Sheets.

Download Template (.xlsx) Learn about RTMify →