Enrollment and progress
How people are enrolled on courses, how progress is tracked, and how readiness is measured.
- See every learner's progress and readiness in one place
- Enroll individuals, whole-org rollouts, or rule-based cohorts — the model is up to you
- Progress and completion are measured by the server, so the numbers can be trusted
Enrolling people
There are several ways to put a course in front of people:
- Hand-pick individuals — for pilots and role-critical training.
- Whole-org rollout — one link, or a claimed email domain, so colleagues join automatically.
- Rule-based (dynamic) cohorts — everyone matching a saved query is enrolled, and stays in sync as people join and leave.
Enrolling someone is idempotent: enrolling them again on the same course changes nothing. Only an active member can be enrolled — a seat is taken when they join the organization, not when they start a course.
How progress works
Progress is owned by the learner and verified by the server. As they move through a published lesson, their percentage and time-on-task are recorded against their enrollment. When every published lesson of a course is complete, the enrollment is marked complete — automatically, by the server. Nobody can mark their own mandatory training complete by hand.
Readiness
Readiness rolls learning up into one number managers can act on. Today it reflects the learn leg — how far people have got. Prove (credentials) and apply (in-product evidence) join the score as those modules ship, each with its own weight. A leg that is not yet measured is left out and its weight is shared across the rest, so the number is always honest about what it knows.
Frequently asked
What are the enrollment models?
Six, from doc 05: hand-pick individuals; a whole-org rollout via a link or a claimed domain; a dynamic cohort that enrolls everyone matching a rule; directory sync from your identity provider; partner organizations; and customer self-serve. The first three are available today.
Who can see a learner's progress?
The learner themselves, and the organization's owners, admins, enablement managers, team managers and analysts. No other learner can see it, and the database enforces that — not just the interface.
How is progress recorded?
As a learner works through a published lesson, their progress and time-on-task are recorded against their own enrollment. Completion is rolled up by the server when every published lesson of a course is finished; a client can never mark its own training complete.
What is the readiness score?
A single 0–100 number that today reflects learning progress. As the proving module (credentials) and the applying module (in-product evidence) come online, they join the score with their own weight. Until then the score reflects only what is measured, so it never reads artificially low.
Related guides
Group people into static rosters or dynamic, self-updating segments — and assign paths on entry.
ReadLive adoption, progress and readiness for your organization, built from the activity stream.
ReadRun your organization's people, teams, invitations and domains from one control plane.
Read