The script is where most eLearning projects succeed or fail. A developer who receives a well-structured script will build your course faster, ask fewer questions, and deliver closer to your vision on the first review. A developer who receives bullet points or a PowerPoint deck will spend 30% of the project asking you clarifying questions — and the course will still require more revision rounds than it should. Writing the script well is the single highest-leverage thing an L&D manager can do before briefing any developer.
Why Script First — Not Slides First
Most L&D professionals are trained to think in slides. When asked to produce training content, the default is to open PowerPoint and start making slides. But slides are a visual medium designed for live presentation — they are optimised for what can be shown, not what needs to be said.
eLearning narration should communicate what cannot be shown: the reasoning behind a procedure, the context around a decision, the nuance of a customer interaction. When you script these things first and then design visuals around the script, you get a cohesive course. When you build slides first and script narration over them, you almost always end up reading bullet points aloud — the least effective pattern in eLearning design.
Scripts also serve as a review document. Stakeholder review of a script is faster and cheaper than stakeholder review of a built course. A two-hour review meeting over a script document prevents a three-week development cycle being thrown out because of a factual error or wrong tone on slide 14.
eLearning Script Structure
A professional eLearning script is a table or document with distinct columns for each type of information. At minimum, your script should separate:
| Column | What It Contains | Why It Matters |
|---|---|---|
| Screen / Slide reference | Numbered identifier (Module 1, Screen 03) | Developer navigates by this; also used in review feedback ("Screen 07 narration is wrong") |
| Narration (audio) | What the voiceover says word for word | Goes directly to the recording session; no interpretation required |
| On-screen text | Text displayed visually to the learner | Must NOT repeat the narration — should complement or summarise |
| Visual / interaction notes | What the developer should build: animations, click interactions, images | Without this, the developer makes assumptions — often wrong ones |
| Developer notes | Technical specifications, assets to use, special requirements | Prevents questions; reduces round-trips |
Writing Narration for the Ear
Narration is listened to, not read. Writing that works on the page often sounds unnatural when spoken aloud. These rules separate professional eLearning narration from amateur narration:
Write short sentences
A sentence that is easy to read can be hard to deliver naturally in one breath. If a sentence takes more than 15–18 words to say, break it into two. Read every narration line aloud as you write it — if you trip over it, the voice talent will too.
Use active voice
"The employee completes the form" is clearer and more engaging than "The form is completed by the employee." Passive voice is a common mistake in corporate training writing. Audit your draft for "is/are + past participle" constructions.
Avoid jargon the audience would not use
Write in the language your learners actually use, not the language your subject matter expert uses. If your warehouse staff call it "the pick list" not "the inventory pick document," use "pick list" in the script.
Do not read the on-screen text
If a bullet point is on screen, the learner can read it. The narration should add context, not repeat what is visible. A learner being read to while they read the same words is one of the most common complaints about corporate eLearning.
Use second person ("you") not third person
"You will notice..." is more engaging than "Learners will notice..." This is especially important in scenario-based content — the learner should feel like they are in the situation, not observing it.
Common Script Mistakes That Cause Development Problems
⚠ Combining narration and on-screen text in one column
The developer cannot tell what should be audio and what should be visual. This creates re-work.
⚠ Writing "as shown in the animation" without describing the animation
The developer has to guess what the animation should show. It will be wrong.
⚠ Leaving interaction design vague ("click to reveal")
There are many ways to implement a click-to-reveal. Specify: click on each hotspot to see a tooltip, or click a button to expand a section, or click an image to open a lightbox.
⚠ Not specifying image requirements
"Show an image of a customer service interaction" will get you a stock photo that may or may not match your brand. Specify: "Use a photo from our brand library of a call centre agent with a headset, no busy background."
⚠ Forgetting assessment items
Quiz questions, drag-and-drop items, and scenario questions all need to be scripted with correct answers, distractors, and feedback text. These are often forgotten until the developer asks.
Template
eLearning Script Template
A structured Word document with pre-built columns for narration, on-screen text, visual notes, and developer instructions. Includes example rows and a module header section. Ready to hand to any eLearning developer. Need us to take the script through to a finished course? Book an EQUIP Strategy Session.
Frequently Asked Questions
What is an eLearning script?
A structured document specifying the narration text, on-screen text, interaction descriptions, and visual notes for every screen of an eLearning course. It is the blueprint from which developers build — equivalent to a film script.
How long should an eLearning script be?
Approximately 130–150 words of narration per minute of finished course. A 20-minute course requires ~2,600–3,000 words of narration. The full script document (including on-screen text, notes, and interaction descriptions) will be longer — typically 4,000–6,000 words for a 20-minute course.
Do I need to write the script before briefing a developer?
A complete script is ideal, but many vendors will help with scriptwriting as part of the project. However, briefing with a well-structured script reduces development cost by 20–30%, reduces revision rounds, and significantly improves the quality of the first build. The template above gives you the structure — you provide the content expertise.
Can I use AI to write an eLearning script?
AI tools (ChatGPT, Claude, Gemini) can draft narration text from your bullet points quickly. AI is good for structure, sentence-level clarity, and first drafts. It is not reliable for accuracy on your specific company processes, regulatory requirements, or brand voice — those require human review and editing.
Key Takeaways
A well-structured script separates professional eLearning development from amateur production. Use the column structure above, write for the ear not the page, and always script before you slide. Use the template above to get the structure right from day one — then hand it to any developer with confidence.
Once your script is ready, see our guide on how to outsource eLearning development to brief your vendor correctly and manage the project without surprises.