Product · Features

Engineering traceability, end to end.

One workspace connecting requirements, specifications, components, vendors, submittals, tasks, risks, and tests — with every link visible and every change governed.

Trace canvas

Every link across your project, in one graph.

The trace canvas shows how requirements connect to specifications, specs connect to components, and components connect to test evidence — in a live, interactive graph. Gaps are visible as missing edges, not missing rows in a spreadsheet.

  • 017 node types: Requirements, Specs, Products, Components, Risks, Decisions, Tests
  • 0211 typed edge kinds — SATISFIES, IMPLEMENTS, MITIGATES, EVIDENCES, BLOCKS, and more
  • 03Gaps appear as isolated nodes with no downstream evidence
  • 04Each node opens the full record inline — no context switching
/projects/medtelemetry · trace · 8 nodes · 7 links
Requirements
Specifications
Components
Tests
REQ-001

Uptime ≥ 99.9%

Customer · v3

REQ-042

Calibration interval

Regulatory

RISK-03

Buffer overrun on loss

High · open

SPEC-019

Telemetry buffer policy

Approved §3.2

SPEC-021

Calibration cadence

In review

CMP-007

Sensor module v4

Subsystem

TC-014

Recalibration drill

Verification

TC-022

Uptime stress test

Verification

SATISFIESIMPLEMENTSMITIGATESEVIDENCES

Trace score

One number that says how close to handover you are.

The trace score is a weighted 0–100 composite across requirement definition, specification coverage, product linkage, verification evidence, and risk mitigation. It tells you which gap is hurting most — and assigns the fix to a specific owner.

  • 01Five weighted dimensions — each gap is named, not just counted
  • 02Verification coverage is the hardest dimension to fill; it surfaces early
  • 03Score updates in real time as test cases are linked and risks mitigated
  • 04One number to report; full breakdown for your engineers
74/ 100Trace score
Requirements defined92%
Specification coverage88%
Product linkage71%
Verification coverage54%
Risk mitigated67%

Score drag: Verification coverage at 54% — 12 requirements have no linked test case. Assign owners in the Verification matrix to recover ~14 points.

Verification matrix

Know exactly which requirements have evidence.

The verification matrix links test cases — by method: TEST, ANALYSIS, INSPECTION, DEMONSTRATION — to the requirements they cover. Gaps are cells, not footnotes. Each gap has an assigned owner so nothing falls through at the handover review.

  • 01Filter by method, discipline, pass/fail status, or open gap
  • 02EVIDENCES links carry the test result and the acceptance record
  • 03GAP rows surface unlinked requirements with recommended owners
  • 04Coverage percentage updates live as commissioning evidence is submitted
Verification matrix46% coverage
Test caseMethod001019042057063071
TC-001TEST
TC-014ANALYSIS
TC-022INSPECTION
TC-031TEST
GAP-004OWNERREQ-071 has no test case — assign before handover review

Requirements governance

Requirements that can't be changed silently.

Every change to a requirement goes through a change request — a diff, an assignee, a review, and an approval — before the baseline moves. The activity log captures every step. Old versions are never deleted; they're always attached to the baseline they lived in.

  • 01Immutable version history — every edit is a snapshot, never an overwrite
  • 02Change requests show a diff of exactly what changed and why
  • 03Approval gates prevent a baseline from moving without sign-off
  • 04Full audit trail: who changed what, when, and from which state
REQ-042 · diff

− Thermal range: −20°C to +85°C

+ Thermal range: −40°C to +85°C // cold-start added

v1

Baseline requirement

Thermal range: −20°C to +85°C

CR

CR-014 submitted

Customer requests cold-start down to −40°C

Assigned for review

Lead Systems Engineer · due 2025-03-19

Approved

All linked specs updated; baseline v3 locked

LockedREQ-042 v2 · Baseline v3 · Approved by S. Lin · 2025-03-19

Risk register

Risk with a full mitigation chain attached.

Risks are scored on a 5×5 impact × probability matrix and linked to the spec sections that address them and the test cases that verify those mitigations. Unmitigated high-impact risks stay visible at the project header — they can't be hidden in a long list.

  • 015×5 heatmap shows concentration of risk before it surprises you
  • 02Each risk links to its mitigating spec and verifying test case
  • 03Unmitigated risks flagged at project level, not buried in a register
  • 04Risk score feeds the trace score — mitigation directly improves project readiness
Impact →
Probability ↑
1
2
3
4
5
·
·
R12
·
·
·
·
·
R07
·
·
·
·
·
R03
·
·
·
R09
·
·
·
·
·
·
Top risks
RISK-03Buffer overrun under packet lossHigh
RISK-07EMI susceptibility at 2.4 GHzCritical
RISK-12Supplier lead time slipHigh
RISK-09Firmware rollback incompatibilityMedium
RISK-07WATCHNo mitigating spec linked — assign before PDR

Ready to see your project traced?

Spin up a workspace in under a minute. Import requirements, connect specs, and watch the trace graph fill in.