A storyboard helps you decide what a video needs before you spend time generating clips. It does not need to be a polished drawing. A simple shot list can explain the purpose of each scene, its subject and action, and the information that must remain consistent from one shot to the next.
The prompts in this guide are planning examples, not documented model outputs. For generation instructions, consult your selected model’s official guidance, such as Runway’s text-to-video guide or image-to-video guide. A storyboard organizes the creative task; it does not remove model limitations.
Write the brief in one sentence
Start with the audience and message. “A short video that introduces a quiet lakeside trip” is more usable than “make an impressive video.” The first brief suggests the tone, subject matter, and kind of action that belongs in the sequence.
Choose the publishing format early. A portrait social video and a landscape presentation need different composition decisions. Set the intended ratio in your project notes, then check which settings are supported in the generation tool and editor.
Keep the message small enough to express clearly. A first video does not need to demonstrate every capability of an AI model. A restrained sequence gives you fewer continuity problems and a more obvious review standard. Use the free storyboard builder to keep your brief, shared notes, and individual shot directions together in an editable three-to-six-shot plan.
Assign a purpose to every shot
For the lakeside example, a three-shot plan could be:
- Establish the location: a still lake with early morning mist.
- Show the journey: a small white sailboat crosses the water.
- Close the idea: the boat approaches a quiet wooden dock.
Each shot has a different role. The first establishes place, the second carries motion, and the last gives the sequence an ending. If two shots communicate exactly the same information, consider whether both are necessary.
Record the intended view and action in plain language. You can add camera terminology later if it helps. The essential question is what the viewer should understand by the end of that shot.
Keep continuity in a shared note
A shared continuity note might include the boat’s white sail, the calm water, sunrise lighting, and restrained natural color. Reuse those important details consistently. Do not rely on unrelated prompt wording to preserve the same subject automatically.
Reference images may help where the chosen model supports them, but they also require preparation and usage rights. Check the model’s specific reference behavior. For image-to-video, an input image already defines appearance and composition; motion instructions should work with it rather than repeatedly replacing it in prose.
Keep a list of authorized source assets with each project. If a model or workflow requires a visual reference, make sure the asset is appropriate for that use before treating it as part of your production pipeline.
Turn the shot into a prompt
For the second shot, combine the main subject, action, setting, and camera direction:
A small sailboat with a white sail glides across a still lake at sunrise, leaving a gentle wake. A smooth tracking shot follows from the shore. Cool mist drifts above the water, with soft golden highlights and restrained natural colors.
For the first shot, the boat may not be needed at all:
A wide view of a still lake at sunrise. Thin mist drifts slowly above the water. The camera holds a steady composition, with soft warm highlights against cool morning tones.
The wording changes because the shot’s purpose changes. Do not paste the whole project brief into every prompt. Include the continuity details that matter, then give each shot its own action and composition.
Separate prompts from production settings
Alongside each prompt, store the model, interface, supported aspect ratio, duration, resolution, reference assets, and output version. Technical values belong in the controls of the tool you use. Prompt prose is not a substitute for checking those settings.
Name outputs with a shot ID and revision number, such as lake-shot02-v03. That simple habit makes it easier to compare revisions and prevents an approved clip from being confused with an earlier draft.
If a result fails, decide whether the problem is the prompt, the reference, a supported control, or an unrealistic shot plan. Sometimes splitting a complicated action is more productive than adding more words.
Assemble before over-polishing
Place acceptable clips into a rough timeline early. A shot that looks attractive alone may not connect naturally to its neighbors. Check the sequence’s visual rhythm, changes in framing, and continuity of light and subject.
Review the complete story before spending the remaining budget on small refinements. Then add narration, sound, captions, or a final title if the brief needs them. Use the storyboard worksheet to plan shots and the workflow checklist to review the finished export.