Test results that always trace back to a calibrated instrument
A testing laboratory whose accreditation depended on proving that every result came from an instrument calibrated at the time of measurement.
Who they are.
A testing laboratory whose accreditation depends on a simple claim it must be able to prove: every result it publishes came from an instrument that was calibrated at the moment of measurement.
Anonymised at the client’s request. Client names are never disclosed without written permission.
What had to be solved.
Traceability was reconstructed at audit time from separate registers. A calibration certificate expiring mid-month invalidated tests that nobody had listed, and the link between a result and its instrument often lived in an operator’s notebook.
What success looked like.
- Tie every test record to the instrument’s calibration validity on the test date
- Catch an out-of-calibration result before the report leaves the lab
- Stop rebuilding traceability during audit week
What Ceertia does here.
A use case for test records that checks the instrument’s calibration certificate against the measurement date on the record itself. A result from an out-of-calibration instrument is flagged before the report is released, with the certificate cited.
The instrument used must hold a valid calibration certificate covering the measurement date.
How it runs, step by step.
The file arrives with its documents, in any format, from whoever sends it.
Every page is identified and mapped against the expected document list. Missing documents, duplicates and out-of-scope pages are flagged on receipt.
Each rule asks the file a question and answers it directly on the documents, with page, zone and source text attached to the verdict.
The team approves, requests a fix, or rejects. No file is approved or rejected automatically.
What changed.
Traceability became a stored verdict rather than an annual reconstruction. Audit week now consists of exporting evidence instead of assembling it.
- Traceability was reconstructed at audit time from separate registers.
- A calibration certificate expiring mid-month invalidated tests nobody had listed.
- The link between a result and its instrument lived in an operator’s notebook.
- Every test record is checked against the instrument’s calibration validity on the test date.
- A result from an out-of-calibration instrument is flagged before the report goes out.
- Traceability is a stored verdict, not an audit-week reconstruction.
Anonymised case. Client names are never disclosed without written permission. Figures describe the file volumes and checks in this scenario.
Other files, same engine.
An inspection body issuing certificates across several schemes, where an inspector’s accreditation had once expired mid-campaign without anyone noticing.
Read the case → InspectionOne equipment reference, checked across every documentA certification body running multi-site campaigns where the report, the certificate and the datasheet had to describe the same equipment — and sometimes did not.
Read the case →See it run on your own files.
Bring one real file to a 30-minute demo. Watch the verification run, evidence on screen.