Make a TV Pitch Navigable When the Reader Skips Ahead

A series deck is written front to back and read sideways.

Someone opens the file at the character page because the producer they're meeting asked who the leads are. Someone else jumps straight to the episode example, because on a procedural they want to know what a Tuesday looks like before they care about anybody's backstory. Someone reads the last page first to see what you're asking for, then works backward only if the ask interests them.

None of that is a problem until the page in front of them doesn't make sense on its own. A character page that assumes you've read the premise. An episode example that never says whether it's the pilot or episode four. A heading that promises nothing in particular and delivers the same.

The repair is not a contents page, and it definitely isn't the premise pasted onto the top of every page. Give each major section the minimum context its own question needs, name the route to the next useful answer, and leave the linear read alone. That's it. The rest of this article is about what "minimum" means in practice and how to check that the routes actually exist in the file you send.

Three orders live in one deck

The show has a chronology. June runs a tool library, and somewhere in episode four something she did in the pilot comes back to her. That's story order.

The deck has a page order, which usually follows the pitch's rhetoric rather than the show's timeline: premise, characters, a sample episode, what exists, what you want. Those two orders already disagree, which is fine, as long as the deck doesn't imply that page five is episode five.

And the reader has an entry order, which may be nothing like either one. Most decks behave as though entry order is fixed at page one, and then get confused when a reader arrives somewhere else and doesn't have the furniture to sit down.

So the practical question is narrow. Which sections are plausible doors, and what does a reader need in the first three lines after walking through one?

Four doors cover most decks: understanding the series proposition, assessing the people, inspecting an episode, and checking what exists. Pick two of them as your test routes, different ones — the character page and a later episode, say — and read from each door to the end. Two is enough to catch the pattern. Testing all four is nicer and rarely necessary, because the missing-context failures tend to repeat.

Read a middle section with the beginning torn off

The diagnostic is simple and unpleasant. Open the deck at a section that isn't the first one, cover everything above it, and read.

Four kinds of omission are worth caring about:

• A role that isn't established. Who is Sal, and what is he to this library?
• A relationship with no history. This page keeps referring to something June owes, and never says what.
• A missing label. Is this example the pilot, a later episode, or something already made?
• A status that's ambiguous. The last page mentions "interest." Real interest, from whom? Or the writer's hope, written as though it were a fact?

Everything else can wait. The test isn't "does this section make sense alone" in some absolute sense — nothing does — but "does the first question a reader brings to this door get answered before the paragraph ends." A reader who opened the character page wants to know who these two people are. They don't need the tone, the comps, or the six-episode arc. They need June, and they need Sal, and they need the one fact that explains why these two are the show.

That distinction does real work: the missing context is a fact, not a summary. "She owes him" is context. Three pages about why she owes him is a rereading of the pilot, and the reader can get that by clicking onward.

Headings that tell the reader where they've landed

A deck I'd want to fix has a section called The Ride. It sits second, after the cover and before the leads. Its actual contents: the show's weekly engine, which here means one borrowed object per episode and the argument that follows it.

The Ride tells a reader nothing except that the writer likes the word. The Series Engine: One Borrowed Thing Per Episode tells them what they'll find and, incidentally, tells them whether they need to read it. A skipped reader benefits more from a heading they can decline than from a heading they can't parse.

This is close enough to a documented principle that it's worth borrowing deliberately. The W3C's Page Structure Tutorial on headings (checked 8 June 2026) explains that headings communicate a document's organization and help readers navigate it — which is precisely the job here, when the reader is not moving from the first page to the last. But borrow the principle, not the compliance. That tutorial concerns web pages and how assistive technology exposes their structure. Applying it to a pitch deck is an editorial adaptation, in the same spirit as "short paragraphs read faster." It is not evidence that a PDF has a heading structure anything can read, or that any accessibility requirement has been met. Both of those need their own inspection of the actual file, and neither is the subject here.

Two smaller habits support descriptive headings.

Keep names consistent. If the deck says "June and Sal" in one heading, "Our Leads" in another, and "The Two" on the episode page, a reader jumping around has to spend a beat confirming they're the same people. Use one set of names everywhere and let the headings do the sorting.

Keep episode and season labels distinct, and label examples honestly. A reader can hold "the pilot" and "episode four" apart; they cannot hold apart a page called Generator and a page called The Van with no indication of where either one sits in the show. If episode four hasn't been written and the page is a preview built from your outline, say so in the heading. Proposed Episode 4 costs nine characters and prevents a misread that would be much more expensive in the room.

Connect to the answer, not to the shelf

The instinct when adding navigation is to build a contents page and link everything to it. Resist this. A contents page answers "where is everything," which is not a question a reader has. Their question is "where is the answer to the thing I now want to know," and the useful link goes directly there.

In practice the connections are short. At the end of the character section, one line: the pilot's dispute is about the generator; see that page. At the top of the episode example, one clause naming the favor and where it comes from. These links do two jobs at once — they orient the reader who arrived here first, and they give the reader who's reading in order a signpost to something they might want to revisit.

A contents page also has a way of becoming proof by ornament. It looks like navigation. It sits there. It doesn't establish that any destination is reachable or that any destination answers anything.

The Loan Desk, before and after

Take a deck of six pages. Call the show The Loan Desk: June runs a tool library in a converted laundromat; Sal has been fixing things in the back room since before she took over; in the pilot, during a blackout, June lends the library's only generator to Sal against her own lending rules, and the argument that follows is the show's pilot. The generator comes back broken, Sal rebuilds it off the books, and June ends the pilot owing him a favor she can't record anywhere.

Before:

1. Cover — "THE LOAN DESK"
2. The Ride — the series engine
3. June and Sal — the leads
4. Generator — the pilot dispute
5. The Van — an episode
6. Where We Are — materials and ask

After:

1. Cover — title, format, the one-line world
2. The Series Engine: One Borrowed Thing Per Episode
3. June and Sal: Who Runs the Library, Who Owes Whom
4. The Pilot: The Generator Dispute
5. Proposed Episode 4: The Van
6. What Exists Now, and What We're Asking For

Same six pages, same order. The changes are all inside.

Route one starts at the character page. Before, it opens on the quality of the friendship — "the easy part of June and Sal is that they never have to explain themselves to each other" — which is a lovely sentence that means nothing if you don't already know who they are or where they are. After:

June runs The Loan Desk, a tool library in a converted laundromat on Delaney Street. Sal has been fixing things in the back room since before she took over, which means he knew the place when it was still full of washing machines. She owes him one favor she can't put in the ledger, for the generator he rebuilt off the books at the end of the pilot.

Three sentences. The first names the job and the place. The second gives Sal a role and a history with the building, not just with June. The third supplies the debt without explaining the blackout, the cracked housing, or the argument — the reader can get all of that one page down.

Route two starts at the episode page. Before, it opens: "Sal asks for the van, and June has to decide whether a favor is a loan." A reader who hasn't read the pilot doesn't know where the favor comes from, what it was, or whether this episode exists. After:

Proposed Episode 4: The Van. Not yet written — this is built from the six-episode outline. Sal calls in the favor June owes him from the pilot (see June and Sal), and asks for the van for a weekend he won't explain.

The heading says proposed. The next sentence names the favor without retelling it. The parenthetical is the route: a reader who needs the fuller relationship gets sent to the page that has it rather than to a contents list, and a reader who doesn't need it keeps moving.

The repair that fails is worth naming because it's the one that feels diligent. It pastes the series overview — the laundromat, the rules, the tone, the comps — at the top of all six pages. Route two's reader now reads the premise once before reaching the episode, and the episode itself has moved further away. Worse, the pasted paragraph is identical everywhere, so it orients nobody toward this section; it's the same furniture in every room. And the deck gets longer without getting clearer, which in a pitch is a cost you pay twice.

Check the routes in the file you'll actually send

Specify the routes, then look at the artifact. An editing view is not evidence. A connector that resolves while you're building is not evidence that it resolves in the exported PDF, in the hosted link, or on someone's phone in a taxi. And a section that appeared onscreen directly under its heading may land across a page break once the file is exported, which quietly separates a label from the thing it labels.

A route-check record is small and dull and does the job. One row per entry point, plus a row for the continuous read:

Record the file format and where you opened it. Write down what actually happened, including the failures — the link that landed at the top of a page whose answer was two screens down, the heading that repeated verbatim from an earlier section, the page break that left a label stranded at the bottom of a page. Then reread the whole thing start to finish once, because local repairs have a way of introducing repetition that only shows up in sequence. The character page that was fixed for the skipping reader may now repeat a sentence the premise page already delivered.

A note on procedure: the The Loan Desk example above is a paper comparison. Nothing has been exported, hosted, opened, or handed to a reader, and the answer column is unfilled and the status column says only "Not inspected" because of it. No navigation check has been performed on any file, and no accessibility finding follows from the W3C tutorial. What the method produces is a specification and a record to fill in — not a claim that navigation works.

One section, repaired

End where the skipping reader actually is. The repaired middle section, in full:

Proposed Episode 4: The Van. Not yet written — this is built from the six-episode outline. Sal calls in the favor June owes him from the pilot (see June and Sal), and asks for the van for a weekend he won't explain.

One label, one clause of context, one named route. That's the whole fix, and it costs two lines. The section now works for a reader who opened the deck here, and it works just as well for a reader moving through in order, who gets a small pointer back instead of a jolt.

The temptation is always to swell these repairs into a redesign — a contents page, a premise on every page, a navigation system for a document six pages long. The useful version of this pass is quieter than that. Find the door, notice the missing fact, add the smallest sentence that supplies it, and name the next useful answer. Everything else in the deck gets to stay exactly as it was.

Frequently asked questions

Why does a TV pitch deck need to work for readers who skip around?

A series deck is written front to back and read sideways. Someone may open at the character page because a producer asked who the leads are, jump to the episode example to see what a Tuesday looks like, or read the last page first to check the ask. A page becomes a problem when it does not make sense on its own, such as a character page that assumes the premise or an episode example that never says whether it is the pilot or episode four. Give each major section the minimum context its own question needs, name the route to the next useful answer, and leave the linear read alone.

How should I test a deck for skipping readers?

Open the deck at a section that is not the first one, cover everything above it, and read. Check for four omissions: a role that is not established, a relationship with no history, a missing label, and an ambiguous status. Pick two different doors, such as the character page and a later episode, and read from each to the end. Two is enough to catch the pattern because missing-context failures tend to repeat.

What heading and labeling practices help a skipping reader?

Use descriptive headings that tell readers where they have landed and whether they need to read the section. 'The Series Engine: One Borrowed Thing Per Episode' tells more than 'The Ride.' Keep names consistent so a reader jumping around does not have to confirm that June and Sal, Our Leads, and The Two are the same people. Keep episode and season labels distinct, and label examples honestly. If episode four has not been written and the page is a preview from an outline, say so in the heading, as in 'Proposed Episode 4: The Van.' The W3C heading principle is an editorial adaptation here, not evidence of PDF heading structure or accessibility compliance.

Should I add a contents page or paste the premise onto every page?

A contents page answers where everything is, which is not a reader's question. Their question is where the answer to the thing they now want to know is, so the useful link goes directly there. Short connections do two jobs: they orient a reader who arrived first and signpost something for a reader moving in order. Pasting the same series overview at the top of all six pages is the repair that fails. It is identical everywhere, so it orients nobody toward this section, moves the episode farther away, and makes the deck longer without getting clearer.

How do I verify the routes in the file I actually send?

Specify the routes, then inspect the artifact. An editing view is not evidence; a connector that resolves while you are building is not evidence that it resolves in the exported PDF, hosted link, or on someone's phone. Record the file format and where you opened it. Use a small route-check record with one row per entry point plus the continuous read, and write down what actually happened, including failures like a link landing at the top of a page whose answer is two screens down or a page break stranding a label. The Loan Desk example is a paper comparison; nothing has been exported, hosted, opened, or handed to a reader, no navigation check has been performed, and no accessibility finding follows from the W3C tutorial.

Further reading

• What Goes in a TV Pitch Deck? — Read first if a section cannot stand alone because its job was never defined; it separates what the overview, pilot, episode example, and ask must each answer.