About RTMify
Compliance-Aware Lifecycle Manager. Starting with the tool every regulated-industry engineer already uses: the spreadsheet.
The problem
Requirements live in spreadsheets. That's not going to change.
Every ALM tool that tried to replace the spreadsheet either failed to gain adoption or became something engineers actively work around. The reasons are structural: spreadsheets are flexible, offline-capable, diffable, and understood by every engineer, QA manager, and auditor on the planet. Nobody needs a training session to open an .xlsx file.
The problem isn't the spreadsheet. The problem is that spreadsheets don't have opinions about what goes in them. No required fields. No status computation. No way to know, at a glance, which requirements have no test coverage. You find out when the auditor does.
RTMify doesn't replace the spreadsheet. It makes the spreadsheet smarter by giving it a schema that maps to what auditors actually look for, and tooling that surfaces gaps before they become findings.
Your QMS tells you how you're supposed to work. RTMify tells you what you actually built and whether it does what it's supposed to do.
The free template
The RTMify Requirements Tracking Template is an .xlsx file with four tabs: User Needs, Requirements, Tests, Risks. The schema is designed to satisfy the traceability requirements of AS9100, ISO 13485, DO-178C, IEC 62304, ISO 26262, and Automotive SPICE simultaneously. Use it for all six, or use it for one.
It's a point-in-time snapshot. You fill it in, you use it, it reflects the state of your program at the moment you touch it. That's useful; it's what the audit artifact is. The template is good for tonight's RTM.
It's not good for keeping 400 — or 4,000 — requirements current across a 6-month program. When requirements change (and they always change) the template doesn't know. You have to update it manually. If you don't, you find out your test coverage has drifted when the auditor checks the traceability chain. That's whey you need RTMify Trace. Scroll down and keep reading.
RTMify: Trace
Drop your .xlsx on RTMify Trace. Get a PDF, Markdown, or DOCX requirements traceability matrix, with requirements, tests, risks, and the full traceability chain resolved.
It runs on your laptop. Nothing is uploaded. There's no account. For engineers at companies where "upload it to a cloud service" is not an option (defense contractors, medical device companies, regulated financial firms), this matters.
Your data stays local. Your Requirements Traceability Matrix is created instantly.
RTMify: Live
We parse the data exhaust of all of your product design and product manufacturing work.
The work is already done. The code was written. The tests were run. The components were assembled. The evidence exists already. It's in git, in test logs, in ATE output, in BOM exports. The problem is that nobody connects it. The connection happens manually, after the fact, in some tedious manual process (usually a spreadsheet) that's always behind, maintained by someone who's always underwater.
RTMify's thesis is: stop building the connections manually. Just parse the data exhaust. The evidence is already there. The graph builds itself.
RTMify Live connects to your Google Sheet and keeps it current — automatically. Every 30 seconds it re-evaluates the full traceability chain. When a requirement changes, Live identifies which tests need re-evaluation, flags them in the sheet, and color-codes every row: green for covered, yellow for gaps, red for errors. No manual updates. No stale RTMs.
But the sheet sync is just the start.
Live reads your git repository. It walks your source tree, finds every comment where a developer referenced a requirement ID — a simple tag like // REQ-047, no special tooling required — and runs git blame on each one. The result: a live map from requirement → source file → author → commit. One convention, no process change, and you can see exactly which requirements have been implemented, by whom, and when — and which haven't been touched since the spec was written.
Live runs an MCP server. MCP (Model Context Protocol) is the standard that lets AI assistants connect to live data. With RTMify Live running, you can open Claude, Cursor, or any MCP-compatible client and have a real conversation with your requirements: "Which requirements have no test coverage?" "What breaks if I change REQ-047?" "Show me the full traceability chain for this user need." "Who implemented this and when?" Your RTM becomes a knowledge base you can actually talk to.
Live knows your standard. Pick a profile — Medical (ISO 13485 / IEC 62304 / FDA), Aerospace (AS9100 / DO-178C), Automotive (ISO 26262 / ASPICE), or Generic — and Live enforces the right traceability chain. Medical needs Design Inputs and Outputs. Aerospace requires HLR/LLR decomposition. Automotive checks ASIL inheritance. Live surfaces the right gaps for your regulatory context, not a generic list.
| Feature | Legacy ALM (Jama / Polarion) | RTMify |
|---|---|---|
| Learning curve | 2-week "certification" | 0 minutes — it's Excel |
| Data privacy | Cloud, or complex on-prem | 100% local / your repo |
| Traceability | Manual linking | Auto-mapped via git blame |
| AI-ready? | No / "Beta" | Native MCP server |
| What engineers actually use | Excel (on the side) | Excel (that's the whole point) |
Contact
Questions, feedback, or a specific standard we haven't covered: hello@rtmify.io