Write a short video script you can actually produce
A useful script names what is said and what is shown. Write those together before recording or generating the video.
A short social video script should describe both the spoken message and the visible action. Start with one viewer question, show the relevant evidence and end with a next step the viewer can take. Write for the footage you can make rather than a duration you cannot fill meaningfully.
You can write the script yourself or develop it with Copilot in Blitz. The output is a production brief until its words, shots and media are finished.
Start with a visible problem
For a product-photo tool, a useful opening might be: “The photo is sharp, but the background distracts from the product.” Show that actual photo while saying it.
“Do you want to transform your business?” gives neither the viewer nor the camera a specific task. Replace broad stakes with the object, situation or result you can show.
Pair each line with a shot
Here is an illustrative script structure:
| Part | Spoken line | What to show |
|---|---|---|
| Opening | “This background hides the product’s edge.” | Original product photo |
| Action | “Remove it, then inspect the fine details.” | Real editing step and edge close-up |
| Check | “Place the export on a different background.” | Actual exported image on a plain surface |
| Ending | “Try the same check before your next listing.” | Checked result and relevant destination |
This is a sequence, not a claim that every video should use these exact lines. If your product needs a different proof, change the shots before polishing the wording.
Separate narration from on-screen text
Use narration to explain the action. On-screen text can name a step or draw attention to a detail. It does not need to repeat every word unless it is serving as captions.
Read the script aloud with natural pauses. When it runs too long, remove an idea or split the post; speeding up the voice can make an already dense explanation harder to understand.
Choose how the video will be produced
- Screen recording: for exact interface actions and real product results.
- Faceless video: for narration supported by relevant stock clips and captions.
- Generated clip: for a short illustrative scene or movement that supports the concept.
A Seedance clip duration is not the length of a complete narrated tutorial. Decide which part is generated and which part still needs recording or editing. A carousel may be simpler when the reader needs to inspect several facts.
Give the assistant the production constraints
Write a short script about [question] for [viewer]. Use only these product facts: [facts]. I have these assets: [assets]. For each beat, provide the spoken line and a shot I can make with those assets. Keep the final action tied to [destination]. Ask about missing evidence before inventing a scene.
In Atelier, finish the selected short script before rendering or deriving a week. The opening, individual beats and closing line should be usable copy, not instructions to a future writer.
Review the completed video against the script
Watch the export and check each promised action. Listen for missing words, confirm that captions match and inspect the real product details. A technically successful render can still tell the wrong story. Save the version that passes review before choosing an account or publishing date.
Practical guides from the makers of Blitz Planner. Product examples describe the current workflow; examples and prompts are illustrative.