What a training certificate actually proves

Echipa HR 365 · reviewed 2026-09-04 · 5 min read

A certificate proves something only if somebody outside can verify, independently, that it was issued and to whom. A PDF file, however official it looks, is an editable document — so it attests exactly as much as your trust in whoever handed it to you.

The three conditions

They are cumulative. A certificate that meets the first two and not the third looks good and attests a value the learner wrote for themselves.

What has to be true, in order

1. Public verification — a code or QR leading to a page stating who, what and when — reachable without an account
2. A link to the record — the certificate points to a record that exists independently of the file and cannot be rewritten from a browser
3. A server-side verdict — passing is decided where the learner cannot reach, not in the page they have open

How you check a certificate you receive

The situation comes up often at hiring, when a candidate brings certificates from previous employers or external providers. The check takes under a minute and is worth doing for any certificate that matters.

The last row is useful internally too, not only when checking: a certificate with no expiry date for training that recurs periodically is a postponed problem. It surfaces at an inspection or at the first incident, which is exactly when it can no longer be repaired.

What you put on the certificates you issue

• The person’s full name, exactly as it appears in your records — not abbreviated, so it can be matched automatically.
• What exactly they passed, not the marketing title of the course. “Workplace training — operating X” says more than “Module 3”.
• The date of passing and, if the training recurs, the date until which it is valid.
• Who issued it: the company, not just a logo. A certificate with no identifiable issuer cannot be verified by anyone.
• The verification code or link, visible, not hidden in the footer at six-point type.

Why it is worth the effort, if nobody asks for it

The usual argument against public verification is that nobody has ever asked for it. True, until the day somebody does — and that is usually the worst possible moment: an inspection, an incident, a dispute, a request from a client auditing their suppliers. The cost of having it is one public page; the cost of not having it is that you can prove nothing retroactively.

The second argument is less obvious: public verification changes how people treat training. A document known to be checkable by anyone is treated differently, both by whoever receives it and by whoever issues it.

What you keep besides the certificate

The certificate is the document that circulates. What stays internal matters more, because it supports the certificate if it is questioned: who attended, when, what content was covered, who delivered the training, and how each person answered the check.

The second row is the most often missed and the hardest to repair retroactively. A course modified four times in three years can no longer prove what somebody covered in the first year — unless the versions were kept separately, with their dates.

Where to start

Take a certificate you issued last year and try to verify it as if you were an outsider. If you cannot, neither can anyone else — and the same applies to the ones you receive from candidates.

Then check where passing is calculated in your own assessments. If the answer is in the learner’s page, the certificate attests what they declared, and the repair is technical rather than procedural.

Finally, check whether you keep versions of the content. It is the only item on the list that cannot be reconstructed retroactively — so the only one that has to start today, even if the rest waits.