How a path runs
Assign it once,
then leave it alone
- 01
Assign the path
To a person, a group, a branch or a role, or automatically on a start date.
- 02
Complete a step
A real completion, at the pass mark set on the course, not a click on next.
- 03
The next step unlocks
Nobody skips ahead, and nobody has to be told what to do next.
- 04
Certificate issued
On finishing the path, filed against the learner, with the manager notified.
What a path can hold
Any content,
in any order
- SCORM, xAPI and cmi5 packages you already own
- Video, PDF and PowerPoint uploaded directly
- Courses generated by the AI course builder
- Practice scenarios, so a path can end in doing rather than reading
- Live virtual classroom sessions as a step in the sequence
What it saves you
The chasing,
mostly
- Automations remind and escalate without a person doing it
- Stalled learners surface on the dashboard while there is still time
- One induction per role, so quality does not depend on who was free
- Recurring paths for anything that has to happen again every year
Before you ask
Common questions
Can different roles get different paths?
Yes. Build a path per role and let an automation choose which applies from the person record, so nobody has to decide manually for each new joiner.
What happens if somebody fails a step?
The next step stays locked and the attempt is recorded rather than overwritten. They can retake it, and the history of attempts remains visible.
Can a path include a live session?
Yes. A virtual classroom session can sit in the sequence, with attendance recorded against the learner like any other step.
Is there a limit on how long a path can be?
No. Longer paths are more about whether people will finish them than about whether the platform allows it.