Schedule course runs and release content over time
A course run, also called a cohort, is a delivery of a course for a particular group or period. For example, you can teach the same course to an October intake and a January intake without writing the curriculum twice.
Course-run scheduling and advanced release policies require the supporting package. If the tools are absent, use the course's ordinary dates and prerequisites, or ask the administrator to check the installed edition.
Create a run
- Open the course's Course tools → Course runs.
- Create a run with a clear title, dates, and timezone.
- Choose the pacing mode offered by your installation.
- Save the schedule, then add the intended members.
- Review the run's lesson availability using a test learner.
The workspace separates Schedule, Members, and Overrides. Being listed in a run does not remove the need for valid course access.
Choose pacing that matches your teaching
| Approach | Suitable use |
|---|---|
| Fixed schedule | Everyone follows the same calendar dates. |
| Relative schedule | Content opens relative to an event such as joining or gaining access. |
| Self-paced delivery | Learners work to their own timetable, subject to the course's rules. |
A schedule anchor is simply the date from which a delay is counted. “Seven days after enrolment” and “seven days after the run starts” can produce different release dates for someone who joins late.
Use the time zone displayed by the editor. Learners may see a local-time version of the date, so record the intended teaching timezone clearly.
Release lessons gradually
Add the relevant date, offset, or run-position condition in the lesson or module's access settings. Combine it with completion requirements when both timing and previous work matter.
Use a learner preview at different dates to check the schedule. A content-release notification also needs its notification rule and background tasks; a date condition by itself is not an instruction to send an email.
Handle individual circumstances
Use a run or learner Override to change a date for a specific situation without moving the whole class. Check opening, due, and closing dates separately. A due date can affect lateness, while a closing date can prevent access.
Optional late policies may allow a grace period, stop submissions after a deadline, or apply a deduction. Explain the selected policy in the assessment instructions and test an on-time and late submission.
Before archiving a run, review its active learners and outstanding assessments. Archived schedules and historical reports should remain understandable after the teaching period ends.
For course-wide prerequisites and the order of lessons, use access and progression. For cohort progress and learners needing attention, see reports.