Every MSL row, verified against its Test Certificate.
Upload a Material Summary List and its Test Certificates. TraceQC's pipeline reads every row, matches it to its TC/MTC evidence, and drafts an 8-section TPI report with a source page on every value. It flags what it can't read. It never signs off — that's still the QC/TPI inspector's call.
No shortcuts. No assumptions. No evidence, no acceptance.
No spam — one email when your access opens.
Dossier — TPI-2026-0842
MSL rows — 19 total
+ 14 more rows in this sample dossier
Evidence citations
Every finding on the report traces back to one of these.
TPI report — draft
Draft ready for QC/TPI review — nothing here is self-approved.
Minutes, not hours — without cutting a corner.
Reading one certificate by hand — finding the right cell, checking it against the requirement, writing it down — typically runs 5–10 minutes per certificate. TraceQC's pipeline drafts the same check in about a minute, with a source page on every value.
Founder's field estimate from manual QC/TPI review experience — not yet a measured benchmark across a published dossier set. Early-access batches will publish real numbers as they come in.
No re-scanning the PDF by hand for every requirement — the pipeline reads it once and cites every field.
Unreadable or ambiguous cells are flagged as Manual Cell Check immediately, instead of an inspector hunting for them.
A multi-agent pipeline classifies, extracts, and cross-checks fields in parallel, not one at a time by hand.
The inspector reviews and signs a draft that already exists — they don't build the table from a blank page.
What sets TraceQC apart
Built around one rule that never bends: AI never approves quality — it extracts, cites, and flags.
Evidence-first
Every value on the table carries a source page. No evidence, no acceptance — no exceptions.
Field-level judgment
Six real statuses, not a binary pass/fail — ambiguity becomes Manual Cell Check instead of a guess.
Multi-agent pipeline
~12 vision/LLM agents classify pages, locate TCs, and cross-check chemistry, mechanicals, and custody.
Audit-ready
Finalized reports are HMAC-signed; every action runs through a tamper-evident audit chain.
The verification pipeline, end to end
One connected flow from raw PDF to a signed report — nothing hops between disconnected tools.
Ingest the dossier as documents, not text
The MSL plus its Test Certificates, lab and NDT reports are rendered page by page — every downstream citation points back to a real page number.
Cross-check every field against its evidence
Each MSL row is matched to its Test Certificate, then checked field by field. A dual read — primary plus a recheck pass — catches disagreements before they ever reach the report.
An 8-section TPI report the inspector finalizes
Every finding shows Requirement, Observed value, Status, Evidence, Source Page, and Reason. The inspector reviews, corrects if needed, and signs off — TraceQC never marks its own work approved.
One MSL row's fields, moving through the pipeline.
TC No., Size, Qty, Grade, Heat No. and chemical/mechanical values each get pulled from the certificate, matched to the MSL row, and cross-checked — field by field, not the whole row at once.
Three steps, in order — the same order a careful inspector uses.
Upload the dossier
The MSL (Material Summary List) plus its supporting Test Certificates, lab and NDT reports. TraceQC renders every page as a document with a page number — not as flattened text.
The pipeline drafts the verification table
A pipeline of vision/LLM agents classifies pages, locates each MSL row's matching TC, and cross-checks TC No., Size, Qty, Grade, Heat No., and chemical/mechanical values against it — with a source page cited on every value. Anything unreadable is flagged for Manual Cell Check, never guessed.
QC/TPI reviews and finalizes
The inspector reviews the draft 8-section TPI report against its citations and makes the accept, hold, or reject call. TraceQC never marks its own work approved — only a human finalizes a signed, audit-ready report.
No evidence, no acceptance.
This is the one rule the product doesn't bend on — and it's why the copy below reads the way it does.
No evidence, no acceptance.
A readable value is the exact extracted value — never rounded or "cleaned up".
An unreadable cell becomes a Manual Cell Check, not a guess.
Final report rows are MSL rows only — nothing is added that wasn't on the list.
The final accept / hold / reject decision is always made by a human QC/TPI inspector.
If a value can't be traced to a page, it doesn't go on the table as fact.
"0.18% C against a requirement of ≤0.20% — p.14."
"Within limit." No number, no page, nothing to verify.
"Cell unreadable — flagged for Manual Cell Check."
Guessing a value to keep a row looking complete.
"Draft ready for QC/TPI review."
"Approved" or "Passed," said by the system about its own work.
Six field statuses. Two row decisions. No silent seventh.
Every field on a TraceQC dossier lands in one of six statuses — including the ones that mean a human needs to look. The row itself only ever gets closed out by the inspector.
Observed value meets the requirement, with its source cited.
Value is close enough to the limit, or ambiguous enough, to warrant a second look.
Source cell couldn't be read with confidence — a person checks it, nothing is guessed.
Passes with a documented concession, deviation, or supporting linkage attached.
Requirement doesn't apply to this certificate or material.
A note worth surfacing that isn't itself a pass/fail judgment.
The six statuses above are per field. Closing out a whole row is never automatic — it's one of two calls, and only the QC/TPI inspector makes it.
Row needs more evidence or a supplier response before it can close.
Row fails the spec as evidenced — the inspector's final call, not TraceQC's.
Built for material data you can't leak
Test certificates carry real supplier and customer information — the platform treats every dossier accordingly.
Curious about TraceQC?
Straight answers — same evidence-first rule applies to the copy here too.
What is TraceQC?+
An AI-assisted verification tool for industrial QC/TPI: it reads a Material Summary List and its Test Certificates, cross-checks every row against its certificate evidence, and drafts an 8-section TPI report for a human inspector to review and finalize.
Does TraceQC approve or reject certificates?+
No. It extracts, compares, and cites evidence — the accept, hold, or reject decision is always made by a human QC/TPI inspector.
What happens when a value can't be read?+
It's marked Manual Cell Check. TraceQC never fills in a value it isn't confident it read correctly.
What documents does it work with?+
A Material Summary List (MSL) plus its Test Certificates (TC/MTC), and supporting lab or NDT reports.
Is our data secure?+
TLS in transit, a tamper-evident audit chain, HMAC-signed finalized reports, and multi-tenant isolation by company — see the Security section above.
When do I get access?+
Early access is opening in small batches. Join the waitlist below and we'll reach out.
Ready to verify your first dossier?
We're onboarding QC and TPI teams in small batches ahead of launch. Leave your email and we'll reach out when a spot opens.
No spam — one email when your access opens.