Course outline generator

A syllabus, an outline and a lesson plan are three different documents

A syllabus is the version you hand to learners: what the course covers, what is expected of them, when it runs and how they will be assessed. An outline is the spine you build from: the sequence of modules, what each one is for, and how each depends on the ones before it. It is written for whoever designs and delivers the course, not for the audience.

A lesson plan sits below both, covering one session, timed, with the materials on the table and the questions you intend to ask. Gagne's nine events of instruction belong at that level: gain attention, recall prior learning, present the material, provide guidance, elicit performance, give feedback, assess, and support transfer back to the job. Stretched across a twelve-session course, that shape produces a document that is neither an outline nor a plan.

Build them in that order, because the outline is where expensive mistakes are still cheap. Moving module four ahead of module two is a two-minute edit now and a week of rework once the slides exist.

• Outline: module sequence, the purpose of each module, the dependencies, and where assessment sits
• Syllabus: scope, prerequisites, schedule, expectations, and how sign-off or marks work
• Lesson plan: one session, minute by minute, with facilitator notes, materials and questions

Sequence by prerequisite, not by topic tidiness

The most common failure in a self-built outline is an order that is logical on the page and unusable in the room. Topics get grouped because they belong to the same family, all the theory together and all the tooling together, rather than because a learner needs one to attempt the next. That produces three sessions of foundations before anybody does anything, and the drop-off gets blamed on engagement.

A more reliable method: for each module, write the single thing a learner must already be able to do before they can start it. That line is the dependency. Order the modules so every dependency is satisfied by something earlier, and where two have no dependency between them, order those by difficulty or by how soon the skill is needed at work. That is the analysis half of ADDIE doing real work rather than being a diagram in a deck.

Then break the tidiness once, deliberately. One self-contained, useful skill in the first session, something a learner can use that afternoon, buys the attention the foundations need. The 70-20-10 model is the corrective: most capability is built by doing the job, so the course exists to make the between-session work possible.

Chunk sessions so working memory can keep up

Cognitive load theory makes one prediction that matters directly for an outline: what limits a novice is not the total volume of material but how many interacting pieces they must hold at once to make sense of a single step. Something an expert states in one clause, reconcile the ledger, is six interacting elements for the person learning it. Splitting that across two sessions is not padding, it is the difference between following and drowning.

So each session should carry one capability and two or three new concepts, with the rest of the time spent on practice and feedback rather than fresh input. Where a module looks heavy, the fix is to move one sub-skill into its own session, not to talk faster. The constraint relaxes as fluency grows: worked examples that help a beginner start to slow an experienced learner down, so later sessions can shift towards problems with thinner scaffolding.

• One capability per session, written as something the learner can do by the end
• Two or three new concepts, not eight; the rest is practice and feedback
• Fully worked examples early, thinner scaffolding later as fluency builds
• Checklists, syntax and policy detail belong in a handout, not in the session

Space the practice, and make them retrieve it

A multi-session course has one advantage a single workshop cannot buy: gaps. Two effects with a long history in cognitive psychology depend on them. The spacing effect is that material revisited after a delay is retained more durably than the same total time massed into one sitting. The testing effect is that recalling something from memory strengthens it more than reviewing does. Both are scheduling decisions, so they belong in the outline.

Open each session by having learners retrieve the last one rather than recapping it yourself: three questions answered from memory before anyone opens their notes, or a short task applying last week's skill to a new example. Then plan for that skill to reappear two or three sessions later, embedded in a larger task rather than reviewed as a block. Once several problem types are on the table, mixing them rather than drilling one at a time feels harder in the room and holds up better afterwards.

• Open every session with retrieval, not recap: they answer, you do not re-present
• Re-use each earlier skill inside a later task, not as a standalone review slot
• Between-session work should apply the skill to the learner's real work

Design the assessment before the content

A quiz bolted onto a finished course tests whatever happened to be memorable. Backward design reverses the order: decide what a learner should be able to do, decide what evidence would convince you they can, then plan the sessions that get them there. Writing the final assessment first usually exposes two or three modules nobody can justify keeping.

Bloom's taxonomy earns its keep as a check on verbs. If an objective says understand, it cannot be assessed, and the honest follow-up is what the learner would be doing if they did: describing, comparing, diagnosing, designing. Early modules can sit at recall; later ones should climb, and a final module that still asks people to list things has not travelled anywhere. SMART objectives fix the condition and the standard: not improve at code review, but review a 200-line pull request and identify both seeded defects within thirty minutes.

Apply Kirkpatrick's four levels honestly rather than completely. Reaction and learning are measurable inside the course's own timetable. Behaviour change is level three, happens back at the desk, and needs a check-in date set weeks after the final session or nobody looks. Results at level four usually need someone other than the trainer to own the number.

What the generator gives you, and what it leaves to you

Describe the subject, the learners and how long you have, and you get a structured outline in about twenty seconds: SMART objectives for the course, three to five modules scaled to the duration, each with its lessons, activities and exercises, and a set of assessment methods. The controls above start at a four-week course for an intermediate technical audience, and you can change format, type, level and duration before generating.

What comes back is a first draft with an argument in it: a sequence, a distribution of practice, and an assessment approach you can accept or overrule. It is not a lesson plan, and it does not know your organisation. Expect to reorder a module once you check the dependencies against your real audience, and to swap an activity for one you already run well. On Premium you edit the plan in place and export to PDF or Word; the free plan covers one saved plan, copy and print.

Common questions

What is the difference between a course outline and a syllabus?

An outline is the structural spine you build from: the module sequence, the purpose of each module, and how they depend on one another. A syllabus is the version you hand to learners, covering scope, schedule, prerequisites and how they will be assessed. Write the outline first, because once the sequence is settled the syllabus is largely a reformatting of it.

How many modules should a multi-session course have?

The generator returns three to five modules scaled to the duration you set, each with two to four lessons, one to three activities and one to two exercises. For a four-week course that usually maps to roughly one module a week. If your subject genuinely needs more than five, it is normally two courses rather than one long one.

Can I generate a course outline without creating an account?

Yes. The generator on this page works for signed-out visitors and returns the full set of objectives plus the complete first module, with the remaining modules shown as titles only. Signed-out previews are limited to three a day. A free account shows every module in full and saves the plan to your dashboard.

Does it produce lesson plans as well as the outline?

Not at the level a facilitator can run from. Each module comes back with its lessons, activities and exercises named, which is the layer directly above a lesson plan, so you still add timings, facilitator notes, materials and the questions you intend to ask. Most people use the outline to settle the sequence, then write session plans for the first two or three sessions they deliver.

Can I edit the outline after it is generated?

Editing a plan in place is a Premium feature at $19 a month, which also includes unlimited plans and PDF and Word export. On a free account you can generate and save one plan, copy the entire outline to your clipboard and print it, so you can always move the text into your own document and edit it there.

Can I export the outline to PDF or Word?

Premium accounts can export any plan as a PDF or as a Word document. Copying to the clipboard and printing are available on every account, including the free one. There is no SCORM or LMS package export, so an outline destined for an LMS has to be moved across by hand.

Does this work for academic courses or only workplace training?

It works for any multi-session subject you can describe, and the structure it produces, sequenced modules with objectives and assessment methods, is the same one educators use. It is built around workplace capability rather than academic accreditation, so it will not generate credit hours, institution-specific marking rubrics or reading lists.