Certificates are files, not records
A PDF proves someone passed once. It does not know whether it is still valid, which version of the training it covered, or who approved it.
Sublime LMS keeps a single registry of who holds what: certifications earned inside the platform, credentials earned outside it, their validity, their approvals, their history and the evidence behind each one. Verifiable by ID, exportable for audit, mapped to skills.
Certificates are issued as PDFs and then scattered: the LMS profile, the inbox, a shared drive, the HR file, a vendor portal. None of them agree, and none of them can be verified.
A PDF proves someone passed once. It does not know whether it is still valid, which version of the training it covered, or who approved it.
Vendor and industry certifications live in email. Their expiry is a surprise, and their existence is a rumour.
A customer or auditor asks whether a certificate is real. Someone goes looking for the original.
Renewal replaces the old certificate, and the trail of what was valid when disappears with it.
One record per person and certification, written to at every step and never erased.
Criteria to earn it, validity period, who approves it, and which skills it evidences.
Training and assessment inside Sublime, or an external credential uploaded with its expiry date.
Where a sign-off is required, the record waits in Awaiting Approval and names the approver.
A verifiable certificate tied to the person, the training version and the evidence behind it.
Validity counts down in the matrix. Expiring Soon triggers renewal; Expired is visible to everyone who needs to know.
A new certificate is issued. The previous one, its approval and every status change stay on the record and in the export.
Certificates Sublime issued sit next to credentials uploaded from vendors and industry bodies, with the same expiry logic.
Where a sign-off is required, nothing is issued until the named approver confirms. The approval is on the record.
Every certificate carries a unique ID. Anyone who holds it can check holder, issue date, version and validity.
The registry is the audit report. Filter, export, done.
Each part of the record is a capability. Together they replace the PDF, the spreadsheet and the inbox search.
Training, assessment, attendance or upload, plus an optional named approver before issue.
Anyone holding the ID can confirm holder, issue date, version and validity.
Per certification, with Expiring Soon and Expired computed, not typed.
The record names the version of the course or policy the certificate covers.
Granted with a reason, attributed, and logged on the record.
Vendor and industry credentials uploaded with expiry, approved, and tracked like the rest.
A certification is verified evidence of specific skills at specific levels.
Every previous certificate, approval and status change stays attached. Nothing is overwritten.
Each person sees their own certificates, expiry dates and renewal paths.
By person, certification, department or period, with the evidence behind each line.
The same organisation, the same Privacy & Data Security certificate. Watch an administrator issue, track and verify it in a traditional LMS, then in Sublime LMS.
Final grades are recorded here. Certificates are not part of the gradebook.
Certificate IDs, expiry dates and file locations are maintained by hand in this spreadsheet. The LMS has no field for any of them.
Hi Devika, our auditor needs confirmation that the attached Privacy & Data Security certificate for Meera Joshi is genuine and still valid. Could you confirm the issue date, the expiry date and who approved it?
cert_meera_joshi_v2_FINAL.pdf · 412 KB| Learner | Course | Score | Issued | Status | Actions |
|---|
Sublime LMSCompleted cycles are kept on record — renewals never overwrite them.
This certificate is authentic and was issued through Sublime LMS.
The learner passes the final assessment and the gradebook records 94%. The LMS has done its job. Everything that turns this into a certification happens somewhere else.
A PDF is generated from a template, named by hand and uploaded to a folder. Different names, different versions, and no ID the system knows anything about.
IDs are typed, dates are copied from PDFs, and the file is wherever it ended up: the LMS folder, an inbox, the HR drive. Expiry is a column someone remembers to fill.
An auditor asks whether a certificate is genuine and still valid. Someone opens the folder, compares a PDF to a spreadsheet row and replies by email.
A file in a folder becomes a verifiable record with a lifecycle.
Every completion flows into one registry. Where sign-off is required, the certificate waits in Pending until the named approver confirms; then a unique ID is issued automatically. External credentials sit in the same list.
Issue date, expiry, score, approver and ID are printed on the certificate and stored on the record. Download it, or send the verification link.
Anyone holding the ID can confirm the holder, issuer, issue and expiry dates and the authenticity key on a public page. No phone call, no folder.
Internal and external certifications live on one learner record with approvals and expiry. Renewals add a new cycle; previous certificates stay on record with their IDs and dates.
A 30-minute walkthrough of the registry, verification and export, with your certifications.
Every certificate carries a unique ID anyone can check for holder, version and validity.
Credentials earned elsewhere are tracked with the same expiry, reminders and renewal path.
Renewal never overwrites. Every prior certificate, approval and status change stays on the record.
A certification is also verified evidence of specific skills at specific levels.
ZionStar's five compliance programmes issue certificates with six- or twelve-month validity. Each one is a verified record with a unique ID, an approval and a full history, and each one feeds the skills layer that follows.
Criteria, validity, approver and the skills each certification evidences. Import the ones you already issue.
Internal certifications are issued on completion. External credentials are uploaded with expiry and approved.
The registry shows every holder, status and expiry. Anyone with an ID can verify a certificate.
Renewals keep the history. Exports answer the audit by person, certification or period.
Yes. External certifications are uploaded with their issuer and expiry date, optionally approved by a named person, and then tracked in the same registry with the same reminders and renewal path as internal ones.
Every certificate Sublime issues carries a unique ID. Anyone holding the ID can confirm the holder, issue date, the training version it covers and whether it is currently valid, without contacting your team.
Some certifications require a sign-off before issue, for example a manager confirming a practical assessment or an admin accepting an external upload. The record waits in Awaiting Approval, names the approver, and records the decision when it is made.
No. Renewal issues a new certificate with a new ID. The previous certificate, its approval and every status change remain on the record and in any export.
Each certification can be mapped to skills at a proficiency level. Earning it becomes verified evidence of those skills, which feeds the skills profiles and gap dashboards that follow in the roadmap.
Yes. Filter the registry by person, certification, department or period and export the result together with the evidence behind each line: training completion, assessment result, approval and issue date.
See internal and external certifications, approvals, verification by ID and audit exports in a 30-minute walkthrough.