The template
Turn a product workflow into a concise scene-by-scene script with on-screen and spoken copy.
Use this scene sequence as an editable outline. Replace sample wording with verified details; the sequence is a planning aid, not a fixed duration or a platform specification.
| Beat | On screen | Narration | Review check |
|---|---|---|---|
| 1. Viewer question | Show the situation that prompts the task. | Ask the question the workflow answers. | Does it match the target audience? |
| 2. Starting state | Show the screen before any action. | Name any prerequisite briefly. | Are labels and permissions accurate? |
| 3. Main action | Demonstrate the core product steps. | Explain why each step is needed. | Can every spoken claim be verified? |
| 4. Visible outcome | Reveal the completed dashboard or task state. | State only the result the screen supports. | Does the result follow from the actions? |
| 5. Next action | Show where a viewer can continue. | Give one relevant next step. | Does the CTA match current access? |
How to fill it in
- Hook: state the viewer's problem or the outcome they want.
- Context: show only the setup the viewer needs to understand the workflow.
- Main action: focus on one or two meaningful product steps.
- Outcome: show what changed, using only claims you can support.
- Next step: give viewers one specific action to take.
Customize it for your audience
Write for one viewer and one task. Put the starting state and prerequisites in the script before drafting voiceover, then pair every instruction with a visible action or result. Use narration for reasons and decisions, while captions reinforce only key terms or accessibility needs. Mark uncertain product behavior as a question for the product owner instead of writing it as fact. Read the script aloud against the scene list: if a sentence runs beyond the screen action, shorten it or split the scene. Keep optional routes in a separate version or help link.
Prepare the final handoff
Give production a script that identifies the exact screen, action, spoken line and caption for every scene. Mark sample records and unresolved product questions, and attach the reference build or screenshots used to verify behavior. This handoff lets an editor spot a changed interface without interpreting the script as a substitute for the product source.
Production and approval checklist
Before recording or animation, confirm the viewer, destination, desired next action and product version. Replace every illustrative name, number and screen with approved material, or label it as sample content. Check that each scene advances the story and that voiceover fits the time available on screen. Review the draft once for product accuracy, once for audience comprehension and once for permissions, accessibility and destination requirements. Make the final reviewer and approval date explicit; recheck volatile facts such as pricing, availability, release status, event details and platform rules just before publishing. Keep the script, source assets and approved export together so an update can be made without guessing which version is current.
Who it serves
A first-time viewer needs to understand one product task, while reviewers need to confirm every action and claim. Write for the viewer's starting knowledge rather than narrating an internal feature tour.
Evidence and review
Pair each spoken line with a screen state, action or approved fact. Mark terms that need product-owner review before voice recording so the narration does not lock in inaccurate details.
Do not read every button label aloud. Let the screen show controls while narration explains why the step matters or what changes after the action.
A worked example
Illustrative scenario, not a customer story: For a fictional analytics product, open on a question a team needs to answer, show how to filter a dashboard, then reveal the report view. Replace every sample label and outcome with facts from the product.
Make it automatically
DemoVexa can use your product code and project context to draft a brief, script, and scene plan. Review every screen, claim, permission, and recording before publishing.
Frequently asked questions
How do I keep a demo script focused?
Write the viewer's goal first and keep only scenes that move toward it. Move unrelated features into another video instead of adding more context to the same script.
Should the script include on-screen text?
Yes, when a label, caption or end card helps comprehension. Keep it brief, coordinate it with narration, and check that both tell the same story without duplicating every sentence.
Can I use this template for free?
Yes. The outline is page content you can copy without an account. Adapt it to your product, check the destination's current requirements, and verify every claim, date, permission and third-party asset before publication.
Make your next product video with DemoVexa
Download the app to make a video from your code, or start a free trial with 15 renders.