What the template should help you decide
A storyboard is useful when it resolves design decisions before expensive authoring begins. It should show what the learner sees, does and receives as feedback—not merely copy the source document into rows.
Recommended storyboard fields
| Field | Purpose |
|---|---|
| Screen/section | Unique reference for review |
| Learning purpose | Why this part exists |
| On-screen copy | Final or near-final learner text |
| Visual/media | Image, diagram, video or layout direction |
| Learner action | Click, choose, practise, reflect or navigate |
| Feedback | What happens after the action |
| Accessibility | Alt text, captions, keyboard/reading-order notes |
| SME/reviewer notes | Open questions and approvals |
Copy this simple template
Screen ID:
Learning purpose:
On-screen content:
Visual/media direction:
Learner action:
Feedback/consequence:
Accessibility notes:
Tracking/assessment notes:
Reviewer questions:
Status:Worked example: handling a customer complaint
Learning purpose: practise choosing the first response to an upset customer.
On-screen content: “A customer says they were charged twice and demands an immediate refund. What do you do first?”
Action: choose from three realistic responses.
Feedback: explain the consequence of each response, then allow a retry. Do not reveal the correct answer before the learner commits.
Accessibility: choices work by keyboard; feedback is announced in reading order; any customer image is decorative unless it carries information.
Use the storyboard to improve SME review
Ask reviewers to check accuracy, realism and consequences rather than redesigning fonts or button colours. Give each screen an ID so feedback is traceable. Resolve policy disagreements before building the interaction.
How detailed should it be?
Use more detail for branching scenarios, regulated content, voiceover, animation or multi-reviewer projects. Use less for straightforward pages where the authoring tool itself is faster than documenting every layout decision.
The storyboard is a coordination tool, not a bureaucratic requirement.
Storyboard-to-authoring checklist
- Outcomes and assessment are aligned
- Every section has a purpose
- Copy has been edited for screens
- Interactions specify feedback
- Media requirements are clear
- Accessibility is designed in
- SME questions are resolved
- Tracking requirements are known
For the full method, read how to storyboard an eLearning course.
Put the guidance into practice
Build a real course in Lumeo, preview it in the browser, and export it to SCORM, standalone HTML or PDF. The free plan does not require a payment card.