Turn a Commercial Deliverables List Into Creative Requirements

A deliverables list is written in the language of files. Durations, aspect ratios, language codes, container formats, and a count somewhere at the bottom. A treatment is written in the language of what a viewer sees, hears, and understands before the film ends. The first job with the list is translation.

The unit that does the work is not the filename. It's a creative requirement: a sentence about what this version has to make a viewer understand under its own constraints. A shared requirement belongs to every version—the viewer registering the recipient's wrong reading of the doorbell before the parcel is revealed. A version-specific requirement, or exception, is what one version needs that the shared approach can't give it. "15-second portrait" is not a requirement. "In the 15, the viewer has to read the recipient's wrong guess at the doorbell inside the first few seconds" is a version-specific requirement built on the shared one.

Everything below works through one invented brief: a parcel-service film with four requested outputs. It's fictional — no client, no tested deliverable, no real brief behind it. It's here to show a method.

Two boundaries before the method. A creative reading of a deliverables list is not a delivery contract. It doesn't authorize an extra output, promise a format anyone can produce, or price anything. The producer's technical list stays exactly as written; this is a companion interpretation of the creative work. And when you group two outputs together, that's a decision — it belongs in writing, where a producer can disagree with it next week rather than after the shoot.

Read the list as several kinds of change

Most lists move along more than one axis at once, and the axes don't all belong to the same person. There's the main film, the one everything else derives from. There are shorter executions. There are language versions. There are frame shapes. There are technical exports, which are the same film in a different container. A 15-second vertical version in a second language is three of those at once, and the person who can answer a question about the language is not necessarily the person who can answer a question about the frame.

Before interpreting anything, copy the list's own words into your working notes and leave them there. Write your reading beside them, not over them. "Vertical social cut, 15s," can become "short-form set" in about ninety seconds of tidying — and then the vertical part stops being a requirement and starts being an assumption. The loss is quiet. If the plan then calls for a wide 15, the shape has turned into a post problem that it never was. It was on line four.

It helps to sort the differences into three rough kinds.

A difference with no viewer consequence. A different encoding, container, or file spec. Same film, different file. Nothing in the treatment changes.

A difference that changes the telling. A different running time, a different shape. Same story, delivered under different constraints.

A difference that can change meaning. A language version, translated on-screen text, and sometimes sound. The story may be carried by words, and words don't always survive substitution intact.

The third kind isn't fixed by its label. A language change is a technical substitution if nothing spoken or written carries the story. It's a meaning change if the beat rides on a phrase. So the real question is whether anything in this film carries the story through words — which your brief may not answer, and which is therefore a question for whoever wrote it.

AICP's Bidding Reference Guide, 2026 edition, is useful here for one thing only: its bidding, deliverables, and post-production questions keep technical requirements separate from creative needs that go beyond running time and frame size (PDF). That separation is the useful part. It's US production-association guidance written as questions, not an answer key. It doesn't tell you what your brief means, and it establishes no platform rule, rate, or contract term.

Ask what changes for the person watching

For each output, three questions, in this order.

How does the viewer arrive? Cold, mid-story, after other content, expecting sound or not expecting it.

What can they see and hear? The frame, any on-screen text, what's spoken, what exists only as sound.

What has to be understood before it ends? The one thing the ending depends on.

Only the third question is creative work in the strict sense. The first two are conditions, and they're where a brief is most likely to be silent. Silence is a question for the brief owner, not an invitation to import a convention.

Now the parcel film. The shared requirement is that the viewer registers the recipient's wrong reading of the doorbell before the parcel is revealed. Without that registration, the ending is just a delivery.

In 30 seconds, a misreading can take its time. The bell sounds, the recipient doesn't go to the door, and the delay itself is the story. Halve the running time and the delay stops being a beat and starts being a hole. The requirement sharpens: the viewer has to see the wrong reading at the moment the bell sounds, not a beat after it. That's still a creative requirement, but it drags a staging consequence behind it. An audible setup may need a visible action next to it — the recipient's face answering the sound. Whether the plan holds both at once is not yours to decide, and it's not something an edit can settle later if the camera never had them together.

The portrait request is a different question wearing the same line item. Half the running time is a timing problem; a tall frame is a spatial one. Change the shape and what has to stay legible within a single composition changes — here, probably the door, the recipient, and the parcel at the step, either sharing one frame or separated into a different order of shots. Neither answer is automatic, and the brief doesn't say which one you're getting.

You may have a habit of reasoning back from what usually happens on a vertical feed. That habit is a guess about placement, and placement isn't in your brief. Ask whether the short version should assume sound. Ask what it sits next to. Ask who approved the shape.

Group by shared communication, then keep the exceptions

Build the comparison before you outline a single version. Four columns: the brief's own words, what the viewer must understand before the end, what the version can share with the main film, and what stays unresolved.

Two rows do real work and one does none, which is the point. In this exercise, the second encoding changes no story choice, so the treatment gains nothing from it. The ability to leave a line alone is part of the skill; a treatment that gives every filename a paragraph is usually hiding the fact that it hasn't worked out any of them.

The portrait row holds two separate questions — one about time, one about space — arriving in a single line item. The language row holds a question the list doesn't answer at all: which running time and shape does it take? The brief lists a second-language version and stops. Don't quietly decide for it. A 30-second landscape in another language and a 15-second portrait in another language are different amounts of work and carry different risks, and the difference is currently nobody's decision because nobody has made it.

Worth separating two things that look alike on this table. An exception is a version that needs something the shared approach can't give it: a different staging at the bell, a different order of shots in a tall frame. An open question is information the brief doesn't supply: which shape the language version takes, whether the film has any spoken or written words at all. Exceptions go to the treatment. Questions go to owners. Mixing them produces a document that argues with itself.

There are two ways to get this wrong, and they're opposites. Treat every filename as its own idea and you write four treatments, none of them developed, which is a summary of a list rather than a plan for a film. Treat every filename as the same film and you promise that one master covers everything — and the first thing to break is the 15-second portrait, where the staging may never have existed in the shape the version needs. Grouping prevents the first error. Exceptions prevent the second. They're two halves of one habit, not competing instincts.

Write the consequence into the treatment

Describe the shared approach once, in a sentence or two about the film. Then say, in plain prose, where a version changes.

One film: the recipient misreads the bell, then finds the parcel. In the 30-second version, the misread can take its time—the bell sounds, the recipient doesn't go to the door, and the delay is the story. In the 15-second portrait version, the misread has to register at the moment the bell sounds, not after a delay. The tall frame has to keep the door, the recipient, and the parcel legible—whether in one composition or a different shot order is pending confirmation. In the second-language version, the same story holds unless words carry it — to be confirmed. A further encoding changes nothing.

That's the shape. Three or four sentences do more than a page of version-by-version description, because the reader can see what's shared and what isn't.

Three rules keep this honest.

Route capture needs to production, and don't announce that the master will cover them. If the plan may not hold the bell and the reaction in one frame, that's a note to production. "The master will cover it" is a promise you can't keep, and it's the sentence that turns a question into a cost overrun.

Keep the producer's list intact. Your document explains creative work. It doesn't add outputs, promise formats, or price anything. If your reading suggests a version that isn't on the list, that's a recommendation, clearly marked as one.

Mark assumptions as assumptions when you move forward without an answer. Treatments get written before every question is closed. The difference between a working assumption and a silent decision is whether anyone can find it later. Write "assuming the 15 shares the master's sound design — pending" rather than building the sound design into the shared approach as though it had been approved.

What the translated list looks like

30-second landscape main execution — The reference film. Carries the misread before the reveal. No exception.

15-second portrait version — Same story, half the running time. The misread has to land on the bell, not after it. Exception: the tall frame may need its own staging or shot order.

Second-language version — Same story, unless words carry the misread. Then it's a meaning question, not a substitution.

Additional encoding of the main film — No creative consequence. Technical spec only.

And the questions, with owners attached:

For the brief owner: Which running time and shape does the second-language version take? Does the film contain any spoken line or on-screen text that carries the misread? Should the 15-second version assume sound?

For the producer: Does the tall-frame staging sit inside the approved plan, or does it need another capture? Does the second-language version change anything on the technical list?

For production: At the bell, is the reaction covered in the same frame or the same moment as the sound?

The list stays the producer's document. The treatment adds the layer that says what each line means to somebody watching, and it says plainly whatever you weren't told. Tidier grouping is worth having, but only when it doesn't quietly shrink the assignment.

Frequently asked questions

What turns a deliverables list into creative requirements?

Translate each output into a sentence about what that version has to make a viewer understand under its own constraints. A shared requirement belongs to every version; a version-specific requirement, or exception, is what one version needs that the shared approach can't give it. '15-second portrait' is not a requirement; a sentence about the viewer reading the misread at the doorbell is.

How do running time and frame shape create different problems?

Running time changes the telling. In the parcel example, 30 seconds lets the misread take its time, but 15 seconds requires the wrong reading to register at the moment the bell sounds, not after a delay. A portrait frame is spatial: it may force different staging or shot order so the door, recipient, and parcel stay legible together. Neither answer is automatic, and the brief may not say which one is wanted.

When is a language version a technical substitution rather than a meaning change?

A language change can be a technical substitution if nothing spoken or on-screen carries the story. It becomes a meaning question if a beat rides on a phrase, because words don't always survive substitution intact. The brief should be asked whether the film contains any spoken line or on-screen text that carries the misread, and which duration and shape the language version takes.

What is the difference between an exception and an open question?

An exception is a version that needs something the shared approach can't give it—a different staging at the bell, a different shot order in a tall frame—and it goes to the treatment. An open question is information the brief doesn't supply—which shape the language version takes, whether the film assumes sound—and it goes to owners. Mixing them produces a document that argues with itself.

What should the creative reading avoid doing to the producer's deliverables list?

It should not replace, add to, promise formats for, or price the producer's technical list. The producer's list stays exactly as written; the treatment adds a companion interpretation of what each line means to a viewer. If the reading suggests a version not on the list, mark it as a recommendation. Route capture needs to production rather than saying the master will cover them.

Further reading

• How to Read a Commercial Brief and Script Before Writing the Treatment — Read this first to build an intake sheet that separates supplied direction from director proposals before you translate any deliverable line.
• Read a Commercial Bid Scope Before Describing What the Budget Covers — Use this when turning open production questions into notes, so treatment language stays conditional on what the bid scope actually includes.