Enrolment depends on someone remembering
A new engineer joins in March. Secure development training is assigned whenever an admin notices, if anyone does.
Sublime LMS reads your org structure from your HR system and turns it into training requirements. New joiners are assigned on day one, the right roles get the right courses, policies are acknowledged in the same place, and every completion becomes audit evidence.
The courses exist. What breaks is the step between the org chart and the learner: knowing who needs what, by when, and proving it afterwards.
A new engineer joins in March. Secure development training is assigned whenever an admin notices, if anyone does.
An analyst becomes a manager. Management compliance never follows them, because nothing is watching the org chart.
Acknowledgements live in inbox threads and scanned PDFs. There is no record of which version was signed, or when.
When the auditor asks, completions are exported, reconciled in a sheet and screenshotted. The evidence is as good as the week it was collected.
Each step is triggered by the one before it. Nobody has to remember anything.
Compliant, Expiring Soon, Overdue and eight more states come from the record behind each cell.
Every requirement traces back to the department, role, location or employee rule that assigned it.
Acknowledgements are requirements too, with versions, reminders and the same status model.
Assignments, completions, assessments, certificates and acknowledgements, filtered to what the auditor asked for.
Training, assessment, policy, validity and audience defined once, assigned everywhere.
By role, department, location, employment status or named employee. Re-evaluated on every sync.
Zoho People first; Workday, BambooHR, HiBob and SAP SuccessFactors on the connector roadmap.
New employees are assigned automatically. Leavers are disabled and archived with their evidence preserved.
Policies are requirements with versions. A new version can require re-acknowledgement.
Every record shows which version a person completed or signed.
Not Applicable, Not Assigned, Assigned, In Progress, Awaiting Assessment, Awaiting Approval, Compliant, Expiring Soon, Expired, Overdue, Exempted.
Status per report, what is due in 30 days, who has ignored reminders.
Reminders go to the employee; escalations reach the current manager from the HRIS feed.
Granted with a reason, attributed to a person, and written to the history.
Every assignment, completion, acknowledgement and status change, timestamped and append-only.
Filter by requirement, department, location or period and export the pack.
One organisation, the same people, the same mandatory training. Watch an administrator run it in a traditional LMS, then in Sublime LMS.
| Name | Login ID | SIS ID | Section | Role | Last Activity |
|---|
Kabir Rao has been inactive for 12 days and his Bloodborne Pathogens renewal is due in 9 days. Likely to lapse without a prompt.
| Employee | Course / certification | Status | Last completed | Due / renewal | Progress |
|---|
| Learner | Enrolled | Overall progress | Status | Certificate |
|---|
| Course name | Modules | Lessons | Enrolled | Completion | Status | Updated |
|---|
Policy v5 was published. 3 lessons changed and an AI draft is ready for review. 168 learners will be scheduled for re-acknowledgement when you publish.
Compliance begins as a course card on a dashboard. No status, no due dates, no owner. The administrator opens the course to find out what is going on.
Every requirement becomes modules, pages and quizzes, added one at a time. Completion rules live per module. There is no validity period, no renewal and no link to a policy version.
Assignment is an enrolment list per course. Invitations wait, inactive accounts linger, and nothing follows a new joiner or a role change. To check one person, you open their record.
Status is a grid of 100s, 0s, ticks and crosses. Nobody can tell who is compliant, who is overdue or when anything expires. The real tracking happens after Export, in a spreadsheet.
Manual compliance management, re-engineered as automated, intelligent compliance management.
Learners, courses, completion and certificates on one screen. The compliance rate is computed live, and Sublime Intelligence flags who is likely to lapse and acts on it, weeks before the deadline.
Not started, in progress, compliant, due soon, overdue: click a metric to filter the whole workforce. Recurring requirements renew on their own cadence; reminders and escalations run without an admin.
New joiners arrive from the HR system. Rules decide what they need and when it is due. Progress, status and certificates sit on one row per person, and the list exports in one click for audit.
When a policy changes, the course flags itself, drafts the update and schedules re-acknowledgement for everyone in scope. Completion stays live per course.
A 30-minute walkthrough with a compliance specialist, using your departments and roles.
New joiners are assigned the moment the HRIS sync runs. No ticket, no reminder, no waiting for an admin.
Status is computed from the record behind it. Nobody types "Compliant" into a cell.
Every change is timestamped and attributed to a person or a rule. Nothing can be edited after the fact.
Org structure comes from your HR system. Workday, BambooHR, HiBob and SAP SuccessFactors follow.
Before external rollout, Sublime LMS runs ZionStar's own compliance programme as the reference implementation. Five requirements cover everyone, AI users, developers and managers, each with its own cadence.
Zoho People syncs employees, departments, roles, reporting managers, locations, joining dates and employment status.
Each requirement carries its training, assessment or policy, its validity, and who it applies to.
My Compliance shows what is due and by when. Managers see their team; reminders and escalations run on schedule.
Filter and export assignments, completions, assessments, certificates and acknowledgements for any period.
Zoho People is the first connector. It syncs employees, departments, job titles, reporting managers, locations, joining dates and employment status. Workday, BambooHR, HiBob and SAP SuccessFactors are on the connector roadmap. Tell us which one you run and we will confirm the timeline.
Rules are re-evaluated on every HRIS sync. New requirements are assigned with due dates; requirements that no longer apply move to Not Applicable, and the history of what was completed stays intact.
Yes. Policy acknowledgement is a requirement type with its own versions, reminders and status. Training requirements can also include an assessment that must be passed before the status becomes Compliant.
Training and policies are versioned. When you publish a new version you decide whether it requires re-acknowledgement or recertification and for whom. Records always show which version each person completed or signed.
Yes. Exemptions and administrative overrides require a reason and are attributed to the person who made them. They become part of the audit history, so an auditor sees who decided what, and why.
Filter by requirement, department, location or period and export the evidence pack: assignments, completions, assessments, certificates, acknowledgements and the timeline of every status change. The history is append-only, so what you export is what happened.
See assignment rules, My Compliance and the evidence export in a 30-minute walkthrough, using your departments, roles and requirements.