An eLearning storyboard template is a screen-by-screen planning sheet for a course. Each screen gets one block that holds its objective, on-screen text, narration, visuals, interaction and feedback. This post gives you the fields, a copyable version and a filled-in example.
There is no file to download. The whole template sits on this page. It suits a small team where a subject-matter expert (SME) supplies the facts and a trainer or instructional designer builds the screens.
Key takeaways
- A storyboard is static and cheap to change. Get content approved there before you build.
- Eleven fields cover most screens, from ID and objective to SME sign-off and status.
- Keep on-screen text short and let the narration carry the full sentences.
- Ask the SME to check facts once per review gate, then freeze approved screens and log later changes on a change list.
What is an eLearning storyboard template and when do you need one?
An eLearning storyboard template is a reusable layout for planning a course one screen at a time. It records the text, audio, visuals, interactions and notes that a developer needs to build each screen. Reviewers approve it before anyone builds.
Three documents are easy to mix up. A script holds only the words. A storyboard adds what the learner sees and does. A prototype is a clickable version of the course. Articulate’s community team, in a post dated April 2015, describes a storyboard as a static document that stakeholders must imagine, and a prototype as an interactive preview. The post and its comments advise getting storyboard sign-off before development, because later changes slow delivery.
In our judgment, write a storyboard first when the main risk is wrong or unclear content. Add a prototype for the one or two screens with complex interactions.
What fields should an eLearning storyboard template include?
A useful eLearning storyboard template has eleven fields per screen: ID, objective, on-screen text, audio script, visuals, interaction, feedback, accessibility note, developer notes, SME sign-off and status. Smaller courses can drop a few. These eleven cover what builders and reviewers usually need in one place.
The list is our own synthesis of fields that published templates describe, plus SME sign-off and status, which we added for review control.
| Field | What goes in it | Rule of thumb |
|---|---|---|
| Screen ID | A unique number such as 2.1 | Never reuse an ID after deleting a screen. |
| Objective | The one objective this screen serves | If a screen serves two, split it. |
| On-screen text | Every word the learner reads, including buttons | Final wording, short phrases. |
| Audio script | The narration, word for word | Write for the ear and read it aloud once. |
| Visuals | What the image or video shows, plus asset name and source | Say what job the visual does. |
| Interaction | What the learner does and what happens next | Name the pattern: click to reveal, drag, single choice. |
| Feedback | Text for correct, incorrect and any hint | Write it now, not at build time. |
| Accessibility note | Alt text, reading order, keyboard action, captions or transcript | Decide it per screen. |
| Developer notes | Timing, branching, tracking | Keep them out of the on-screen text. |
| SME sign-off | Reviewer role and decision | Use set words: approved, approved with changes, not reviewed. |
| Status | Draft, in review or frozen | Only frozen screens go to build. |
What does the copy-and-paste version look like?
Paste this block once per screen, or turn each line into a table column.
Screen ID: [2.1] Module and lesson: [Module 2, Lesson 1] Objective: [Learner will be able to ...] On-screen text: [final wording, including buttons] Audio script: [word for word] Visuals: [description, asset name, source] Interaction: [what the learner does, what happens] Feedback: [correct / incorrect / hint] Accessibility note: [alt text, reading order, keyboard, captions] Developer notes: [timing, branching, tracking] SME sign-off: [role, date, decision] Status: [Draft / In review / Frozen]
Pro tip: Number Screens Like Contracts. Reviewers, translators and developers all need to point at one screen without describing it. A fixed ID lets a comment like “2.3, second button” mean the same thing to everyone, even after you reorder the course.
How do you fill in an eLearning storyboard template step by step?
Fill in the template in this order: objectives, outline, on-screen text, narration, visuals and interaction, then feedback and accessibility notes. This order stops you from writing screens that serve no objective, and it keeps the SME reviewing text instead of debating layout.
Step 1: Write the objectives first
Every screen traces back to an objective. If you have none yet, see our guide on how to write learning objectives, then copy each one into the screens that serve it. A screen with no objective is a candidate for deletion.
Step 2: Outline the modules and screens
List the modules, then the screens, with one job per screen. Our comparison of instructional design models shows how ADDIE, SAM and others differ.
Step 3: Write the on-screen text in final wording
Write exactly what the learner will read, including button labels and instructions. The SME approves what they see here, so a later rewrite reopens the review.
Step 4: Write the audio script
A University of Washington learning-technology page summarizing Richard Mayer’s principles says to avoid putting on screen the same words that are narrated. So put key phrases on screen and let the script carry the sentences. For length, the studio eLearning Art divides voice-over word count by 150 words per minute. Treat that as a planning estimate only.
Step 5: Describe the visuals and the interaction
Reuse a small set of patterns so developers do not invent a new one each time. Our post on reusable interactive eLearning templates lists ten blocks worth building once.
Step 6: Write the feedback and the accessibility note
For every choice, write feedback that says why the answer is right or wrong and what to do next. Then record the alt text, reading order, keyboard action and captions or transcript. The Web Content Accessibility Guidelines (WCAG) 2.2 set a Level A requirement in Success Criterion 1.1.1: non-text content needs a text alternative that serves the equivalent purpose. Purely decorative images should be built so assistive technology can ignore them.
What does a filled-in storyboard look like?
A filled-in storyboard shows short on-screen text, a full narration script, one interaction per screen and written feedback. The example below has two screens from an invented course called “Report a Suspicious Email.” Your own steps would differ, so treat it as an illustration.
| Field | Screen 2.1 (explain) | Screen 2.2 (practice) |
|---|---|---|
| Objective | Identify three warning signs in a suspicious email. | Choose the correct action for a suspicious email. |
| On-screen text | Heading: Three warning signs. Markers: Urgent request. Unknown sender address. Link that does not match its text. | Heading: What would you do? Body: An email from “IT Support” asks you to confirm your password within one hour. Buttons: Reply with my password. Delete it. Report it. |
| Audio script | “Most suspicious emails share a few signs. Look for pressure to act fast. Check the sender’s address, not just the name. Then point at a link to see where it really goes.” | “Read this message. Then pick what you would do.” |
| Visuals | Mock email with three numbered markers (asset: mock-email-01). | Same mock email, no markers. |
| Interaction | Click each marker to reveal a one-line explanation. Continue unlocks after all three. | Single choice, one try. Continue unlocks after the answer. |
| Feedback | None. Explanations appear on click. | Report it: “Yes. Reporting lets the security team check it.” Reply: “Not quite. Never send a password by email. Report it instead.” Delete: “Deleting protects you, but others may get the same email. Report it too.” |
| Accessibility note | Alt text: “Email from IT Support with three warning signs marked.” Markers work with the keyboard. Reading order: email, then markers. Transcript provided. | Choices are real buttons reachable with the Tab key. Test feedback with a screen reader. |
| SME sign-off | Security lead: approved. | Security lead: pending. Confirm reporting steps. |
| Status | Frozen | In review |
How should an SME review and sign off a storyboard?
Send the storyboard to the SME once per review gate, with a clear request: check the facts, check the wording and set the sign-off field. Ask for comments on content, not layout. Freeze approved screens and log later changes on a change list, so one edit does not reopen the whole course.
Our course development process for small training teams suggests one round per gate, plus a short check showing the SME how each comment was handled.
For your own review, Adobe’s eLearning blog published a storyboard review guide in September 2023. Its checklist groups checks into areas, including these:
- Flow and sequencing, from simple to complex, with no gaps.
- Alignment with the learning objectives, including quiz questions.
- Interactivity that is varied and mirrors real situations.
- Accessibility, such as alt text and captions or transcripts.
The full list is in Adobe’s guide to reviewing storyboards.
Pro tip: Label Silence, Do Not Count It as a Yes. If the SME has not reviewed a screen, leave its sign-off as “not reviewed” where everyone can see it. Never treat a missing reply as approval. For safety or regulated content, hold the screen until a person has signed it.
Which format works best: Word, PowerPoint, Google Docs or your authoring tool?
Use the format your reviewers will actually open and comment in. Word and Google Docs suit text-heavy courses, PowerPoint suits layout-first thinking, a spreadsheet suits large courses, and an authoring tool suits small ones. The pairing below is our judgment.
| Format | Works best when | Watch out for |
|---|---|---|
| Word or Google Docs table | Content is text-heavy and several people comment | Layout stays abstract, and file copies multiply |
| PowerPoint or Google Slides | You think in layouts, one slide per screen | Reviewers may edit slide design, not content |
| Spreadsheet | The course has many screens, or you track status and translation | Long text in cells is hard to read |
| Authoring tool directly | The course is small and the team knows the tool | SMEs need access, and changes cost more once screens exist |
When can you skip the storyboard or keep it light?
You can keep a storyboard light for very short courses, or when you build in a tool your reviewers can open. The Articulate post says there is no single right answer. Do not skip it when an SME must approve every fact.
If you are converting a classroom course, the facilitator guide is often your script source, and our post on digitizing a facilitator guide and participant workbook shows which parts become screens.
What should you do next?
Copy the template, then storyboard three screens before you write the rest of the course. Pick one explain screen, one practice screen and the screen with your hardest interaction. Send those three to your SME and note how much they change.
When you are ready to build, you can sign up for SimpliAuthor. Its site shows a “Start Free” button that links to registration, though the pages do not say what the free plan includes. SimpliAuthor is made by SimpliTrain, the same company that publishes this site, so weigh our suggestion accordingly. We have not tested it for this workflow.
As of November 2026, SimpliAuthor’s AI page says its AI can extract objectives from your documents and build a multi-lesson outline that you edit. The same page lists text grids, accordions, interactive media and assessments as editable blocks.
Frequently asked questions
What is the difference between a storyboard and a script?
A script holds only the words, usually the narration. A storyboard holds the script plus everything else that appears on the screen: text, visuals, interactions, feedback, accessibility notes and developer instructions. Many teams write the script inside the storyboard so the SME reviews both together.
Can I use PowerPoint as an eLearning storyboard?
Yes. PowerPoint is a common choice, with one slide per course screen, a sketch of the layout and the script in the notes pane. It works best when layout matters. Tell reviewers to comment on content, because they may otherwise edit slide design.
How many words of narration fit into one minute?
A common planning figure is 150 words per minute, which many voice-over services use for pricing. Divide your spoken word count by 150 to estimate minutes of audio. Pauses and animation timing change the real length, so test a sample before you lock the script.
Should on-screen text match the narration word for word?
Usually not. A summary of Richard Mayer’s principles says to avoid putting on screen the same words that are narrated. Use short phrases, labels and key terms on screen, and let the narration carry the full sentences. Keep exact wording for buttons and instructions.
Who should approve an eLearning storyboard?
An SME should approve the facts, and the project owner should approve scope and flow. Ask for one round per review gate and record each decision in the sign-off field. For safety or regulated content, have someone with the right authority sign the screen before it moves to build.



