No certificate issued on a lapsed accreditation
An inspection body issuing certificates across several schemes, where an inspector’s accreditation had once expired mid-campaign without anyone noticing.
Who they are.
An inspection body issuing certificates across several schemes, using a pool of accredited inspectors. Its authority to certify rests entirely on those accreditations being valid at the moment each inspection was carried out.
Anonymised at the client’s request. Client names are never disclosed without written permission.
What had to be solved.
Accreditation was verified when an inspector was assigned, then trusted. One accreditation expired mid-campaign without anyone noticing, and every certificate issued in that period became questionable. Reconstructing which inspections were affected took days.
What success looked like.
- Check accreditation against the inspection date, not the assignment date
- Stop a certificate being issued on a lapsed accreditation
- Be able to show, per certificate, which accreditation backed it
What Ceertia does here.
A use case per scheme that reads the inspection date from the report and checks the inspector’s accreditation validity against that date specifically. A lapse blocks the certificate before issue, rather than surfacing in an audit afterwards.
The inspector’s accreditation must be valid on the inspection date — not on the certificate issue 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.
One lapse was caught in the first month. More importantly, the link between a certificate and the accreditation behind it became a stored record — so the question can be answered per certificate instead of per campaign.
- Accreditation validity was checked at assignment, not at the moment of inspection.
- A lapse discovered later put every certificate from that period in doubt.
- Reconstructing which inspections were affected took days.
- Validity is checked against the inspection date on every single file.
- A lapsed accreditation stops the certificate before it is issued.
- The audit log shows, per certificate, which accreditation backed it.
Anonymised case. Client names are never disclosed without written permission. Figures describe the file volumes and checks in this scenario.
Other files, same engine.
A 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 → LaboratoryTest results that always trace back to a calibrated instrumentA testing laboratory whose accreditation depended on proving that every result came from an instrument calibrated at the time of measurement.
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.