Use one storyboard row per visual beat. Put the spoken line beside what must appear on screen, then add a specific review note.
For example: the narrator says “put checked videos in Exports,” the picture shows the file moving, and the review note says “folder name must be readable.” That is enough to give the editor a clear job.
The template below is designed for narrated faceless YouTube Shorts and TikTok videos. It works for real footage, diagrams, or generated visuals. It records what each scene must communicate before you choose how to produce it.
Download the filled storyboard or download the blank CSV. Both open in spreadsheet software.
The seven columns in the template
| Field | What to write | Why it matters |
|---|---|---|
| Scene | A stable scene ID | Connect feedback to one place |
| Timing | A provisional range | Check duration against narration |
| Narration | The exact spoken line | Keep voice and picture aligned |
| Visual | A visible action or comparison | Prevent unrelated background footage |
| Caption | The text viewers need | Reserve space before editing |
| Source | Original, licensed, or cited material | Find the supporting asset again |
| Review | One observable acceptance check | Make approval specific |
Do not add a dozen fields because a production template looks more serious with them. A solo creator needs a board that stays current. Add an owner or due date when another person joins the workflow.
Keep source links separate from a generated image prompt. A prompt explains how you asked for an image; it does not support a historical or scientific claim.
Filled example: stop mixing sources and exports
The filled worksheet uses a file-organization tutorial. Adjust its provisional timings after recording the narration.
| Scene | Narration | Visual | Check |
|---|---|---|---|
| 01 | Which of these files is ready to post? | Three generic file cards with ambiguous names | No real private filenames |
| 02 | Keep source footage in Sources. | Move recording cards into a Sources folder | The folder label is readable |
| 03 | Put checked videos in Exports. | Move one accepted video into Exports | Do not imply a draft is approved |
| 04 | Add a date, topic, and version. | Build one example filename in three parts | Visual and spoken order match |
| 05 | Check the new export before replacing the old one. | Play a revised file, then mark it accepted | Approval happens after review |
You can record a demonstration folder or animate the file cards. Either way, show the correct file entering the correct folder.
If you use a real screen recording, create a clean workspace first. Remove notifications and personal paths. If you use a diagram, make it visibly explanatory rather than presenting it as a screenshot of an actual product.
Write visual instructions that can be checked
“Professional, engaging workspace” is not a scene instruction. It gives a style without saying what viewers should learn.
“Two folders sit side by side. Source recordings move into the left folder; one checked export moves into the right” specifies an action. A reviewer can compare the result with that instruction.
| Item | Weak instruction | Usable instruction |
|---|---|---|
| A concept | Show productivity | Separate source and export files |
| A claim | Show success | Display the cited comparison |
| A process | Make it dynamic | Show the action in order |
| A result | Look satisfying | Identify the accepted file |
For generated assets, request one clear focal action per scene. Accurate text, exact product details, or software controls may need to be added or recorded separately. Inspect the output instead of assuming the prompt's requirements were followed.
Set timing after the voice draft exists
A script line can need longer on screen than it takes to say. Building a filename, locating an item, or comparing two diagrams requires inspection time.
Start with provisional beat lengths. Then play the narration and adjust the visual boundaries. Extend the demonstration when viewers need to see a step. Remove an unnecessary sentence if the scene becomes crowded.
A new scene is useful when the information changes. It is not mandatory every few seconds. A continuous action may be easier to understand without a cut.
For a narration starting point, use the 15-, 30-, and 60-second script templates. Their durations are planning labels too.
Reserve caption space before producing assets
Put the main demonstration where the platform's controls and captions will not obscure it. Keep explanatory labels away from the edges. Preview the actual result in each destination platform.
A storyboard should distinguish a caption that follows the narration from an on-screen label such as “Sources.” They can coexist, but stacking both over the same detail defeats the scene.
The vertical dimensions guide covers framing. The caption guide explains the difference between a caption track and text rendered into the video.
Approve the scene against its row
- 1.LineWhat the narrator says
- 2.VisualWhat proves or explains it
- 3.ExportWhat the viewer receives
- 4.CorrectionUpdate the same scene ID
Give each rejected scene a specific note. “Caption covers the folder name” tells the editor what to fix. “Make this better” creates another interpretation task.
After a correction, review any linked elements. Changing a number in narration can also require a visual and caption update. Keep the accepted export attached to the same episode record.
Reuse the format while changing the lesson
A recurring series can reuse camera framing, typography, and the storyboard fields. Each episode still needs its own evidence, demonstration, and outcome.
ShortsFast's faceless video workflow supports recurring production for YouTube Shorts and TikTok. Keep the CSV open as a planning and review worksheet. It is not an import file for ShortsFast.
Save the template after removing episode-specific content. Keep the filled version beside the video so the next correction has somewhere to go.