How to Scope a Shoot Before You Have a Budget

Key Takeaways

• Build three coherent tiers, not one scope with things to cut. A stripped-down version of an ambitious plan is usually incoherent.
• Cost in shoot days and crew size first. Currency comes later and varies by market; days are the honest unit.
• Identify the irreducible core, the thing without which the project has no reason to exist. It appears in all three tiers.
• Say what each tier cannot do. A tier without stated limitations reads as a promise.
• Never present the tiers as good, better, best. Present them as three different projects that answer the brief differently.
• The middle tier is the one you are recommending. Say so, or the client will pick by price alone.

Why One Scope Fails

The instinct is to design the right version of the project and then adjust. It fails in both directions.

Scoping high. You design the version you want to make. It needs five days, a crew of eight and a studio. The number comes back and it is a third of that. Now you are cutting, and cutting an ambitious plan does not produce a good small plan. It produces the ambitious plan with holes in it: the same number of locations with less time at each, the same shot count with fewer people, the same ambition with none of the support it needed.

Scoping low. You guess conservatively to keep the project alive. The budget turns out to be larger than you assumed, and you have already anchored everyone to a modest version. Worse, the low scope is often what gets approved, and you deliver a smaller piece than the money could have bought.

The real problem is that cost does not scale linearly with ambition. Going from two shoot days to three is not a fifty percent increase in everything, because some costs are fixed and some step. A second location may cost nothing if it is next door, or add half a day of travel and a second permit if it is not. A scope that assumes smooth scaling is wrong at every point except the one it was built at.

A useful diagnostic: take your last scope and ask what the same project would look like at half the size. If the answer is "the same thing but shorter", the scope was never really designed, and the small version will be a compromised large one.

Build the Irreducible Core First

Before any tier, write down the thing without which the project has no point.

Not the nice-to-have list inverted. The actual core. For a founder story it might be one long interview in a space that means something. For a product film it might be three demonstrations of the product working. For a documentary sequence it might be a single event that happens once and cannot be restaged.

The core has three properties. It appears in all three tiers unchanged. It is what you protect when the day goes wrong. And if it is cut, the project should be cancelled rather than made smaller, because a version without it is not a cheaper version of the same thing, it is a different and pointless thing.

Most projects have a core of one or two elements. If your core has six, you have not finished thinking.

Writing this down first does two useful things: it gives you the spine that every tier is built around, and it gives you a clean answer when someone proposes a budget below the core's cost. That is not a smaller project, it is no project, and saying so early is far better than discovering it on day one.

The Three Tiers

Each tier is a coherent project, designed as though it were the only option.

Tier one: the core, done well

The smallest version that is genuinely good rather than merely complete.

This is not the compromise tier. It is the version where you do the core properly and nothing else: one location, minimal crew, one or two shoot days, a tight and honest piece.

The discipline here is resisting the urge to sneak extras in. A tier one that quietly includes a second location is not a tier one, and when the client picks it you will be delivering tier one and a half on tier one money.

What tier one buys: the essential thing, well made, with enough time to get it right. What tier one cannot do: breadth, alternates, coverage for a long edit, multiple deliverables.

Tier two: the recommended version

The core plus the elements that make it work harder.

Usually a second location or a second subject, enough coverage to cut a longer piece and several short ones, and one day of contingency. This is almost always the tier that represents the best value, because the fixed costs are already paid by tier one and the marginal day buys a lot.

Say explicitly that this is what you recommend, and why. Clients presented with three unlabelled options default to price. Clients told which one you would choose, and given the reason, mostly take it.

Tier three: the version with room

The core, the breadth, and the things that need budget rather than effort: more days, a bigger crew, specialist kit, original music, motion design, talent.

Tier three is not a fantasy tier and should not be padded to make tier two look reasonable. If a client picks it you must be able to deliver it, so it has to be a real plan.

Its honest purpose is to show what the money actually buys, so that a client with more budget than you assumed can spend it. This happens more often than people expect, and a two-tier scope leaves that money unspent.

Keeping the three visible at once is what makes this work in practice. When each tier is a separate document, the shared core gets restated three times and drifts, and by the third revision the tiers disagree about what the project is. On a Storyflow canvas the core sits once and each tier builds outward from it, so a change to the core updates the thing all three depend on rather than one of three copies. Its AI reads the whole board, so asking what tier two adds over tier one gives you an answer from the actual plan, which is the summary you need for the client conversation anyway.

Cost in Days, Not Currency

Until the budget exists, price the tiers in the units that actually drive cost.

Shoot days. The single biggest driver, because a day carries crew, kit, location, catering and travel simultaneously.

Crew size. Not a headcount preference. Each role either exists because the day cannot happen without it or it does not.

Locations and moves. A move is often more expensive than a location, and scopes routinely count locations and ignore moves.

Post days. Consistently underestimated. Edit, grade, sound and revisions. Two rounds of revisions is a scope item and should be stated, because unlimited revisions is where profitable projects die.

Specialist items. Anything needing hire, licensing or a specialist: original music, motion design, drone, underwater, talent, archive.

Numbers are illustrative; the structure is the point. Note that contingency appears only from tier two, which is honest: tier one has no slack, and saying so protects you when day one runs long.

Presenting Them

Never label them good, better, best. That framing makes tier one look like the bad option, and a client choosing it then feels they have bought something inferior, which sours the project before it starts.

Label them by what they are. "The interview film." "The interview film plus the workshop." "The full campaign."

State the limitations of each in a single line. "Tier one cannot deliver social cutdowns, because there is no coverage budget for them." A limitation stated in advance is a scope boundary. The same limitation discovered later is a failure.

Give one recommendation. With a reason tied to what they said they needed.

Put the core on the page. Show that all three contain it. This is what stops the conversation becoming "can we have tier three for tier one money", because the shared spine makes visible what the extra money is actually buying.

What Goes Wrong

The tiers are the same project at three lengths. No real design happened. Each tier should differ in shape, not just in duration.

Tier one is a trap. Deliberately underspecified so the client upgrades. They will pick it, you will deliver it badly, and the relationship pays for it.

Contingency in every tier. Then tier one is not really the minimum. Be honest: the smallest tier has no slack.

Post is underscoped. The commonest error by a distance. Post routinely takes longer than the shoot and is scoped as an afterthought.

Revisions are unbounded. State the number. Two is standard. Unbounded revisions are how a profitable project becomes a loss.

The core was never written down. So when the budget comes in below it, the project gets made anyway in a form that cannot work.

The Bottom Line

Write the irreducible core first, then design three coherent projects around it rather than one project with things to remove. Cost them in days and crew rather than currency, state what each one cannot do, and name the tier you recommend.

The budget conversation then stops being a negotiation about your number and becomes a choice between three things you can actually deliver, which is a better conversation for everyone in it.