Test the complete learner path
Use a fresh account to verify discovery, payment or access, content, assignment, submission, feedback, and support.
Online course launch checklist
Check content, payments, policies, quality, learner access, launch communication, retention, and updates before publishing.
Define quality before promotion
A launch cannot compensate for missing evidence, unclear audience, broken mobile content, or inaccessible practice.
Schedule post-launch decisions
Choose when you will review traffic, activation, lesson completion, feedback, support load, and conversion.
Common mistake: launch as a one-day event
The first cohort or purchasers provide evidence that should change the programme and offer.
Interactive planning tool
Plan your course launch
Set a launch date, work through each stage, and keep your progress on this device. Copy or download the dated plan when ready.
0%tasks complete: 0 / 16
Choose a launch date to see the suggested milestones.
COURSE POSITIONING
LEARNING QUALITY
OPERATIONS
LAUNCH
Your entries stay in this browser; they are not saved to your SubSchool account.
Copy, edit, and use
The complete editable template
No email gate. Copy it now or download a Markdown version.
COURSE POSITIONING
[ ] Specific learner and outcome
[ ] Prerequisites and who it is not for
[ ] Clear programme and sample
LEARNING QUALITY
[ ] Objectives and evidence
[ ] Practice and feedback path
[ ] Mobile/accessibility check
[ ] Source/copyright review
OPERATIONS
[ ] Price, tax/payment and refund terms
[ ] Enrolment and access tested
[ ] Support owner and response path
[ ] Analytics events verified
LAUNCH
[ ] Course page QA
[ ] First-lesson path tested
[ ] Email/social/partner plan
[ ] Feedback and update schedule
[ ] Post-launch decision dates: 7 / 30 / 60 / 90 daysSee the blank structure used with fictional data
Every example is labelled, copyable, and keeps learner-facing text separate from private notes.
Example
Completed launch example
Fictional four-week chemistry course
EXAMPLE — FICTIONAL DATA
MUST HAVE BEFORE LAUNCH
[x] Audience, prerequisites, outcome, programme, price, support, refund terms.
[x] Sample lesson and first-lesson access tested with a fresh account.
[x] Original practice, answer expectations, and feedback route reviewed.
[x] Mobile 360–430 px and keyboard checks completed.
CAN WAIT
[ ] Additional bonus module.
[ ] Second promotional video.
[ ] Advanced certificate design.
LEGAL / SOURCE CHECKS
[x] Permission for every PDF, video, image, and quotation.
[x] Current curriculum terminology checked against official sources.
ANALYTICS
[x] Page, CTA, enrolment/purchase, lesson-open, assignment, and feedback events tested without user content.
POST-LAUNCH
Day 7: access failures and support questions.
Day 30: activation, first-lesson progress, feedback load.
Day 60: revisions and retention evidence.Keep the fields that change a real decision
- Must-have list protects the learner path
- Can-wait list prevents polish from blocking quality
- Legal/source checks protect ownership and currency
- Analytics verify decisions, not surveillance
- Post-launch dates turn feedback into updates
Protect privacy and avoid false precision
- User content in analytics
- Unlicensed media
- Unsupported testimonials or outcomes
- Launching without a fresh-account access test
Useful next step
Test the real learner path before publishing
Create the course as a draft, inspect programme and lesson access, then change its course type only when the launch checks pass.
Questions and limits
Common questions
Continue in SubSchool
Turn the page into a real teaching workflow
Check content, payments, policies, quality, learner access, launch communication, retention, and updates before publishing.