Pitch a Crossover Without Requiring Every Viewer to Know Both Series

Two shows. One event. The pitch that gets approved is rarely the one with the most exciting collision; it's the one where a viewer who watches only one of the two can still describe what happened and why it mattered.

That sounds like a constraint on ambition. It's actually a constraint on clarity. The question isn't "how do we get both casts in a room" but "where does the story begin, where does it resolve, and who has to be watching for that resolution to land."

Everything below is a proposed construction, using two invented series, to let you inspect the decisions rather than the vibes.

The scenario

Two fictional shows share a city and a night.

Radio: Signal follows a community radio station. Its ongoing situation is being broke, overextended, and dependent on volunteers who keep leaving. On the night in question, the station is running a benefit broadcast for its own survival. It has been relying on an improvised generator connection that a listener set up months ago.

Crew: Nights follows a municipal maintenance crew on the late shift. Its ongoing situation is being blamed for things it didn't cause and never being told when it did cause something. On the same night, the crew is called out to a district-wide power failure.

The collision: the station's improvised connection is what prevents a safe reconnection of the grid in that block. The crew discovers this. The station doesn't know it yet.

Note what I've built: a shared event (the power failure and its cause), two separate ongoing problems (the station's survival; the crew's reputation), and one fact that matters to both. That fact — the improvised connection — is where the crossover is decided. Everything else is local.

Map the event once, before writing either side

Before writing a single scene, write the event as a single list. Not an episode order. A chronology of what physically happens and what each side learns, in the world's time.

1. Power fails across the district.
2. The benefit broadcast is interrupted.
3. The station switches to its improvised generator connection.
4. The crew is dispatched.
5. The crew finds the improvised connection and realizes it blocks safe reconnection.
6. Someone has to decide what happens to the broadcast.

That's six beats. Keep them flat. "Someone has to decide" is deliberately unresolved — the decision is exactly what differs between routes.

Now, separately, note what each side knows and when. The station knows its connection exists; it does not know it's blocking anything until beat 5 at the earliest. The crew knows the connection is a problem; it does not know it's attached to a live broadcast until beat 5. If your two viewpoint summaries disagree about what happens at beat 3, that's a continuity error, not a mystery. If you intend a disagreement — someone lied about the connection's provenance — mark it as deliberate and decide which account is true in the world.

This list is the document that keeps you honest. It is not the viewing order.

What each show's viewer already knows

Assume nothing about recall. The Radio viewer has been told, over the season, that the station is broke and that a listener set up a generator connection. The Crew viewer has been told that the crew keeps getting blamed for other people's failures. Neither viewer has been told the other show exists.

That gives you a concrete list.

Local to Signal, must be introduced on screen:

• That the crew exists as a function (a maintenance crew, not a named cast).
• That the connection is relevant to the wider grid. The viewer does not need to know why.

Local to Nights, must be introduced on screen:

• That a community radio station is broadcasting from the affected block.
• That the station's survival is at stake. One line, in a crew member's mouth or a radio overheard in the truck, is enough.

Optional recognition, for viewers of both:

• Specific named volunteers at the station.
• The crew's specific prior grievances.

Familiar characters still need a functional role. A station regular crossing into Nights needs to do something there — carry a fact, object, or decision — not simply be recognized. Recognition is a bonus, not a job.

Now the two route pairs. Same six beats, different distribution.

Route A: sequential dependence

The Radio episode runs through beats 1–4 and stops at 5. It ends with the crew arriving, the problem stated, and the broadcast still on. The Radio episode's last shot is a hand on a switch. The Crew episode opens on that same moment and resolves it.

Let me write both endings, because the pitch lives or dies here.

Radio episode ending (hypothetical):

INT. STATION — NIGHT

The generator hums. MARA watches the meter. Behind her, the benefit is still going out.

CREW MEMBER (through door): Ma'am. We need to shut this down.

Mara's hand hovers over the switch.

CUT TO BLACK.

That's a cliffhanger. It's also a promise that the answer is in the other show. The Radio-only viewer closes the app with the switch unflipped.

Crew episode opening (hypothetical):

INT. STATION — NIGHT

CREW MEMBER: Ma'am. We need to shut this down.

Mara looks at the meter, then at the crew member, then at the small crowd of volunteers behind her.

MARA: How long.

CREW MEMBER: Ten minutes. Maybe twenty.

MARA: We've got forty of them listening. Some of them paid.

CREW MEMBER: Then I need you to tell me what you'd rather lose.

Note what the Crew episode opening does: it re-states the problem in the crew member's terms, introduces Mara as a stranger with a stake, and gives the Crew-only viewer everything they need in about twenty seconds. The cliffhanger is resolved, not re-explained.

But the Crew viewer has missed the setup. They don't know why the station is broke, why the connection exists, or who set it up. The episode has to carry that. It can — in the truck, in the thirty seconds before arrival, in a line from dispatch.

Now the arithmetic: the Radio-only viewer has a switch unflipped, and no way to see it flip. The Crew-only viewer has a stranger's problem restated, and can follow it. That's the asymmetry of Route A. The Crew viewer gets a complete episode; the Radio viewer gets an incomplete one.

That's not a reason to reject Route A. It's the reason to state it in the pitch. The Radio episode is a cliffhanger whose resolution lives in a show half its audience doesn't watch. The pitch should say so, in those words, and the network should approve it knowing it.

It does mean Route A fails the standard this piece opened with: the Radio-only viewer can describe where they were left, not what happened. Route A is here as the instructive case, not the disqualifying one — the dependency is available, approvable even, but only as a declared choice. Undeclared, it's the failure the rest of this piece is written against.

Route B: local completion, two ways

Same six beats. Different distribution.

Radio episode ending (hypothetical):

EXT. STATION ROOF — NIGHT

The generator is dead. A crew member holds the improvised line, cut clear of the cabinet.

CREW MEMBER: Whose hookup is this?

Mara looks at the meter, then at the cable.

MARA: Ours.

CREW MEMBER: Then the block stays dark a while longer, and somebody's going to want to know why.

Mara speaks into a phone, on speaker, to a volunteer holding the line open from a car.

MARA: We're going acoustic. If you can hear me, we're still here.

She looks at the meter. There's no meter reading. There's just Mara, and a microphone, and forty people on the other end who don't know the difference.

The Radio episode resolves: the station completes a stripped-back outdoor broadcast. The problem it established — the benefit continuing — is answered. It also establishes a task owed to the crew. The crew has just asked, on screen, whose hookup it pulled, and been told; the station has heard that the crew will be asked to explain the dark block. The next ordinary Signal episode owes the correction that follows: say out loud whose connection it was, or let the crew carry the blame for the station's improvisation.

Crew episode ending (hypothetical):

EXT. STATION ROOF — NIGHT

The crew looks at the cut connection. The live feed is off.

FOREMAN: Log it. Connection wasn't ours, wasn't ours to pull, but it was the block.

CREW MEMBER: They're going to blame us anyway.

FOREMAN: Then we get ahead of it. We tell them what we pulled and why. Tonight.

The Crew episode resolves: the crew makes the block safe and takes the first step on its own ongoing problem — being blamed for things it didn't cause. It also establishes a task owed to the station: an explanation about the delayed work.

Both episodes complete their local problem. Each retains a consequence that points at the other series. Neither requires the other to make sense as an episode.

What the parallel route costs: the two episodes are less eventful together. There's no single moment where the event turns. Route A has a switch; Route B has two resolutions. If your pitch's appeal was the collision, you've given up some of the collision.

What it gains: each episode can be watched on its own. The Radio viewer's problem is answered where they watched it. The Crew viewer's problem is answered where they watched it. The enrichment is optional, not load-bearing.

Allocate the revelations, not the airtime

You cannot give every character equal space. Signal has maybe four recurring leads; Nights has maybe five. A crossover episode that tries to service all nine will give each about four minutes and none a decision. Choose the one or two per side who carry the crossing, and let the rest be present as context.

Which revelations go where, in Route B — the route in which both episodes end:

The rule: a fact introduced in one episode is re-stated in the other only where that side's viewer needs it first; where a local resolution does not turn on it, the other series may carry only its consequence. The re-statement is not a recap. It's the same fact from the other side, doing a different job.

Route A's difference. One row moves. The station owes the crew a correction has no Signal-ending source in Route A: that episode stops at the switch, before anyone has told the station what its hookup was doing to the block. The crew's account has to arrive in the Nights resolution, or the correction has to be originated by the next ordinary Signal episode, which then discovers after the fact what it is apologising for. Both work; they give the Nights episode different jobs, and the pitch has to say which one it is buying.

What each series carries forward

The failure mode at the end is silent reset. The crossover ends, and the next ordinary episode proceeds as if nothing happened. That's not a creative choice; it's a hole.

The Radio show's next ordinary episode has, pending whatever the writers decide, a station that owes the crew a public correction. That's a local problem for Signal: the station has just told its audience to trust it, and now has to admit it got something wrong. It's a story seed the crossover paid for.

The Crew show's next ordinary episode has a crew that has to explain why the block was dark longer than it should have been. That's a local problem for Nights.

Record both as tasks in the shared timeline before writing the crossover ending. In Route B each finale can set up its own task, because each finale is where the task is born. In Route A only the crew's explanation has a source in its own episode; the station's correction has to be carried by the Nights resolution or deferred, as above. The test is the same wherever a task originates: an ending that owes a consequence has to put it in motion. If it doesn't, the crossover hasn't ended cleanly; it's just stopped.

Read each side aloud, hiding the other

Temporarily hide the companion episode. Read the Radio account on its own. What is unintelligible? What is unfinished?

In Route A, the Radio-only read leaves the switch unflipped. That's an intentional dependency, but it must be stated plainly, not disguised.

In Route B, the Radio-only read is complete on the surface. The station's benefit goes out, and the cut is not hidden from that viewer either: they watch the crew take the hookup off the grid and hear that the block stays dark longer because of it. What they don't get is the crew's stake. They don't know this crew has spent its season being blamed for things it didn't cause, so the question — whose hookup is this? — reads as procedure rather than a man getting ahead of an account that is about to be written without him. The station's correction is legible, because the station now knows whose connection it was. The reason the crew wants it said out loud isn't, and that belongs where the crew's season lives.

Missing context is repairable; a dependency the pitch doesn't admit is not.

What a real pitch would still need

This is a paper construction. It has not been filmed, tested with viewers, or approved by anyone. The two shows are invented; the scripts are hypothetical; the claims about what "the Radio-only viewer" would follow are editorial reasoning, not viewer research.

For a real case, you'd need the authorized scripts or episodes themselves, with locators for where context is delivered and where each resolution lands, plus a creator or showrunner account of how the crossing was coordinated. Neither is supplied here, and I haven't inspected any. Audience migration, cast permission, and production coordination cannot be inferred from a released event — a crossover that aired is not evidence that both audiences found it legible, only that it was made.

If you're pitching tomorrow, take one thing from this: choose the dependency, name it in the pitch, and give each side a local problem it actually solves. Route A, chosen out loud, is that — it fails the standard this piece opened with, and it can still be the right pitch, because the network approves it knowing what it bought. The one that never works is the dependency nobody names: two cliffhangers pointed at each other, wearing a single title.

Frequently asked questions

What's the practical test for a crossover episode?

Read each side aloud with the companion episode hidden. A viewer who watches only one series should still be able to describe what happened and why it mattered, and the episode should still be intelligible and finished on its own. Missing context is repairable; a dependency the pitch doesn't admit is not.

How do the two routes distribute the same six beats differently?

Route A is sequential dependence: the Radio episode stops at the crew's arrival with the broadcast still on and a switch unflipped, and the Crew episode opens on that moment and resolves it. The Crew viewer gets a complete episode; the Radio-only viewer is left with an unfinished one. Route B has each episode resolve its own local problem while retaining a consequence that points at the other series, so the enrichment is optional rather than load-bearing.

Why write the shared event as a flat chronology before drafting either side?

It keeps you honest about what physically happens and what each side knows and when. It isn't the viewing order. If the two viewpoint summaries disagree at a beat, that's a continuity error — unless the disagreement is deliberate, in which case it should be marked and you decide which account is true in the world.

Does bringing back a familiar character from one series count as a crossover role?

Only if they do something in the other series — carry a fact, an object, or a decision. Recognition is a bonus, not a job. And you can't service every lead: choose the one or two per side who carry the crossing and let the rest be context.

What would a real pitch still need that this construction can't supply?

The authorized scripts or episodes themselves, with locators for where context is delivered and where each resolution lands, plus a creator or showrunner account of how the crossing was coordinated. Audience migration, cast permission, and production coordination can't be inferred from a released event — a crossover that aired shows it was made, not that both audiences found it legible. The two series, the scripts, and the claims about viewers here are all invented and editorial.

Further reading

• Pitch a Spin-Off With Its Own Reason to Continue — A comparison for the same dependency problem: a spin-off pitch has to work without the parent show, much as each episode has to work without its companion series.
• Build a Story-Day Breakdown From a TV Pilot — Read it when you move from the beat list to drafted scenes, to build a chronology from the pages and mark parallel action and gaps rather than guessing.