Trace Map

One serial.
The whole story.

Type a record number — or a serial, job, or reference number — and QFormance walks the connected graph across every module. The NCR, the meeting where it was discussed, the actions it spawned, the audit that caught it, the product and supplier behind it — one expandable, exportable tree.

app.qformance.io / trace-map ? q=NCR-0042
NCR-0042
Trace

3

Open actions

5

Closed actions

1

Overdue

7

Records

NCR 1 · MTG 2 · AUD 1 · MOC 3

NCR-0042Surface finish out of spec
Meetings(2)
MTG-0118CAPA review — week 12
Actions(2)
Re-validate polishing stationAction
Update WI-PROD-07Action
Audits(1)
AUD-0031Q2 internal — production
Products(1)
PRT-3391 Rev C — Housing bracketProduct
Suppliers(1)
Meridian CastingsSupplier

Two ways in. One graph out.

Start from a specific record, or from a number that shows up on many records at once. Either way you get the same connected tree.

By record number

Type a record number and trace outward from it — the classic single-thread investigation.

  1. 1Enter NCR-, MOC-, AUD-, MTG-, RISK-, EX-, JHA-, or FMEA-
  2. 2The record becomes the root of the tree
  3. 3Everything it links to fans out beneath it
  4. 4Follow record → record → record to any depth
MOC-0208RECORD
MOC-0208New solder profile
FMEAs(1)
FMEA-0044Reflow process
Documents(1)
WI-PROD-07 — Reflow work instructionDoc
Actions(1)
Qualify new profile on line 2Action

By shared reference

Type an exact reference, serial, or job number and find every record across every module that carries it.

  1. 1Enter a serial / job / reference number
  2. 2Every record that shares it becomes a seed
  3. 3Each seed opens into its own connected tree
  4. 4See the full footprint of one physical thing
SN-88231-AREFERENCE
3 records share this reference
NCR-0042Surface finish out of spec
EX-0017Temporary rework exemption
MTG-0118CAPA review — week 12
Reading the tree

Grouped, expandable, and clickable end to end.

  • Module groups

    Under every record, its connections group by module — Non-Conformances, Meetings, Audits, and so on — each with a count. No wall of undifferentiated links.

  • Expandable records

    Linked records are expandable nodes: open one and its own connections fan out. Small traces open fully; large ones start collapsed at the module level so they stay legible.

  • Hyperlinked leaves

    Products, suppliers, clients, and linked documents appear as leaves — they don't expand further, but every one links straight to its detail page.

  • Actions & the overdue flag

    Actions raised against a record hang beneath it. An open action past its due date is flagged inline so nothing that's slipping hides in the tree.

Trace tree · NCR-0042
NCR-0042Surface finish out of spec
Meetings(1)
MTG-0118CAPA review — week 12
Actions(2)
Re-validate polishing stationAction
Update WI-PROD-07Action
Products(1)
PRT-3391 Rev C — Housing bracketProduct
Suppliers(1)
Meridian CastingsSupplier
Clients(1)
Northwind AerospaceClient
Trace summary

3

Open actions

5

Closed actions

1

Overdue actions

7

Records in trace

NCR 1 · MTG 2 · AUD 1 · MOC 3

Created:3 mo6 moLast 12 months24 moAll time
Action status & date filter

The follow-up work, summed up front.

Above the tree, four cards roll up every action in the trace: open, closed, and overdue counts, plus a total record count with a per-module breakdown. You see whether the thread is still live before you read a single node.

A created-date filter bounds which records the trace pulls in — defaulting to the last 12 months, with 3 / 6 / 12 / 24-month presets, an all-time option, and a custom range. A sprawling history stays readable; a narrow window keeps the export tight.

Export for auditors

Hand an inspector the whole thread.

Export the trace and it prints fully expanded — every node open, regardless of how you left it on screen — behind a header that records the query, the mode, the created window, who traced it, and when. Drop it in the audit file as evidence that a record's connections were reviewed end to end.

Fully expanded

The printed tree opens every record and group, so nothing hides in a collapsed node when it reaches an inspector.

Traced-by header

Query, mode, date window, the person who ran it, and a UTC timestamp — the provenance an auditor asks for.

Rollup on the page

Record count and open / closed / overdue action totals print alongside the tree for a one-glance summary.

How it behaves

Directional, read-only, and permission-scoped.

Trace Map is a view over links that already exist. It doesn't create, edit, or delete anything — and it shows you nothing you couldn't already open yourself.

Outgoing links

The tree follows links in the direction they were drawn — from the source record outward. A record you sourced a link from appears under it; the reverse direction isn't walked, so the thread stays directional and finite.

Leaves link out, don't expand

Products, suppliers, clients, and linked documents are endpoints. They're hyperlinked so you can jump to them, but the trace doesn't keep walking through them into unrelated records.

Read-only, RLS-scoped

Every query runs as you. If your permissions don't reach a record, it simply doesn't appear in the trace — the map never becomes a back door around access control.

Follow the thread. Prove the story.

Start your 30-day free trial and trace any record across your whole QMS from day one.