Two kinds of certificate problem
Your course offers a certificate, which matters to students who want to show it to an employer or clients. Your platform issues it when a student marks the last lesson complete. Some students click through every lesson in an afternoon to get it. Others did all the work, passed the quiz and submitted the final project, but the certificate never appeared because they skipped one optional video.
Meanwhile a student emails asking for a certificate with her name spelt correctly, and an employer asks you to confirm that someone really completed the course.
Why built-in certificates fall short
Most platforms issue certificates on a simple trigger: all lessons complete, or a quiz passed. Your real requirements are often more specific: a pass mark on the final quiz, an approved project, attendance at some live sessions, a minimum time enrolled. Those rules live in your head or your sales page, not in the platform, so either the certificate means less than it should or you issue them by hand.
- Completion means clicking through, not meeting requirements.
- Project approval and live attendance are tracked elsewhere.
- Names on certificates come from checkout details and are often wrong.
- There is no way for a third party to check a certificate.
- Manual issuing is slow and inconsistent.
What weak certificates cost
If certificates are easy to get without doing the work, they are worth less to the students who did. If they are slow or wrong, students who need them for a job are frustrated. If anyone can edit a PDF and nobody can check it, your name is on documents you cannot vouch for.
Certificates tied to your rules
- Your completion rules are written down as settings: required lessons, quiz pass marks, project approval, live attendance, minimum enrolment time.
- Progress, quiz scores and project status are read from your platform, with live attendance from Zoom or your meeting tool.
- When a student meets every rule, they are asked to confirm the name to appear on the certificate.
- The certificate is generated with a unique reference and the date, and sent by email and added to their account.
- A public check page lets anyone enter a reference and see the student's name, course and date, with nothing else revealed.
- Students who are close but missing a requirement see what is outstanding, so they can finish.
- Certificates can be revoked if needed, for example after a refund, and the check page reflects it.
| Requirement (your rules) | Where it is checked | Student sees |
|---|---|---|
| Core lessons complete | Course platform | Progress list |
| Final quiz passed | Course platform | Score and pass mark |
| Project approved | Your review queue | Status and feedback |
| Live sessions attended | Zoom attendance | Sessions counted |
What your certificate represents, and whether it carries any accreditation, is for you to decide and describe honestly. We make sure it is issued according to what you say.
Certificates that mean something
Take the student who did everything but skipped an optional video. Under your rules the optional video does not count, so her certificate is issued the day her project is approved. The student who clicked through in an afternoon sees a list: final quiz not yet passed, project not submitted. Both outcomes match what your sales page promised.
Students who did the work get their certificate promptly, with their name spelt correctly. Students who clicked through see what is still required. Employers and clients can check a certificate in seconds. You stop issuing certificates by hand and answering emails about them.
Signs your certificates need rules
- Certificates are issued when the last lesson is clicked.
- Students who did the work sometimes do not get one.
- You issue or correct certificates by hand.
- Names on certificates are often wrong.
- Nobody can check whether a certificate is genuine.