The material for your next course already exists: the policy, the recorded workshop, the expert who gave it. Turn it into a course with a quiz and a certificate, assign it by role, and keep the evidence ready for the day someone asks.
Nobody writes a course from a blank page. The policy, the workshop, the expert who gave it — the hub turns them into lessons, a check and a certificate.
The security policy, last quarter's recorded workshop, the IT runbook. Already written, already approved.
Short lessons in order: watch, read, practise. Each one cites the source it was built from.
A quiz that proves comprehension, not attendance. Retakes allowed, results kept.
Everyone gets the essentials. Finance gets the payments module. New hires get it in week one.
Completion, scores, certificates with an expiry — and a reminder before it lapses.
Assigned, in progress, complete — by team, by role, by cohort. The reminder goes out before a certificate lapses, not after.
The scramble before an audit is the cost of tracking training in spreadsheets. When completion and acknowledgment are logged as people learn, the evidence is a list you export.
| Course | Cohort | Status | Acknowledgment |
|---|---|---|---|
| Information security basics | All employees | Completed | Acknowledged |
| Data handling for finance | Finance | Completed | Acknowledged |
| Incident reporting | Engineering | In progress | — |
| Code of conduct | All employees | Completed | Acknowledged |
No. Customer data stays in company systems; use the remote access setup instead. This is covered in the data handling policy you completed.
A course is one afternoon. The policy it taught comes up every week. The hub answers those questions from the same approved source, so what was learned is what gets done.
Tell us what your people have to be trained on, where that material sits today, and what evidence you need the day someone asks for it.