Read a Commercial Bid Scope Before Describing What the Budget Covers

The number arrives first. It sits at the top of the scope, it gets forwarded around, and within a day it stops being a figure on a document and becomes a fact about the job: the budget. From there it's a short step to the treatment, where sentences start appearing about finished spots, cutdowns, and stills the budget "covers."

Some of those sentences are guesses. The fix is not complicated, and it doesn't require pricing experience. It requires reading two documents in the right order: first the dated request, then the producer's scope with its own date. The headline amount is a total, not an inventory. The inventory is the component list, and that's the part that decides which treatment sentences you can actually write.

One boundary before we start: this is a reading exercise, not a contract review. Nothing here determines what any particular bid includes, and a treatment writer shouldn't be interpreting contractual responsibility. The job is narrower and more useful than that. Document what the paperwork supports, and turn everything else into a question for the producer.

Start with the request and the version of the scope being discussed

Two documents, two dates, and the dates matter more than they look. The request tells you what was asked for and when it's wanted. The scope tells you what one production company says it will hand over. If you don't know which revision of the scope you're holding, you don't know what you're describing.

The comparison below is invented for practice. The documents don't exist, the amount is notional, and nothing in it has been priced, reviewed legally, or approved by anyone. It's built so the reading steps have something concrete to bite on.

Agency request, March 4. One :30 hero film for broadcast and online. Two :15 cutdowns with different end cards. Six finished stills for print and social. One licensed music track, which the advertiser says it will supply. First cut reviewed March 30, final delivery April 20. The memo's subject line reads "all-in production."

Scope A, March 11. Pre-production, one shoot day, camera and crew. The documented endpoint is organized camera material delivered to the agency's editor. Post-production: not mentioned. Music: not mentioned. Stills: not mentioned.

Scope B, March 12. Pre-production, one shoot day, camera and crew. Edit, colour and mix through to a finished :30 and two finished :15s. Music: listed as client-supplied. Stills: not mentioned.

Both documents quote the identical headline amount.

Notice what the request did that neither scope did: it used an umbrella phrase. "All-in" is the requester's word, not the producers'. Each producer answered with a component list instead, and those two lists describe different work. The word never got shared, so it can't be the thing you compare. Keep it visible as a conflict rather than resolving it in your head.

Also keep an eye on what isn't in the packet. A call on March 10 that clarified something is not a document. Conversation can settle a question, but until the answer appears in a scope — or at least in a written note from the producer — it isn't a work boundary. And an arrangement from the client's last campaign, however similar, can't establish what this scope covers. That's a different job, a different date, and probably a different post path.

Follow the deliverable to its stated endpoint

A scope's endpoint is the condition the work is in when it leaves the production company's hands. Scope A ends with organized camera material in the agency's editor's possession. That's a real deliverable with a real handoff, and it's genuinely useful. It just isn't a finished commercial.

Once you trace Scope A to its endpoint, the downstream list writes itself: offline edit, colour, mix, versioning, finishing, delivery. Those things have to happen for the April 20 date to mean anything, and Scope A doesn't say where they happen. The tempting move is to fill the gap with habit — production companies usually handle post — but habit isn't a line in a document. "Usually" is how a treatment ends up promising work nobody has agreed to do.

Scope B ends somewhere else entirely: finished spots, delivered. If you're describing a finished film in a treatment — the cut, the grade, the mix, the track sitting under picture — that description belongs to Scope B in a way it does not belong to Scope A. Same script, same amount, different kind of promise.

The request's review schedule is a related clue, and it deserves the same skepticism. A first cut reviewed on March 30 tells you the agency expects an edit to exist by then. It doesn't tell you whose. For Scope B, the edit is plainly inside the work being described. For Scope A, the review date points at a post team the scope never mentions.

Run the standard categories past every scope — editing, colour, sound, effects, music, versions, stills, source media — and write down the actual word each document uses. A category in your head is not an included service. It's a checkbox, and checkboxes don't deliver anything.

Map included, supplied, excluded, and unresolved elements

Four states, and the differences between them carry most of the work:

• Included — the scope says it's in, and names it.
• Supplied — someone else provides it, and the scope says who.
• Excluded — the scope says it isn't in. An exclusion is a sentence someone wrote.
• Not mentioned — the scope is silent. This is the state people misread most often.

Music shows why the distinction matters. Scope B says the track is client-supplied. That's the clearest line in the whole comparison: someone wrote it down, and the advertiser's own request agrees. If your treatment says music is part of the production budget, you've contradicted the document you're summarizing. Scope A says nothing about music at all — a different state entirely. Both get flattened into "the budget covers it" the moment you stop reading and start assuming.

The stills are the harder case, and the honest answer is that they're unresolved. Six finished stills were requested on March 4. Neither scope mentions stills anywhere. That is not an exclusion, because an exclusion would be a sentence like "stills not included." It's a silence. It could be a separate photo commission, a second bid still being weighed, something the agency is deciding internally, or an oversight. All four are possible, and the documents don't distinguish among them. Writing the stills into a treatment as covered would be inventing a commitment; writing them out as excluded would be inventing a refusal.

Where the trade's own guidance is worth knowing about: a check of the AICP Bidding Reference Guide 2026, pages 1–3, recorded on September 18, 2026, prompts exactly these kinds of questions — all-in elements, handoff endpoints, and what is actually being delivered. Treat it as context, not as authority over your project. It's US trade-association material. It isn't a contract, it isn't a rate source, and it can't tell you what any particular bid includes.

Which brings up the comparison you shouldn't make. Two scopes with the same amount and different endpoints are not equivalent, and they aren't rankable either. You can say precisely what each one promises. You can't say which is better value, because that would mean pricing the work one scope leaves out and finding out where it lands — and neither document does that. Equal numbers, unequal promises. Leave the ranking alone.

Write the producer questions before the treatment commitment

Now the questions. Keep each one narrow, tied to a dependency that changes what you write, and phrased so it asks about scope rather than responsibility. "Who's legally on the hook for post?" is a question for someone else's meeting. "Is any edit work inside this scope?" is the question that unblocks your second paragraph.

• Scope A's endpoint is camera media handed to the agency's editor. Is any edit, colour, mix or finishing work part of this scope, or does all of it sit with the agency's post team?
• Whose edit is being reviewed on March 30 — the agency's post team's, or one attached to this scope?
• Scope B counts two :15 cutdowns. Is that count fixed at two, and what does a third version change about the scope?
• Who is expected to handle the six finished stills — this scope, a separate commission, or nobody yet?
• Scope A: does the licensed track appear anywhere in this scope, or does it go straight to whoever edits?
• After delivery, what happens to the source camera media and the project files?

Six questions, and every one of them resolves something you'd otherwise be guessing at in the treatment.

Then there's the change that arrived late. On March 18, after both scopes were issued, the agency added a third :15 with a different end card. Trace where it enters the map and the chronology does most of the work: the revised request postdates both documents, so neither can include the extra version on any reading. Not because the producers declined it — because they hadn't been asked when they wrote.

For Scope A, the extra version is a post activity, and post isn't in Scope A's endpoint at all. So the change lands on whoever edits, which is precisely the question you already asked. For Scope B, versioning is inside the scope — but the scope enumerated two. A third exceeds that count, so the useful question is whether the count is fixed, not what the extra version costs. Cost is a producer's conversation, and it isn't your sentence to write either way.

Only after an answer comes back do you revise the treatment language. Until then, the wording stays conditional: pending confirmation of version count, or subject to a separate stills commission. Conditional language is not weakness in a treatment. It's the accurate description of a document that hasn't settled yet.

The scope map, annotated

What follows is the whole comparison in one place. Everything in it comes from the four fictional documents above.

Questions the documents don't answer

The six questions above are the ones with creative consequences, and they're all still open. So is the placement of the extra :15 in whichever column turns out to own the versioning.

Two warnings worth keeping in the file next to the map. First, a scope's silence isn't a refusal or an inclusion; it's an unresolved line, and it stays unresolved until someone with authority answers it. Second, a named answer is not automatically a contractual one — if your producer says the count is flexible, that's a working understanding you should confirm in writing before you lean on it in a treatment.

The map states what the documents commit to. The questions state what they leave open. A treatment can hold both — it just has to keep them on separate lines.

Frequently asked questions

Why isn’t the headline bid amount enough to describe what a treatment can promise?

The headline amount is a total, not an inventory. Read the dated request and the producer’s scope in order; the component list and the scope’s stated endpoint decide which treatment sentences are supported.

How can two scopes quote the same amount yet describe different work?

In the invented comparison, one scope ends with organized camera material delivered to the agency’s editor and doesn’t mention post, music, or stills. The other includes edit, colour and mix through finished spots, lists music as client-supplied, and still doesn’t mention stills. Equal numbers, unequal promises; they are not rankable without pricing the work one leaves out.

What is the difference between “excluded” and “not mentioned” in a bid scope?

Excluded is a sentence saying the item isn’t included. Not mentioned is silence and remains unresolved. The six stills are not mentioned in either scope, so writing them as covered invents a commitment, while writing them out as excluded invents a refusal.

How should the late-added third :15 be handled before the treatment language changes?

It postdates both scopes, so neither can include it on any reading. For the camera-material scope it is a post activity, and post isn’t in that endpoint. For the finished-spots scope versioning is inside the scope, but only two cutdowns were enumerated, so ask whether the count is fixed rather than asking what the extra version costs.

What should a treatment writer do when a category like music is addressed differently across the documents?

Write down the actual word each document uses. If one scope says the track is client-supplied, a treatment saying music is part of the production budget contradicts it. If the other scope says nothing about music, that is a different state and remains a producer question.

Further reading

• Turn a Commercial Deliverables List Into Creative Requirements — Once you know which deliverables the scope names, this translates each output into what the viewer must see or understand under that version's constraints.
• The Commercial and the Still Campaign Need Different Moments. Can One Shoot Serve Both? — When the stills are unresolved, this asks what each still must communicate by itself and whether a shared shoot produces a common moment or a separate commission.