Certificates of Completion: What They Actually Prove

Certificates are one of the few parts of e-learning that everybody asks for and almost nobody examines. Learners like receiving them, procurement asks whether you issue them, and regulators sometimes require evidence that looks like one. It is worth being precise about what they actually establish.

What does a completion certificate prove?

That a named person reached the end of a named course on a particular date. That is the entire claim, and it is a genuinely useful one — it is evidence of exposure, and a great deal of compliance obligation is satisfied by demonstrating exposure.

What it does not prove is competence. Someone can complete a course without absorbing any of it, and if your knowledge checks can be passed by trial and error, completion is barely even evidence of attention.

Does that mean they are worthless?

No, and the cynicism about them is overdone. A certificate does three real jobs:

• It is a record with a date on it. When someone asks what training a person had before an incident, a dated record is what answers the question.
• It marks an ending. Courses without a clear finish get abandoned in the last ten per cent, and a certificate is a visible, concrete finish line.
• It travels. A contractor can show it to a site supervisor, a professional can attach it to a CPD log, a supplier can include it in a tender response.

The mistake is treating it as a competency claim rather than an attendance record.

What is the difference between a certificate and accreditation?

This is the distinction that matters most and gets blurred most often. A certificate you issue says that someone completed your course. An accredited qualification says that a recognised body has assessed the training against a standard.

Anyone can issue the first. Only an authorised body can award the second, and in Australia issuing something that implies nationally recognised training when it is not is a serious matter. If you are producing training that sits near the vocational sector, the safe practice is to be explicit: state on the certificate that it is a statement of completion of your course, and do not use words like "accredited", "qualification" or "nationally recognised" unless they are literally true.

Should the certificate require a pass mark?

It depends what you want it to mean, and you should decide deliberately rather than by default.

Completion-only is honest and simple: the person went through the material. Requiring a pass mark makes the certificate a slightly stronger claim, but only if the assessment is worth passing — a certificate gated on a five-question quiz with obvious answers looks more rigorous than it is, which is worse than not gating it at all.

If you do set a threshold, say what it was on the certificate. "Completed, scoring 8/10" tells a reader something. "Successfully completed" tells them nothing they can evaluate.

What should a certificate actually contain?

Enough for a third party to verify it and evaluate it:

• The learner's full name, as it appears in your records.
• The exact course title and, ideally, a version or date of the content.
• The date of completion.
• Who issued it.
• The score or threshold, if there was one.

The content version is the one everyone omits and the one that matters in three years, when the course has been revised twice and someone asks what a certificate from March actually covered.

How does this work in an LMS?

Most of the time the LMS issues the certificate, not the course. A SCORM package reports a completion status and a score back to the platform, and the platform decides what to do with that — including whether to generate a certificate and what it says.

That is usually the right division of labour, because the LMS holds the person's identity and their record. It also means the certificate design is a platform setting rather than something you control from the course, which surprises people who expected to design it alongside the content.

What about learners who just want the PDF?

They exist, they are not the enemy, and their behaviour tells you something. If a large share of people are clicking to the end to collect a certificate, that is feedback about the course rather than about them. The fix is content worth reading, not a longer minimum time on each screen — timers produce learners who leave the tab open and go for coffee.

The honest position

Issue certificates. Make them accurate, dated and specific about what they cover. Then treat the completion record as what it is — evidence that training was delivered — and use knowledge checks, scenarios and on-the-job observation for the entirely separate question of whether anyone can now do the thing.