Present a Commercial Treatment Without Reading It Aloud

You finished the treatment. It reads well on its own — that was the point of writing it that way. Then you stood up in an empty room, opened page one, and started saying what was on page one. By page four you could hear it. You weren't presenting anything. You were reading, slowly, out loud, to an audience that reads faster than you talk.

The fix isn't a better script for the same recital. It's accepting that the document already does most of the work, and that the live version has one job the document can't do: carrying timing, emphasis and the relationships between choices — the things a static page flattens into equal weight. A treatment is the written proposal for the film: the interpretation, the beats, the look, the sound, the reasoning behind each. It's good at all of that. It's bad at rhythm.

So the spoken route is deliberately incomplete. You will skip pages. You will point at one and tell people to read it later, slowly. You will spend thirteen uncomfortable seconds saying nothing, on purpose, because the silence is the argument. And afterward the document still has to hold up alone, because some of the people who matter will read it without you in the room.

Everything below runs through one example. It's constructed, not a production: a fictional forty-five-second spot called The Long Pour, for a fictional roaster, Halloway Coffee. None of it has been rehearsed, recorded or shown to anyone. Treat its numbers as the numbers I'd write into a plan, not measurements taken from a call.

1. Say what the film is before you say what's in it

There are two openings available and only one of them is a presentation.

The first is the contents tour: "Page two is the exterior. Page three moves us inside. Page four has the counter diagram." It proves the document is complete, which the client can see. It tells them nothing about what they're about to watch.

The second says what makes this version of the brief a particular film. For The Long Pour, it's one sentence: Forty-five seconds about a woman making a coffee for somebody who isn't coming, and drinking hers anyway, with no sadness anywhere in the frame.

That sentence is the whole route. Everything you choose to show afterward is evidence for it.

It also frees you from the document's order. The live route can move through the material however the argument needs — the client can find the underlying explanation later, as long as you tell them where it lives. Name the pages out loud as you go ("the stool reasoning is on page four"). That's not housekeeping; it's the locator that makes a non-linear presentation safe.

2. Choose the moments that only a voice can carry

The test for any spoken line is simple and slightly brutal: does saying it aloud tell the client something the page already tells them? If yes, cut it from the route. Not from the document. This is the mistake that turns presentations back into recitals — the director, worried about leaving something out, deletes useful leave-behind text and says it into the room instead. The document loses the sentence and the room gains nothing.

Three kinds of moment pass the test:

• A performance turn whose timing can't survive as prose.
• A reveal that depends on the audience arriving slightly late.
• An image-and-sound relationship where the length or the overlap is the decision.

Here's how that splits for The Long Pour. The document is eleven pages; the spoken route visits five of them.

Page 4 stays on the page. It carries this paragraph, and it's a good one to read twice:

The empty stool is at the end of the counter, against the wall, not in the middle. A middle stool reads as a seat somebody got up from. An end stool reads as a seat somebody chose. The film depends on that difference, and the difference only survives if the camera never moves off it.

That's spatial reasoning. It rewards a second pass. A client can look at the plan, look at the paragraph, look back at the plan. Saying it aloud spends twenty seconds and leaves nothing behind, so it doesn't go in the route. It stays where it works.

The hold and the smile get performed. Beat three is the thirteen-second locked-off wide shot at 0:23: the woman behind the counter, the full cup at the end stool, street noise through the door, nothing happening. Beat four is at 0:36 — she looks at the stool, and about half a second later she smiles.

Neither of those can be demonstrated with an adjective. "She smiles a beat too late" is accurate and useless. So don't say it. Say the order, and let the pause do the work:

She looks at the stool... [pause] ...and then she smiles.

The pause is the demonstration. Two directors will land that gap differently, and hearing two versions is the entire point — it's the difference between a woman seeing something and a woman remembering something. The page can describe the delay. Only the room can hear how long it is.

The hold is the same idea with a higher cost. Stand in it — and where you can, play the room tone and street noise under the count, because the sound is half of what those thirteen seconds are. If playback isn't available, count the thirteen seconds in silence and say as much: that version demonstrates the duration of the beat and nothing about its texture. Either way it will be uncomfortable. That discomfort is most of the information the client needs, and what it measures is duration and attention — how long thirteen seconds occupies a room, how much patience the shot is asking for. It is not a report on how an audience will feel. The client's discomfort now is a rough proxy for the size of the ask, not evidence about the finished spot, and it's the ask they're deciding about: whether the shot survives the edit.

One caution, and say it if anybody asks: performing a pause demonstrates an intention. It is not a claim that a production test has succeeded. The actor, the grade, the sound mix and the audience's patience all get a vote later. "Here's the rhythm I'm proposing" and "we tried it and it works" are different sentences, and only one of them is true at this stage.

3. Plan the join between showing and listening

Most presentation problems aren't in the material. They're in the seams.

Three habits do most of the work. Say what you want noticed in one sentence before the clip or the page, then stop talking. Never talk over a sound example whose sound is the point — the client is listening for something and your voice is noise in front of it. And finish one explanation before asking anyone to read the next. A page in front of someone and a sentence in their ear compete.

Then mark a place where discussion can enter. Not "we'll take questions at the end" — a particular stop where a question is genuinely useful and where the answer might change the proposal. Page eight, the last frame and tag, is where the presentation ends and the closing Q&A begins; it isn't the first place a question is welcome.

For The Long Pour, that stop is after the hold, before the smile. The question the client will ask is "is thirteen seconds too long?" That question isn't an interruption; it's the creative decision, and it deserves the room's full attention rather than the last four minutes of the meeting. Take it there.

Which means the way back has to be rehearsed too. When the question resolves, you don't restart, and you don't rush the remaining pages to make up time. You say where you are: We stopped on beat three. Next is page five, the smile. One sentence, and everyone re-enters the argument instead of re-orienting.

Worth saying out loud in the room, too: a question can change the proposal without changing the brief. If the client says "let's try eight seconds," that's a change to your treatment. It isn't automatically a change to what they asked for. Directors who blur those two in the moment end up re-doing work nobody requested.

4. Rehearse what the other person actually receives

On a remote call the route has a second failure surface, and it isn't the material — it's the setup. What the recipient sees and hears is not what you see and hear, and the gap is widest exactly at the moments you built the presentation around.

Before the call, in the app and on the machine you'll actually use, check the small number of things this particular presentation depends on. Does the audio of your sample reach them, or only you? Sharing computer sound is usually a separate control from your microphone, and its name and location differ between tools and between versions of the same tool. Check yours, in your setup, rather than trusting a habit from a different one. Does the thirteen-second still hold up when compressed and shared, or does it break apart? Can you stop media the instant someone starts talking, or will you be talking over a sample you can't silence?

Then build the failure branch into the route, before you need it.

Suppose the planned sample is thirteen seconds of room tone and street noise — the actual sound of beat three — and playback fails. The question that sample was answering was "does thirteen seconds feel long?" A different reel, or a spot you happen to like, answers nothing; it's an unrelated substitute and the room can tell. The right fallback is the same question through a different instrument: an annotated still of the empty stool with the timecode and frame count burned into it, plus you counting thirteen seconds aloud. Same question, less of it — and say what's missing, because the sound was part of the point.

If your team writes down how remote reviews are run, keep that checklist separate from the treatment, and check the controls against the version you're on at the time you write it. Interface details go stale fast, and a screenshot from last year is worse than no screenshot. Nothing in this section has been tested here; the branch above is a plan, not a report of a call that happened.

5. Leave a document that doesn't need you

The spoken route adds. It never carries.

The check is concrete. Hand the document to someone who wasn't in the room and ask them one question: what choice is being proposed here, and where does the support for it live? If they can name the interpretation and find the reasoning behind it — the stool paragraph, the thirteen seconds, the smile — then the leave-behind is doing its job. If they can only follow the beats and not the argument, the detail is sitting in your mouth instead of on the page, and it needs to move.

Rehearse the joins, not just the opening. Most directors run the first ninety seconds four times and improvise from there, which is precisely where the page-by-page recital creeps back in. Practise the transition out of the hold, the transition back from a question, the sentence that hands page four to the reader.

And be honest about what a rehearsal proves. One run-through with one colleague is a readability check on the document and a timing check on you. It is not an audience study, and it isn't evidence about how a client will respond. Record what you actually observed — where you ran long, where the pause felt wrong, where the collaborator got lost — and leave it at that.

The measure of the whole thing is narrow. Did the presentation make a choice clearer than a second reading of the same paragraph would have? If yes, it earned its place and the document is stronger for what you left in it. If no, you have a good treatment and a reading of it. That's not a failure of the writing. It's just not a presentation yet.

Frequently asked questions

If the treatment reads well on its own, what does presenting it live add?

One job the document can't do: carrying timing, emphasis and the relationships between choices — the things a static page flattens into equal weight. A treatment is good at the interpretation, beats, look, sound and reasoning; it's bad at rhythm. So the spoken route is deliberately incomplete. You skip pages, point at one and tell people to read it later, and you may spend thirteen uncomfortable seconds saying nothing on purpose because the silence is the argument. Afterward the document still has to hold up alone, since some people who matter will read it without you in the room.

How do I choose which moments to perform?

Apply the test: does saying it aloud tell the client something the page already tells them? If yes, cut it from the route, not from the document. Three kinds pass — a performance turn whose timing can't survive as prose, a reveal that depends on the audience arriving slightly late, and an image-and-sound relationship where the length or the overlap is the decision. In the worked example that means the thirteen-second hold and the delayed smile get performed, while the counter floor plan stays on the page, because that paragraph is spatial reasoning that rewards a second pass and saying it aloud leaves nothing behind.

Does performing the hold prove the shot works?

No. Performing a pause demonstrates an intention, not a claim that a production test has succeeded; the actor, the grade, the sound mix and the audience's patience all get a vote later. In the example, counting the thirteen seconds measures duration and attention — how long the beat occupies a room, how much patience the shot asks for — not how an audience will feel. The client's discomfort now is a rough proxy for the size of the ask they're deciding about. "Here's the rhythm I'm proposing" and "we tried it and it works" are different sentences, and only one of them is true at this stage.

What should I do if a sample fails to play on a remote call?

Build the failure branch into the route before you need it. First check, in the app and on the machine you'll actually use, whether the audio of your sample reaches them — sharing computer sound is usually a separate control from your microphone, and its name and location differ between tools and versions, so check yours rather than trusting a habit from a different setup. Then, if the room-tone sample fails, don't substitute an unrelated reel; that answers nothing and the room can tell. Use the same question through a different instrument: an annotated still of the empty stool with timecode and frame count burned in, plus you counting thirteen seconds aloud — same question, less of it — and say what's missing, because the sound was part of the point. The article notes this branch is a plan, not a report of a call; nothing in that section was tested.

What does a rehearsal prove, and how do I check the leave-behind?

One run-through with one colleague is a readability check on the document and a timing check on you — it is not an audience study and isn't evidence about how a client will respond. Record what you actually observed: where you ran long, where the pause felt wrong, where the collaborator got lost. For the document, hand it to someone who wasn't in the room and ask what choice is being proposed and where the support for it lives. If they can name the interpretation and find the reasoning behind it — the stool paragraph, the thirteen seconds, the smile — the leave-behind is doing its job. If they can follow the beats but not the argument, the detail is sitting in your mouth instead of on the page and needs to move.

Further reading

• Build a Live Treatment-Demo Feed With Preview and Program Kept Separate — When the remote route includes showing a demo, this covers separating what you prepare from the outgoing feed and checking what the client actually receives.
• Write Speaker Notes That Support an Explanation, Not a Recital — Sorting the spoken route: what must be said exactly, what you can phrase on the day, and what belongs on the page rather than in your mouth.