How to plan an online course curriculum, from learning outcome to assessment

An effective online course outline starts with a learner’s observable final performance, then connects the prerequisites, modules, lessons, practice, and assessment needed to reach it. This guide helps course creators, coaches, and training businesses turn a course idea into a production-ready curriculum in an editable document or spreadsheet.

The deliverable is a planning document—not a published course or a folder of finished videos. It should specify what learners will do, how you will prepare them, what acceptable work looks like, and which assets you need to produce. Teachable’s outline guidance describes this relationship among outcomes, modules, teaching content, practice, and learning checks.

What you need before you start

• A course topic and access to subject-matter expertise. You need to identify the work involved, common mistakes, and the foundations a beginner may lack.
• A provisional learner and use case. “Freelancers creating a client-onboarding process” gives you a more useful starting point than “anyone interested in business.”
• An editable document or spreadsheet. Use a course header followed by module and lesson rows. No particular learning management system, or LMS, is required.

The running example is a hypothetical Client Onboarding SOP course for freelance service providers. An SOP is a standard operating procedure: a document specifying how a recurring task is performed. The example and its proposed review criteria illustrate curriculum decisions; they are not an existing offer, tested result, or professional standard.

1. Define the learner, starting point, and course outcome

Create the course header

Start by defining who the course is for and the situation in which they will use it. Record:

1. Intended learner: their role and relevant experience.
2. Current difficulty: a task they cannot yet complete reliably.
3. Entry knowledge and tools: what they must already know or be able to access.
4. Course-provided instruction and resources: what you will teach or supply rather than assume.
5. Scope exclusions: related tasks the course will not cover.

For the hypothetical onboarding course, the learner understands a basic service-delivery workflow and can edit a document. The creator will supply a fictional client brief and project details. Those materials belong in the production plan, not in the entry requirements.

This distinction matters because prior knowledge can support learning when accurate and available, but insufficient or inaccurate knowledge can obstruct it, as Carnegie Mellon’s Eberly Center explains. Flag missing foundations for the module-mapping step instead of silently assuming them.

Write a performance-based course promise

Use this structure: By the end of the course, learners will be able to + observable action + product or performance. Teachable recommends an action followed by a demonstration or end product.

For example: “Given a sample client brief, create a client-onboarding SOP containing an intake checklist, a kickoff agenda, a handoff map, and an exception-handling path.”

That is narrower than “understand client management.” It tells you what the course must prepare learners to produce and excludes unrelated topics such as prospecting or pricing services. If your outcome says only “know” or “understand,” ask what someone would do to make that knowledge visible.

Record the intended offering

Decide provisionally whether the outcome fits a standalone course, a smaller focused course, or instruction combined with coaching. For example, distinguish producing one defined document from receiving ongoing help applying a process to different clients. This is an offering-design decision, not a requirement to buy a platform subscription.

Save the header, including a working title and, if useful, a short description. You are ready to continue when another person can identify the intended learner, required starting knowledge, scope, and final observable performance.

2. Specify acceptable performance and optional baseline checks

Define the final demonstration and criteria

Decide what will count as evidence of the course outcome before choosing teaching formats. Carnegie Mellon’s assessment guidance distinguishes tasks that reveal recall, application, evaluation, and creation. If you promise creation, learners need to create something—not merely identify its definition.

1. Copy the outcome from your course header into a final-demonstration field.
2. Describe the task conditions: the materials learners receive and the work they must submit or perform.
3. List the criteria you will use to review that work. A rubric is simply an organized set of such criteria.
4. Check whether every criterion is within the promised scope. Flag any additional skill that needs instruction later.

For the hypothetical SOP course, the final task is to assemble the onboarding document from the sample brief and revise it after a missing-information scenario. Proposed criteria could require:

• All required client inputs have a source or a follow-up question.
• Responsibilities and handoff recipients are named.
• Steps appear in a usable order with clear completion conditions.
• Missing information triggers an explicit response rather than an unexplained stop.

These are proposed design criteria, not an industry standard. A factual quiz about SOP terminology could support foundational knowledge, but it would not demonstrate the ability to produce this document.

Decide whether a baseline check is useful

Pre-course and post-course checks are optional in Teachable’s guidance. Record either “No baseline check planned” or the purpose and type of an optional check:

• Performance sample: shows what the learner can currently produce or execute.
• Knowledge check: reveals relevant factual or conceptual knowledge.
• Confidence question: records perceived readiness.
• Combination: captures these separately for different purposes.

For example, “How confident are you in designing an onboarding process?” asks about confidence. It does not supply the SOP required by a creation objective. Keep those results separate.

If you plan a before/after comparison, name the comparable task or questions and the criteria used at both points. A change can describe the difference between those observations; change alone does not prove the course caused it.

Save the final task, review criteria, and diagnostic decision. If your only evidence is recall but your promise requires application or creation, replace or supplement the check now.

3. Map prerequisite skills into sequenced modules

Separate entry skills from skills you will teach

Break the final performance into its component skills—the smaller capabilities needed to complete the whole task. Use subject-matter expertise to identify both visible actions and decisions an expert may take for granted.

1. List the skills needed for the final demonstration.
2. Mark each as entry requirement, required course skill, or supplementary material.
3. For each required skill, record what learners must already be able to do before attempting it.
4. Where prior knowledge may be inaccurate, plan an explanation or check that brings the relevant foundation into use.

For the onboarding example, document editing is an entry skill. Extracting client inputs, designing a kickoff, mapping responsibilities, and handling missing information are course skills. A broader discussion of growing a freelance business would sit outside the required path.

Order dependencies before assigning a calendar

Arrange foundations before work that uses them, then group related skills into modules with clear milestones. Carnegie Mellon’s learning principles distinguish acquiring component skills, practicing their integration, and knowing when to apply them. Separate pieces are not enough if learners never practice combining them.

A useful sequence for the example is:

1. Extract intake requirements from the brief.
2. Use those requirements to design the kickoff.
3. Map the handoffs needed to carry out the work.
4. Assemble and test the complete SOP, including an exception scenario.

Make each module’s contribution to the final outcome explicit. Udemy generally recommends one objective per section; OpenLearning also describes modules combining outcomes. The practical requirement is a clear relationship, not an inflexible one-objective rule.

Now assign provisional pacing. If you have a fixed delivery window, test whether the necessary sequence fits it. If not, narrow the promise or reconsider the window rather than removing essential foundations. If timing is flexible, derive the schedule from the required work. Teachable allows either timeframe-first or topic-first planning; its five-week illustration is not a universal module quota.

Save the ordered modules and dependencies. Correct any task that uses an untaught skill, add integration practice where components remain disconnected, and move unrelated material out of the required path.

4. Write measurable module objectives and focused lessons

Turn milestones into observable objectives

For each module, complete: Learners will be able to + action verb + product or performance. Use verbs such as draft, compare, implement, review, or assemble when they accurately describe the required work. This follows Teachable’s objective-writing formula.

For the kickoff module, “understand kickoff meetings” becomes “turn the sample intake information into a kickoff agenda covering scope, responsibilities, unresolved questions, and next actions.” The second version tells you what instruction must support and what the learner can check.

Write the objective into the outline before splitting it into lessons. If a module has several objectives, identify the lesson or activity supporting each one.

Give each lesson a focused contribution

1. Identify the explanations, demonstrations, and decisions learners need to achieve the module objective.
2. Split them into focused lessons rather than choosing a fixed lesson count.
3. Give each lesson a descriptive label and a one-sentence takeaway.
4. Check that the lesson advances its module objective.

For example, a kickoff module might distinguish extracting agenda decisions from writing actionable next steps. A label such as “Assign owners and next actions” is easier to revisit than “Lesson 2.” Udemy emphasizes focused lectures and findable labels so returning learners can locate a particular skill.

If a lesson contains several independent concepts, split it where doing so improves navigation and practice. If an objective has no supporting lesson, add the instruction or revise the objective.

Add a beginning and an ending

Plan orientation that states the outcome, explains entry requirements and expectations, introduces the instructor’s relevant expertise, and tells learners how to navigate the course. Include any foundations they need and, where useful, an early activity. In the example, learners could inspect the sample brief and identify unresolved inputs.

Plan a final lesson that summarizes the key skills, thanks learners, and encourages application beyond the sample scenario. Udemy recommends an introduction, practice-rich middle, and conclusion. A promotional bonus lecture is optional and platform-dependent, not part of the required curriculum.

Save the module objectives and lesson rows. Every lesson should now have a clear contribution, even though its finished teaching materials have not yet been produced.

5. Select teaching formats, practice, and resources

Choose formats for the teaching job

Choose the medium that makes the explanation, demonstration, or working aid useful. Teachable describes five common content types, and a lesson can use one or combine several:

• Text and images: use for explanations, annotated examples, and references learners may need to scan again. A multistep task can still use text when the sequence is clear.
• PDFs and downloadables: use checklists, spreadsheets, workbooks, templates, or reference sheets when learners need something to complete or reuse. A bare checklist may need additional explanation if the decisions behind it are complex.
• Slides: use for a structured visual explanation that emphasizes one point at a time.
• Screencasts: record a screen or narrated slide walkthrough when learners need to see an on-screen procedure and the reasoning behind it.
• Camera video: use direct explanation or a physical demonstration when seeing the instructor or the work adds value. An appropriate existing webinar or event recording may be reusable if it serves the lesson objective.

Combine formats for distinct purposes—for example, an agenda walkthrough plus an editable agenda template—not merely to add variety.

Do not assign formats to fixed “visual,” “auditory,” or “kinesthetic” learner categories. The Education Endowment Foundation’s school-focused synthesis rates evidence for learning-style approaches as extremely low and warns against restrictive labels. That review does not quantify adult commercial-course effects. For this outline, base format decisions on the task and the learner’s access needs instead.

Attach practice outputs and resource requirements

For every lesson row:

1. Record the teaching format and why it fits.
2. Add an action in which learners perform the target skill.
3. Name the resulting output, such as an intake checklist or revised agenda.
4. List the examples, files, and tools needed for that action.
5. Mark resources as required or optional, and identify whether the learner supplies them or you must produce them.

Watching someone build an agenda is instruction; building an agenda is practice. Both may belong in the same lesson, but they do different jobs. Udemy’s outline guidance pairs teaching with practice and reference materials.

For the onboarding course, list the sample brief, complete and incomplete examples, agenda template, handoff worksheet, worked SOP, and missing-information scenario as planned course assets. Deeper reading can remain optional. Do not make an essential task depend on an unlisted file.

Use Podia’s video as a planning companion

In its English-language creator video, Podia advises keeping the outcome manageable, turning milestones into modules and lessons, and choosing formats according to whether they help deliver that outcome. Use it to revisit scope and format choices before committing to production.

Save the lesson rows with formats, practice outputs, and resources. A skill objective supported only by passive viewing still needs an application task.

6. Plan aligned assessments, feedback, and reflection

Match each check to the objective’s action

Use the final-demonstration criteria from step 2 to plan learning checks throughout the course. Practice gives learners a chance to develop the skill; assessment supplies evidence of where their performance stands. One task may serve both purposes when learners receive feedback and revise.

1. Read the action in each objective.
2. Select a task that makes that action visible.
3. Record the output and the criteria used to review it.
4. Check that instruction and practice prepare learners for the same demand.

Carnegie Mellon’s alignment guidance supports these distinctions:

• Recognize or identify: use suitable matching, labeling, or multiple-choice questions.
• Explain or compare: require an explanation, comparison, classification, or other response showing the relationship.
• Apply or implement: require execution of a procedure or a simulation.
• Evaluate or critique: require judgment against stated criteria.
• Create or design: require a product or performance.

For the SOP course, review the component artifacts as learners build them, then assess the integrated SOP. If the final task requires handling missing information, learners need relevant instruction and scenario practice before that check. A summary-only lesson cannot prepare them for an unpracticed critique task.

Specify feedback and an opportunity to revise

Record who or what supplies feedback: instructor review, peer review against criteria, or structured learner self-review. Specify when it arrives and what learners do next. Carnegie Mellon connects useful feedback to target criteria and timing that allows learners to act on it.

For example, replace “Improve the handoff map” with “The review handoff names an owner but no recipient; add the recipient and state what makes the handoff complete.” Then plan a revision before the learner assembles the final SOP.

Formal grading is optional for this planning method. A self-review can serve its purpose when the criteria and expected work are clear; “looks good” cannot explain a gap or guide an improvement.

Add reflection and optional post-course checks

Use reflection when it helps learners monitor their decisions: “Which input was missing, what did you change, and why?” Reflection complements the SOP; it does not replace producing it.

If you selected optional pre/post checks, add the comparable end task or questions and their timing now. A survey can collect confidence or knowledge responses, while a performance task requires the relevant work. Keep these result types separate.

Save an assessment, review method, and revision opportunity for each objective. Check that no creation objective relies only on reflection and that feedback identifies both a criterion and a useful next action.

7. Audit alignment, workload, and production readiness

Read the outline across, not just down

A plausible list of modules can still contain gaps. Audit each row as objective → assessment → practice → explanation and resources, using Carnegie Mellon’s alignment questions.

1. Confirm that every promised outcome has an observable assessment.
2. Confirm that every assessed skill has supporting instruction and practice.
3. Check that prerequisites are taught earlier or explicitly disclosed at entry.
4. Check that each required lesson contributes to a promised outcome.
5. Confirm that required examples and files are either learner prerequisites or planned production assets.
6. Label optional diagnostics and supplementary references consistently.

Correct the gaps before signing off. An assessment requiring untaught work needs revised instruction or a revised assessment. Material unrelated to the promise belongs outside the required path. An essential resource with no stated source belongs in the production inventory.

Estimate total learner effort

Estimate more than video runtime. Vermont State University’s teaching center includes reading, writing, media, discussion, exams, assignments, and meetings in workload estimation. Its academic credit-hour framework does not set a required duration for a noncredit commercial course.

For each lesson, record estimated time for:

• Reading, viewing, or listening.
• Practice, writing, and assignments.
• Assessment and revision.
• Discussion and meetings, when included.

Keep categories distinct so you do not count the same activity twice. Add the applicable categories to estimate module effort, then compare that effort with your intended pace. Label the figures as planning assumptions, not measured completion times. A short demonstration can accompany a substantial production task; do not equate the two.

Save the production-ready plan

Maintain production effort separately from learner effort. For each asset, identify what must be made, who is responsible if a team is involved, and its status—for example, planned, drafted, or ready. A production-ready outline can include uncreated assets, but it must identify them clearly enough to guide the work.

Save the completed header, ordered modules, lesson rows, criteria, workload assumptions, and production inventory. The plan is ready when there is no unexplained dependency, unpracticed assessment demand, or essential resource missing from the inventory.

In Teachable’s terminology, the outline primarily serves course design, while a syllabus communicates the course to learners. You can derive that student-facing document from the outline by adding expectations, requirements, assignment information, dates where applicable, grading details if used, and relevant conduct rules. Producing the teaching assets, uploading them to an LMS, and publishing the course are subsequent tasks—not evidence that this planning step is complete.

Worked example and reusable planning template

Hypothetical course: Client Onboarding SOP

This proposed course is for freelance service providers who understand their service workflow and can edit a document. The creator supplies the fictional brief, project details, templates, and examples. The final artifact is an onboarding SOP covering intake, kickoff, handoff, and exceptions.

The design applies Carnegie Mellon’s component-skill and integration principles and assessment-alignment guidance. All criteria in the table are hypothetical design choices, not validated standards.

Module	Observable objective	Lessons and format	Practice output	Success criteria
Define intake requirements	Extract the information needed to start the sample project	Read an annotated brief; compare complete and incomplete intake examples	Intake checklist	Each required input has a source or a follow-up question
Design the kickoff	Turn intake information into an actionable kickoff agenda	Watch a narrated agenda walkthrough; edit an agenda template	Kickoff agenda	Agenda covers scope, responsibilities, unresolved questions, and next actions
Map the handoff	Specify who supplies, reviews, and receives each deliverable	Study a visual workflow; complete a handoff worksheet	Handoff map	Each handoff has an owner, recipient, and stated completion condition
Integrate and test the SOP	Assemble the components and revise the process after a missing-information scenario	Review a worked SOP; run a scenario and explain revisions	Complete SOP and revision note	The process remains usable when an input is missing, and its components are consistent

The outputs accumulate rather than becoming disconnected exercises. The intake checklist informs the kickoff, the handoff map clarifies responsibilities, and the final scenario tests whether the combined process works when information is incomplete. That integration task should not introduce a new skill learners have never practiced.

The proposed final review also exposes a common design mistake: a quiz defining an SOP would leave the course’s creation promise unassessed. The artifact and scenario are the relevant evidence; reflection explains decisions made while producing them.

Reusable course outline fields

Copy these fields into your own document or spreadsheet. Their purpose is to keep the teaching plan, learner work, and production requirements connected.

Course header

• Working title and short description.
• Intended learner, use case, and current difficulty.
• Entry knowledge and required tools, separated from course-provided materials.
• Observable final outcome and scope exclusions.
• Final demonstration, task conditions, and acceptable-performance criteria.
• Offering, delivery, and pacing assumptions.
• Optional baseline/post-course check plan, or an explicit decision not to include one.

Repeat for each lesson

• Module and lesson identifier, descriptive title, and prerequisite or earlier lesson.
• Observable objective and focused lesson takeaway.
• Teaching format and required example or resource.
• Practice task and resulting output.
• Assessment task, review criteria, and feedback or self-review method.
• Revision opportunity and reflection prompt, where useful.
• Estimated reading/viewing time, doing time, and assessment/revision time.
• Discussion or meeting time, where applicable.
• Required or optional designation.
• Production asset, responsible person where relevant, and status.

Final handoff check: someone using the saved outline should be able to identify what to produce, why it belongs, what learners will do with it, and how the promised performance will be checked. If any of those answers depends on an unstated assumption, resolve it in the corresponding row before production begins.