Treatment, Script Response, or Craft Note: What Does This Commercial Pitch Need?
Treatment, Script Response, or Craft Note: What Does This Commercial Pitch Need?
Someone asks you for a treatment. The word arrives with a script and a deadline and no further explanation. It might mean a complete directorial proposal for the whole spot. It might mean a short note about the cut into the product shot. Both get called a treatment by somebody, and neither length tells you which one is wanted.
What tells you is the decision the other person is still trying to make. If they haven't settled how the film should feel, they need your interpretation, and enough of it connected for them to judge. If they've settled that and only want to know how a written beat will play, they need a response to the script, not a second film underneath it. If they have one specific craft question, they need an answer to that question with enough context attached to make the answer arguable.
So the useful response answers the decisions actually open. Not the longest document anyone would accept under the name "treatment," and not the shortest one either — a three-line note that leaves the reader unable to judge what you're proposing isn't disciplined, it's unfinished.
This is about the document going out. The companion piece on briefs, scripts, treatments and storyboards deals with the decisions carried by the material coming in; this one starts where that leaves you, with the material read and something owed back.
Ask what the recipient still needs to decide
The request is usually the best evidence you have, and it's usually thinner than it looks. Read what actually came with it. Is there a script? Is any part of it marked settled? Is there a board, a budget, a previous film they liked? Whose name is on the email, and do you know what that person decides?
Then look for the open question. Three things commonly remain open, and they're different sizes:
- how the whole commercial should be interpreted;
- how particular written beats should be realized;
- what to do about one craft element — a performance, a cut, a piece of sound.
When the request doesn't clearly point at one of them, ask the person who owns the commission. That's not a weak move; it's cheaper than a day of writing the wrong document. What you shouldn't do is infer the scope from a filename, a familiar label, or the length of the last job they liked. Labels don't travel well between companies. What one place calls a treatment, the next calls a director's statement. The distinctions here are about decisions, not vocabulary, so check the vocabulary with whoever is using it.
Here is an invented job to make the three sizes concrete. A brand, Norvik, is launching a stand mixer with a thirty-second spot. The script is written in fourteen numbered beats. Beats one through eight are story: Ines comes home late, opens a cabinet holding two jars, a box of pasta and the mixer on the top shelf, takes the mixer down, ties her hair back, sets the bowl on the base. Beats nine through fourteen are the demonstration and the close — her reach for the flour, the hook turning, batter pulling into a spiral, the bake, the plate, the product lockup. The mixer is already in her kitchen; the spot isn't about buying it.
Three requests can land on that same script:
- The brand team writes: "Send us your treatment."
- The creative director writes: "Walk us through beats four and nine. Everything else is written and we're not reopening it."
- The producer writes: "Send a note on how we get from the story into the demo."
Same script, same thirty seconds, three different documents — because each leaves a different decision open. None of this is drawn from a real job, and none of it is a claim about how any particular company labels its paperwork.
Choose a full treatment when the choices depend on one another
The first request leaves the whole interpretation open, so the response takes a position on the whole thing. That doesn't mean every department gets a paragraph. It means the choices that lean on each other get explained together.
In this spot, several do. Suppose the film is quiet: handheld, close, natural light, a night kitchen that sounds like a night kitchen. That stance decides things downstream. The performance stays small because the camera is close enough to see small. The cabinet beat has to be sparse without being sad, because a sad kitchen changes what the mixer means when she reaches past the pasta for it. And the demonstration becomes the one passage where the machine is the loudest thing in the film — which is a decision about sound before it is a decision about editing.
Take the other stance — stylized, locked off, designed frames — and the same beats want different answers. The performance has to get bigger to survive the distance. The cabinet's few contents become a composition rather than a mood. The demonstration stops being a turn, because the whole film was already formal.
Those aren't two checklists. They're two interpretations, each committing you to consequences you should say out loud. A treatment reading "handheld, warm palette, tactile sound, natural performance" has named four moods and connected none of them. A treatment saying the camera moves until the mixer starts and then stops has told the reader what the film believes.
Scope follows those dependencies. If the interpretation genuinely needs a line about music, include it. If the product lockup is fixed by the client and can't move, say so and explain how the rest of the film sets it up rather than proposing a new one. And even a treatment that's mostly argument has to carry the story — not every beat, but enough that someone reading their fifth document this week knows what they're judging.
A treatment becomes excessive when it reopens something the recipient settled and hasn't asked about. If the brand has already locked the ending and the track, three pages re-proposing the ending isn't thoroughness. It reads as not having listened, and it spends attention that was going to go on the part that was actually open.
Keep a script response or craft note narrow but intelligible
The other two requests are smaller, and both carry a version of the same trap: narrow doesn't mean context-free.
The script response
The second request covers two beats, with everything else closed. Your job is to say how you'd play those two and why — without smuggling in a whole interpretation.
For beat four, the answer depends on what beats one through three have already done. If they've shown Ines arriving, from the front, taking off a coat, the audience knows her, and beat four can afford to stay on the shelf and let her be a shoulder and a hand. If they haven't, that same shot is your only introduction to her and it can't carry the load. So the response states its assumption about the first three beats in a sentence and answers. That's the context it needs. It doesn't need a paragraph on the whole film.
For beat nine, the answer depends on a stance rather than a fact. Is this the machine's film or her hands' film? Flour hitting the bowl and the hook turning can be shot as engineering — clean, close, the product doing exactly what it should — or as hands, with the machine half out of frame and the work in the foreground. Both are defensible. Neither can be judged if the response doesn't say which one it's doing, and the request doesn't settle it. So say it. One sentence, then the answer.
If a closed beat has to change for your reading to hold, name it and ask. That's a question for whoever holds the script, not something to settle quietly in a subordinate clause.
The craft note
The third request sounds like the smallest one. One cut. It isn't quite, and the reason is worth understanding, because the same shape shows up constantly.
Beat eight ends with the bowl going down on the base. That gives you a sound: bowl on metal, a small ring. Sound is the cheapest transition available. Cut on it. The mixer picks up the note, the demonstration starts, and the film crosses from story to product without anyone rewriting anything.
There's a better-looking option, and it costs something. A match cut on rotation — the arc of Ines's hand into the turning of the hook, motion into motion, so the two halves of the spot feel continuous. It's a lovely move. But beat eight as written has no arc to match: it ends with the bowl going down, not with anything turning. So the match cut requires beat eight to change, and beat eight is a written beat.
That's the dependency. A question about a cut is partly a question about what the preceding beat contains, because the cut doesn't only follow the action — it decides what the action has to be. The note says that plainly: here's the transition that works with what's written; here's the one that's better and what it would cost; the cost is a script decision, so it needs a yes or a no before the note is finished.
What the note must not do is become the treatment. It doesn't need the ending, the casting or the music. It needs one line of premise — the demonstration is where the film changes register, say — borrowed from an interpretation that already exists or supplied in a sentence. One line, then the cut.
That premise will usually settle the choice by itself. Motion into motion argues the film is continuing, not changing modes. If your premise is the opposite, the sound cut is the one that agrees with you.
Agree on the object and the boundary before polishing it
Once you know what's open, write the scope down in ordinary language — before you polish, ideally before you write much at all. The test is whether someone outside the conversation could read the scope and know what they're about to get.
Four things, in plain words: who reads it, what decision it answers, what material it works from, what it doesn't cover. For the fictional job above, that might read:
Treatment. The whole film, beats one to fourteen, with a position on how the night kitchen, the performance, the sound and the demonstration hold together. Assumes the script is open.
Script response. Beats four and nine only. Assumes beats one to three and five to fourteen stay as written, that the ending and track are settled, and that the cabinet contents are locked. Covers how those two beats would be played and what each is doing inside thirty seconds. Assumes the audience has already met Ines by beat four.
Craft note. The transition from beat eight into beat nine. Assumes the demonstration is where the film changes register. Excludes casting, music and the ending. Flags one script question — whether beat eight is open — because the answer changes the cut.
Notice what those sentences don't do. They don't state a page count. "Six pages" tells a reader nothing about what's inside or what it's for. "The cut into the demonstration, assuming the rest of the film is settled" tells them everything they need before they start reading. Let extent follow from the decisions covered instead of standing in for them.
Then compare the scope against the actual request and look for duplication. In the job above, requests two and three both touch the cut into beat nine. If both are running — plausibly, if the creative director asked for one and the producer asked for the other — say so rather than doing the same thinking in two documents that reach two different readers. Either put that material in one place and point the other document at it, or agree that only one of the two goes out.
Duplication is the cheap failure. The expensive one is quiet expansion. You start answering the transition question, find it depends on a premise nobody has settled, and add three sections resolving the film's interpretation because you needed the answer. That may well be the right thing to do — but it's a different document, and the person who asked for one cut should hear about it before they receive a treatment.
End on the question, not the label
Whichever of the three you write, the first line should be the question the document answers. Not "Treatment — Norvik stand mixer." Something like: how the story hands off to the demonstration, assuming everything but beat eight is closed. Now the reader knows what they're judging, and so do you.
That line is also the thing to settle before you spend a day polishing. Scope agreed late is scope rewritten, and a treatment that quietly became something else is the version that gets read as though it were what was asked for.
Precision here isn't stinginess. A narrow note still needs the context that makes its one proposal understandable: the premise line, the beat it attaches to, the small consequence of getting it wrong. What it doesn't need is the rest of the film.
And if the recipient's next question turns out to be "yes, but what about the ending?" — you've learned what to write next, and you'll be asked for it. That's a better outcome than guessing, and it costs one more email.
Frequently asked questions
How can I tell whether a request is asking for a treatment, a script response, or a craft note?
Look at which decision is still open: whole-film interpretation, specific written beats, or one craft element. If the request does not clearly point to one, ask the person who owns the commission rather than inferring scope from a label or filename.
What should a scope statement for one of these documents include?
Four plain things: who reads it, what decision it answers, what material it works from, and what it does not cover. Page count is not a substitute because it does not tell the reader what is inside or what the document is for.
When does a treatment become excessive?
When it reopens something the recipient has settled and has not asked about. If the ending and track are locked, three pages re-proposing the ending reads as not listening and spends attention meant for the open question.
What should a craft note do if its proposed cut requires changing a written beat?
Name the dependency and ask for a yes or no. The note can say which transition works with what is written and which better option would cost a script change, but the script decision must be settled before the note is finished.
What should I do if two requests touch the same material?
Say so rather than doing the same thinking in two documents that reach two different readers. Put the material in one place and point the other document at it, or agree that only one goes out.