What the verification page reports
Valid means the training completed and the certificate still stands. Revoked means it was withdrawn. Expired means the training happened and is due again — deliberately not the same as fake. The record is tied to your organisation's issuing data, not a screenshot.
- A public check needs no Elumio relationship and no account.
- Certificates already issued stay verifiable if you cancel later.
- Serial number + QR — the credential identity auditors and clients can re-check.
Designer vs verify
Certificates are branded under your organisation's name in the designer (logo artwork, custom text, signature on the PDF). The public verify page shows holder, course, issuing organisation, completion date, and serial — Valid, Revoked, or Expired.
Certificate expiry and refreshers
Set certificate validity to match your programme cycle. When a credential expires, the verification page says the training happened and is due again — not that it was counterfeit. Email reminders before expiry when enabled for the course: trainees are notified before their own certificate lapses; trainers get a digest of who is coming due so a refresher gets scheduled rather than discovered late. Notice window is set per course (seven days by default). Set reminder days to 0 to disable emails for that course. Trainers see who's due and can reset progress so they must re-watch; prior attempts stay on record.
Completion before the certificate
Certificates are only as strong as the completion rules behind them. Elumio measures watch credit on the server from intervals actually reached — not a dragged playhead. Strict mode per course when required modules cannot be skipped. Assessments unlock only after required lectures are genuinely finished; grading stays on the server so the answer key never reaches the browser.
When one QR isn't enough
Audit packs summarise training for a person or the whole organisation with a checksum — included on Starter and above. Free includes them as a trial capability. For client-facing views scoped to their own people, see Business and Scale plans. Link directly to the verify page when you want someone to check without scanning.
Who this is for
Clients and auditors who re-check months after the training happened; agencies and BPOs that must show proof someone outside the company can verify; training centres issuing certificates under your own name.
What we do not claim
Elumio does not issue credentials on its own behalf. If you are a DOLE-accredited training centre, you control the certificate text — the platform is yours, accreditation wording is yours. Elumio does not claim to be DOLE-accredited or TESDA-accredited and does not issue government credentials (BOSH, COSH, TESDA NC). Structured accreditation schema on the verify page is not implemented today. What you get: a platform to run courses and issue certificates under your organisation's name, with public QR verification so anyone can check valid / revoked / expired.
Related questions
How does certificate verification work?
Every pass issues a PDF containing the holder's name, the course, the dates, a serial number and a QR code.
Scanning the QR opens a public page that reports one of three states — valid, revoked, or expired — checked against the issuing organisation's records. No login and no Elumio relationship is required for whoever is checking.
Expired is deliberately not the same as fake: the page says the training happened and is due to be retaken.
On a custom training address the verification page may wear that organisation's theme, and it answers only for certificates that organisation issued. elumio.io/verify stays the global check, in Elumio's theme, for any certificate.
Do certificates survive if we stop paying?
Yes. Certificates already issued stay valid and stay publicly verifiable. A certificate records that somebody completed training; it does not depend on whether their employer is still subscribing.
Does anyone get warned before a certificate expires?
Yes, and both sides are told without anyone having to remember. The trainee is emailed before their own certificate lapses, and the trainer receives a digest of everyone across their courses who is coming due — so a refresher gets scheduled rather than discovered late.
How far ahead that email goes out is set per course, because a quarterly refresher and an annual one do not need the same notice. Seven days is the default.
The cohort screen flags anyone expiring within thirty days, separately from the emails. That is the planning view a trainer opens on purpose; the email is the nudge that arrives when the date is close enough to act on.