How to plan a short two-subject storyboard
A shot plan is an order of observable actions. It helps you decide what happens first, which subject leads and where a later edit could join. It is not a promise that a video model will generate a whole sequence in one request.
Written and documentation checked
1. Give each shot one job
Start by naming the change the viewer should notice: establish the pair, show a response, or settle into an ending. If your sentence contains three unrelated actions, split the planning problem before adding camera motion. A quiet opening can be useful because it gives you a clear comparison point for both subjects.
Original example: in “Call & response”, shot 1 holds both subjects still, shot 2 lets A gesture while B nods, and shot 3 returns them to a neutral pose. The point is a readable exchange; these instructions have not been tested in a video model.
2. Treat time as a planning choice
The workbench allows one to six shots, each from one to fifteen seconds. Those are local editing limits, not a provider’s allowed durations. A seven-second plan made from 2 + 3 + 2 seconds might need separate generations and a video editor. Check the chosen provider before spending credits.
| Beat | Observable task | Review point |
|---|---|---|
| Opening | Both subjects stay on their assigned sides. | Compare the selected references with the opening frame. |
| Exchange | Only one subject leads; the other responds. | Look for overlap or a hand passing over a face. |
| Ending | Return to a simple pose. | Inspect the last frame before planning the next join. |
3. Carry continuity through the joins
Record left/right placement, wardrobe, light, camera height and the position of the microphone. When a later shot needs a new first frame, inspect it as a new input. Do not assume a text description transfers visual identity or the final pose perfectly between independent runs.
A practical join note could be: “Begin with A’s hands lowered, B facing forward, the microphone centered.” This is a visible condition to inspect. It is more useful than writing “seamless” without defining what should match.
4. Keep the plan separate from the evidence
Build the English brief, edit it, then save a named version before changing the shot order. The export includes room for actual model, date, cost, elapsed time and failure notes after an authorized run. Until those fields have real evidence, keep the work labelled as a plan.
If your edited brief differs from current controls, the workbench warns you and keeps your writing. Rebuild only when you want to replace the text, or reconcile the changes manually. Undo restores the previous workspace.
Make this decision in a real plan
Read the complete example Load it in the workbenchSources and limits
Provider documentation supports the input distinctions. Practical checklists and example revisions here are original preparation advice. No real render, user study, success rate or cost result is claimed.