Build a Reusable Treatment Template That Leaves the Creative Decisions Empty

By pitch.dogFoundation12 min read20 September 2026

Advertising

The failure rarely looks dramatic. Someone opens last season's treatment deck because the deadline is Thursday, changes the client name on the cover, and keeps the spine: same page order, same confident sentences, same implied promises about casting, music and tone. By Friday the file makes decisions nobody in the room made.

The distinction that prevents this is plain enough once it is named: some parts of a treatment document can be reused, and some parts are decisions wearing the costume of infrastructure. Styles, containers, labels and note positions are infrastructure. Openings, promises and rationales are the film. A reusable template should carry the first group and leave the second conspicuously blank.

The line moves as the work changes. The useful skill is not memorising a list of which parts are which — it is learning to sort a document you already have, and to notice when a default is quietly arguing for a version of the film.

Separate reusable infrastructure from inherited answers

Take an existing treatment you have the right to reuse at all — your own, ideally empty of anything borrowed — and go through it asking one question about each element: would this survive a genuinely different brief unchanged?

What tends to survive:

Heading levels and the type hierarchy that makes a deck skimmable
Page dimensions and the grid that holds images in relation to text
Where source notes live, and how they are distinguished from the treatment's own argument
Media containers: image areas, video stills, audio cues
Labels such as Wardrobe, Location, Cast that name a class of decision
A running footer with project, page number and version

What tends to be an answer rather than infrastructure:

A director's statement
A casting promise
A music reference
A paragraph explaining the tone
A diagram of the intended edit
Any sentence that names what the audience will feel

The dividing line is not phrase quality; it is authorship. Infrastructure poses a question the team will answer. Inherited answers are questions that were answered on someone else's project and left in the file.

If the existing document is from a real shoot, the sorting has a rights step before a design step. Reusable structure — the capacity to arrange page jobs for a given brief, not the inherited habit of putting the mechanism page before the turning point — is a method. A client's logo, product photographs, script excerpt, name or commissioned illustration is not yours to carry forward without the right to reuse it. The blank template should contain none of it. Move illustrative content into a clearly separate demonstration file, and label it as an example so that nobody later mistakes a sample's language for a house position.

Define optional page jobs instead of a compulsory order

A template built around sections forces the same argument onto every brief. A template built around jobs does not, because a job can be fulfilled, fused with another, or skipped altogether.

A page job is a sentence describing what this page helps the reader understand. It is not a heading, and it is not a fixed slot in a sequence. Useful ones sound like:

What world the spot lives in
Whose story this is and what they want
What the product actually does
Where the turning point sits
What the scene has to hold, and for how long
What the audience should have understood by the last frame
What still has to be decided before this can be shot
Logistics: schedule shape, locations under consideration, delivery considerations

Write these as a menu rather than a ladder. Nothing requires every treatment to use every job, and nothing requires the jobs in the order the last project happened to use them. Keeping a residue of the previous sequence isn't harmless: if the template's page order has a "problem" before a "product," every brief now starts by establishing a problem, even the brief where the product is introduced at ease and the problem never appears. Convenience has quietly become a claim about the story.

Two mechanics keep the menu optional in practice, not just in the introduction:

Labels that describe a role, not a brand. "Demonstration," not "Kitchen table shot." "Turning point," not "the rejection." A label with the old project's content in it will pull the next brief toward that project even when the page is technically deletable.

A note on every job about what it costs. "Camera and edit implications — remove if not yet decided" is a real help. A page type that claims to be optional but whose removal leaves a hole in the argument is not optional; it's compulsory with better manners.

Leave prompts that require actual decisions

Templates usually fail in the same spot: the placeholder. A field that says "Add tone description here" invites a writer to paste the first competent sentence they think of. A field that asks a question that cannot be answered without a real decision does not.

Consider a default director's-introduction page. A bad version reads:

Our approach brings authenticity and cinematic craft to the brand's story, with a warm and modern sensibility.

Nothing here is an answer to this brief. It is a leftover from templates everywhere, and it sounds finished enough that a hurried director might leave it in, then find it describing a film they never intended. Replace the whole page with a short field:

What does the audience have to understand about these people that the brief does not already say?

The safest placeholder is not a weaker version of the answer. It is a question. A few principles for writing these:

Name the decision, not the flavour: "What changes in the product's behaviour on this page?" works; "Describe the product feel" does not.
Ask about response, not adjectives: "What is she responding to?" rather than "What is her attitude?"
Keep it short enough that it cannot be mistaken for prose.
Make the empty area obviously empty. A prompt in a distinct style — different colour, bracketed, flagged — cannot slide into a finished deck.

The test for any prompt is whether it could survive being sent to a client by accident. If it reads even slightly like treatment copy, it is a placeholder pretending to be finished.

Use two briefs that resist the same structure

A template cannot be validated by looking at it. It has to be applied to two briefs with genuinely different shapes. What follows is a worked pair of invented examples — teaching constructions, not client work, and not decks that have been produced.

Brief A: the container. A short product-led demonstration. A countertop food container closes with a press and a quiet click, and opens by pressing a release that lets the lid rise on its own. The film has to show the mechanism clearly enough that a viewer understands it without narration.

Brief B: the proposal. A performance-led quiet comedy. A man is about to propose on a walk home. His mother calls at the exact moment he kneels. The humour depends on a delay: the ring box is open, his partner hasn't noticed, and he has to wait, holding the pose, while the call goes on.

Run both through the same blank system — same grid, same heading levels, same jobs menu, same prompt style, and nothing else. Brief A selects: world (the kitchen surface and drawer that will be cleared), demonstration (the click and the lift, in a container built for close detail and a note about what changed between takes), and decision list (the still-open question of whether the release is heard or only seen). Brief B selects: world (the walk, the street, the ordinary evening), hold (the pose kept while the phone hums — a container whose job is duration and reaction), and decision list (whether the call is diegetic sound or only visible). Brief B skips the demonstration container entirely. Brief A has no reason for a hold page and drops it. Neither is more complete than the other.

That is the point, and also the limit of this sketch. Nothing here establishes that the template actually accelerates assembly, or that these two briefs would land as intended on a real shoot. What the exercise can show is narrower: which jobs each brief selected and which it skipped. It cannot show where a shared container helped or where a default imported an argument; those questions belong to a real application. When the two applications start to resemble each other — same number of pages, same placement of the turning point, same underlying claim about how products should be filmed — the template is making decisions it should leave open. Reordering pages is a legitimate fix. Removing a shared default is a better one.

One reusable page job is worth defending even here. A single page whose job reads what still has to be decided travels easily across both briefs precisely because it holds nothing: it collects whatever questions remain, and it closes a deck without pretending the questions are closed.

Save the blank system separately from its examples

A template rots by absorbing the project it was last used on. The way to slow that down is to keep the blank system and the filled examples in separate files with separate names, and to return every structural improvement to the blank one.

When a change works well on a live treatment, ask what part of it is a shape: a page role, a grid decision, a note position, a label convention. That part goes back into the reusable file. The sentences, images, names and promises stay in the example. If a document model supports versions, the blank system is the trunk and the examples are branches; if it doesn't, the discipline has to be maintained by habit and by naming.

Before storing the blank version, run this check:

Does this file contain any promise, name, quotation, location, permission or number that belongs to a specific job?

If yes, it is not blank yet.

Then confirm the file still preserves what should be reused. A useful structure that was removed along with a project-specific sentence is work thrown away. The blank version should still be recognisably your document: your heading hierarchy, your media containers, your jobs menu, your prompt style, your source-note convention.

And label unresolved prompts unmistakably. A blank treatment with the appearance of finished copy is the dangerous artefact; a blank treatment with visible questions is a genuinely usable starting point. Test the prompting style by opening the blank file cold, as if you had never seen the project. If you cannot immediately tell what still requires a decision, the prompts are doing too little.

The template is not the film. It is the part of the document that can be settled in advance so that the rest — the route, the imagery, the promises — stays unsettled until it is actually decided.

Frequently asked questions

What belongs in a reusable treatment template, and what should stay blank?

Reusable infrastructure includes heading levels and type hierarchy, page dimensions and grid, where source notes live, media containers, labels such as Wardrobe, Location, and Cast, and a running footer with project, page number, and version. Decisions to leave blank include a director's statement, a casting promise, a music reference, a tone paragraph, an edit diagram, and any sentence naming what the audience will feel. The test is whether the element would survive a genuinely different brief unchanged; infrastructure poses a question the team will answer, while inherited answers were answered on someone else's project.

How should a template handle page order?

Define optional page jobs as a menu rather than a compulsory sequence. A page job is a sentence about what the page helps the reader understand—what world the spot lives in, whose story this is, what the product does, where the turning point sits, what the scene has to hold and for how long, what the audience should understand by the last frame, what still has to be decided, or logistics. Use labels that describe a role, not a brand, such as 'Demonstration' rather than 'Kitchen table shot.' A default 'problem' before 'product' can make every brief start by establishing a problem, even when the product is introduced at ease.

What makes a useful placeholder in a template?

A useful placeholder is a question that requires an actual decision, not a weaker version of the answer. Name the decision, not the flavour: 'What changes in the product's behaviour on this page?' works; 'Describe the product feel' does not. Ask about response, not adjectives: 'What is she responding to?' rather than 'What is her attitude?' Keep it short enough that it cannot be mistaken for prose, and make the empty area obviously empty with a distinct style, brackets, or a flag. If a prompt could be sent to a client by accident and reads like treatment copy, it is a placeholder pretending to be finished.

How can I test whether a reusable template actually leaves creative decisions open?

Apply it to two briefs that resist the same structure. The body's invented pair is a product-led container demonstration and a performance-led quiet comedy about a proposal interrupted by a phone call. Run both through the same blank system—same grid, heading levels, jobs menu, prompt style, and nothing else—and see which jobs each brief selects and skips; neither is more complete. The limit is that this sketch does not establish that the template accelerates assembly or that the briefs would land as intended on a real shoot. It can show selected and skipped jobs, not where a shared container helped or where a default imported an argument. If two applications start to resemble each other in page count, turning-point placement, or underlying claim, the template is making decisions it should leave open.

How should the blank system be stored and checked?

Keep the blank system and filled examples in separate files with separate names, and return every structural improvement to the blank one. When a change works on a live treatment, ask what part is a shape—a page role, a grid decision, a note position, a label convention—and put that in the reusable file; sentences, images, names, and promises stay in the example. Before storing the blank version, check: does this file contain any promise, name, quotation, location, permission, or number that belongs to a specific job? If yes, it is not blank. Confirm it still preserves your heading hierarchy, media containers, jobs menu, prompt style, and source-note convention. Label unresolved prompts unmistakably; a blank treatment with visible questions is usable, while one that looks like finished copy is the dangerous artefact. Also, client logos, product photographs, script excerpts, names, and commissioned illustrations are not yours to carry forward without the right to reuse them.