One click enrolls the cohort; the learning plan delivers the rest on time
Left: how it's configured in Docebo. Right: a test learner enrolled on Day 0 — move the clock, break things, and check that every release lands when it should.
Docebo configuration
Unlock delays are editable — change one and the simulator and checkpoints re-run against the new configuration. That is the "adjust" loop. Delays count from completing the prerequisite; the test learners complete Prework on their first day.
Day 0
● release ■ live event red line = today
Automated checkpoints —
| Day | Expected | Observed | Result |
|---|---|---|---|
| Run to see results. | |||
Risks of one session for every event — and what the build does about them
Unlock notifications and long delaysDocebo's "new course unlocked" notification is reported not to fire when a prerequisite delay is longer than two weeks.Mitigation: a scheduled notification per release, set to the unlock date, rather than relying on the unlock event.
Can't skip one eventA learner who must miss Week 4 is still enrolled; a strict rule would fail the session.Mitigation: session completion = attended ≥ 3 of 4 (set in the tree); instructor override; make-up event added to the same session.
Capacity is per sessionRoom and Zoom limits differ; one session has one capacity.Mitigation: capacity 16 = the in-person room; Zoom meeting (not webinar) sized above it; waitlist on.
Time zonesZoom events shift to the learner's zone; in-person events don't.Mitigation: venue events entered in venue time and labelled; test with the "other time zone" scenario above.
Changing a date re-notifies everyoneOne edit to an event emails the whole cohort.Mitigation: calendar agreed before enrollment opens; changes batched and announced first.
Late joinersUnlock delays count from each learner's own prework completion, so a Day-10 joiner gets Assignment 1 on Day 17 and has missed the kickoff.Mitigation: decide with the program owner: back-date the enrollment (dates re-align) or accept a shifted schedule; kickoff recording linked in the prework.
Alternative buildsB — one ILT course per event (four enrollments; maximum flexibility). C — two sessions in one course (in-person track / remote track).Recommendation stays with one session for the learner experience, with per-event attendance and a make-up policy.