How to write a whiteboard animation script

A strong whiteboard script does two jobs at once. It tells a clear story when heard, and it creates useful opportunities for the canvas to reveal that story. If the narration is written first as a dense article and visuals are added afterward, the animation often becomes a stream of literal icons chasing the voiceover.

Write for speech, scenes, and visual change from the beginning. Scribe Animator gives each scene its own objects, duration, timeline state, camera state, and possible audio relationships, so the script should make those boundaries intentional.

Begin with the promise

Complete this sentence:

After watching, the viewer will understand _____ and be able to _____.

The first blank is the idea; the second is the action. “Learn about expense approvals” is weak. “Understand the three approval checks and submit a complete request” gives the script an observable destination.

Now name the audience and their starting point. A first-time employee needs context that a finance approver does not. Write down terms the audience already knows and terms that need to be introduced visually.

Build a spoken structure

Most short explainers can use five functions without sounding formulaic:

1. Orientation: What situation are we in?
2. Friction: What goes wrong or remains confusing?
3. Model: What is the simplest useful way to understand it?
4. Application: What should the viewer do with that model?
5. Next action: What happens immediately after the video?

These are functions, not mandatory scenes. A complex model may need three scenes; a simple orientation and friction can share one.

Write the first draft as spoken language. Use short clauses, concrete verbs, and one new idea at a time. Read every line aloud. If you repeatedly rephrase a sentence while reading it, revise the sentence on the page rather than hoping the voice artist will rescue it.

Pair every line with a visual change

Create a planning table before opening the editor:

Scene purpose	Narration	Canvas change	Timing note
Name the problem	What the viewer hears	What appears, moves, or remains	Pause, emphasis, or audio cue

The canvas change should communicate, not decorate. “Teams lose time when requests arrive incomplete” does not require drawings for teams, time, requests, and incomplete. One request card stopping before an approval node may express the whole line.

Use visual continuity. If an object represents the request in scene 1, do not change its shape and color in scene 2 without a reason.

A worked Scribe script

The following is a hypothetical example, not a customer story. The goal is to teach employees a three-check expense process.

Scene	Narration draft	Scribe visual direction
The delay	“An expense request slows down when one of three details is missing.”	Draw one request card moving toward an approval circle, then stop it. Reveal three empty check positions.
Check one	“First, attach the receipt that shows what was purchased.”	Reveal a receipt icon and label. Use one accent color for the completed check.
Check two	“Next, choose the project that should carry the cost.”	Add two project branches, then highlight the selected branch.
Check three	“Finally, explain the business purpose in one clear sentence.”	Add a short text line; keep it readable instead of animating every letter.
Result	“With all three checks complete, the request can move to approval.”	Complete the connector to the approval circle. Hold the finished diagram before the call to action.
Next action	“Open the expense form and complete the three checks before you submit.”	Keep the three-check diagram visible and add one concise action label.

Notice what is absent: no invented statistics, no decorative scene unrelated to the task, and no claim that approval will always succeed. The script teaches the controllable part of the workflow.

Write timing that Scribe can support

Do not force a final duration before reading the script. Record a rough narration or read it at a comfortable pace. Mark pauses where the viewer must inspect a completed diagram.

In Scribe, scene duration must cover:

• the spoken line;
• the object's entrance or drawing time;
• reading time after the object is complete;
• camera movement, if any;
• scene-scoped audio; and
• the transition into the next scene.

If a bound audio segment is too short for a comprehensible drawing sequence, fix the script, audio, or scene. Compressing every Draw Step into a burst protects the timestamp but damages the explanation.

The voiceover and synchronization guide explains project versus scene audio, recording, clips, markers, and explicit object binding. The timeline guide explains how presets, property keyframes, and Draw Steps combine.

Give the voice room to sound human

Punctuation is direction. Commas suggest a light separation; full stops allow a thought to land. Use contractions when they match the speaker. Replace parenthetical detail with a second sentence or remove it.

For recording:

• keep names and technical terms consistent;
• add pronunciation notes outside the spoken copy;
• record a clean test before a complete take;
• use headphones to catch background noise and clipped words;
• leave a small clean margin at the beginning and end of each segment; and
• listen against the animation, not only as an audio file.

Music and sound effects should support comprehension. Keep speech intelligible and avoid placing a sound on every visual event.

Common script problems and repairs

The opening explains the company instead of the viewer's problem

Repair: begin with the recognizable situation, then introduce the product or process as the response.

The narration describes everything visible

Repair: let the voice explain meaning while the image shows structure. A label can name a node; the narrator does not need to read every label.

One scene carries several conceptual turns

Repair: split where the question changes. Name scenes by their narrative job and review them in the scene manager.

The script depends on vague claims

Repair: demonstrate a mechanism or remove the claim. If evidence is required, provide a verified source in the publishing context rather than inventing certainty in the animation.

The call to action asks for too much

Repair: choose the next concrete step. “Transform your workflow today” is weaker than “Open the form and complete the three checks.”

Every word receives motion

Repair: reserve Draw Steps, presets, and camera changes for information order. Let finished visuals remain still long enough to be understood.

The final script handoff

Before animation begins, the handoff should contain:

• the audience and promised outcome;
• final spoken copy;
• scene names;
• visual direction for each line;
• required assets and their source;
• pronunciation notes;
• intentional pauses;
• the next action; and
• any factual statement that still needs verification.

Then build a rough project using simple text and shapes before polishing art. The first-animation workflow covers this loop, while text and typography helps keep labels editable until the wording is settled.

Related reading

• Storyboard the script before production
• Plan voiceover and sound design