How to Storyboard a Video Essay Before You Start Editing

A video-essay storyboard is not a row of polished illustrations. It is a decision document: a way to test the relationship between narration, evidence, visuals, and time before expensive editing begins.

If a collaborator can review the plan and say exactly what should change, the storyboard is doing its job.

What each scene needs

Every scene should answer six questions:

1. What does the narration say? Include the relevant beat, not the entire script.
2. What should the viewer understand? State the scene’s cognitive goal.
3. What appears on screen? Describe the actual composition and sequence.
4. Where does it come from? Record the asset or evidence source.
5. How long does it need? Estimate from comprehension, not aesthetics alone.
6. What happens if the asset fails? Add a fallback approach.

Separate the visual job from the visual object

“A satellite image” is an object. “Orient the viewer to how close the two sites are” is a job.

Writing both prevents a common failure: keeping an attractive asset even when it no longer supports the revised narration. The object can change while the job remains stable.

Storyboard at two levels

Use a two-level structure:

Sequence level

At the sequence level, track the major question, the change in understanding, and the emotional or informational pace. This shows whether the overall argument builds.

Scene level

At the scene level, track exact narration, visuals, assets, rights, timing, captions, and transitions. This shows whether the plan can actually be produced.

The sequence view protects the story. The scene view protects execution.

Use rough frames on purpose

Early frames should be specific but inexpensive. A crop from a source document, a quick diagram, or a labeled placeholder is enough to test the idea.

High-fidelity mockups can make weak decisions feel finished. Delay polish until the visual logic survives review.

Run three review passes

Story pass

• Does each scene move the argument forward?
• Is any necessary context missing?
• Does the ending answer the opening question?

Visual pass

• Does each scene have a clear job?
• Are adjacent scenes visually repetitive?
• Are dense graphics given enough time?

Production pass

• Is every asset obtainable and usable?
• Are sources and rights recorded?
• Is there a fallback for fragile scenes?

Make feedback addressable

Number scenes and keep revisions attached to them. “Scene 7 needs a clearer comparison” is actionable. “The middle feels off” is not.

When the storyboard changes, record what changed and why. That history prevents solved problems from returning during later revisions.

BrollCat treats the storyboard as a review surface rather than a disposable pre-production file. You can inspect the plan, revise individual scenes in conversation, and carry the approved decisions into delivery. Choose a starting direction or begin with your own brief.