01 / START HERE
A useful way to approach it.
A written storyboard connects each beat to what the viewer sees and hears. It can expose a missing demonstration or awkward transition before anybody draws a frame. Give each shot a purpose so camera instructions support the story rather than merely adding work.
Draft text from a script and material list you provide. This workflow does not generate frames or analyze unseen footage. The fictional thirty-second example uses authored descriptions and planned durations, not rendered scenes or measured playback.
02 / THE PROCESS
Go from question to next step.
- 01
Start with the story beats
List the question, demonstration, explanation, and resolution your outline needs. Mark any beat requiring evidence rather than an atmospheric image. Supply the script or talking points and known material. If the story depends on a process you have not described, ask for clarification instead of letting the assistant invent the missing action.
- 02
Describe visuals and audio together
For each scene record what is visible, what is heard, and how those elements support the beat. Name spoken text, natural sound, or planned silence when relevant. Keep camera descriptions practical and consistent with your equipment. A close-up can illustrate a detail; it cannot establish a claim the detail does not actually show.
- 03
Check continuity and transitions
Track changes in location, objects, clothing, direction, and sequence that could confuse the viewer. Note the transition into and out of each scene. Ask whether the audience has enough context to understand a new shot.
- 04
Make a feasible shot list
Group shots by location and setup where that helps production, while preserving their story positions in the scene table. Distinguish essential shots from optional coverage. List people, props, permissions, and access needed for each setup. An unavailable shot should lead to a revised plan or a replacement you can genuinely capture.
- 05
Review and revise after capture
Check the proposed table against the brief before filming. Treat durations as planning estimates and leave room for the actual performance or demonstration. After capture, compare the available material with the essential beats and update the edit plan. Written scene descriptions do not prove that the footage exists or that a final cut meets the brief.
03 / YOUR STARTING POINT
A prompt you can make your own.
Replace the bracketed fields. Add only information you have permission to share. This is a reusable text prompt; it does not run a task from this page.
Turn this outline into a written storyboard and shot list: {{outline}}. Message: {{message}}. Available locations, people, props, and equipment: {{resources}}. For each scene show purpose, visual description, audio, planned duration, continuity notes, and required material. Label durations as estimates. Separate essential coverage from optional shots and flag infeasible or missing inputs. Use text descriptions only; do not invent captured footage or claim generated frames. Finish with continuity questions and the minimum shots needed to deliver the stated message.04 / SEE THE SHAPE OF IT
Illustrative thirty-second written storyboard
Fictional shoot and authored scene descriptions. Durations are planning estimates totaling thirty seconds, not actual footage timings.
| Scene / planned time | Visual and audio | Purpose / required material |
|---|---|---|
| Opening / 6 seconds | Wide view; maker names the question | Establish the workspace and topic |
| Detail / 8 seconds | Close view of one shaping step; natural sound | Show the actual step clearly |
| Explanation / 10 seconds | Maker compares two example pieces | Connect the visible detail to the explanation |
| Resolution / 6 seconds | Return to both pieces; brief recap | Resolve the opening question |
The table gives the crew something to inspect before capture: story coverage, audio purpose, and necessary objects. Actual timing will need review in the footage.
05 / KEEP YOUR JUDGMENT
What to watch before you use it.
Filling a table with decorative shots
A scene needs a story or evidence purpose. Remove shots that add production work without helping the viewer understand the message.
Ignoring audio
A visual plan can still fail when dialogue, natural sound, or transitions are missing. Describe what the viewer should hear alongside each scene.
Treating planned timing as measured timing
Use durations to organize the draft, then inspect actual material. Do not claim a cut exists because the written estimates add up.
06 / THE FINAL PASS
A little review goes a long way.
Your checks stay on this page. They do not approve or run a task.
07 / GOOD QUESTIONS
Before you begin.
Is a text storyboard useful without drawings?
Yes. It can clarify scene purpose, required material, audio, and continuity before production. Drawings may add detail later, but written descriptions alone can reveal gaps in the story and help organize a practical shot list.
Does this create storyboard images?
This guide drafts written scene descriptions. It does not promise generated frames or a finished video. If you use a separate image workflow, review its actual outputs and permissions rather than treating the scene table as evidence of generated artwork.
Should the storyboard follow the shoot order?
Keep the scene table in story order so the narrative can be reviewed. A separate shot list can group setups by location or equipment. Retain identifiers connecting both views so efficient production does not lose required story coverage.