Ask for the Outside Read Your Film Pitch Actually Needs
Ask for the Outside Read Your Film Pitch Actually Needs
You send the deck to four people and ask what they think. You get back four different films. One wants the middle tightened. One loved the middle. One asks why the protagonist is passive. One asks a question the deck answers on page three, which means they skimmed, which means you now have to weigh their note against your suspicion that they skimmed, and you have no basis for doing that either.
Four opinions, no evidence. The problem isn't that the readers were wrong. It's that nobody was asked the same question, so nothing they said can be added up.
There's an order of operations that fixes this. Name the uncertainty first. Then choose the person, the materials, and the conditions that can actually expose that uncertainty. A read is an instrument. It measures what you built it to measure and mostly nothing else, and the most expensive mistake in this process is finding out afterwards which one you built.
Write the question the outside read must answer
"Is it good?" is not a question. It's a request for a verdict, and verdicts come back shaped by whatever the reader already cares about. You can't act on one.
Most pitch uncertainty falls into three families, and they need different questions.
Comprehension. What does this document say when you're not in the room to defend it? A usable question: Read this once, at normal speed, without me. Then retell the film in the order you received it, in a few sentences, and mark the exact place you first understood where you were.
Formal legibility. Does a specific choice — a structure, a point of view, a visual proposal — come across on the page? A usable question: This deck proposes X to produce effect Y. Reading only what's here, does X produce Y? Quote the passage that decided your answer.
The package. Is the thing you're offering legible as an offer? A usable question: Here is the current status — what's attached, what isn't, what the budget band is. Given what you do all day, could you say yes to this, and what would have to be true first?
Each of those asks the reader to report something they can actually observe: what they understood, what the material did, what their own job would require. None of them asks for taste.
Then there's a condition question that people skip. Will the recipient read this alone, or will you be presenting it? A deck that carries a live pitch and a deck that has to work by email are two different documents with two different jobs, and a reader who saw your presentation cannot tell you how the deck reads. If you plan to be in the room, say so in the brief, so the reader doesn't hand you a comprehension report about a situation that will never happen.
And don't fold several jobs into one quick favor. "Take a look and tell me what you think" gets you a response that answers none of the above, phrased kindly enough that you can't tell.
Choose relevant experience without demanding a universal expert
The right reader is the one whose position lets them see the specific thing you named.
For a comprehension question, you want someone who has not already been coached through the project, and who can read under the conditions the real recipient will face. That may mean a reader who knows your genre's conventions, or a reader who deliberately doesn't. Both are defensible. What isn't defensible is a reader who has heard you talk about the film for two years, because their comprehension is now partly your comprehension.
For a formal question, look for relevant craft experience — someone who has worked in the specific territory the choice lives in. Someone who has cut a film with two timelines can tell you whether a two-timeline device reads on paper. Somebody who loves movies can tell you whether they enjoyed it.
For a package question, identify the actual responsibility being assessed. If the question is whether a producer could take this on, the useful reader is someone whose job includes that decision, reading the current status. That's a different person from the craft reader, and their notes will be about attachments and comparable titles, not about act two.
Now the part people resist: say what this person cannot establish. A trusted friend is not a festival programmer. A paid reader is not a buyer. One reader is not an audience, and ten readers are still not an audience — they're ten readers. If you ask someone to guess what "the market" wants, you've asked them to do something no individual can do, and you'll get a confident answer anyway.
Decide what the reader should know before opening the file
This is where the two kinds of read separate, and where people break the instrument without noticing.
A cold read receives the material and the context the eventual recipient would genuinely have. That means the deck as you'd send it, plus whatever a stranger in that position would already know. It does not mean a cover note explaining the ambiguity on page four. If your deck only works with a note attached, you've just learned something real about the deck, and you learned it by leaving the note off.
An informed review receives the deck plus whatever is needed to judge the named decision: the specific scene, the written sequence, the visual reference, the honest package status.
The distinction is about interpretation, not about logistics, and it does not extend to everything. Never withhold safety information, access details, confidentiality terms, deadlines, or the actual task. "I didn't tell them the shoot dates so the read would stay pure" is not discipline. It's just a worse brief.
Nor does it extend to material you're embarrassed by. There's an instinct to leave out the weak scene on the theory that its weakness will distract from the real question. That instinct is usually wrong. The reader's reaction to the weak thing is data, and if you didn't ask, they'll volunteer it anyway.
One honest limit here: if the deck cannot survive being sent without a long explanatory email, that is a finding about the deck, and it belongs in your revision notes rather than in your reader's inbox.
Agree on the work and the useful return
Before anything is read, get these on the table, even in a short message:
- The files and the version, named specifically.
- The question, in one or two sentences.
- The scope — what's in and what's out. "Pages 1–20 only" is a scope.
- The return format and the timing.
- Confidentiality, in whatever form fits the situation.
- Compensation, where it applies. Working out what that number is sits outside this article; that you've settled it before the read does not.
Then describe the return you actually want. The most useful shape is an account of what the reader understood, plus the passage that produced it. I understood the sale as a betrayal because the kitchen scene reads as tender right up until the offer. That's an observation with a location. You can act on it.
Ask them to label the rest: interpretations and suggestions. A suggestion — swap this scene for that one — is not worthless, but it's a statement about the reader's taste and instincts as much as about your draft. When suggestions arrive unlabeled, they tend to get treated as findings, and then you spend a month fixing something that wasn't broken.
A short written response is usually enough for a comprehension question, and it has one large advantage: it's a record of what the reader thought before you said anything. A conversation is a different instrument. It lets you supply context the instant confusion appears, which is excellent for development and terrible for measurement. If you want to know what the deck does alone, don't be on the call.
Separate the read from the development discussion
Capture the initial response before you explain the film. Then read it before you react to it, and resist drafting a reply while you're still scrolling.
Only then have the conversation. And here's the thing worth doing carefully: as you supply context, note what changes. If the reader's account of the timeline snaps into place the moment you say "the second thread is the earlier one," that's information about the deck — it needed you. It is not evidence that the deck was fine all along.
Which means you should never report a clarification reached in conversation as proof that the document was self-sufficient. It wasn't self-sufficient. You were there, and you were doing work the deck couldn't do.
Finally, keep the read from quietly turning into a commission. When a reader says the middle is soft, they've given you an observation. Deciding what to do about the middle is your job, and it's a different process — one that starts with weighing their observation against everything else you know and probably ends with a fix they never proposed. A reader who offered one diagnosis is not a co-writer, and expanding their brief without agreeing to it is how a free favor becomes an awkward invoice.
One pitch, two briefs
The rest of this section is invented. Nettle Season is a fictional feature, the readers below don't exist, and neither brief has been sent. No one has responded to either one, so nothing here is a result. What follows is a demonstration of how the same pitch generates two different requests.
Nettle Season moves between 1973 and 2019 in a fictional coastal town. Ada works a saltmarsh hay farm in the earlier thread; Ruth, her granddaughter, has come back to sell the same land in the later one. The deck proposes to shoot both periods in the same aspect ratio and with the same lens set, separating them only through color — a warmer, slightly desaturated treatment for 1973, a cooler and cleaner one for 2019 — plus a recurring fixed shot of the tidal channel at dusk, repeated in both periods from the same position.
The intention behind that proposal is specific: the two periods should read as simultaneous rather than sequential, as one place under continuous pressure. The recurring shot is the hinge. The color split does the rest.
Brief A. To a reader who has never heard of the project.
What I'd like from you: read the attached deck once, at normal speed, without me in the room and without looking anything up. It's the version I'd send to someone I'll never meet.
Then send me, in writing, before we talk:
- The film as you understood it, retold in the order you received it, in a few sentences.
- The exact place in the deck where you first understood you had moved to a different period, quoted, or a note that you never did.
- Anything you had to decide for yourself along the way.
No suggestions, please. I'm not asking whether it's good or what to cut. I'm asking what the document does on its own.
Brief B. To a filmmaker with two-timeline work in their credits.
Attached: the deck, plus the matched kitchen-table scenes written out — the 1973 argument over the marsh rights and the 2019 argument over the sale — which are deliberately rhymed in blocking.
Here's what I'm trying to achieve. The two periods are meant to read as parallel, not as a flashback subordinate to the present. Equal weight, same place, same hour. The deck proposes to carry that with a warm/cool color split plus one repeated fixed shot of the tidal channel.
My question is whether that proposal actually does it. Specifically: does the warm/cool division read as parallel, or does it import the nostalgia convention and push 1973 into memory? Point me at the passages in the deck and the scene pair that produced your answer, and mark anything you're proposing as a change rather than an observation.
I'm not asking whether the deck reads cold. You already know too much for that.
They're joined by one pitch, one deck version, and one device. They are not interchangeable, and the difference isn't politeness — it's what each response can establish.
If the editor in Brief B says the warm split imports nostalgia, that is not evidence that a cold reader got lost. They were told what to look for. If the cold reader finishes the deck and can't say when the period changed, that is not evidence that the color proposal is wrong; they never saw the scene pair, and the deck's signal may simply be failing to land for a different reason than the one you're investigating.
And one more constraint that costs people a reader they liked. You cannot get both readings from one person in one pass, because the moment you say "watch for the two timelines," the cold read is gone. The cold read is a single-use instrument with that reader. You can brief them again later for the informed review, and that's a reasonable use of a good reader, but you'll never get their unprompted account of this deck again.
One caveat about the method itself. The reasoning above is editorial judgment, not the result of examining practitioner accounts of cold reads or project-specific feedback. That work hasn't been done here, and doing it later would be the thing that could change how these briefs are written — most likely the return format, and possibly the reading conditions. It wouldn't turn a good read into approval from anyone.
The brief you can send today
Strip it to this and fill it in.
READER BRIEF — [project], deck v[N]
What I need to learn:
[one uncertainty, in a sentence you could answer]
What I'm sending you:
[files, version]
What I'm not sending, and why:
[scope, and anything you deliberately withheld for the read]
Conditions:
[read alone / in a call with me; deadline if relevant]
What I want back, in writing, before we talk:
1. [what you understood, in your words]
2. [the exact place that decided it]
3. [anything you had to resolve yourself, and how]
Please label interpretations and suggestions separately.
What I'm not asking for:
[verdicts, rewrites, or questions about the package]
Timing: [date]
Confidentiality: [what applies]
Compensation: [as agreed]
The line that matters most is the first one. Everything else — who reads it, what they see, what they send back — follows from the single uncertainty you decided you needed to resolve. Get that wrong and the rest of the brief is just a more organized way to collect opinions.
Get it right and a single reader, reading once, can tell you something you couldn't have found out from four.
Frequently asked questions
Why can four readers of the same pitch deck produce notes that don't add up?
Because nobody was asked the same question. Each response is a verdict shaped by what that reader already cares about, so the notes address different films rather than one uncertainty the writer can act on.
What distinguishes a cold read from an informed review?
A cold read gets the material and the context the eventual recipient would genuinely have, without a cover note explaining ambiguities. An informed review gets the deck plus whatever is needed to judge the named decision, such as a scene, sequence, visual reference, or honest package status.
Can one person supply both a cold read and an informed review of the same deck?
No, not in one pass. Once you say "watch for the two timelines," the cold read is gone. A cold read is single-use with that reader; you can brief them again later for an informed review, but you won't recover their unprompted account of this deck.
What should a reader brief settle before the read?
The files and version, the question in one or two sentences, scope, return format and timing, confidentiality, and compensation where it applies. It should also ask the reader to label interpretations and suggestions separately.
What can't an outside reader establish, no matter how trusted or experienced?
A friend is not a festival programmer, a paid reader is not a buyer, and one reader—or ten—is not an audience. No individual can reliably guess what "the market" wants. The reasoning is editorial judgment, not the result of examining practitioner accounts or project-specific feedback, and doing that work later could change how briefs are written.