Vericord MTR Validation
Catches reported values that do not meet code before nonconforming material enters your supply chain.
Line-item report
Sample data
Illustrative values, not from a real specification.
| Item | Reported | Required | Status |
|---|---|---|---|
Carbon Sample spec, Table 1 | 0.21% Required: 0.30% max | 0.30% max | Compliant Reported value is within the maximum. |
Manganese Sample spec, Table 1 | 0.92% Required: 0.29% to 1.06% | 0.29% to 1.06% | Compliant Reported value is within the range. |
Tensile strength Sample spec, Table 2 | 57 ksi Required: 60 ksi min | 60 ksi min | Non-compliant Reported value is below the minimum. |
Yield strength Sample spec, Table 2 | 38 ksi Required: 35 ksi min | 35 ksi min | Needs review Low-confidence read, surfaced for review. |
Requirement not machine-validated Sample spec, Table 3 | — Required: Manual verification | Manual verification | Exception Report Listed for mandatory manual verification. |
One failing value fails the MTR.
- Exception Report: 1 requirement for manual verification
- Sign-off: requested from 2 reviewers
Processing takes 30 seconds to 3 minutes per MTR, depending on size.
You pay per scan from a prepaid wallet; see MTR Validation pricing.
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.
The line-item report
For every line item, the report shows the extracted value, the required value, the governing section and footnotes, the status, and a written reason.
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.
Access
Admin, User, and Viewer roles and organization-wide two-factor authentication control who can see and change records.
Proof
Do deterministic rules decide every pass or fail?
Deterministic rules decide every result.
Is every in-scope requirement accounted for?
Each one is machine-validated or listed in the Exception Report for mandatory manual verification.
Do card details stay out of Vericord’s systems?
Card details go to Stripe and never reach Vericord.
Accuracy is 95% or better in testing, measured on both correct extraction and correct requirement values.
The same extracted values always produce the same verdict.