Requirements Traceability Gap Findertrace sheet
For whoever owns the trace before the assessor samples it

Paste your requirements export. See every break in the trace.

Requirements Traceability Gap Finder reads your requirements export and test results line by line. Paste your requirements export and test results: IDs, parent links, verification method, linked tests, results and dates, with or without the requirement text. Every requirement comes back traced up to its parent and across to its verification, with the breaks an assessor samples: no parent, no verification, a test that failed or never ran, a requirement changed after its last passing test, and tests that trace to nothing, each cited to the clause of ISO 26262, IEC 62304, ISO 13485, DO-178C, AS9100D or IATF 16949 that asks for it.

Trace your own exportA first-pass traceability integrity review of your export; it never claims the matrix is complete. 25 requirements free, no account.
  1. Paste IDs and links only if you prefer; the requirement text is optional and nothing leaves your browser until you save.
  2. A paste, never a connection: an export from your requirements tool or your spreadsheet matrix. Nothing connects to DOORS, Jama, Polarion or anything else.
  3. Every break shows the clause that asks for the link and the column it read.
  4. It rules on nothing. It never calls a product or a project fit for assessment: every break is a question for the requirement owner or the reviewer.
Specimen, one chain of 40an invented infusion pump program
  • UN-2user needvalidationVAL-02recorded
    • SYS-2system requirementtestST-03passed2026-06-19
      • SRS-3software requirementclass CtestUT-103passed2026-09-12IT-201passed2026-09-15
      • SRS-54class CtestUT-105passed2026-09-22
      • HW-2hardware requirementtestHT-301passed2026-07-08
    • SYS-3testST-04passed2026-06-19
      • SRS-63software requirementclass BtestUT-106failed2026-09-22

40 requirements, 7 with no passing verification, 1 changed since it was tested.

8 of 10 findings raised on 15 requirements, 2 tests tracing to nothing, every one cited to IEC 62304, ISO 13485 or the FDA QMSR.

An engineer working on a laptop inside a vehicle wiring and seat test rig
Walk into the confirmation review or the design file review already knowing each link the assessor will pull on, and the clause behind it. It works from the export you already have, in your browser, with no connection to your tools.
01

Paste the export as it comes

One requirement per row: ID | Parent at least, or a header row with level, verification method, verified by, status, safety rating, last changed, derived and validation. The column names requirements tools and spreadsheet matrices export are read as they are. Test results go in the second box.

02

Read the trace, need to proof

Each chain is drawn from the top-level requirement down, with the verification on the right: highlighted where it is traced and passed, ringed where it breaks, struck through where the requirement changed after its pass. Safety-rated requirements come first.

03

Take the questions to the review

Ten findings in a fixed order, each naming its requirements and the clause of the standard you ticked. The review sheet has blank columns for the reviewer's decision; the board summary puts the counts on one page.

Box 1, one requirement per row: ID | Parent, or a header row with any of Level, Verification Method, Verified By, Status, ASIL or DAL or Safety Class, Last Modified, Derived, Validation, Text. Box 2, optional, one test per row: Test ID | Result | Date, with Requirements if the export carries it. Tabs, pipes, commas or double spaces. First lines such as standards: ISO 26262, ASPICE or as at: 2026-10-01 set the options below.
Nothing is sent anywhere until you choose to save.
What you tell it (first lines of a paste set these too); nothing else is assumed

Your requirements traceability matrix, read the way an assessor samples it

A requirements traceability matrix is the table that ties each requirement to the one above it and to the test, analysis or inspection that proves it. An assessor rarely reads it end to end; they pull a thread: pick a requirement, follow it up to the need it serves and across to its passing result, and ask about any requirement changed since. This reads your matrix, or the export your requirements tool produces, and pulls every thread at once, in your browser.

The rules are published in full: what each standard asks of the trace, the ten findings, the requirement levels it reads, the verification methods, what a requirements traceability matrix is, suspect links and the requirements traceability matrix template. It reads the paste only; a finding names the clause and asks the question, never a ruling on the product.