Software demo video template: a production brief
Use this software demo video template to brief the person recording one feature. Specify the starting screen, the exact control they will use and the visible result a viewer should check. Copy the blank brief into your own document, replace every bracketed field and share it with your recorder.
This is a text production brief. It does not include a downloadable editing project or generate a video.
Copy the blank production brief
Keep the demonstration to one feature. If reaching the result requires several controls, list every action in order instead of describing them as one click.
Product and feature: [name and version or build]
Viewer and question: [who is watching; what they need to understand]
Recording owner and reviewer: [names or roles]
Starting screen: [page, selected item, sample data and initial state]
Literal action: [exact visible control label; click, type or drag; ordered steps]
Visible result: [changed text, status or position; where it appears]
Proof to keep visible: [matching item identifier and unchanged context]
Capture assets: [recording or screenshots; file locations; resolution and aspect ratio]
Permissions and redactions: [asset approval; fictional or consented data; items to hide]
Timing and edits: [planned duration; result hold; any wait or omitted steps to disclose]
Caption or narration: [describe only what the footage supports]
Handoff and approval: [destination, reviewer and acceptance criteria]
Prepare the screen and assets
- Choose a build and a resettable starting state. Keep a reference screenshot so the recorder can recreate it.
- Supply the sample input and expected visible result. Use fictional data or data approved for public recording.
- Confirm permission to publish the interface, logos, recordings and any audio. Record approval with the asset locations.
- Hide email addresses, customer names, tokens, billing details and notifications before capture. Review the entire recording for accidental exposure.
- Agree on the capture size and final aspect ratio. Check that the control label and result remain readable at the intended viewing size.
Filled example: illustrative task-status change
This invented example shows how to fill the same fields. The product, control labels and result below are illustrative; they are not observations from the Launchry sample or a tested software workflow.
Product and feature: Fictional task board, demo build; completing one task.
Viewer and question: A teammate asking how to mark a task as done.
Recording owner and reviewer: Recorder captures the take; feature owner checks the state change.
Starting screen: Task list with the fictional item Review launch script selected and its status set to Open.
Literal action: Click the button labeled Mark complete on that selected item.
Visible result: The same item's status reads Complete in its detail panel.
Proof to keep visible: Keep Review launch script and its status in frame before and after the action.
Capture assets: Planned screen recording and starting-state screenshot; place both in the team's approved handoff folder. Agree on 16:9 capture before recording.
Permissions and redactions: Use fictional task data; obtain interface publication approval; hide account details and notifications.
Timing and edits: Plan a short take and hold the final status long enough to read. Preserve the actual wait, or label any shortened wait.
Caption or narration: Mark the selected task complete. Do not claim a time saving from this demonstration.
Handoff and approval: Send the take and starting screenshot to the feature owner; approve only if the same task is visible and the status change is readable.
Replace the invented labels with controls that actually exist in your product. If the operation fails or produces a different state, correct the brief before handing it off.
Tested terminal example: format a demo JSON file
Record a terminal formatting a small JSON fixture, then open the file it wrote. This independent example was run in a clean temporary directory with Python 3.9.6 and /bin/sh. It only formats demo data; it does not release a product or verify that a feature is ready.
You need Python 3 and a shell. Keep this fixture separate from your project: do not use or overwrite an existing release.json. The optional setup below creates a new temporary directory and changes into it before writing the sample input. If setup fails, stop.
demo_dir=$(mktemp -d "${TMPDIR:-/tmp}/launchry-json-demo.XXXXXX") &&
cd "$demo_dir" &&
printf '%s\n' '{"feature":"Export activity","status":"ready"}' > release.json1. Show the starting input
Open release.json in the new directory and show its single line. The status value is fictional sample data, not a product readiness check.
{"feature":"Export activity","status":"ready"}
2. Run one command
In that same directory, record this exact command. It reads release.json and writes formatted JSON to preview.json; the confirmation prints only if formatting succeeds.
python3 -m json.tool release.json > preview.json && printf 'Wrote preview.json\n'3. Keep the terminal output visible
Wrote preview.json
The recorded test returned this stdout line with a trailing newline, empty stderr and exit code 0. If your run fails or differs, inspect it before recording a successful result.
4. Open the matching artifact
Open preview.json from the same directory in your editor. Show the filename and both values so the viewer can compare them with the input. The tested file contained:
{
"feature": "Export activity",
"status": "ready"
}
Film in this order: starting input → command → terminal output → the matching preview.json file. Hold the result long enough to read the four-space indentation and unchanged values. Caption: “Format the demo JSON and open preview.json.” These are recording instructions for the tested command, not a finished video or a product launch claim.
The Command to Proof animation is a separate visual reference for arranging a terminal and an artifact. This Python run was independent of that Skill; it does not validate the animation's command or demonstrate its materials.
Check the starting screen against the result
- Watch without sound. Can a reviewer identify the starting state, the action and the changed state?
- Pause before and after the action. Confirm the item name, selection and relevant context match, so an edit cannot silently substitute another item.
- Read the literal action against the interface. Include any prerequisite or intermediate action needed to reproduce the result.
- Check captions against the visible evidence. A state change alone does not establish speed, reliability or customer outcomes.
- Review the final crop for readable labels and private data. If the result is unclear, revise the capture before adding a claim.
Compare with a public visual example
See the Productivity App Reveal example for an illustrative interface sequence. Its mock interface is not a tested software product or a customer result. Use it as a visual reference, then fill this brief with your own actual controls and expected state. Access to the example's Premium materials is separate from using this text brief.
Return to Product demo video guides.