A learning path is an ordered route of courses, activities and checks that takes a defined group of people to one defined outcome, such as a new hire being ready for customer calls. A good one has six parts: a behavioural outcome, an automatic enrolment rule, short stages, gates that test application, due dates relative to each learner's start, and an owner who keeps it current. Measure it by time to competency, not completion rate.
Key takeaways
- A learning path is not a catalogue or a playlist. It has an order, gates and timing, all tied to one outcome.
- Start with the outcome as an observable behaviour, then work backwards to stages and gates.
- Early gates can be quizzes. Later gates should test application: scenarios, roleplay, observation.
- Use due dates relative to each learner's start date, and enrol people automatically by role.
- Start with a fixed path, add a few branches, and only then make it adaptive.
- Measure time to competency and stage drop-off, not just completion rate.
What a learning path is (and what it is not)
A learning path is an ordered route of courses, activities and checks that takes a defined group of people to a defined outcome: "ready to take customer calls", "certified to operate line 3", "able to run a quarterly business review". The path decides three things the learner should not have to work out alone: what comes next, what has to be proven before moving on, and by when.
The word gets used loosely, so it helps to separate it from the things it is often confused with:
| Thing | What it is | What it is missing |
|---|---|---|
| Course catalogue | Everything you offer, browsable | No order, no outcome, no deadline |
| Single course | One topic, start to finish | Usually too narrow for a role outcome |
| Playlist / collection | A curated list of content | No gates: you can skip to the end |
| Learning path | Sequenced stages + gates + timing, tied to one outcome | Nothing, if it is designed well |
| Curriculum / programme | A larger structure, often several paths | Usually built from paths, not instead of them |
If you want the one-paragraph definition, our glossary has it: learning path. This guide is about the harder part: designing one that people actually finish and that changes how they work.
The four types of learning path most organisations need
Almost every path we build for clients falls into one of four shapes. Knowing which one you are building settles most design questions before you start.
1. Role-based onboarding paths
Outcome: a new hire is productive in their role. Typical length: 30 to 90 days, in stages. Gated by: knowledge checks early, practice and a manager sign-off later. This is the path with the most business value, because the cost of a slow ramp-up is easy to see. Our Onboarding AI page shows the 30/60/90-day version we use.
2. Skill and upskilling paths
Outcome: an existing employee can do something new: lead a team, use a new system, sell a new product line. Typical length: a few weeks, often self-paced. Gated by: applied assessment rather than recall, because the people taking it already know the basics of their job.
3. Compliance and certification paths
Outcome: a person is certified and stays certified. Typical length: short, but it repeats. Gated by: a pass mark, an acknowledgement, sometimes a practical check. The defining feature is the recertification cycle: the path re-opens automatically when the certificate expires. See our guide to compliance training software for what auditors expect to see.
4. Extended-enterprise paths
Outcome: a partner, distributor, dealer or customer can sell, deliver or use your product. Gated by: certification, because you are vouching for people you do not employ. We cover this in extended-enterprise LMS training.
The anatomy of a learning path that works
Strip away the tooling and every good path has the same six parts. If one is missing, it shows up later as low completion, or as completion that means nothing.
- One outcome, written as a behaviour. "Can handle the five most common objections on a live call", not "understands objection handling". If you cannot say how you would observe it, the path has no finish line.
- An enrolment rule. Who gets this path, and what triggers it: a job role, a department, a location, a new record in your HR system. Paths that depend on someone remembering to enrol people quietly stop being used.
- Short stages in a deliberate order. Group content into stages of a week or two, each with its own small goal. Order by what the learner needs first on the job, not by how the content happens to be organised.
- Gates that test the right thing. A gate is a check that must be passed before the next stage opens. Early gates can be quizzes. Later gates should test application: a scenario, a Gelato AI roleplay, a submitted piece of work, a supervisor's observation.
- Timing. Due dates relative to each person's start date ("Stage 2 within 21 days of joining"), not fixed calendar dates that break the moment someone joins late.
- An owner and an expiry. Someone is responsible for the path's content, and the path has a review date. Paths without owners drift out of date and start teaching last year's process.
A worked example: a 90-day path for a new inside-sales rep
Here is how those six parts come together in a real shape. The content is illustrative; the structure is the point.
| Stage | When | What's in it | Gate to move on |
|---|---|---|---|
| 1. Essentials | Days 1–10 | Company, product basics, CRM walkthrough, mandatory policies | Short quiz per module; policy acknowledgement |
| 2. Product depth | Days 11–30 | Product modules by line, pricing logic, competitor positioning | Scenario-based assessment (choose the right response) |
| 3. Practice | Days 31–60 | Objection-handling and discovery-call practice with AI roleplay | Roleplay score above the agreed threshold on 3 scenarios |
| 4. Apply | Days 61–90 | Shadowing, first live calls, call reviews | Manager sign-off against a short checklist |
| Ongoing | Every 12 months | Refresher on policy and product changes | Recertification quiz |
Notice what the gates do. The early ones check that the basics went in. The later ones check that the person can do the job, which is what the business actually cares about. A path that ends with a recall quiz has measured the wrong thing.
How to design a learning path in 7 steps
This is the process we follow when we build a path with a client. It works whether you have five courses or five hundred.
- 1Write the outcome as a behaviour
Describe what the person will be able to do at the end, in terms you could observe on the job. This becomes the final gate.
- 2Define the audience and the trigger
Decide exactly who gets the path and what starts it: a role, a department, a location, or a new record in your HR system.
- 3Work backwards to stages
List what someone must be able to do just before the outcome, then just before that, and group the result into stages of one to two weeks.
- 4Map the content you already have
Assign existing courses and activities to each stage. Mark the gaps rather than stretching old content to fit.
- 5Set a gate for each stage
Choose the check that proves the stage worked. Use quizzes for knowledge, and scenarios, roleplay or sign-offs for skills.
- 6Add timing and reminders
Give each stage a due date relative to the learner's start date, and decide who is reminded when someone falls behind.
- 7Pilot, measure, then scale
Run the path with one small cohort, look at stage drop-off and gate pass rates, fix the weak stage, then roll it out.
Fixed, branching or adaptive: which kind of path?
Once the structure is right, the next question is how much the path should change from one learner to the next.
| Type | How it works | Best for | Watch out for |
|---|---|---|---|
| Fixed | Everyone takes the same stages in the same order | Compliance, regulated roles, small cohorts | Experienced hires get bored and click through |
| Branching | Rules send people down different routes: by role, location, or a test result | Onboarding across several roles; mixed experience levels | Rules multiply fast; keep the number of branches small |
| Adaptive | The system adjusts content to each learner: skipping what they have shown they know, adding support where they struggle | Large audiences with mixed starting points; upskilling | Needs good assessments, or it adapts to noise |
Most organisations should start with a fixed path, add one or two branches where roles genuinely differ, and only then add adaptive behaviour. Adaptive paths are powerful, but they depend on assessments that actually measure skill. For the mechanics, read our guides on adaptive learning platforms and AI-powered personalised learning paths.
What your LMS needs to support learning paths
Many platforms say they have "learning paths". In practice the label covers anything from an ordered list to a fully automated programme. When you evaluate an LMS, or audit the one you have, check for these:
- Automatic enrolment by job role, department, location or seniority, ideally triggered from your HR system. Our guide to HRMS–LMS integration explains how that sync works.
- Prerequisites and unlock rules: a stage or course opens only after the previous one is complete or a score is reached.
- Relative due dates and automatic reminders to the learner and their manager.
- Practice-based gates, not only quizzes: scenarios, roleplay, assignments, observation checklists.
- Manager visibility: who is on which stage, who is overdue, who is stuck at a gate.
- Recertification: the path re-opens automatically when a certificate expires.
- Mobile access for frontline and field staff who will never sit at a desk to learn.
- Stage-level reporting, so you can see where people drop off, not just whether they finished.
If your LMS is Moodle
Moodle can do most of this, but the pieces are spread across several features, which is why admins often say it "has no learning paths". The usual mapping:
| What you need | Moodle feature |
|---|---|
| Order and gates inside a course | Activity completion plus Restrict access (unlock on completion, grade, date, group or profile field) |
| Role-based enrolment | Cohorts with Cohort sync enrolment, often fed from your HR system |
| Skills and outcomes across courses | Competencies with learning plan templates assigned to cohorts |
| Multi-course paths with deadlines and recertification | Programs and Certifications in Moodle Workplace, or a third-party programs plugin on standard Moodle |
The catch is that each piece is configured separately, and reporting across them takes effort. That gap is where most of our Moodle path work happens.
How to tell whether a learning path is working
Completion rate is the number everyone reports, and on its own it is the least useful one. A path can show 95% completion and still produce people who cannot do the job. Track these instead:
- Time to competency: days from enrolment to passing the final practical gate. This is the number the business cares about.
- Stage drop-off: where people stop. One stage with a sharp drop usually means it is too long or its gate is unclear.
- First-attempt pass rate at each gate: very high means the gate is too easy; very low means the stage before it is not teaching what the gate tests.
- Overdue rate: how many people are past a stage's due date. Rising overdue rates usually mean the timing does not fit real workloads.
- An on-the-job signal: whatever the outcome promised. Call quality scores, error rates, audit findings, first-month sales activity.
We go deeper on this in course completion metrics that matter and how to measure LMS ROI.
Six mistakes that quietly kill learning paths
- Making the path too long. Twelve courses in a row feels like a sentence, not a path. If a stage takes more than two weeks, split it or cut it. Short microlearning modules help here.
- Gating everything. If every module needs a quiz, people learn to game quizzes. Put real gates at stage boundaries only.
- Treating completion as the outcome. The outcome is a behaviour on the job. Completion is just evidence the path was taken.
- One path for everyone. Forcing a ten-year veteran through basics is the fastest way to teach people to click through. Add a test-out option or a branch.
- Manual enrolment. If the path depends on someone remembering to add new joiners, it will be missed for a share of them every month.
- No owner and no review date. Products, policies and systems change. A path nobody owns ends up teaching an old version of the job.
How edzlms handles learning paths
In edzlms, learning paths are built around the six parts above, so most of the wiring is done for you:
- Role-based assignment: paths are assigned automatically by job role, department, location or seniority, so every employee sees what they need. See edzlms for corporate learning.
- HR-triggered onboarding: when a new employee record appears in your HR system, Onboarding AI builds their path and starts the 30/60/90-day sequence.
- Adaptive adjustment: if someone struggles on a quiz or roleplay score, remedial content is added for them; if they are clearly ahead, they move on faster.
- Practice gates with Gelato AI: Gelato AI roleplay can be the gate between stages, so people prove they can handle the conversation, not just recall the script.
- Certification tracking: certificates are tracked, managers are alerted, and recertification paths re-open automatically on expiry.
- Filling content gaps fast: if a stage needs a module you do not have yet, the EDZLMS AI Course Builder turns your SOPs, policies and slide decks into a course you can review and publish.
A course catalogue
- Learners decide what to take and in what order
- No clear finish line
- Completion can't be linked to a job outcome
- Managers can't see who is ready
- New hires are enrolled by hand
A designed learning path
- Stages in the order the job needs them
- One outcome, tested at the end
- Gates prove each stage worked
- Managers see who is on which stage
- Enrolment and recertification are automatic
Need something custom-built?
Want learning paths wired to your HR system, custom reports by region or role, or a path built around your own certification rules? edzlms designs and builds it for you. Book a free demo or email marketing@edzlms.com and we'll scope it with you.
Start with one role
Don't redesign your whole catalogue at once. Pick the one role where slow ramp-up costs the most, build its path, measure time to competency for one cohort, and use that result to make the case for the next path.
Frequently asked questions
What is a learning path in an LMS?
A learning path is an ordered sequence of courses, activities and assessments in an LMS that takes a defined group of learners to a defined outcome. Unlike a catalogue, it controls the order, unlocks later stages only after earlier ones are passed, and usually sets due dates.
What is the difference between a learning path and a curriculum?
A learning path leads one audience to one outcome, such as onboarding for a sales role. A curriculum or programme is usually larger and is often made of several learning paths, for example a full leadership programme with separate paths for each level.
How long should a learning path be?
As short as the outcome allows. Onboarding paths often run 30 to 90 days in stages; upskilling paths a few weeks. Keep each stage to one or two weeks, and split any stage that runs longer.
What is an adaptive learning path?
An adaptive learning path changes for each learner based on how they perform. People who show they already know a topic skip it, and people who struggle on an assessment get extra support before moving on. It depends on assessments that genuinely measure skill.
Can Moodle create learning paths?
Yes, but the pieces are separate. Activity completion and Restrict access handle order and gates inside a course, cohorts handle role-based enrolment, competencies and learning plans track skills, and multi-course programmes with recertification need Moodle Workplace or a third-party plugin.
How are learning paths assigned automatically?
Through enrolment rules based on job role, department, location or seniority, usually synced from your HR system. When a new employee record is created, the matching path is assigned and the first stage starts without anyone enrolling them by hand.
How do you measure whether a learning path works?
Track time to competency, drop-off by stage, first-attempt pass rate at each gate, the overdue rate, and an on-the-job signal tied to the outcome. Completion rate alone can be high while people still cannot do the job.
Sources
Moodle Docs: Restrict access, Cohort sync, Learning plans, Programs (Moodle Workplace). Published 22 October 2026.
For more on learning design and LMS strategy, connect with Mihir Jana on LinkedIn.
Turn your courses into paths people finish
We'll map one of your real roles into a staged learning path, with gates, deadlines and reporting, live in a 45-minute demo.