Documentary Short script template

A 40 to 60 second documentary Short needs a fixed beat structure more than it needs a good camera. In a July 2026 Similarweb snapshot, aviation disaster channels in our measured set held an 85 saturation score against a demand score of 94, which means viewers are there and most uploads still fail on structure, not footage. This template gives you the skeleton: six named beats, each with a proportional time budget and one job.

The template

Copy this block. Replace every bracketed line. Total runtime target: 40 to 60 seconds, so keep the whole script short enough to read aloud inside that window.

DOCUMENTARY SHORT SCRIPT
Topic: [one real event, one date range]
Runtime target: [40-60 seconds]

BEAT 1 - COLD FACT (first fifth of the runtime)
[One measured fact stated flatly. A number, a date, a place.
No greeting, no "did you know".]
Job: earns the opening before the swipe.

BEAT 2 - THE STAKES (next short block)
[What was at risk, in concrete terms: lives, money, distance.
Name who was involved.]
Job: tells the viewer why this event mattered to someone.

BEAT 3 - TURNING POINT (the longest block, about a quarter of the runtime)
[The moment things went wrong, or went right. One decision,
one failure, one discovery. Present tense works well here.]
Job: carries the middle of the video where drop-off peaks.

BEAT 4 - CONSEQUENCE (a medium block after Beat 3)
[What happened as a result. Numbers if you have them,
sourced. If no number exists, describe the change.]
Job: pays off Beat 3 without repeating it.

BEAT 5 - RESOLUTION OR OPEN QUESTION (a medium block)
[Either how it ended, or what remains unexplained.
Unresolved topics hold retention; say what is still unknown.]
Job: gives the viewer a reason to finish the video.

BEAT 6 - CLOSING LINE (the final few seconds)
[One sentence. Either a sourced fact that reframes the story,
or a single question left open. No call to action needed.]
Job: ends cleanly so the loop or the next video can start.

Rules that apply across all six beats:

1. Every number must come from a source you can name. If you cannot name it, cut the number, not the source check.
2. One idea per beat. If a beat needs two sentences of setup, split the topic into two videos.
3. Write present tense for Beats 2 and 3, past tense for Beats 4 and 5. The tense shift does the pacing work that music usually fakes.

How to use it

1. Pick one event with a verifiable date. Not a theme, an event. "The Concorde crash" qualifies; "aviation disasters" does not.
2. Collect three sources before writing anything: one primary account, one official report or record, one piece of archive footage you can license or confirm is public domain.
3. Fill Beat 1 first. If you cannot state a cold fact in a single short sentence, your topic is too broad.
4. Draft each beat to its share of the runtime, then read the whole script aloud once. Cut any sentence you stumble on.
5. Match each beat to a visual: archive clip, map, or chart. Note the source next to each visual as you go, not after.
6. Time yourself reading. Over the window, cut from Beat 4 first. Under it, add detail to Beat 3.

A worked example

Filled in for an aviation disaster topic, using the structure above:

Beat 1: On 25 July 2000, a Concorde crashed shortly after takeoff from Paris.

Beat 2: People were aboard a passenger aircraft flying at twice the speed of sound, and its safety record had been clean until that morning.

Beat 3: During the takeoff roll, a strip of metal on the runway tore a tyre apart. Debris ruptured a fuel tank directly above the engine.

Beat 4: Fire reached the engines before the plane could return. Everyone aboard died, along with people on the ground where the aircraft came down.

Beat 5: Concorde returned to service the following year with reinforced fuel tanks, but passenger numbers never recovered.

Beat 6: The crash investigation ran for years and changed how debris on runways is treated worldwide.

Each beat maps to one visual: newsreel footage, a route map, a diagram of the tank position, and a chart of Concorde's passenger numbers after the crash.

What this template will not fix

It will not make weak sources strong. If your only source for Beat 3 is a forum post, the structure will just deliver the error faster. It will not replace licensing work: archive footage still has to be cleared, and a script does not do that for you. It also will not rescue a topic with no turning point. Some events are simply a sequence of facts with no Beat 3, and those videos underperform no matter how the beats are labeled. Finally, the timing assumes English narration at a normal pace; other languages shift it.

<!-- faq -->

Frequently asked questions

How long should each beat actually be?

Follow the proportions rather than exact cuts. Beat 3 should always be the longest block, around a quarter of total runtime.

Can I use this for topics that are not disasters?

Yes. The beats are event-shaped, not genre-shaped. Heists, expeditions, and engineering failures all fit; listicles and explainers do not, because they lack a single Beat 3.

Do I need a hook phrase like "wait for it"?

No. Beat 1 is the hook. A dated, specific fact outperforms a verbal tease, and it survives being clipped out of context.

How many drafts does this need?

Two. Draft one fills every bracket. Draft two cuts words and re-times the beats. More than three drafts usually means the topic is wrong, not the writing.