Pitch a Show With Both Episode Stories and a Continuing Plot
Pitch a Show With Both Episode Stories and a Continuing Plot
A hybrid pitch fails in a specific way. The writer says "episodic and serialized," lists a season arc, then describes three episodes that could air in any order. The buyer reads a genre label and two separate documents stapled together.
The fix is a representative episode narrated twice: once as mostly self-contained, once as serial-led, with the production problem held constant. Same cinema, same collapsed booking, same sibling employees. Only the architecture changes. Then you can see what each version asks of the viewer and what each version carries forward.
Separate the local question from the continuing question
Screen Australia’s July 2018 Story Documents Drama guide distinguishes continuing, self-contained and hybrid story patterns. That historical Australian practitioner guidance supplies vocabulary, not current buyer requirements or evidence for the fictional comparison here.
Pick one installment, not the season.
"For episode four, the repertory cinema's Saturday program collapses when the distributor pulls the print. The house manager and her brother have that day to find a replacement. The continuing story is who ends up controlling the cinema's bookings."
That's a start, but it's still two sentences sitting next to each other. For this comparison, the episode question closes within the installment while the continuing question remains live. A hybrid can close both, or deliberately leave both open. What the pitch needs to show is why this installment ends where it does and what the next one inherits.
The failure mode is a scene that touches the subplot without interacting with it. A thirty-second beat where the brother glares at a ledger at the end of an unrelated episode gives you continuity, not architecture. The continuing story has to change the local problem's conditions, and the local resolution has to change the continuing story's state. Both directions, or you're coasting.
State which is which in the pitch. Readers can't infer it from a description that doesn't say.
Build the mostly self-contained version
The two-version comparison below is a constructed example, not a filmed episode, not audience-tested, not submitted to any buyer. It exists to expose the architecture. The premise is fixed: the repertory cinema, the collapsed Saturday booking, the two siblings. Call this Version A.
Local problem. By Friday afternoon the Saturday 7 p.m. slot is empty. The house manager needs programming by tomorrow.
Local resolution. She calls in a favor with a distributor she used to work for. She books a restored print of a film the cinema has never shown. She announces it Friday night.
Carried-forward consequence. To close the deal, she agreed to a two-week hold on a slot her brother had protected for a repertory series. She did it without telling him first.
Next-episode condition. The brother learns about the hold when the schedule posts. He now has to decide whether to fight it.
That's a hybrid episode with the weight on the local side. A new viewer can watch it without the earlier episodes and follow the whole thing: program collapses, house manager scrambles, she finds a print. The contract she signed is a consequence inside this episode, so it lands even cold.
What prior context enriches: the relationship between the siblings, why the brother protected that slot, why the house manager had a favor to call in at all. This is texture. It sharpens the scene without being load-bearing.
What prior context is genuinely required: almost none, in this version. If a beat depends on knowing that the brother left his previous job to come back to this cinema, then it's required; if it just makes the moment funnier, it's enrichment. A pitch that claims accessibility while burying essential information three episodes back contradicts its own promise.
The risk with Version A is drift. If every episode closes its own problem and only drops a consequence into the next one, you get a string of self-contained stories with a slow leak. That can work — plenty of shows run on it — but the continuing story has to keep accumulating, not just store things.
Build the serial-led version of the same material
Same collapsed booking. Keep it the same cinemas, the same distributor print, the same siblings. Version B changes only what the episode is about.
Prior event that makes this task matter. Two episodes earlier, the siblings agreed to a truce: neither would book outside the other's approval. The house manager broke it once already and was caught.
Local task. Find a replacement for Saturday. Failure means a dark screen and a refunded house.
Local turn. She calls the same favor-holder from Version A, gets the print, and takes the two-week hold. She succeeds at the booking. She also breaks the truce again, deliberately this time, and knows she's doing it.
Continuing state. The truce is now dead. The brother has grounds to escalate. The cinema's own governance is the live question, not the Saturday slot.
Notice that the local task has an achieved objective — a print is booked. The local turn happens. But the larger question, who runs this place, is not closed. The episode stops at the moment of the breach, not the moment of the reckoning. That's the difference between a serial-led episode and a serial-led installment that ends before its own work is done.
A cliffhanger can be a deliberate installment boundary. In this example, though, the episode doesn't stop with the slot empty: the print gets booked, and it's the truce that stays open. If you'd rather end on the dark screen, that's a different and weaker episode — one that leaves its own booking problem visibly unfinished, with only the truce left carrying the installment. Label it as an alternative ending if you use it.
The prior event that makes the task matter is now load-bearing. Cut the truce episode and Version B doesn't land: the breach has nothing to break. That's the trade. Almost no required prior knowledge in Version A, one required prior episode in Version B. Both are legitimate. The pitch has to name which one it's selling.
Compare what entry out of sequence preserves and loses
Here's where you test your own claim before a buyer does it for you.
Take Version A and imagine a viewer starting at episode four. What do they understand? The program collapses and gets replaced — fully. That the brother is upset about a schedule change — fully, once it happens onscreen. Why he cares so much — partially; they can infer a pattern, they can't reconstruct it.
Now Version B, same viewer, same episode. The booking gets made. The sister’s hesitation can signal a cost, but the brother has not yet learned of the breach. Without the earlier episode, the viewer cannot supply the truce, the first breach or what that agreement cost both siblings. The pitch should not count those facts as available merely because the writer knows them.
Understanding the immediate task survives entry out of sequence in both versions. Understanding its significance is fully available in A, partly available in B, and that difference is the honest structural trade the pitch needs to describe.
This is a reading of the material, not a viewer study. You are not claiming that anyone can start anywhere. You are stating what the presented information supports and what it withholds.
Make the pitch's episode examples show the chosen balance
Whatever version you pick, the examples have to chain. Each entry starts under the conditions the last one created.
Version A pitch example, three episodes:
Episode four: booking collapses, house manager secures a replacement, signs the two-week hold without consulting her brother. Ends with the hold in place.
Episode five: the schedule posts, the brother sees the hold, he books a competing weekend without consulting her. Ends with both holds live: he knows about hers, while she does not yet know about his.
Episode six: the collision becomes visible. Both siblings walk into the same Monday meeting with schedules that can't coexist. Ends with the general manager forcing a resolution neither of them chose.
Each example carries forward a consequence the previous one created. The two-week hold from four triggers five. The double-booking from five triggers six. The local problems in five and six are about programming again, but the continuing state keeps moving.
Version B pitch example, same three slots:
Episode four: booking collapses, house manager takes the print, breaches the truce for the second time. Ends with the breach known to her, not yet to her brother.
Episode five: the brother finds out. He doesn't confront — he starts quietly building a case to have her removed from scheduling authority. Ends with his first meeting with the general manager.
Episode six: the general manager sides with the brother on procedure but with the sister on outcome. She keeps booking authority; he gets veto power. Ends with a new arrangement neither trusts.
Same three slots, same premise. Different engine.
Don't pitch both versions to the same buyer as interchangeable. Pick the one matching the intended viewing experience. If the show is genuinely intermediate — some episodes lean local, some lean serial — say so and give the actual ratio, or give one local-leaning and one serial-leaning example side by side and name what makes them different. "Episodic and serialized" with no further qualification tells the reader you haven't decided.
End with one annotated episode, not a summary
Take the representative installment from the version you're pitching — episode four — and annotate it directly in the pitch, as a block, not as scattered description. One version, one block. The two are set side by side below only because this article has been comparing them; a pitch carries whichever one you're selling.
Episode 4 — "Dark Saturday" (Version A) Local closure: the Saturday 7 p.m. slot is programmed by episode end. Failure would have cost the house one night's revenue and the trust of the subscription audience. Continuing change: the two-week hold on the brother's protected slot is now in force, signed without his knowledge. Required prior knowledge: none. The local problem closes inside the episode; the hold creates a carried-forward consequence, which episodes five and six pick up rather than resolve here.
Episode 4 — "Dark Saturday" (Version B) Local closure: the slot is programmed. She gets the print and succeeds at the booking. Continuing change: the truce is dead, and the breach was deliberate this time. Known to her, not yet to her brother — and unresolved at the episode's end. Required prior knowledge: the truce established in episode two, the earlier breach, and what the agreement cost both siblings. Without them the breach has no weight.
That annotation is the pitch's most useful page. A reader can see, in one view, how the episode satisfies and what it can't reset. Then close with one plain sentence describing the relationship:
"This is largely self-contained with accumulating consequence" is a sentence. "This is episodic and serialized" is a shrug.
The pitch works when a reader can finish it knowing which episodes need watching first, which turns can't be undone, and what the show is about under the local stories. Everything else — the logline, the world, the characters — sits on top of that decision, not beside it.
Frequently asked questions
What is the basic failure in a hybrid pitch?
The writer says the show is episodic and serialized, lists a season arc, then describes three episodes that could air in any order. The buyer reads a genre label and two separate documents stapled together. The problem is not the label but the lack of shown architecture: the local problem and the continuing question are not interacting.
What does the article recommend instead of explaining the label?
Take one representative episode and narrate it twice, once as mostly self-contained and once as serial-led, with the production problem held constant. Same cinema, same collapsed booking, same siblings; only the architecture changes. That lets a reader see what each version asks of the viewer and what each version carries forward.
In the repertory cinema example, what separates the mostly self-contained version from the serial-led version?
In the mostly self-contained version, the local problem is an empty Saturday 7 p.m. slot. The house manager calls in a favor and books a restored print; the carried-forward consequence is a two-week hold on her brother's protected slot, signed without telling him. In the serial-led version, a prior truce established two episodes earlier makes the task matter. She gets the print and succeeds at the booking, but also deliberately breaks the truce again. The truce is dead and the cinema's governance is the live question.
How should required prior knowledge be handled in the pitch?
Name it. The mostly self-contained version requires almost none; prior context about the siblings and the protected slot enriches the scene but is not load-bearing. The serial-led version requires the truce from episode two, the earlier breach, and what the agreement cost both siblings. Without those, the breach has no weight. The pitch should not count facts as available merely because the writer knows them.
How should episode examples chain, and should both versions be pitched to the same buyer?
Each example should start under the conditions the last one created. In the version A chain, the two-week hold triggers episode five, and the double-booking triggers episode six. In version B, the breach leads to the brother quietly building a case, then to a new arrangement neither trusts. Do not pitch both versions to the same buyer as interchangeable. Pick the one matching the intended viewing experience; if the show is intermediate, state the ratio or give one local-leaning and one serial-leaning example and name what makes them different.