How an episode ends and the next one opens
Five tools in the register say something about the seam between two episodes. One storyboards every episode to a cliffhanger, one carries an open loop into the next cut, one makes recap clips and teasers as separate pieces, and one requires every ending to stay unresolved, rotating between three kinds. As of 2026-10-13.
| Tool | What is published | Detail |
|---|---|---|
| Crano AI | Repeatable episode structures built for a publishing schedule | A rhythm, with no ending rule stated |
| Medeo | Part 1, Part 2, Part 3, recap clips and next-episode teasers | Recaps and teasers as extra pieces |
| Pexo | An open loop at the end of one cut carries the cast into the next | The ending as a bridge |
| SceneMixer | Every ending unresolved, rotating between three kinds; openings start on the problem | A rule in the episode breakdown |
| StoryShort | Shots storyboarded as hook, escalation, reveal and cliffhanger | A beat pattern inside each episode |
Inclusion rule. Tools whose pages describe endings, openings, recaps or teasers between episodes. A tool that describes episodes without saying how they meet is not given a row. Order. Alphabetical by tool.
1An ending is decided when the script is divided
Where an episode stops is the decision that most affects whether anyone watches the next one, and it is made when a story is cut into episodes, long before any picture exists. One page makes that explicit: the hook is a constraint the episode breakdown has to satisfy, and the outline for each episode, a few sentences including how it ends, is the cheapest place to change it.
A cliffhanger written into a beat pattern inside each episode reaches the same place by a different route. Both put the ending in the plan rather than in an edit after the fact.
2Rotation is the part most pages leave out
Only one page addresses repetition. It names three kinds of unresolved ending, someone's real identity exposed, a feeling left hanging, an understanding overturned, and states that the kind rotates, so a run of eight episodes does not use the same trick eight times. Three hanging confessions in a row, its reasoning goes, teach the viewer to expect a non-answer.
That is a statement about a season rather than an episode, which is the scale serial drama is judged at.
3Openings, recaps and teasers are three different jobs
The other side of the seam is the first shot of the next episode. One page states that openings start on the problem and that no text is burned into the frame; another carries an open loop across the cut so the cast arrives already in motion. A third makes recap clips and next-episode teasers as separate pieces, which serve a feed rather than the episode itself.
- Script to episodesRepeatable episode structures are described as something the user builds in order to publish on an ongoing schedulea shape rather than a split
- Script to episodesThe page describes turning one larger story into Part 1, Part 2, Part 3, recap clips and next-episode teasersas a repeatable shape
- Script to episodesAn open loop set at the end of one cut is described as carrying the cast straight into the next so a whole season stays consistentcut to cut rather than script to season
- How an episode endsEvery episode is required to end on an unresolved beat, and the kind rotates: identity exposed, feeling suspended, understanding overturned
- How the next episode opensOpening shots start on the problem, and no text is burned into the frame
- Serial formatEpisodes default to 16:9 with 9:16 available, and outlines are generated with cliffhanger pacingstated as the default
- Script to episodesThe AI is described as writing the script scene by scene, casting consistent characters and storyboarding every shot as hook, escalation, reveal and cliffhangera named sequence
4The words this register uses
Terms with a page of their own, each recording what vendors publish about it, include segment and shot, reference image, character consistency, storyboard script, scene plate, novel to video, AI short drama and vertical micro-drama.
5Sources
Each cell above traces back to a vendor page named in the register, read 2026-10-13. Where the boundary sits between documented, claimed and absent is spelled out under how read. Also here: Keeping a cast, Splitting a script, Assembly.