People freeze up at the idea of writing an episode because they picture it as one slice of a giant thing — how do you write chapter seven of a book you haven't written? But that's not what an episode is. The best way to understand an episode is this: it's a whole story, just a small one, that happens to take place inside a larger story that's still going.

Think of your favorite show. Almost any single episode has a beginning, a middle, and an end that you actually feel. Something starts, builds, and lands by the time the credits roll. That's a complete story. But underneath it, a bigger current keeps moving — relationships shifting, a season-long question inching forward. An episode rides on top of that current. Two things at once: complete in itself, and a step in something larger.

The two layers: what happens this week, and what's always happening

Nearly every episode is built on two layers running together, and if you can hold both in your head, you understand episode-writing:

A good episode weaves the two so the self-contained problem gives you a satisfying story tonight, while the ongoing layer moves just enough to make you need next week. Lean too hard on the self-contained layer and the show feels repetitive and weightless. Lean too hard on the ongoing layer and each episode feels like it never quite starts or finishes. The craft is the braid.

The A-story and the B-story, in plain words

Here's where two common terms finally make sense, now that you have the plain idea underneath them. When writers talk about the A-story, they just mean the main thread of the episode — the biggest, most screen-time thing happening this week, usually the self-contained problem. The B-story is the secondary thread — a smaller storyline running alongside it, often carrying a quieter emotional beat or nudging the ongoing layer forward.

That's all those words mean: the main story and the side story of a single episode. Most episodes have an A and a B; some add a small C. The reason to run more than one is rhythm and contrast — the B-story lets you cut away, change the tone, and let the A-story breathe, so an hour doesn't feel like one unbroken note. Often the smartest move is to have the B-story secretly comment on the A-story, so the two rhyme by the end.

The A-story is the main thing that happens this week. The B-story is the quieter thing beside it. The magic is when the B-story rhymes with the A-story — two threads that turn out to be about the same thing.

How an episode satisfies and still pulls you forward

This is the balance every episode has to strike, and it sounds like a contradiction until you see it working. You want a viewer to reach the end feeling like they got a real, finished story — not cheated, not left dangling on a technicality. And you also want them to feel the pull to keep going. How do you do both?

You close the small question and leave the big one open. The self-contained problem — this week's case, tonight's crisis — gets a real resolution. That's what delivers the satisfaction. But resolving it nudges the ongoing layer: the win costs something, or reveals something, or shifts a relationship. The door on this week shuts firmly; the door on the season opens a crack wider. Satisfaction and momentum aren't in tension when they live on different layers.

Working out your first episode?

StoryEngine helps you find the self-contained story for a single episode and see how it feeds the bigger one — asking plain questions and taking the next step with you, at your pace.

Start With My Idea → No experience required · Start free · Your story stays yours

A simple way to shape an episode

You don't need a formula, but a rough shape helps when the blank page feels like too much. Try answering these, in order, one at a time:

  1. What's the problem this week? The self-contained thing that appears near the top and needs resolving by the end.
  2. Who does it land on hardest? Point the A-story at the character it costs the most, so it matters.
  3. What quieter thread runs alongside? Your B-story — ideally something that rhymes with the A-story's theme.
  4. What in the ongoing layer moves? One relationship or season-long thread that shifts, even slightly, because of what happened this week.
  5. How does it end so it's both done and not done? Close the week's question; leave the season's a little more open.

Answer those five and you have the skeleton of an episode. You don't answer them all at once — each answer makes the next easier, because you stop staring at "an episode" and start looking at one small, real question.

Where the episode sits in the bigger build

If you're writing your very first episode as the one that launches the show, remember it's carrying extra freight — it also has to introduce the world and the engine. That special first episode has its own guide: what is a TV pilot. And if you haven't yet nailed down the renewable situation your episodes draw from, step back to how to write a TV show from an idea — the engine there is exactly what hands each episode its self-contained problem.

Last thing. Writing an episode is real craft, and craft is learnable — not "learnable if you're gifted," learnable full stop. You pick up each term after you understand the plain idea it names, the way "A-story" only meant "the main thread" all along. And being guided through an episode doesn't take it out of your hands: the questions get asked, the choices stay yours. Your words, your voice, your copyright — your story stays yours.