Why Open Badges Standards Matter for Open CPD

Open Badges is the international technical standard for digital credentials. A badge that follows it is not a picture of an achievement, it is a file that carries structured, machine-readable information about who earned it, who issued it, what it represents and how to check that it is genuine. Open CPD issues to that standard for a practical reason: a credential that only exists inside the platform that made it is worth much less than one that travels.

What makes an Open Badge different from a badge image

Plenty of platforms issue attractive badge graphics. The graphic is the part people notice and the least important part of the credential. What matters is the metadata attached to it.

An Open Badge carries, inside the credential itself, the identity of the issuer, the identity of the recipient, the criteria the badge was awarded against, the date of issue, and a link back to a hosted record that can be checked independently. Any system that understands the standard can read all of that without a human interpreting a JPEG.

Strip the standard away and you have an image. An image can be copied, relabelled and reposted by anyone, and there is no way for a recipient to interrogate it. That is the difference the standard makes.

Who maintains the standard

Open Badges began at the Mozilla Foundation and is now maintained by 1EdTech, the standards body formerly known as IMS Global. It is an open specification rather than a product, which is the point: no single vendor controls it, and credentials issued to it are not tied to the platform that issued them.

Open CPD issues Open Badge 2.0 badges alongside every certificate. Version 3.0 exists and aligns the standard with the wider verifiable credentials work happening across the sector. The reason 2.0 remains the sensible issuing target today is support: it is the version the platforms learners actually use will accept and display.

Why portability is the whole argument

CPD has a recognition problem that is really a portability problem. A learner trains with one provider, changes employer, moves sector or moves country, and the evidence of what they learned stays behind in a system nobody at the new organisation has access to.

A badge built to an open standard does not have that problem. The learner holds it. They can display it on a professional profile, attach it to an application, add it to a portfolio, or hand it to a regulator, and in each case the receiving party can read the same structured information and follow the same verification link. Nobody has to be a customer of Open CPD for the credential to make sense to them.

For a provider, that portability is quietly commercial. Every badge a learner displays carries the issuing organisation's name, permanently, in a place where other people in the same profession will see it.

What Open CPD puts inside the badge

The badge carries the same substance as the certificate it accompanies. The issuing provider and their OCPD Provider ID. The course, and the aims, skills and outcomes it was built around. The CPD hours. The date of issue. A unique verification ID and a link to a public achievement page that anyone can open without an account.

That last point does more work than it seems. Most credential checks fail not because the credential is fraudulent but because checking it is inconvenient. Removing the login removes the excuse.

Cross-sector and cross-border recognition

Training providers increasingly serve learners in more than one country, and a certificate issued under one national framework does not automatically mean anything under another. Open Badges does not solve equivalence, and nothing does. What it solves is legibility. Wherever the badge lands, the receiving party can read what the training aimed to do, what the learner can now demonstrate and who stands behind the claim, and can verify all of it directly.

That is a more modest promise than international recognition, and a more useful one, because it is true everywhere rather than negotiated country by country.

What the standard does not do

It is worth being precise about the limits. Open Badges does not assess quality. It does not verify that the training was good, only that the credential is authentic and says what it says. There is no body checking course content behind the standard, and Open CPD does not review or endorse training content either.

The credibility of a badge comes from the provider publishing clearly, under their own name, in a permanent and checkable place, and from the specificity of what they publish. The standard is what makes that publication legible to everyone else. The two work together, and neither substitutes for the other.

Where to see it working

Every certificate issued through Open CPD comes with a badge, at no extra step for the provider or the learner. You can see what a live record looks like on the verification page, read what sits on the certificate itself in what your certificate carries, or look at the wider picture in how it works.