Course on How to design adaptive learning paths in Moodle

Section 1: Adaptive Paths Within a Course [1 hour]

  • Core features and the course scenario: An adaptive learning path changes what learners can access based on their progress or needs. Follow one employee onboarding program: Course A covers workplace basics, and Course B covers advanced procedures. Explore how Moodle resources, activities, grades, completion tracking, and access rules support different routes through Course A.

  • Progress signals and completion settings: Understand activity completion, which records whether a learner meets an activity’s requirements. Cover viewing a resource, submitting an assignment, receiving a grade, and earning a passing grade. Explain how completion tracking, activity settings, and the gradebook—Moodle’s record of learner grades—work together. Distinguish completing an activity from passing it.

  • Access rules for micro-routes: A micro-route is a short sequence of content within a course. Explore Restrict access, Moodle’s feature for controlling access to activities and course sections. Cover conditions based on grades, activity completion, dates, groups, and user profile fields. Explain nested restriction sets, which combine conditions using “all” or “any,” and the difference between hiding unavailable content and displaying its access requirements.

  • A connected route through Course A: Follow a worked configuration example: an initial quiz score below 80% makes a support lesson available, while a score of 80% or higher opens an advanced topic. Completing the support lesson opens a follow-up check, whose passing result also unlocks the advanced topic. Explain how quiz attempts and grading methods affect this route. Contrast these course-level rules with branching inside Moodle’s Lesson activity, where answers can lead learners to different pages.

Section 2: Completion and Course Enrollment [1 hour]

  • Defining when Course A is complete: Building on the internal routes, explain course completion—the overall completion status recorded for a course. Cover selected activity requirements, grade requirements, manual completion options, and how required conditions combine. Show why optional support content should not accidentally become mandatory for everyone. Clarify that course completion records progress but does not, by itself, enroll learners in another course.

  • Preparing the completion-based enrollment plugin: Introduce enrol_coursecompleted, an enrollment plugin that can enroll learners in a destination course after they complete a source course. Explain administrator responsibilities for checking Moodle-version compatibility, installing the plugin, and enabling the enrollment method. Distinguish site-level plugin availability from configuration within an individual course, including the permissions needed to manage enrollment methods.

  • Connecting Course A to Course B: Trace the configuration sequence without an implementation assignment: open Course B’s enrollment methods, add the completion-based enrollment method, select Course A as the source, and review the available enrollment settings. Explain the destination role and any supported enrollment limits or timing options. The input is a qualifying completion record for Course A; the expected output is enrollment in Course B. Distinguish this process from merely displaying a link to Course B.

  • Timing, visibility, and reliable progression: Explain cron, Moodle’s background task runner, and why completion updates or enrollment may not appear immediately. Cover checks for missing completion records, disabled enrollment methods, incorrect source-course selection, and destination-course availability. Discuss existing enrollments and previously completed source courses as behaviors to confirm against the installed plugin version. Distinguish enrollment from actual access, which may also depend on course visibility and other restrictions.

Section 3: Final Review

  • Review of key concepts

  • Future learning directions

Skill Level: Beginner