Rehearse a TV Pitch as a Conversation, Not a Recital
Rehearse a TV Pitch as a Conversation, Not a Recital
You can read your deck out loud without looking down. That is a real skill and it is not the one you need. What you have practiced is the ability to produce a fixed sequence of sentences in a fixed order. A pitch is not a fixed order. It is a person across a table deciding, in real time, whether they want to see more of your show.
So the interruption is not a failure of your preparation. It is the normal condition of the room. Someone stops you at slide three and asks what an ordinary episode looks like, and if the only place your explanation exists is inside the slide order, you have nowhere to stand. You restart. You read faster. You hope the next slide rescues you.
The fix is not a better memory. It is a different object to memorize. Build a route: a small number of points you can reach from more than one direction, so an interruption costs you a step rather than the whole walk.
That is the whole argument. What follows is how to build the route, how to keep two different questions from collapsing into one answer, how to practice being interrupted on purpose, and how to close on what actually happened in the room rather than what you hoped would happen.
Build a spoken route independent of the slide order
Start by deciding what the listener has to leave understanding. Not everything true about your show — the three or four things without which the rest is noise.
For most series that comes down to three anchors:
- The situation. The world and its pressure, stated in a sentence someone could repeat to a colleague.
- The people or the format. Who is doing what to whom, or what the recurring shape of an episode is.
- The recurring reason to watch. Why this does not exhaust itself after one hour.
Write those as short notes. Fragments. "Desk, not owner." "Two needs, one object." Not sentences — sentences are what you are trying to stop reciting. If you write full paragraphs on the card, you will read the card, and you will have relocated the problem rather than solved it.
Then decide what each slide is for. A live deck and a document that gets read alone are doing different jobs. A read-alone deck has to carry the explanation, because nobody is standing next to it. A live deck can carry proof: a floor plan, a photo of the actual room, a one-line title that puts a name to the thing you just described. When a slide is doing structural work — showing the recurring shape, showing the cast arrangement — it should look like that, not like a paragraph you intend to narrate.
Here is a route card for an invented series. It is a teaching example, made up for this exercise; nobody has pitched it and nobody has responded to it.
The desk. A residential building has a repair desk where residents borrow tools and log what needs fixing.
The caretaker. A new one takes over the desk. She does not own the tools. She cannot decide who deserves what. She can only decide the order.
Why another episode exists. Every week, two legitimate needs compete for one object, and the decision happens in public, at the desk, in front of the neighbors.
Three lines. If you can say those three lines from any starting point, you can survive a meeting. Notice what is not on the card: how she got the job, what the building looks like from the outside, the name of the neighborhood. Those are good details. They are not load-bearing.
One more thing about this stage. If you tell the route out loud and it knots — if you cannot get from the caretaker to the reason to watch without a detour — that is information about the show, not about your delivery. A missing connection between two anchors is a gap in the proposition. Do not cover it by talking faster. Fix the thing, or admit in the room that you are still working out that part.
Rehearse the pilot question and the series question separately
These get asked in the same words and they are not the same question.
"What happens?" can mean what happens first — walk me through the opening. It can also mean what happens in general — what does this show do on a Tuesday. The second question is the one that kills pitches, because the person asking it does not want the rest of your pilot plot. They want to know whether the pilot is standing on something that keeps producing.
Practice both answers until they are audibly different.
The pilot answer. What happens first. In the invented series, the caretaker arrives, finds a log book half-filled in by whoever came before, and takes the desk. She learns that the ladder, the drill, and the tile cutter belong to the building collectively, and that she is the one who has to say who waits.
The series answer. What stays in place. The desk stays. The rule stays — she sequences, she does not own. The neighbors stay, and they will want the same things again.
The representative episode. One that does not repeat the setup. In this invented series: a resident wants the ladder for the afternoon to paint a ceiling. Another needs it for fifteen minutes, right now, to reach a shutoff valve that is leaking. Same ladder, two incompatible uses — one long and ordinary, one short and urgent. The caretaker has to decide in front of both of them, and the episode is really about how she decides and what it costs her with each of them.
That episode is what makes the distinction audible. It contains no arrival, no first day, no orientation. It could not be the pilot. If your "ordinary episode" example could still be your pilot with different names, you have not found the engine yet.
So when the question comes, say which level you are answering. "The pilot opens with her first day — but if you mean a normal week, it's this: a ladder, two people, fifteen minutes of leaking." Then the listener can follow you instead of waiting to find out which question you heard.
Insert an interruption and find the right return point
Rehearsing alone will not test the thing that actually breaks. You need a second person, and their job is to interrupt you before you are finished.
Give them the assignment plainly: ask one concrete question in the middle of the explanation, one that comes from the show rather than from politeness. Not "how long is the season." Something like: What happens in an ordinary episode?
Now the important part. Do not answer and then start over. The route is not a corridor; it has places to stand.
Three moves, in order:
- Answer the question. The ladder. Two residents, incompatible uses, a decision made aloud. Three sentences is enough.
- Name where you are. Say, out loud, which anchor the interruption already covered — "so that's the recurring reason to watch" — so you both know what has been established.
- Resume at the next useful point. Not the next slide. The next thing the listener does not yet know.
For the invented series, there are two sensible return points, and which one you take depends on what the listener still needs.
Return point one — the engine, then forward. "So that's the pattern: every week, one object, two legitimate needs, and she has to rule on it in front of everyone." From there you go forward into whatever you have not yet covered — tone, why now, who it is for. This is the return point to use when the listener has understood the situation and is evaluating whether it sustains.
Return point two — back to the pilot, compressed. "That's the job she takes on in the first episode." You return to the arrival, but in one clause, because the listener now knows what the arrival is for. This is the return point to use when the listener still does not have the shape of the opening — the ladder episode has just explained why the desk matters, so the origin story can land in a fraction of the time it would have taken cold.
Both are recoveries. Neither is a restart. Neither asks you to pretend the interruption did not happen.
A note on what to measure. The goal is not zero pauses and not an answer that fits your planned order. If the partner's question pulls the conversation somewhere better than your plan, follow it. The things worth recording afterward are different: where the show became genuinely hard to explain, which anchor you kept reaching for and missing, and which question made you improvise a version of your own series that you had not heard before. That last one is usually the most valuable output of the whole session. Write it down before you forget it.
And if the hard part turns out to be the show rather than the telling — if there is a real hole in the engine — that belongs in your development notes. Rehearsal is not the place to learn to talk around it more gracefully. A pitch that hides a structural problem buys you a meeting you cannot deliver on.
Close on the actual conversation
The close gets neglected because it feels like the easy part. It is the part you can actually get wrong in a way that matters, so rehearse it too.
Three things to practice saying, in some order:
- Restate the unresolved question. Whatever the listener raised that you did not fully answer, say it back. "You asked what an episode looks like when nothing goes wrong for her. I don't have a clean example of that yet."
- Confirm the specific material requested. Not the material you would like to send. If they asked for one short episode example, that is what you confirm. Not the season bible, not the script package, not the deck plus the pilot plus the show's website.
- Record the next action, and who owns it. Keep yours separate from theirs. "I'll send the ladder episode as a one-page on Thursday" is a proposed action by you. "Send it and we'll read it" is something they said, and it is worth more than anything you inferred. Interest and warmth are not a submission invitation, and they are not a timetable. A friendly meeting where someone leaned forward and said "this is fun" has told you they were engaged. It has not told you what happens next.
That distinction is the whole point of rehearsing the close. The temptation, in the last two minutes, is to convert goodwill into a commitment because the room feels good. Practicing the sentences beforehand makes it easier not to.
An example close to say aloud, for the invented series:
"Two things. You asked for a short episode example, so let me make sure the ladder one covers it — if you want a different kind of episode, tell me and I'll bring that instead. And I don't think I answered your question about what happens when the two residents are both right. I'll go back to that. I'll send the ladder episode on Thursday; that's on me, not on you."
Notice what is not there. No request for a decision. No timeline attributed to the person across the table. No bundle. The listener asked for one episode and got one episode.
This is not a script for outreach, and it is not a rule about how anyone else should behave in a meeting. It is your half of a conversation, practiced so that it survives contact.
The revised route card, and the close to practice tonight
Here is what the invented route card looks like after the interruption, because the interruption taught the card something. The engine moved to the top and the chronology was demoted to a clause:
One object, two legitimate needs, decided in public at the desk. A new caretaker runs a building's repair desk; she does not own the tools, only the order. She arrived in the pilot. That is the last thing you need to say about the arrival.
The first draft had the arrival first because the pilot has the arrival first. That is the classic recital instinct: following story order instead of explanation order. The revision says what the show is and files the origin as a supporting fact. You will only find that out by saying it while someone interrupts you.
So here is the practice to run, and it takes half an hour.
Say the three anchors out loud from memory. Have your partner cut in with "what happens in an ordinary episode?" Answer in three sentences. Name the anchor you just covered. Resume at one of the two return points. Then have them ask for the close: one short episode example, nothing else. Give it, confirm that it is the item they asked for, and state your own next action without attaching a promise to theirs.
Then write down the place where you got tangled. That is the thing to work on — not the smoothness, and not the elimination of pauses. A stumble you understand is worth more than a recital you cannot interrupt.
Frequently asked questions
What should a speaker memorize instead of the slide order?
A route: a small number of points reachable from more than one direction. For most series, three anchors: the situation and its pressure, the people or format, and the recurring reason to watch. Write them as fragments, not full sentences, so the card does not become a script to read.
How can you tell whether an ordinary episode example is separate from the pilot?
The example should not repeat the setup. If it could still be the pilot with different names, the engine has not been found. A representative episode contains no arrival, first day, or orientation; it tests the recurring tension, such as one object with two incompatible uses.
What should happen after an interruption during rehearsal?
Answer the question in about three sentences. Then name the anchor the interruption already covered. Resume at the next useful point, not the next slide. Two possible return points are the engine then forward, or back to the pilot compressed, depending on what the listener still needs.
What is worth recording after an interruption rehearsal?
Not zero pauses or an answer matching the plan. Record where the show became genuinely hard to explain, which anchor was repeatedly missed, and which question forced an improvised version of the series. If the hard part is a real hole in the show, put it in development notes rather than learning to talk around it.
How should the close of a pitch be practiced?
Practice three moves: restate the unresolved question, confirm the specific material requested rather than a bundle, and record the next action with its owner, keeping your action separate from theirs. Interest or warmth is not a submission invitation or a timetable.