Skip to content

Setup Considerations: mandatory learning

Mandatory learning is defined by rule rather than assigned person by person, so the audience is worked out from who people are instead of from a list somebody maintains. Getting the rules right is what makes a compliance figure mean something.

Most training is assigned. Compliance training is different in kind, and the difference decides which tool you use.

OptionDescription
A mandatory ruleThe audience is derived from a scope, and new joiners who match are picked up when the rules are enforced. The question it answers is who has not completed.
Enrolling learners directlyYou choose the people. Nothing is inferred, and nobody is added later.

The test is whether you can state who needs the training without naming anyone. “Everyone in Operations” is a rule; “these fourteen people” is an assignment.

Example: annual security training for everyone at HC Corp UK Ltd is a rule. A course for the six people rolling out a new system is an assignment.

Decision 2: how narrow the scope should be

Section titled “Decision 2: how narrow the scope should be”

A rule targets one scope, and the choice decides both who is reached now and who is picked up in future.

OptionDescription
All EmployeesEveryone. The right answer for genuinely universal training.
By DepartmentEveryone in a named department.
By Job ProfileEveryone holding a named profile. Follows the work rather than the reporting line.
By GradeEveryone at a named grade.
By Business UnitEveryone in a named unit.

Prefer the scope that describes why the training is needed. Where the reason is the work somebody does, job profile survives reorganisations that department does not.

Example: handling training required by a warehouse role at HC Corp UK Ltd is better scoped by job profile than by department, because moving the team under a different department would silently drop them from a department-scoped rule.

The form previews how many employees a rule will apply to before you save it, and can show a sample of who they are. Treat a count that surprises you as a wrong scope rather than a surprising organization.

A rule targets either a single course or a whole path. A path is the right target where compliance genuinely means several pieces of training, because one rule then tracks the whole obligation rather than three rules tracking parts of it.

Decision 4: what the deadline is measured from

Section titled “Decision 4: what the deadline is measured from”

The deadline is a number of days from enrollment, not a fixed date in the calendar. Everybody therefore gets the same amount of time, and a new joiner’s clock starts when the rule reaches them.

That is usually what compliance training means, and it is not what people expect if they were thinking of a year-end date. A rule with a thirty-day deadline gives a January joiner until February and a September joiner until October.

Example: a thirty-day deadline on induction training at HC Corp UK Ltd means each new starter has their own month, which is the sensible reading. The same setting on training everyone must finish before a fixed audit date is not, because nobody’s deadline lines up with the audit.

A rule can recur after a number of months, or not recur at all. Recurrence is what turns a one-off course into an annual obligation without anybody remembering to re-run it.

Set it where the requirement genuinely repeats. A recurrence set on training that only needs doing once produces a compliance figure that falls every year for no reason.

Decision 6: what enforcement actually does

Section titled “Decision 6: what enforcement actually does”

Enforcing evaluates all active rules and enrols matching employees who are not yet enrolled. The confirmation states the limits of it: people already enrolled or already completed are skipped.

Two consequences follow. Enforcement is safe to run repeatedly, because it does not duplicate or reset anybody. And a rule does nothing on its own — creating it defines the requirement, and enforcing it is what puts people on the course.

Decide who runs enforcement and how often. A rule created in March and never enforced shows an audience count and no enrolments.

Deleting a rule is refused while active enrolments still reference it, and the product tells you to deactivate it or reassign them first. Where a delete does go through, the confirmation warns that enrolments the rule created may need sorting out by hand.

Deactivating is the safer route. It stops the rule reaching anybody new while leaving the history of what it required intact.

DecisionCost of changing later
Scope on a live ruleHigh. People join or leave the audience at the next enforcement, and enrolments already created do not disappear.
Deleting a rule with active enrolmentsHigh. It is blocked while they exist, and enrolments may need sorting out by hand afterwards.
Target course or pathHigh. What people were enrolled on does not change retrospectively.
RecurrenceMedium. It changes when the requirement comes round again.
Deadline daysMedium. It applies from the next enrolment.
Rule nameLow.

Create your rules, enforce them, then watch the compliance figure and the overdue list. The compliance percentage reported against mandatory training is produced by these rules, so a figure that looks wrong is almost always a scope that is wrong.