18 min read
Best LMS with Course Prerequisites in 2026
A student who jumps into an advanced course without the foundational knowledge it assumes usually blames the course for being confusing, when the actual problem was sequencing. Prerequisites, requiring completion of one course or lesson before another becomes accessible, solve this at the platform level rather than relying on a student’s own judgment about whether they’re ready. We compared ten platforms specifically on prerequisite depth: course-to-course requirements, lesson-level dependencies, and whether the enforcement is real or just a suggestion in the course description.
This guide sits next to two related comparisons built on the same evaluation criteria. Our look at drip scheduling flexibility covers the timing half of pacing a course on its own, and our guide to combining drip scheduling with prerequisite gating covers what happens when a course business needs both mechanisms working together across a multi-course sequence. This piece stays focused on prerequisites by themselves: whether a requirement reaches across separate courses, whether it holds at the lesson level within one course, and how strictly it’s actually enforced.
What course prerequisites actually solve, and what they don’t
Prerequisites answer a readiness problem, not a pacing problem. Without them, a course catalog leaves sequencing entirely to a student’s own judgment, a description that says “recommended: finish the fundamentals course first” is easy to skip when the advanced course looks more interesting. Requiring genuine completion at the platform level, rather than hoping a student reads and follows a suggestion, turns a recommended order into an actual one, and it protects the more advanced content from being consumed by someone who doesn’t yet have the context to make sense of it.
What prerequisites don’t solve on their own is pacing. A student who finishes every prerequisite in one aggressive weekend can burn through an entire multi-course program before a cohort or a live component ever catches up. That’s the gap drip scheduling closes, spacing releases out on a calendar regardless of how fast a student clears each requirement, and it’s why the strongest platforms in this comparison support prerequisites and drip scheduling together rather than treating either as a complete answer by itself.
Key Takeaways
- Course prerequisites control what has to happen first. They don’t control pacing, a fast student can clear every requirement in one sitting unless drip scheduling is layered on top.
- Learnomy enforces prerequisites at both the course-to-course level, through Learning Paths, and the lesson level, through completion enforcement settings with a configurable strictness of strict, advisory, or off.
- LearnDash has the most established, strictly enforced prerequisite feature on this list, blocking access outright rather than just suggesting an order.
- Tutor LMS, Sensei, MemberPress Courses, and Thinkific mostly enforce sequencing within a single course. Cross-course prerequisites, chaining separate courses into a program, are the real limitation across all four.
- Strict enforcement genuinely blocks access. Advisory enforcement shows the recommended order without stopping a student from skipping ahead. Neither is universally correct, the right choice depends on whether the content is genuinely sequential.
In this guide:
- What Course Prerequisites Actually Solve
- How We Evaluated This Comparison
- Quick Comparison
- 1. Learnomy
- 2. LearnDash
- 3. LifterLMS and WP Courseware
- 4. Tutor LMS, Sensei, MemberPress Courses, and Thinkific
- 5. LearnPress and Kajabi
- Why “Strict” Versus “Advisory” Enforcement Matters
- Buying Criteria: What Actually Matters
- Common Mistakes When Setting Up Prerequisites
- Frequently Asked Questions
- Cost Structure Across the Ten Platforms
- Two Real Use Cases
- Verdict
How We Evaluated This Comparison
Every platform was checked against three distinct prerequisite mechanisms: whether an entire course can require a different course to be completed first, whether a single lesson can require a prior lesson within the same course, and how strictly the requirement is actually enforced, a hard block that prevents access versus an advisory note that a student can bypass. We also checked whether enforcement strictness is configurable per course or lesson, or fixed as a single site-wide rule, since a reference-style module and a genuinely sequential one usually call for different answers on the same site. Where documentation described a feature only in general terms, we looked for the specific scope, course-to-course, lesson-to-lesson, or both, rather than accepting a broad claim at face value. None of the comparisons here rest on marketing language alone, each capability was checked against its own documentation for the specific mechanism described, course-to-course or lesson-level, rather than a general “supports prerequisites” label that can hide a real gap in one of the two scopes.
Quick comparison
The Availability column below describes where each capability lives structurally, built into a core editor, included as a standard plugin feature, or requiring a separate add-on, rather than what it costs.
| Platform | Course-Level Prerequisites | Lesson-Level Dependencies | Enforcement Strictness | Availability |
|---|---|---|---|---|
| Learnomy | Yes, via Learning Paths + completion rules | Yes, via completion enforcement settings | Configurable: strict/advisory/off | Built into Learning Paths and the lesson editor |
| LearnDash | Yes, mature prerequisite feature | Yes | Strict | Included in the core plugin |
| LifterLMS | Yes | Yes | Reasonable | Included in the core plugin |
| Tutor LMS | Limited | Yes, within a course | Moderate | Included in the core plugin |
| WP Courseware | Yes | Yes | Reasonable | Included in the core plugin |
| Sensei LMS | Limited | Yes, within a course | Basic | Included in the free core plugin |
| MemberPress Courses | Limited | Yes, within a course | Basic | Included in the Courses add-on |
| Thinkific | Limited | Yes, within a course | Moderate | Available on hosted plans |
| LearnPress | Limited | Yes, within a course, via add-on | Basic | Free core plugin; deeper sequencing needs a paid add-on |
| Kajabi | Limited | Yes, within a course | Moderate | Included on every hosted plan |
1. Learnomy, prerequisites at both the program and lesson level
Learnomy handles prerequisites at two distinct levels, which matters because “prerequisites” can mean genuinely different things depending on scope. At the course-to-course level, Learning Paths enforce genuine sequential requirements, a student can’t access course two in a career-track path until course one is actually completed, not just enrolled in. At the lesson level, within any single course, completion enforcement settings control how strictly progression is required: “Require Lessons to be completed in order” with a minimum time-per-lesson setting, and a configurable enforcement level, inherit the site-wide default, strict, advisory, or off entirely, that a course or even an individual lesson can override.
That configurability matters practically: a course teaching genuinely sequential technical material (each concept builds on the last) benefits from strict enforcement, while a reference-style course where lessons stand more independently might reasonably use advisory or no enforcement at all, letting students jump to whatever’s relevant to them.
That last point is worth expanding on: enforcement only means something if “completed” reflects a real outcome. Learnomy’s gradebook rolls each course’s quizzes, assignments, and SCORM packages into a single weighted grade with a defined pass mark, so a course marked complete for prerequisite purposes means a student actually passed, not just opened every lesson once and closed the tab. An instructor can override a grade by hand when a specific situation calls for it, with the reason recorded against the override.
Learning Paths also handle auto-enrollment as a student clears each step, so a student doesn’t have to manually find and register for course two the moment course one finishes, the path itself carries them forward. Combined with a path certificate awarded on completing the full sequence rather than each course individually, the effect is closer to a single guided program than a set of independently linked courses a student has to piece together on their own.
Go deeper: The Course Isn’t the Finish Line, the Program Is covers course-to-course sequential enforcement through Learning Paths. The Course Builder That Doesn’t Make You Learn Software First covers lesson-level completion enforcement settings.
2. LearnDash, the most established prerequisite implementation
LearnDash’s prerequisite feature is one of its long-standing, well-refined capabilities, supporting genuine course-to-course requirements with strict enforcement. For a course business built around a clear, mandatory learning sequence, LearnDash’s maturity here is a real strength, backed by years of production use across a large install base.
3. LifterLMS and WP Courseware, solid, functional prerequisite support
LifterLMS offers working prerequisite enforcement configured at authoring time as part of course access rules, so a course can require a completed prerequisite course, or sit behind a membership tier, without an extra plugin. Its Engagements system layers on top of that: automation rules can award a certificate, unlock an achievement, or send an email the moment a student satisfies a requirement, marking the prerequisite as cleared without an instructor manually checking each student’s progress.
WP Courseware covers the same common case, requiring one course before another becomes accessible, with reasonable enforcement that holds up for straightforward sequencing needs. Neither offers a dedicated learning-path object for chaining several courses into one named, sequenced program with its own certificate; prerequisites here work course-to-course, but building a five-course track still means configuring five sets of prerequisite relationships rather than defining one path and adding courses to it.
4. Tutor LMS, Sensei, MemberPress Courses, and Thinkific, mostly within-course only
Tutor LMS enforces lesson-order sequencing well within a single course but treats cross-course prerequisites as a limited, non-core capability, adequate for a well-paced single course, weaker for a program built from several genuinely separate courses that need to gate each other.
Sensei handles lesson sequencing within a course in its free core plugin, with cross-course prerequisite chains staying outside its core strength. A course business relying on Sensei for a single, self-contained course finds this adequate; one planning a multi-course certification track should test cross-course behavior directly first.
MemberPress Courses inherits MemberPress’s membership-gating strength, so a course or a whole sequence can sit behind a specific membership level, but cross-course prerequisites specifically remain a real limitation rather than a documented core capability. Pairing MemberPress’s membership gating with a platform that handles course-to-course prerequisites more directly is a common workaround for a business already invested in MemberPress for billing rather than switching the entire stack over a single missing capability.
Thinkific supports lesson-level sequencing within a course as a standard hosted feature, with the same cross-course limitation as the other three, workable for a single sequenced course, less so for chaining several separate courses into one enforced path.
For a course business where prerequisites are mainly about lesson sequencing within one course, all four are entirely adequate; for a multi-course program with real prerequisite chains between separate courses, it’s a real limitation worth testing directly before committing a curriculum to any of them.
5. LearnPress and Kajabi, a lightweight plugin and a hosted platform at opposite ends
LearnPress keeps course-to-course prerequisites limited in its core, with deeper lesson-level sequencing available through a separate add-on rather than built into the base plugin. That makes it a reasonable starting point for a course business testing whether WordPress-based course delivery fits their workflow, less so for one that already knows strict multi-course sequencing is a day-one requirement rather than something to configure once the catalog has already grown.
Kajabi handles lesson-level sequencing within a course as a standard hosted feature, with cross-course prerequisite chains staying limited in the same way as most of the platforms in this comparison. As a fully hosted, all-in-one platform, the tradeoff is architectural rather than feature-based, a course business chooses Kajabi’s hosted convenience over owning the underlying site and its data, and accepts the same within-course sequencing ceiling most non-WordPress platforms share.
Why “strict” versus “advisory” enforcement is worth understanding
It’s worth being specific about the enforcement-level distinction Learnomy makes explicit, because it applies conceptually to any platform’s prerequisite system even where it’s not as clearly configurable. Strict enforcement genuinely blocks access, a student cannot open lesson 3 until lesson 2 is marked complete, full stop. Advisory enforcement shows the recommended order and perhaps a note about what should come first, but doesn’t technically prevent a student from skipping ahead if they choose to. Neither is universally correct, strict enforcement protects genuinely sequential content from being consumed out of order, while advisory enforcement respects a more experienced student’s judgment about which parts they already know. A platform offering both, configurable per course or per lesson, gives you the flexibility to match enforcement to the actual content rather than being locked into one philosophy site-wide.
Buying Criteria: What Actually Matters When Choosing Prerequisite Enforcement
Prerequisite support looks similar across a feature list until it’s tested against a real, multi-course catalog. A few specific questions separate the platforms that handle simple sequencing from the ones that hold up on a genuinely complex program. Working through these before committing a curriculum to a specific plugin saves a rebuild later, once several courses already depend on whatever structure was chosen first.
Does the prerequisite reach across separate courses, or stop at the edge of one?
This is the single biggest split in this comparison. Several platforms enforce lesson order well within one course but treat “course two requires course one” as a limited or unsupported case. A course business building a single, self-contained course rarely notices the difference; one building a multi-course certification track or onboarding program hits this limitation immediately and should test cross-course behavior directly before committing a curriculum to a specific platform.
Is enforcement strictness configurable, or fixed site-wide?
A single site often hosts both genuinely sequential courses and reference-style ones where lessons stand on their own. A platform that only offers one enforcement mode, always strict or always advisory, forces every course on the site into the same philosophy regardless of whether the content actually calls for it. A per-course or per-lesson override, inheriting a sensible site-wide default, is meaningfully more flexible.
Can an admin or instructor bypass their own prerequisite gates?
Building a five-course sequence with real prerequisite gates and then discovering the person building it can’t see beyond course one without a separate test account wastes real setup time. Confirm admin and instructor bypass behavior directly before building out the whole sequence, rather than assuming it works the same way it does on drip-locked content.
Does “completed” mean a real outcome, or just opening every lesson once?
A prerequisite is only as meaningful as what counts as completion. A platform that marks a course complete the moment every lesson has been opened, regardless of quiz or assignment performance, offers a weaker guarantee than one tying completion to an actual passing grade. Check whether a specific platform’s completion definition includes graded assessment or just a viewed-lesson checklist before relying on it to gate genuinely sequential content.
What happens if a prerequisite course is edited, unpublished, or deleted later?
A broken prerequisite reference can behave in one of two unhelpful ways: silently dropping the requirement so the gate stops working, or leaving a downstream course permanently inaccessible because the reference never resolves. This edge case is worth testing directly, on any platform, before it happens with real enrolled students mid-sequence rather than in a test environment, since recovering from a broken prerequisite chain after a cohort is already underway is far more disruptive than catching it beforehand.
Common Mistakes When Setting Up Course Prerequisites
- Setting strict enforcement everywhere by default. A reference-style course where lessons genuinely stand on their own doesn’t benefit from a hard block that only frustrates a student who already knows the material. Reserve strict enforcement for content where the order is actually load-bearing.
- Relying on prerequisites alone to pace a cohort. A pure completion gate lets a fast student burn through an entire program in a weekend, then sit idle waiting for a cohort discussion or live component that hasn’t happened yet. Pair a prerequisite with drip scheduling if a cohort needs to move together.
- Building cross-course prerequisites manually when the content actually forms one program. Chaining several standalone courses with individual prerequisite settings works, but it leaves no single view of a student’s position across the whole sequence, and no natural place to award one certificate for finishing the path rather than five separate ones.
- Not testing the admin or instructor preview path. Building a five-course sequence with real prerequisite gates and then discovering the person building it can’t see beyond course one without a separate test account wastes real setup time. Confirm admin bypass before building the whole sequence.
- Forgetting what happens if a prerequisite course is edited or unpublished later. A broken prerequisite reference can silently drop the requirement or leave a course permanently inaccessible. Worth testing directly, on any platform, before it happens with real enrolled students.
- Treating “completed” as identical across every platform. Some platforms mark a course complete once every lesson has been opened; others require a passing grade on graded assessments. Assuming the stricter definition when a platform actually uses the looser one means a prerequisite may be enforcing far less than it appears to.
- Not communicating the enforcement level to students. A student blocked by a strict prerequisite with no explanation assumes something is broken rather than working as designed. A short note on the course page about what’s required first heads off a real share of support questions before they happen.
FAQ
Learnomy’s per-course and per-lesson override on top of a site-wide default enforcement setting supports this directly. Confirm on other platforms whether enforcement is a global setting or configurable per course.
This is worth testing directly, a prerequisite pointing to a course built by a different instructor should function identically to one within the same instructor’s own catalog, since the prerequisite relationship is between courses, not tied to authorship.
Worth checking directly on any platform, a broken prerequisite reference could either silently remove the requirement or create a confusing state where a course is permanently inaccessible. This is an edge case worth testing before it happens on a live site with real enrolled students.
No. A prerequisite ties access to genuine completion of prior content regardless of how much time has passed. A drip schedule ties access to a calendar date or a delay after enrollment regardless of whether prior content was actually completed. A sequenced, multi-course program generally needs both working together rather than either alone.
Most platforms compared here don’t offer a built-in student-facing exception request flow, an admin typically has to manually mark a lesson or course complete on a student’s behalf to clear a strict gate. Confirm whether manual override is available and how much administrative effort it takes before relying on strict enforcement for a large cohort.
Not usually. Lesson-level sequencing within a single course is common across free core plugins, but genuine cross-course prerequisites, requiring an entirely separate course to be finished first, are more often limited or reserved for a more capable plugin like LearnDash or Learnomy. Check a specific plugin’s own documentation rather than assuming cross-course enforcement is included by default.
On platforms where course completion is tied to a weighted grade rather than a simple viewed-lesson checklist, a prerequisite effectively requires a passing score, not just having opened the content. Confirm whether a specific platform’s completion definition includes graded assessment before assuming a prerequisite guarantees actual competency rather than just exposure.
Prerequisites alone can chain courses together, course two requires course one, course three requires course two, but that leaves no single view of a student’s position across the whole sequence and no natural place for one certificate covering the entire path. A dedicated learning-path structure, like Learnomy’s, packages the sequence as one object with its own progress tracking and path certificate rather than a set of individually linked courses.
Cost structure across the ten platforms
Cost structure here means where a capability sits, not what it costs. Learnomy’s lesson-level completion enforcement and course-to-course Learning Paths both sit in the same platform, built into the lesson editor and the Learning Paths structure rather than requiring a separate purchase decision. LearnDash’s mature prerequisite feature spans its full plan range as a core capability. LifterLMS and WP Courseware both include prerequisite support as part of their standard offering, configured at authoring time without a separate add-on. Tutor LMS, Sensei, MemberPress Courses, and Thinkific all support within-course lesson sequencing as part of their core or standard hosted plans, with cross-course prerequisite chains staying limited regardless of which plan tier is in use. LearnPress keeps its core plugin free but moves deeper sequencing into a separate paid add-on, a common pattern among lightweight, freemium WordPress plugins. Kajabi, as an all-in-one hosted platform, includes lesson-level sequencing on every plan rather than treating it as a separate line item, while sharing the same cross-course limitation as most non-WordPress hosted platforms.
Two real use cases this decision affects
Two scenarios below make the practical difference concrete rather than abstract.
The single technical course where sequence genuinely matters. A course teaching a skill that builds concept by concept, a programming language or a regulated compliance topic, benefits from strict, lesson-level enforcement within that one course. A student cannot reasonably skip to lesson eight without lessons one through seven, and strict enforcement protects the content from being consumed out of order regardless of which platform handles the rest of the catalog.
The multi-course career track requiring real cross-course gating. A certification path or an onboarding curriculum built from several separate courses needs prerequisites that reach across course boundaries, course two genuinely inaccessible until course one is finished, not just recommended in a description. This is exactly where the split in this comparison shows up most clearly: platforms strong on lesson-level sequencing within one course aren’t automatically strong on this cross-course case, and the two shouldn’t be assumed interchangeable when evaluating a specific plugin against a real, multi-course curriculum.
Verdict
Ten platforms compared on this specific pairing surface a clear pattern: within-course sequencing is widely available, cross-course sequencing with genuine enforcement is not. Judged purely on within-course lesson sequencing, most of the platforms in this comparison land in a similar place, that’s common ground by now across the category. What separates them is course-to-course reach: whether a prerequisite can genuinely gate an entire separate course, and whether enforcement strictness can be configured per course rather than fixed as one site-wide rule. For prerequisite enforcement at both the course-to-course and lesson level, with genuinely configurable strictness, Learnomy and LearnDash are the two strongest options, Learnomy for its combination of Learning Paths sequencing with flexible per-lesson enforcement settings, LearnDash for its long-established, mature implementation. LifterLMS and WP Courseware offer solid functional alternatives. LearnPress and Kajabi sit at opposite extremes, a free core plugin needing a paid add-on for deeper sequencing, against a hosted platform bundling lesson-level sequencing into every plan while sharing the same cross-course ceiling as most hosted platforms. The remaining platforms handle within-course lesson sequencing well but are more limited for genuine cross-course prerequisite chains.
Prerequisites alone answer only half of the sequencing question. For a program that also needs realistic pacing, so a fast student doesn’t burn through an entire cohort’s material in one weekend, see our companion comparison on drip scheduling flexibility, or the combined guide to sequencing drip content and prerequisites into one multi-course program for platforms that handle both mechanisms together.
Sequence a real program, not just a course list
Course-to-course Learning Paths, configurable lesson-level completion enforcement, a gradebook that ties completion to an actual passing grade, and a migration wizard from LearnDash, Tutor LMS, and LifterLMS all ship in Learnomy, on a site you own.
Related reading