MTR
Vericord MTR Validation
MTR Validation checks mill test reports against code requirements.
Each value shows what the MTR reports, what the code requires, the governing section and footnotes, the status, and a written reason.
Verified Compliance for MTRs and Inspections
Ask Veri
Veri answers from Vericord’s published documentation and can be wrong. Verify before any acceptance or safety decision.
Veri sends your question to Vericord’s documentation service and an AI provider to answer it. Don’t include personal or confidential information. Privacy Policy
MTR Validation in numbers
30 s to 3 min per MTR, depending on size
95% or better in testing, measured on both correct extraction and correct requirement values
about 20 to 45 min saved per MTR, modeled from Vericord assumptions
$25 per scan up to 3 pages
Two products from Vericord
IQ3
Vericord IQ3
IQ3 is an inspection and multimedia records platform.
Inspectors record video, audio, list, and form inspections in the IQ3 app on iOS and Android devices.
Records upload to the IQ3 MMS (Multimedia Management System), the web platform where teams monitor live events, run remote video inspections, play back recorded events, and generate reports.
How it works
Upload
Upload the MTR in the Vericord Portal.
Extract
The model reads the reported values.
Validate
Deterministic rules built by materials subject matter experts (SMEs) from the code books make every pass or fail.
Exception Report
In-scope requirements not machine-validated are listed in the Exception Report for mandatory manual verification.
Sign-off
Multi-party electronic sign-off, internal or external, sequential or parallel, recording name, time, and IP address.
What it catches
Catches reported values that do not meet code before nonconforming material enters your supply chain.
The same extracted values always produce the same verdict.
Built for the record
Uncertain values
Uncertain values are surfaced for review; corrections are logged with old value, new value, user, and time.
Records and audit trail
Saved records are locked with the original MTR preserved, with a change log and a field-level audit log.
Your data
MTRs are never used to train AI models, by Vericord or its AI providers; AI providers do not retain customer documents.
Requirements library
Hand-built from the code books and verified by materials SMEs, with values taken from the printed code in its own units, never converted or recalculated.
Security
Covered by a SOC 2 report, available under NDA, with AES-256 at rest and TLS 1.2 or 1.3 in transit.
The model reads; it never rules.