How CPD Certificate Verification Works
CPD certificate verification allows employers and learners to confirm a certificate is genuine. It sounds straightforward, but the way most certificates are issued makes proper verification impossible. Understanding the difference between a verifiable certificate and an unverifiable one matters — particularly for employers making decisions based on what a candidate presents to them.
This post explains how verification works on Open CPD, why it is technically reliable, and how it compares with the two most common alternatives you will encounter in the UK training market.
The Problem With Most CPD Certificates
The majority of CPD certificates are issued as PDFs. A PDF certificate has no verification possible — there is no underlying record to check against, no unique identifier, and no system to query. Anyone with basic software can alter a name, a date, or a course title and produce something that looks entirely plausible.
This is not a theoretical risk. Employers who accept PDF certificates at face value are accepting a document that could have been edited at any point between issue and submission. The certificate might be genuine, or it might not — there is no way to tell.
A second common approach involves displaying a bought accreditation logo on a certificate. This is worth being clear about: a logo on a certificate does not verify the certificate is genuine. The logo indicates that an organisation has paid for or been granted the right to display a mark. It says nothing about whether that specific certificate was actually issued to that specific learner for that specific course. The two things are entirely separate.
How Open CPD Verification Works
Open CPD takes a different approach. Each certificate contains a unique secure URL embedded directly into the document. That URL points to a verification page hosted on Open CPD’s infrastructure, and the record it displays is pulled from the original database entry created at the point of issue.
Anyone can click the link — no login required. There is no account to create, no form to fill in, and no need to contact the training provider. The verification page shows the provider name, learner name, course name, date issued, CPD hours, and the course Aims, Skills, and Outcomes as recorded at the time of accreditation.
That last point is significant. The Aims Skills Outcomes are not added retrospectively. They are defined when the provider submits the course for accreditation on the platform, and they become part of the permanent record. When an employer views a verification page, they are seeing exactly what the course was designed to cover — not a summary the learner has written themselves.
What Instant Verification Actually Means
Instant verification means there is no waiting, no contacting the provider, and no administrative lag between a certificate being presented and its authenticity being confirmed. An employer receiving a certificate can check it in under a minute, from any device, without any prior knowledge of Open CPD or the training provider.
This matters in practice. HR teams and line managers are not going to phone a training company to ask whether a certificate is real. If the process requires effort, it simply will not happen. Instant verification removes that friction entirely.
It also removes the provider from the verification loop. The record is held independently of the provider’s own systems. Even if a provider changed their website, rebranded, or ceased trading, the certificate record on Open CPD would remain queryable. The certificate does not depend on the provider staying in business to remain verifiable.
The Technical Infrastructure Behind It
The verification infrastructure runs on AWS — Amazon Web Services. AWS-hosted secure verification infrastructure gives Open CPD the reliability and uptime that verification genuinely requires. A verification system that goes offline intermittently, or that slows under load, undermines the trust the whole mechanism depends on.
Each unique secure URL is generated at the point of certificate issue and is tied to a specific database record. The URL itself is not guessable or sequential — it cannot be constructed by trial and error. This means that producing a fraudulent certificate that passes verification is not simply a matter of editing a PDF; it would require access to the database itself.
The result is a system where the certificate and the underlying record are inseparable. The document you hold and the record you can query online are two views of the same thing, not two separate items that might or might not match.
What This Means for Employers and Learners
For employers, CPD certificate verification through Open CPD means a straightforward, reliable check. The verification page shows everything relevant — provider name, learner name, course name, date issued, CPD hours, and Aims Skills Outcomes — without requiring any relationship with the provider or any prior familiarity with the platform.
For learners, it means their certificates carry genuine evidential weight. A verifiable certificate is demonstrably different from a PDF that could have been altered. That distinction is worth having, particularly in sectors where CPD records are scrutinised by regulators, employers, or professional bodies.
The broader point is this: a certificate is only as useful as the trust it carries. A PDF certificate offers no verification possible and therefore no reliable trust. A bought accreditation logo confirms a commercial relationship, not the authenticity of any individual certificate. A unique secure URL that resolves to an AWS-hosted secure verification page showing a full course record is a different category of thing entirely — and the difference is not cosmetic.
