Video call / screen-share format: structure, script and how to clone it
Video call / screen-share format is a proven short-video structure. Here is why it holds attention, how its beats are timed, a script you can start from, and the command that clones it for your own subject.
Why this format works
A call layout lets you show software honestly: the interface is the evidence, and a second face makes it feel observed rather than advertised.
Structure breakdown
1. Join moment (0–3s)
Open on the call already in progress; someone is mid-sentence.
2. Problem on screen (3–15s)
Share the ugly state — the spreadsheet, the failing build, the wrong output.
3. Fix (15–40s)
One action, shown, with a caption naming what changed.
4. Reaction (40–50s)
The other person reacts; the human response is the payoff.
5. Close (last 3s)
State the outcome in one line.
A script you can start from
Segments, takes and selection anchors — this is the part of the project that changes when you re-run the format:
<script>
<segment> id="call">
<take>Look at || @the-diff the diff. || That is || @one-line one line. || <D | Dee> Run it again.</take>
</segment>
<media-track>
<item source=screen-1.png during={script.selection.the-diff}/>
</media-track>What you need
- — Screen recording
- — A second person (or a voice)
- — A layout that keeps the screen legible at 9:16
Run it
hypit run clone --reference ./reference/video-call.mp4 --script ./call.svs --runThe reference video stays fixed. Change the script, re-run, and you get a new edit in the same format — that is the whole point of cloning instead of prompting.
Keep reading
FAQ
Can I run this without a second person?
Yes — a voice-only counterpart works, or you can narrate the reaction yourself.
How do I keep UI text readable on mobile?
Crop to the region that matters and let captions carry the detail rather than showing the whole window.
Is the call format good for developer audiences?
It is the strongest one for them, because the screen recording is verifiable evidence rather than a claim.