For analytical laboratories
Stop answering the same report question twice.
TECRID gives each laboratory-issued report a persistent identifier, a verified issuer signature, and a versioned record that customers and authorized recipients can resolve without asking the laboratory to reconstruct the evidence by email.
The operational problem
PDF delivery ends the laboratory’s control over provenance.
A PDF or Certificate of Analysis is a document—not a TECRID. Once that file is downloaded, forwarded, renamed, cropped, or manually transcribed, the laboratory is pulled back into verification calls and disputes. TECRID keeps the verified issuer, structured findings, source fingerprint, status, and correction history attached to a persistent record.
What changes
A report becomes reusable evidence.
Answer “did this come from us?” with a resolver.
A TECRID or source-document fingerprint can be checked against the laboratory-issued record and produce a durable verification receipt.
Route issuance to the customer workspace.
The brand receives the issued TECRID in its portfolio while recipient-specific grants can deliver narrower packages to certifiers, retailers, or government programs.
Correct or revoke without erasing the past.
Corrections and revocations append a signed status event or version. The prior fingerprint, reason, and verification receipts remain in the authorized audit trail.
Add the TECRID to the final laboratory report.
Reserve an identifier, render it or its resolver URL in the report template, fingerprint the final PDF, sign the canonical payload, and finalize issuance through the API.
A controlled workflow
From LIMS release to customer delivery.
- 01Reserve the TECRID
The laboratory reserves the identifier before rendering the final report so the report itself can display the TECRID and resolver destination.
- 02Canonicalize and sign
TECRID returns the exact UTF-8 payload. The laboratory signs it with its verified Ed25519 key.
- 03Finalize the report
The final PDF fingerprint, structured results, methods, identifiers, dates, and signature become the issued record.
- 04Resolve, route, and maintain
The customer receives the record in its workspace; authorized recipients receive only their granted evidence scope. Corrections and revocations remain traceable.
Trust without overclaiming
Registry verification is not blanket technical endorsement.
- ICS verifies the laboratory identity, authority, evidence, approved issuance scope, signing-key control, and TECRID conformance.
- A PDF or COA does not become a TECRID merely because an identifier is printed on it; the record must be finalized by an authenticated issuer.
- Accreditation and method scope are shown as evidence; TECRID does not expand or replace a laboratory’s accreditation.
- A valid signature proves origin and integrity. It does not prove that sampling was representative or the scientific interpretation was correct.
- Private and controlled records are not made public by joining the registry.
Begin with one workflow
Your laboratory says GO. Use the same-day launch path.
Create a sandbox key, issue the fictional test record, call the candidate VLE evidence endpoint, and review the production checklist. Live issuance remains locked until every issuer-verification gate passes.