Map the episode before filling every segment
Write the opening promise, the main development and the closing outcome. A recurring format gives viewers a recognisable experience, but each segment still needs a reason to appear in this episode. Avoid carrying a familiar section forward when it adds no useful information or change.
For a fictional workshop show, the episode might introduce a broken object, explore competing repair ideas and reveal the result. The rundown helps you see whether the middle develops the question or merely delays the reveal.
Copy the episode header and segment block
Complete the header once, then repeat the segment block for each part. Record estimated timing as an assumption and note where a read-through or rough assembly will test it. If a segment contains factual material, keep its verification dependencies visible.
Transitions deserve their own field. A segment can work alone yet leave the audience confused about why the programme moves to the next topic.
EPISODE TITLE / NUMBER:
FORMAT / INTENDED AUDIENCE:
EPISODE QUESTION OR PROMISE:
VERSION / DECISION OWNER:
PLANNED ENDING / VIEWER TAKEAWAY:
OPEN WHOLE-EPISODE QUESTIONS:
SEGMENT ID / TITLE:
PURPOSE IN THIS EPISODE:
CONTENT / ACTION / REVEAL:
HOST / CHARACTERS / CONTRIBUTORS:
REQUIRED ASSETS OR SOURCES:
PROVISIONAL TIMING / BASIS:
TRANSITION IN:
TRANSITION OUT:
REVIEW OR VERIFICATION NEEDED:
STATUS / OWNER:Worked illustration: a workshop episode
This fictional rundown excerpt describes an episode about repairing a clockwork bird. It uses a clear question to connect demonstration, disagreement and outcome. The timing remains open until the action can be reviewed.
An optional segment is identified as optional rather than allowed to expand the episode unnoticed. That distinction helps protect the central story when production choices change.
Review the programme as a complete sequence
Read the segment purposes in order without the detailed content. They should describe a coherent journey rather than a list of assets. Check whether the opening promises something the ending actually delivers and whether each transition makes the next question understandable.
When one segment changes, review the surrounding transitions and the whole-episode balance. Mark removed segments clearly and update the required assets. Keep a current rundown beside the production brief so a team member can distinguish a local adjustment from a change to the programme’s central promise.
Questions & answers
Is a rundown only for factual shows?
No. It can organise entertainment, quizzes, recurring explainers and story-led episodes. Adapt the fields to the decisions the format requires while preserving purpose, sequence and transitions.
Should each episode have identical timing?
Use the format’s constraints where they exist, then test the actual material. Consistency can come from a recognisable structure without forcing every idea into identical segment lengths.
Explore the workflow with your own idea.