LearnDash Course Setup Checklist Before Launch

Intent and ownership

This checklist owns course-setup acceptance, not every LMS project

This guide owns one informational task: prepare and accept one LearnDash course before enrollment opens. It covers the source outline, hierarchy, course page, enrollment mode, access authority, progression, lesson settings, quizzes, certificates, integrations, representative tests, launch evidence, reporting, recovery, and owner handoff. It does not install LearnDash, write the course curriculum, provide instructional-design accreditation, migrate an LMS, configure every checkout or CRM, guarantee accessibility conformance, or certify a live course.

Use LearnDash Course Structure Setup when the requested outcome is the existing LMS-047 fixed-scope implementation: one course structure with up to ten lessons or topics under the listed `$197` scope and 3-5-business-day target after access, content, assets, and scope are confirmed. That page retains its price, inclusions, exclusions, request route, proof route, and commercial phrase `LearnDash course setup service`. This article helps a buyer prepare and test the inputs; it does not replace the paid owner.

Use LearnDash Course Launch QA when the course already exists and the main task is an audit of the learner path. Use LearnDash Quiz Setup Pack when question entry and quiz configuration are the bounded implementation. Use LearnDash Access Automation Map when enrollment depends on payment, membership, CRM, group, or several systems. Use WooCommerce to LearnDash Access After Purchase when the problem begins after a WooCommerce order.

LearnDash core, add-ons, WordPress, themes, page builders, ecommerce systems, membership plugins, AI tools, and custom code can change. Confirm the current official documentation, installed versions, licenses, live settings, hosting limits, and representative student behavior before production work. This guide is implementation guidance, not LearnDash affiliation, education or legal advice, privacy certification, accessibility certification, or a guarantee of launch, enrollment, ranking, traffic, AI citation, leads, or revenue.

User task	Canonical route	Owned outcome	Not owned
Prepare and accept one course before launch	This guide	Informational setup contract, decisions, checks, tests, and handoff	Hands-on WordPress or LearnDash implementation
Build one bounded course structure	LMS-047 setup	Paid course, lesson, and topic implementation under the listed scope	Open-ended curriculum, migration, integration, or redesign work
Audit an almost-ready learner path	Course Launch QA	Focused launch-path review and findings	Building the full course or every connected automation
Map cross-tool enrollment and recovery	Access Automation Map	Source-to-access roadmap across the agreed systems	Course-content structure by itself
Find the first conflicting system owner	Systems Audit	Evidence-led diagnosis across WordPress, payment, CRM, access, email, and reporting	A routine known single-course setup

Stage 1: source of truth

Freeze the learner promise, course inventory, and launch contract before building

Start outside the Course Builder. Record the course name, learner, measurable outcome, delivery model, launch date, owner, review date, and one approved outline. Give every section, lesson, topic, quiz, download, assignment, and certificate a stable source identifier that does not depend on its temporary WordPress post ID. The purpose is not bureaucracy; it is to prevent one title in a document, another title in LearnDash, and a third title in the sales or onboarding path.

Define the smallest complete learner path. A representative path usually includes the public course or sales page, registration or purchase, enrollment, first lesson, any required topic, one completion action, one quiz when used, certificate or completion page when used, email or support handoff, and reporting evidence. Build and test that path before entering the entire content library. It exposes wrong access assumptions while the change surface is still small.

Distinguish required inputs from optional enhancements. Required inputs include approved copy, content files, lesson order, enrollment authority, progression, completion, support ownership, privacy limits, and acceptance criteria. Optional inputs include a community, achievement points, advanced reporting, cohorts, elaborate certificates, marketing automations, and AI-assisted expansion. A launch date should not convert undecided optional features into hidden acceptance requirements.

If AI assists with the outline, preserve the human-approved source. LearnDash documents that its Course Outline Builder creates lesson titles only; it does not create lesson content, topics, quizzes, or assignments. Treat generated titles as proposals. The course owner still approves learning outcomes, sequence, claims, accessibility, source rights, assessment quality, and the content that will be published.

01Contract
02Structure
03Enrollment
04Progression
05Content
06Handoffs
07Test
08Launch

Crawlable workflow equivalent for the article visual: course contract, structure, enrollment, progression, learning content, external handoffs, representative testing, and controlled launch.

Contract layer	Required decision	Minimum evidence	Hold condition
Learner outcome	Who should be able to do what after completion	Approved promise, prerequisites, completion evidence, and owner	The course is organized only around available files
Content inventory	Sections, lessons, topics, quizzes, assignments, files, and certificates	Stable source IDs, titles, owners, versions, rights, and status	Assets are scattered or cannot be matched to the outline
Access contract	Who enrolls the learner, when, for how long, and how access ends	Enrollment mode, authoritative system, states, and exception route	LearnDash and another system can both grant or revoke access
Acceptance path	The smallest visitor-to-completion scenario that proves the setup	Test identities, expected steps, negative assertions, and receipts	The first end-to-end test is planned after all content is entered
Launch ownership	Approver, operator, support owner, rollback decision, and review date	Named people or roles and an accessible handoff record	No one owns student-impacting failures after launch

Stage 2: course hierarchy

Build sections, lessons, topics, and quizzes from a stable hierarchy

LearnDash courses contain an ordered hierarchy. Sections are text-only dividers similar to chapters. Lessons are the primary learning steps. Topics are optional child steps and must belong under lessons; a course can use lessons without topics, but it cannot use topics without lessons. Quizzes can sit under a topic, under a lesson, or as final course quizzes. Decide the hierarchy in the source outline before dragging items in the builder.

Use topics only when the additional level improves navigation, progression, ownership, or reuse. Turning every short video into a topic can create a deep tree that is difficult to maintain on mobile. Conversely, putting a long multi-part module into one lesson can make completion and support evidence too coarse. Each step should have a learner-facing purpose, a source owner, and an observable completion rule.

LearnDash warns that new lessons, topics, and quizzes created through the Course Builder are automatically published and set Public after the course changes are saved. That makes build order a launch-control issue. Use a non-public staging environment, restrict discovery and enrollment appropriately, or create a documented content-state process before entering sensitive or unfinished content. Do not assume a new builder item is a private draft.

Decide whether Shared Course Steps are allowed. Reuse can improve consistency, but one edit can affect several courses. Record every course that uses a shared lesson, topic, or quiz, who may change it, and which regression paths must run after a change. Keep titles descriptive and stable, save builder changes before opening an individual step for editing, and verify the final order from the learner interface rather than trusting the admin tree alone.

Element	Use it for	Acceptance evidence	Common setup defect
Course page	Expectation, description, featured image, URL, materials, and entry point	Correct public and enrolled views, metadata, links, and owner	The sales promise and the learner course page disagree
Section	Text-only grouping of related lessons	Readable labels and at least one correctly placed child step	A section is treated as a content page or left empty
Lesson	Primary learning step with content, materials, and completion behavior	Correct course association, content, order, visibility, and completion	A lesson exists outside the intended course or in the wrong order
Topic	Optional hierarchy within a lesson	Correct parent lesson, content, schedule, and completion path	A topic is used without a lesson or adds unnecessary depth
Quiz	Assessment at topic, lesson, or final-course level	Correct association, questions, pass rule, retakes, feedback, and result	The quiz is built but not attached to the intended step
Shared step	Approved reuse across more than one course	Dependency list, change owner, and regression paths	An edit silently changes several live courses

Stage 3: enrollment authority

Choose one enrollment mode and one system that owns access

Enrollment mode is not a cosmetic button setting. It defines whether content is public, registration is required, LearnDash collects payment, or another system controls enrollment. LearnDash currently documents five modes: Open, Free, Buy Now, Recurring, and Closed. Record why the selected mode matches the sales and access path, then test that exact mode with a clean user.

Open exposes course content without enrollment, although progress is tracked only for logged-in users and linear progression applies only to logged-in users. Free requires registration or login but no payment. Buy Now and Recurring use LearnDash-supported payment behavior. LearnDash explicitly says not to use Buy Now or Recurring when selling through an external shopping cart or membership plugin; use Closed so the external system or an approved manual process owns enrollment.

Closed does not mean broken or hidden. It means LearnDash does not apply automatic enrollment rules and access is managed externally, manually, or through groups. Record the external sales or checkout URL, the event that grants enrollment, the key that relates the order or membership to the WordPress user, the rule that removes access, and the evidence support will use when systems disagree.

Keep the learner identity contract explicit. Define whether email is the approved identity, how guest purchases become WordPress users, whether existing accounts are reused, how changed email addresses are handled, and what happens when an order cannot be matched safely. Never expose passwords, private student data, order exports, API keys, or live credentials in a setup worksheet. Use no-private-data QA identities and revoke temporary access after the approved test.

Enrollment mode	Primary behavior	Use when	Critical test
Open	Course content is publicly available without enrollment	Public access is intentional and progress limits are understood	Visitor visibility and logged-in completion behavior match policy
Free	Registration or login is required without payment	LearnDash registration is the intended entry point	A new user can register, enroll, log in again, and resume
Buy Now	One-time payment through supported LearnDash payment behavior	LearnDash owns the one-time purchase and enrollment path	Successful and failed payment produce the correct enrollment state
Recurring	Recurring payment through supported LearnDash payment behavior	LearnDash owns recurring billing for the course	Initial payment, renewal, cancellation, and access duration match policy
Closed	Enrollment is external, manual, or group-managed	WooCommerce, a membership plugin, CRM, group, or operator owns access	The external event creates or resolves the user and grants exactly one enrollment
Unknown or mixed	More than one path can grant, extend, or revoke access	Never as an accepted launch state	Hold launch and map the authoritative owner plus every exception

Stage 4: progression and release

Define how a learner advances, waits, completes, and returns

LearnDash offers Linear and Free form progression. Linear requires learners to complete steps in order; Free form allows them to navigate in another order, although child topics still must be completed before their parent lesson is complete. Select the mode from the learner outcome, not from a generic belief that one mode is more professional. A reference library and a compliance sequence have different needs.

Record every prerequisite, required quiz, pass score, retake policy, assignment approval, completion action, course point requirement, access-expiration rule, start date, end date, and completion destination. Test conflicts rather than reading settings independently. A learner may be enrolled but unable to begin because the start date is future, a prerequisite is incomplete, a lesson is scheduled, or a manual assignment is awaiting approval.

Lesson schedules can be immediate, enrollment-based, or tied to a specific date. LearnDash notes that one enrollment-based day means 24 hours after enrollment, not the next calendar day. Topics associated with a scheduled lesson inherit the lesson schedule; separately associated topics can have their own release schedule. Use explicit timestamps and time zones in test evidence where a calendar or cohort promise matters.

Changes after launch need a policy. LearnDash documents that adding or removing lessons does not reset completion for learners who already completed the course. Decide whether new material is optional for prior completers, whether a new course/version is required, how certificates remain valid, and what support communicates. Do not change a live course hierarchy and assume historical completion will be recalculated automatically.

Rule	Decision to record	Representative test	Failure signal
Progression	Linear or Free form and why	Attempt the next and a later step before completion	A learner can bypass or cannot reach intended content
Prerequisites	Any selected or all selected courses, points, or other gate	Eligible and ineligible clean users	The message, link, or eligibility state is wrong
Release schedule	Immediate, elapsed from enrollment, specific date, start, or end	Before, at, and after the boundary with the expected time zone	Content releases early, late, or under a different clock assumption
Completion	Required steps, quiz, assignment, certificate, and destination	One pass, one fail, one retake, and one returning session	Completion appears without required evidence or never closes
Post-launch edits	Effect on prior learners, certificates, reports, and support	Add or change a QA-only step against completed and active users	Historical completion or navigation behaves differently than assumed

Stage 5: learning content and assessment

Configure every lesson and assessment from one explicit learner action

Each lesson or topic should answer four questions: what the learner sees, what the learner does, what proves completion, and what happens next. Verify the title, body, video or embed, transcript or alternative, downloads, links, materials, completion button, parent association, visibility, release rule, and mobile behavior. A file appearing in the editor does not prove that the intended learner can open it.

LearnDash documents a critical compatibility rule: Video Progression, Assignment Uploads, and a Forced Lesson Timer cannot all be enabled on the same lesson; only one can be active. Choose the feature that proves the intended action. Video Progression can gate completion around viewing behavior, assignments can require a file and optional manual approval, and a timer can enforce time on the lesson page. Combining the conceptual requirements in a spreadsheet does not make the settings compatible.

Course and lesson materials need a visibility review. LearnDash states that course materials can be visible to all users, including people who are not enrolled. Course-content-list visibility does not hide WordPress editor content. Treat every course page, materials tab, sample lesson, media URL, transcript, download, and embed as a separate surface. Test while logged out and in a private browser session without relying on an administrator account.

Build quizzes from an assessment contract: purpose, association, question source, allowed types, answer keys, explanations, pass score, time limit, retakes, statistics, feedback, assignment or essay approval, and certificate behavior. LearnDash supports quizzes at topic, lesson, and final-course levels. Verify the association in the Course Builder and the result in the learner path. Quiz statistics and reports should be enabled before evidence is needed; some data is not retroactive.

Certificates require two decisions: create the certificate and associate it with the course, quiz, or approved group path. Test with real QA completion data because dynamic certificate fields depend on the associated context and user record. Confirm spelling, dates, identity fields, eligibility, download behavior, repeat access, and what happens after course or quiz rules change. A visual preview without representative completion data is not launch evidence.

Feature	Evidence it should prove	Compatibility or visibility boundary	Acceptance test
Video Progression	The configured video behavior precedes lesson completion	Cannot share the lesson with Assignment Uploads or Forced Lesson Timer	Early completion is blocked and normal completion succeeds on supported devices
Assignment Uploads	A permitted file is received and approved under the chosen rule	Host upload limits and file types apply; manual approval can hold progress	Allowed, blocked, oversized, repeated, and approval-required files behave as planned
Forced Lesson Timer	The learner remains on the lesson for the required duration	Cannot share the lesson with video progression or assignments	Mark Complete is blocked before time and enabled after the tested duration
Materials and downloads	The correct learner receives the correct current resource	Course materials and editor content can be visible outside enrollment	Logged-out, enrolled, and non-enrolled views plus link and file responses pass
Quiz	Assessment, feedback, pass, retry, and progression decisions	Association and statistics settings determine downstream evidence	Pass, fail, retake, timeout, essay or approval, and result reporting pass
Certificate	Completion or quiz-pass evidence under the approved identity	Must be created and associated with the correct completion source	A QA learner earns the correct dynamic certificate and can retrieve it as intended

Stage 6: external handoffs and agents

Keep LearnDash facts separate from payment, membership, CRM, email, and AI actions

LearnDash should own course structure, enrollment and progress facts under the approved configuration. A checkout owns payment facts. A membership platform may own entitlement. A CRM owns contact and relationship records. An email system owns message delivery. A reporting layer owns defined aggregates. Write those authorities down before connecting them. A tag called `Course Active` is not proof that a user is enrolled, paid, able to log in, or able to reach the first lesson.

When the unresolved architecture question is whether a broad CRM-to-WordPress synchronization layer or a membership-focused access layer should own the connection, use the WP Fusion vs Memberium comparison. Keep this LearnDash checklist as the course setup and launch acceptance owner. After a platform is selected, the LearnDash Access Automation Map owns the source-to-access design. When Memberium and LearnDash are selected but the path has not launched, use the Memberium + LearnDash launch checklist for stack-specific verification of Keap tags, WordPress identity, enrollment, payment, login, and recovery. An existing Memberium path that is already failing belongs to the Memberium and LearnDash access audit.

For every handoff, define the source event, identity key, required source state, target action, idempotency rule, current-state readback, success receipt, retry behavior, reversal, reconciliation, and owner. Cover successful purchase, delayed payment, duplicate webhook, existing WordPress user, changed email, refund, cancellation, membership lapse, manual enrollment, manual removal, and course-version change when those cases apply.

Emails should be consequences of verified states, not substitutes for them. Record who sends registration, purchase, enrollment, welcome, drip, completion, certificate, failure, and support messages. Confirm links, sender identity, unsubscribe or preference behavior where applicable, time zone, duplicate prevention, and the support route. A successful email does not prove access, and a successful enrollment does not prove the learner received a usable login path.

LearnDash 5 documentation describes MCP support for creating, updating, or deleting courses and applying bulk settings through REST API v2 while respecting permissions. That expands the change surface. Use least-privilege credentials, a staging environment, a bounded command, a before-state export or snapshot, human approval, an allowlist of courses and fields, a dry run when available, a change receipt, and representative post-change tests. Do not give an agent unrestricted production authority because the tool can perform a task.

AI-generated outlines need the same boundary. The Course Outline Builder produces lesson titles, not completed instructional content. Do not present generated titles as expert-reviewed curriculum, factual instruction, accessibility evidence, or finished assessment design. Record the prompt purpose and reviewer only when useful; never place private student data, client materials without permission, credentials, API keys, or confidential business records into an AI prompt.

Layer	Authoritative fact	Allowed LearnDash effect	Required evidence
Checkout or payment	Order, transaction, amount, payment, refund, and subscription facts	Grant, hold, extend, or remove enrollment under the approved policy	Source ID, user relation, state, time, effect receipt, and reconciliation
Membership	Entitlement, level, start, grace, cancellation, and expiration	Associate or remove course or group access	Membership ID, user ID, rule version, effect, and exception owner
CRM	Contact identity, consent, relationship, owner, and approved lifecycle facts	Receive enrollment, progress, or completion facts without owning LearnDash state	Stable IDs, field map, timestamp, source, deduplication, and readback
Email	Message template, recipient, send, delivery, and preference evidence	Send a state-backed learner or support communication	Trigger, message key, destination, result, and duplicate suppression
AI outline	Proposed lesson titles only	Create a draft proposal for human review	Approved source outcome, reviewer, revisions, and publication decision
MCP or automation agent	Only the allowlisted operation and approved source data	Bounded staging or production change after approval	Permission scope, before state, command, result, diff, test, and rollback

Stage 7: representative acceptance

Test the learner journey, not only the administrator settings

Use no-private-data QA users that represent the actual paths. At minimum, test a logged-out visitor, a new eligible learner, a returning learner, an enrolled but not-started learner, an in-progress learner, and an administrator or support owner. Add a buyer, group member, subscription member, manually enrolled user, or external-identity case when the live design uses those paths.

Capture the before state, action, expected result, actual result, relevant IDs, timestamps, screenshots without private data, and final state. Verify the public course page, registration or checkout link, account creation, login, enrollment, first step, locked step, scheduled step, quiz, assignment, completion, certificate, email, report, and support route. Check both desktop and a realistic mobile viewport with keyboard navigation and visible focus.

Negative tests matter. Attempt access without enrollment, skip a required step, fail the quiz, upload a blocked file, use an expired or ineligible account, repeat the same purchase or event, arrive from a stale email link, and revisit after completion. Where external systems are connected, test delayed delivery, duplicate events, target outage, retry, and reconciliation. The correct result can be a controlled hold or support case; it should not be an unexplained redirect or silent state mismatch.

Test visibility outside an administrator session. Administrators can be auto-enrolled and can bypass conditions depending on configuration, which makes them poor learner proxies. Use a clean browser profile or private session and a QA learner with the same role and access source as the intended audience. Confirm that unfinished content, materials, direct URLs, quizzes, and certificates are not exposed beyond the approved policy.

Scenario	Expected path	Negative assertion	Evidence to retain
Logged-out visitor	Sees only approved public course, outline, sample, and enrollment content	Cannot reach protected lessons, topics, quizzes, files, or certificates	URLs, viewport, public links, response state, and screenshots
New eligible learner	Registers or is created, enrolls once, logs in, and reaches the first step	No duplicate user, duplicate enrollment, wrong course, or missing login route	Source identity, WordPress user, enrollment, email, and first-step receipt
Progression and release	Completes available steps and reaches the next allowed step at the right time	Cannot skip required content or open future content early	Step IDs, completion times, schedule, time zone, and learner view
Assessment	Pass, fail, retake, feedback, approval, completion, and certificate follow policy	No pass from an invalid answer, missing approval, or stale result	Attempt, score, approval, completion, report, and certificate state
Returning learner	Logs in again, resumes at the correct place, and can retrieve allowed resources	Progress is not lost, duplicated, or attached to another identity	User, course, completed steps, current step, and last activity
Failure and recovery	A delayed, duplicate, failed, expired, cancelled, or revoked case reaches its owner	No duplicate message, orphaned paid learner, or unauthorized continued access	Source state, event, target state, queue/log, repair, and reconciliation
Mobile and keyboard	Navigation, media, quiz, forms, downloads, focus, and completion remain usable	No horizontal overflow, hidden control, focus trap, or unreadable label	Viewport, browser, keyboard path, console, resource, and accessibility results

Stage 8: launch and operation

Reconcile the accepted setup, open enrollment deliberately, and hand off ownership

Reconcile the source inventory against LearnDash before launch. Every approved course, section, lesson, topic, quiz, assignment, material, certificate, and rule should be present once, in the expected hierarchy, under the expected visibility and access policy. Every implemented item should map back to an approved source row or an explicitly accepted deviation. Classify missing, extra, duplicate, stale, wrongly associated, unpublished, unexpectedly public, and unresolved items.

Freeze a release receipt: plugin and theme versions, course ID and URL, enrollment mode, hierarchy snapshot, progression, schedules, integrations, QA identities, tests, known exceptions, approver, operator, support owner, and rollback decision. Open enrollment in a bounded window when possible. Watch registrations, enrollments, first-step access, failed logins, payment or membership handoffs, scheduled content, quiz and assignment queues, completion, email failures, and support cases.

LearnDash reporting can filter by course, user, group, date, and progress state. Decide which indicators matter before launch: eligible users not enrolled, enrolled users unable to begin, not-started versus in-progress, stalled progression, pending assignments or essays, quiz failures, completion, certificate issues, and access contradictions. Reporting is an observation layer; reconcile critical enrollment or payment claims with their authoritative source.

Handoff should let the owner operate the course without reverse engineering the build. Include the source outline, hierarchy, page URLs, enrollment authority, progression and release rules, quiz and certificate settings, integration map, emails, reporting views, support playbook, privacy boundary, change process, backup or rollback location, current exceptions, and next review date. Document which changes require a regression test, especially shared steps, enrollment mode, external integrations, progression, schedules, assessments, and agent permissions.

Operating layer	Reconciliation question	Acceptance rule	Recovery route
Structure	Does every approved source item exist once in the correct hierarchy?	No missing, extra, duplicate, stale, or wrongly associated required step	Correct the smallest item and repeat affected navigation tests
Visibility and access	Can each approved identity see exactly the intended surfaces?	No public leak, orphaned eligible learner, or conflicting access owner	Hold enrollment, restore policy, repair identity, and reconcile users
Progress and assessment	Do completion, schedules, quizzes, assignments, and certificates agree?	Every accepted test has source-backed progress and result evidence	Repair the rule or record; never mass-reset progress without approval
External handoffs	Do payment, membership, CRM, email, and LearnDash states reconcile?	No paid or entitled learner lacks access and no ineligible learner retains it	Use the source event, identity, logs, replay rule, and named owner
Agent changes	Did every AI or MCP action stay inside the approved allowlist?	Diff, permission, human approval, tests, and rollback evidence are complete	Disable the credential, restore the accepted state, and review the full change log
Owner handoff	Can support explain and recover the most likely learner failures?	Current map, evidence locations, escalation, and review date are accessible	Keep launch bounded until ownership and recovery are accepted

Browser-local worksheet

Complete the 32-check LearnDash course setup review

The checkboxes and progress state stay in this browser through local storage. They are not submitted to eArif.com and do not certify a LearnDash installation, course, curriculum, accessibility state, enrollment path, payment, integration, launch, student outcome, or business result. Reset clears the saved state. Print can be used for a privacy-safe review record.

Do not place passwords, license keys, API keys, OpenAI keys, private student records, course exports, payment details, copyrighted client materials without permission, unredacted screenshots, or production access information in this worksheet.

Implementation route

Choose the route that matches the first incomplete layer

Current evidence	Best next route	Why
The outline and assets are ready for one bounded course build	LearnDash Course Structure Setup	LMS-047 retains the `$197` fixed-scope commercial owner for up to ten lessons or topics under its listed inputs and exclusions.
The supplied outline and content are ready, but the selected platform is GoHighLevel rather than WordPress and LearnDash	GoHighLevel Course Setup Starter Pack	GHL-005 retains the `$297` starter scope for one defined GHL course; it does not own LearnDash configuration, community setup, payment-to-access QA, or migration.
The course exists and needs learner-path findings before launch	LearnDash Course Launch QA	The first incomplete layer is acceptance and diagnosis, not content entry.
Question entry, quiz rules, or certificates are the bounded task	LearnDash Quiz Setup Pack	The quiz owner keeps assessment implementation separate from the broader course checklist.
Payment, membership, CRM, group, or email owns enrollment	LearnDash Access Automation Map	The needed deliverable is a source-to-access roadmap before implementation.
A WooCommerce purchase does not produce the expected course access	WooCommerce to LearnDash access guide	The dedicated article owns order, user, enrollment, retry, revocation, and reconciliation diagnosis.
Several systems disagree about payment, identity, access, progress, or messaging	Systems Audit	The problem is cross-tool authority and first-divergence diagnosis.
The scope, owner, or safe starting point remains unclear	Contact Arif with privacy-safe context	Routing can start from the course outline, platform versions, public URLs, redacted screenshots, access source, and first known mismatch without credentials or student data.

Review LearnDash and WordPress LMS Services for the broader service map, LearnDash vs Tutor LMS when platform selection is still open, Proof before treating a public guide as project evidence, Privacy before sharing learner or system context, Learning Cave for adjacent guides, and the AI Search Profile when a search or research agent needs the correct source for Arif's role and service boundaries.

Primary sources reviewed July 30, 2026

Official LearnDash sources used for this checklist

LearnDash 5, course settings, enrollment modes, builder behavior, reports, add-ons, and AI or MCP capabilities can change. Recheck the live official documentation, installed plugin and add-on versions, selected payment or membership documentation, WordPress configuration, and representative learner tests before production work.

LearnDash: Courses for current course structure, shared steps, access, progression, course pages, and LearnDash 5 MCP overview.
LearnDash: Course Builder for sections, lessons, topics, quizzes, ordering, shared steps, and the warning that new builder content is published and Public after saving.
LearnDash: Setting Up Your First Course for the current builder-to-settings-to-preview-and-test path.
LearnDash: Global Course Settings for builder, shared-step, pagination, ordering, and site-wide course configuration.
LearnDash: Course Display and Content Settings for materials, content-list visibility, completion pages, pagination, ordering, and public editor-content boundaries.
LearnDash: Course Enrollment Mode Settings for Open, Free, Buy Now, Recurring, Closed, prerequisites, expiration, dates, cohorts, and external enrollment guidance.
LearnDash: Course Progression for Linear and Free form behavior and the effect of course edits on previously completed learners.
LearnDash: Course Sections for text-only section organization and learner display.
LearnDash: Lesson Access Settings for course association, sample lessons, immediate or scheduled release, and external lesson attendance.
LearnDash: Lesson Display and Content Settings for lesson materials and the mutually exclusive Video Progression, Assignment Uploads, and Forced Lesson Timer settings.
LearnDash: Topics for lesson-topic hierarchy, sample-content differences, schedules, and supported content.
LearnDash: Topic Display and Content Settings for topic materials, assignments, timers, associations, and release schedules.
LearnDash: Global Quiz Settings for builder, shared questions, templates, search, archives, and global quiz behavior.
LearnDash: Quiz Display and Content Settings for quiz materials, autostart, question display, ordering, and title behavior.
LearnDash: Quiz Access and Progression for associations, access, passing, retakes, certificates, and course-progression effects.
LearnDash: Certificates for creating and associating completion or quiz certificates.
LearnDash: Certificate Builder Add-On for dynamic preview, association, QA completion data, and builder behavior.
LearnDash: Reporting for course, user, group, date, progress, activity, export, and support visibility.
LearnDash: User Management for enrollment, progress, completion, quiz evidence, and the boundary around permanent data deletion.
LearnDash: Course Outline Builder for AI-generated lesson-title scope, OpenAI key requirements, and the content, topic, quiz, and assignment exclusions.
LearnDash: General Settings for current template, login, Focus Mode, responsive video, and administrator behavior.

Frequently asked questions

LearnDash course setup and launch questions

What is the correct order for setting up a LearnDash course?

Approve the learner outcome and source outline first. Then define sections, lessons, topics, quizzes, materials, and certificates; select the enrollment authority and mode; configure progression and release rules; build one representative learner path; test visitor, new learner, returning learner, assessment, mobile, and failure cases; reconcile the source against LearnDash; and only then expand or open enrollment. This order exposes access and structure mistakes before bulk content entry.

Should I use Open, Free, Buy Now, Recurring, or Closed enrollment?

Use Open only when public content is intentional, Free when registration without payment is the intended LearnDash path, and Buy Now or Recurring when LearnDash owns the supported payment and enrollment behavior. LearnDash advises using Closed when an external shopping cart or membership plugin manages enrollment. Record one authoritative access owner and test the exact grant, login, expiry, cancellation, and recovery path.

Can LearnDash lessons use video progression, assignments, and a timer together?

No. LearnDash documents that Video Progression, Assignment Uploads, and a Forced Lesson Timer are mutually exclusive on a lesson. Enabling one disables the others. Choose the feature that best proves the intended learner action, then test its completion, failure, mobile, and support behavior. If the course needs several forms of evidence, split the learning actions across approved steps instead of assuming incompatible settings can coexist.

How do I keep unfinished LearnDash content private?

Do not rely only on the Course Builder or an administrator view. LearnDash warns that new lessons, topics, and quizzes created in the builder are published and Public after saving. Course materials and WordPress editor content can also have broader visibility than the course-content list. Use a controlled staging or build-state process, verify direct URLs while logged out and non-enrolled, and test every sample, material, file, quiz, and certificate surface.

Can AI or an MCP agent build a LearnDash course safely?

AI can assist, but capability is not acceptance. LearnDash's Course Outline Builder generates lesson titles only, not lesson content, topics, quizzes, or assignments. LearnDash 5 MCP can perform course-management changes under permissions. Use least privilege, staging, an allowlist, human approval, a before-state snapshot, bounded commands, diffs, change receipts, representative tests, and rollback. Never provide private student data or secrets to an unapproved prompt or agent.

What should I test before launching a LearnDash course?

Test logged-out visibility, registration or checkout, account creation, enrollment, login, first access, progression, locked and scheduled content, media, downloads, quizzes, assignments, completion, certificates, emails, reports, returning learners, mobile and keyboard use, and the support route. Add ineligible, failed, duplicate, delayed, expired, cancelled, revoked, target-outage, retry, and stale-link cases when the design uses external systems.