Corporate training management: from mandatory courses to real learning

Corporate training carries two different needs under one roof, and when they are confused the system stops working. The first is mandatory training: health and safety, data protection, the code of ethics — required by law or policy, and it has to be evidenced. The second is development training: content people take by choice, to grow. The first needs tracking; the second needs encouragement.

Do you need a separate LMS?

For a large organisation managing certifications and running SCORM packages, yes. But in most companies the need is far simpler: a few dozen courses, a video or document, a short assessment at the end, and a record of who completed it.

Buying a separate learning management system for that usually creates two problems. Employees have to learn one more system, and a second place to manage identities appears. A training module inside the intranet sits where people already sign in, which noticeably raises completion rates.

Course types: four is enough

An overly rich set of content types complicates administration and nobody uses it. In practice four types cover most companies:

• Video — a link to a recording hosted elsewhere.
• Document — the existing policy or guide itself.
• Link — a redirect to an external training platform.
• Quiz — a short assessment that checks whether learning happened.

These should be combinable: a course should be able to play a video and then ask five questions.

Where should the quiz be scored?

This looks technical but is really a question of trust. If the correct answers are sent to the browser, passing an exam becomes a matter of reading code — and the evidentiary value of a mandatory training record drops to zero.

Our approach is clear: questions and options go to the client, the correct answer never does. Answers are sent to the server, the comparison happens there, and the score is written server-side. We apply the same principle to recognition points and request approvals — no logic that produces a score or a decision is left to the browser.

Evidencing mandatory training

In an audit, "everyone took the safety training" isn't enough. Three things have to be shown: who, when and which version. When training content is updated, earlier completions should lapse; otherwise someone who watched a version from two years ago counts as compliant with today's rules.

This is the same versioning logic as in the document centre — we detail it in our documents article.

Assignment or catalogue?

Both models exist and both are needed. Assignment: a specific course made mandatory for a specific group, with a deadline. Catalogue: an open list anyone can browse and start on their own.

Systems that work only through assignment position learning as a burden. Systems that work only as a catalogue can't track mandatory training. Having both lets the same module serve two different needs.

Training goals and visibility

In companies with an annual training-hours target per person, letting employees see their own position raises participation: how many hours have I completed this year, how far to the target? Putting that where the employee already looks — the homepage — works far better than a separate report page.

What matters is that the goal is calculated from real data. A decorative progress bar showing a fixed percentage undermines the credibility of the whole page the moment it is noticed.

Measurement: completion isn't enough

Four indicators worth tracking:

1. Completion rate — what share of assigned courses was finished?
2. Average duration — how many days from assignment to completion?
3. Quiz pass rate — consistently high means the test is too easy; consistently low means the content is inadequate.
4. Drop-off point — where do people abandon the course?

The third says the most. A quiz everyone passes first time with 100 per cent is measuring clicking, not learning.

The privacy balance

Training progress is personal data. Who completed which course should be visible to the person, their manager and HR. Department-level reports should be aggregated; "this person failed three times" being visible to the team doesn't raise participation — it discourages people from trying.

Where to start

Start with mandatory training: a job that already has to be done and already gets tracked shows its benefit immediately once digitised. Open the development catalogue in a second stage. The rollout order is in the 90-day plan, and ways to sustain participation are in our engagement article.