Certificates worth something to the person checking them.
Map competencies to questions, let the evidence award mastery, and issue credentials anyone can verify at a URL — without an account.
How a Lurno credential is checked
Every credential Lurno issues carries a serial, a public link and a QR code printed on its PDF, all pointing at one verification page. Anyone — a recruiter, a regulator, a parent — can open it without an account and see whether the credential is valid, revoked or expired, what it was for, who issued it and when. Nothing else is disclosed: the recipient's name appears only if the learner switched it on, and only while the credential is valid. With a verified custom domain, that page sits on your host rather than ours.
- Competency framework
- A named set of competencies — skills, outcomes, standards — with a rule for what counts as mastery on each. A framework belongs to one organisation or to the platform; platform frameworks are read-only inside a tenant, so copying one into your organisation is how you get a version you can edit. Each competency carries a code, a title, a mastery method and an optional re-certification window.
Behind the credential sits the other half of this page: a framework that says what a skill is, questions mapped to it, and evidence that adds up to mastery without anyone pressing a button.
Assessments produce the evidence, and the chain matters most in higher education — though a corporate academy running training for 15 client companies from one tenant issues its compliance certificates the same way.
The page an employer actually opens
Four answers, and nothing more
A lookup returns one state: valid, revoked, expired, or not found. A valid one shows its title, issuer, issue date and serial. A revoked or expired one shows title, issuer and date — enough to see what was withdrawn, and no further.
- Three ways in: the public link, the QR code on the PDF, or a serial typed into the lookup.
- The page runs before authentication. No account, no cookie, no sign-up wall.
- Shared links unfurl with the artwork, so the preview is the certificate.
The learner decides whether their name is on it
By default the public page shows the credential, not the person. A learner turns their name on from their wallet, and off again. Score, cohort, email and the evidence behind the mastery never appear there.
Every lookup is logged, and the log is not a list of people
Each check records the method, the outcome and a truncated keyed hash of the caller's address — never the address itself. Lookups are rate-limited per caller and per credential, so nobody can walk your register.
How Lurno handles dataFrom one question to one credential
- 01
Map the competency to the work
Attach a competency to an assessment, and to the individual questions inside it. Each attachment carries its own weight and can override the framework's threshold.
- 02
A graded attempt writes evidence
When an attempt finishes, an evidence record is appended against each mapped competency with its source and score. Staff add evidence by hand for work done off the platform.
- 03
Mastery is recomputed, not declared
A threshold rule masters on average score, an evidence-count rule on repetition, a manual rule never auto-masters. Every transition writes to the audit log that cannot be quietly edited.
- 04
A rule fires, once
The certificate definition on that competency issues the credential — exactly once per definition and learner, enforced in the database, with the triggering row snapshotted as evidence.
- 05
The credential renders on the server
A worker turns the template into a share card and a PDF with the verification QR embedded. Branding resolves organisation, then issuer, then template, so a sub-organisation signs with its own seal.
What stands behind the certificate
Your frameworks and the platform's
Build your own, or start from one published across the platform. Copy a platform framework into your organisation and it becomes yours to edit.
Import instead of retype
Seed a framework in one pass from a list of competencies or a set of published standards. Items arrive already filed under subject, grade and domain.
Grouped the way a curriculum reads
Group by subject, then grade, then domain. The grouping is derived at read time, so it cannot corrupt item counts. Add your own facets to tag beyond those axes.
Evidence records, not a mark book
Each piece of evidence keeps its source, purpose and score, and is never edited afterwards. Mastery is a function of the evidence, so it can be explained.
Matrix, timeline, dossier
Learners get a mastery matrix, the evidence behind each cell, their credentials, and a dossier export that composes all four into one stamped record.
Mastery that lapses
Give a competency a re-certification window and a nightly sweep flips lapsed mastery back to expired, with an audit row for each one.
Design it once, issue it for years
A gallery, then an editor
Four templates ship ready to use. Recolour one and toggle the optional fields, or open the editor and place the text, images, panels, QR and merge fields yourself. Versions are append-only, so redesigning this year leaves last year's certificate rendering exactly as it did.
Definitions say what it means
A definition carries the credential type, its validity — perpetual, valid for N days, a fixed expiry, or renewable on an interval — and credit hours where a body asks.
Rules and triggers
Attach a definition to a program, module, lesson, assessment, assignment or competency. Choose what earns it — completion, a pass, a score at or above a mark — and when it is released.
Register and wallet
Staff search the issued register by recipient or serial, filter, and export to CSV. Learners get the artwork, a PDF, a share link and an add-to-profile link for LinkedIn.
A completion PDF and a verifiable credential are not the same object
Most platforms email a file at the end of a course. A file is a picture of a claim, not the claim.
| Capability | A PDF emailed on completion | A Lurno credential |
|---|---|---|
| Can an outsider confirm it? | Only by telephoning your office | A public page, a QR code or a serial |
| What happens when you withdraw it? | Nothing — the file still exists | Verification answers *revoked* from that moment |
| Does it expire? | No | Perpetual, fixed date, valid for N days, or renewable |
| What stands behind it? | A completion flag | A snapshot of the attempt or mastery that earned it |
| Who sees the recipient's name? | Anyone holding the file | Only on the learner's opt-in, while valid |
| Can it be issued twice by mistake? | Yes — every re-run sends another | Once per definition and learner, enforced in the database |
Both directions matter in procurement: checkable from outside your organisation, withdrawable from inside it.
Questions buyers ask
Bring us a certificate you already issue.
Show us the one your institution hands out today and we will walk through the rule that issues it, the template that renders it, and the page an employer opens.