What auditors and clients actually ask
The hard moment is not assigning the course — it is the questionnaire, the renewal, or the site visit where someone asks you to show that this person completed this pack. A page-open completion in a generic LMS answers a different question than public, re-checkable proof.
- Watch credit is calculated server-side from intervals actually reached — not from a dragged playhead.
- Strict mode stops skipping ahead; rewinding stays free.
- The assessment unlocks only after every required lecture is complete.
- Audit packs summarise one person or the whole organisation with a checksum — not certificate-by-certificate hunting.
Watch → exam → verify
Completion is a chain: measured watch credit, a gated assessment graded on the server (the answer key never reaches the browser), then a certificate with a serial number and a public QR page reporting valid, revoked, or expired. Expired means the training happened and is due again — deliberately not the same as fake.
Proof is the job — platform details live elsewhere
This page is for the auditor-grade proof job. For running org-wide mandatory packs and onboarding in one place, see the training platform page. For the credential and QR experience itself, see verifiable certificates.
Related questions
How do you know a trainee actually watched the video?
Watch credit is calculated on the server, from intervals actually reached — not from where the playhead sits. A dragged slider or an idle tab banks nothing.
Rewinding is always free; it is skipping ahead that is restricted. Strict mode is a per-course switch, so optional material can stay freely browsable while mandatory training is locked down. Watching faster than the permitted rate earns no extra credit.
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.
Can I hand an auditor everything at once, rather than certificate by certificate?
Yes. An audit pack covers one person or your whole organisation: a PDF summary with a CSV of the underlying rows, and a checksum that shows the file has not been altered since it was generated. The pack itself can be checked from the same public verification page a certificate uses.
It states its own method rather than leaving it to be assumed. It says what watch evidence does and does not prove, shows refused progress reports as anomalies instead of quietly dropping them, records which revision of the course each person actually did, and marks rows for courses that carry no assessment as completed with the attempt columns blank — because there was nothing to attempt, not because something is missing.
It reports what Elumio recorded. It does not assert that anyone is or is not compliant — that judgement belongs to the reader, and the pack says so in as many words.