Video production planning: a pre-production system for creative teams

Video production planning is the work you do before the pipeline: deciding what the brief actually requires, what has to be on camera, who is needed and when, and what "ready to shoot" means for this specific job. It ends the moment the first setup is lit. Everything you skip here gets paid for later, either in a reshoot or in an edit that cannot find the shot it needs.

This is a system you can run on your next job: four steps, the intake fields that actually change scope, and the arithmetic that tells you how many days to book.

Planning is not pipeline management

A pipeline is the sequence work passes through once it exists: intake, assembly, rough cut, review, delivery. Planning is the gate before that sequence, and it answers a different question. The pipeline asks where a job is right now. Planning asks whether the job should start, and with what.

A team with a tidy pipeline and no planning gate still ships broken projects. A card can move cleanly through every stage and still be missing the one shot the edit needed, because nothing upstream forced anyone to name that shot before the shoot day.

If you want the stage-by-stage side, that is covered in how to organize a video production pipeline. This article covers the decisions upstream of it.

Step 1: brief intake and the gate that rejects work

An intake form is only useful if it changes what you plan. Most fail by asking for mood boards and reference links while missing length, aspect ratios and the reason the date is fixed.

Keep the fields that do real work:

The gate is one test: could someone who was not on the call write a shot list from this brief? If not, the brief is incomplete. "Energetic and cinematic" is a direction, not a gap. "We want it to feel premium" with no length, no platform and no decision maker is the gap.

Worked example. A client asks for "a 90-second brand film, cinematic" and says the date is fixed. Fifteen minutes of intake turns that into: one 90-second 16:9 master, a 9:16 cutdown for paid social, voiceover-led, footage of the product plus two people using it, one location, delivery tied to a trade show four weeks out. That is plannable. The aspect ratio alone changes the shot list, because a 9:16 cutdown means vertical headroom on every people shot or a separate framing pass.

Tradeoff: the longer the form, the more people route around it. Ask only what changes scope. Anything you can learn by reading their existing content, read instead of asking.

Step 2: creative scoping and the shot-list breakdown

Turn the brief into a numbered list of everything that must be seen and heard. Every line is either a setup on the shoot day or an asset someone has to find, license or make. That list is the plan; the schedule is derived from it.

Put two columns on every line: must-have, and nice-to-have. Must-haves are the shots the edit cannot survive without. Nice-to-haves are what you shoot when the day is going well. This split is the most useful thing you can hand a crew, because it tells them what to protect when a location runs two hours behind.

If the film is voiceover-led, record the read before the shoot where you can. A recorded voice with timings tells you how many shots you need and roughly how long each should hold, which is a far better brief for a camera crew than a page of adjectives. The process for turning a read into a shot list is in how to turn a recorded voiceover into a video editing plan.

Worked example, continued: 40 setups. Fourteen product, including the vertical framing pass. Eighteen people. Eight location and establishing. Of the 40, 31 are must-have and 9 are nice-to-have. That number, 40, is the input to the next step.

Step 3: resource allocation and the shoot-day arithmetic

Setups per day is the lever that converts a shot list into booked crew days. It is also the number teams guess at most often, usually optimistically.

A working starting point for a small crew on one location is about 12 setups in a 10-hour day. That assumes a single camera, one lighting setup per location group, and setups of a few minutes each rather than full company moves. It is not a benchmark. It is a placeholder you replace with your own measured rate after one job. If your setups need relighting every time, you might be at three or four a day, and the same 40-setup list becomes two weeks.

Shoot-day estimator from your shot list

Estimate how many shoot days a shot list needs before you book crew and quote the client.

Shoot days equal total setups divided by setups per day. Round up to whole days when booking crew, then add your own contingency on top.

Assumptions: Illustrative planning inputs, not measured benchmarks. Assumes a single camera, a small crew, one lighting setup per location group, comparable day lengths and no talent, permit or travel constraints. Replace the default rate with your own observed setups per day once you have one job of data.

Worked example: Total setups on the shot list: 40 setups; Setups per shoot day: 12 setups/day. Estimated shoot days: 3.33 days.

At 40 setups and 12 per day, the math says 3.3 days. Book four: a fractional day is not bookable, and the 0.7 is your contingency. Those four crew days become the input to the budget, alongside location, gear and talent. The line items are in how to build a video production budget template.

Crewing follows the shot list, not the job title. A product table with one light and two people does not need the same call sheet as a dialogue scene with continuity requirements. Build the smallest crew that covers the must-have list, name a backup for each critical role, and decide in advance who is booked versus on call.

Say the assumption out loud when you present the schedule: "four days assumes one camera and one lighting setup per location." That invites the correction you want. If the client insists on drone footage or a second unit, the number changes and so does the quote.

Step 4: the pre-production sign-off gate

Sign-off is one person confirming a short list is true, not a group discussion. Before day one:

• Script or beat sheet approved, with the must-have shot list attached.
• Shot list carries location, time of day and framing notes for each setup.
• Day-one call sheet issued, with addresses, times, contacts and parking.
• Gear list matched to the shot list, with backups for anything you cannot rent locally at short notice.
• Location and permit confirmations in writing, plus a weather or access fallback.
• A named on-set decision maker who can approve a change without phoning the client.
• Talent and crew confirmed, each reachable on the morning.

If any line is false, you are not in pre-production, you are in a countdown. Most mid-pipeline collapses trace back to a missing item here rather than a failure during the shoot itself.

Multiple approvers at this gate is how reshoots happen. One person signs; everyone else gives input before they sign.

Wiring the plan into a board so production starts clean

Once the plan exists, it needs a home where the state is visible. One card per deliverable, with columns for intake, scoped, scheduled, shoot, edit, review, delivered.

Two rules make the board do real work. A card cannot leave scoped without an approved shot list attached. A card cannot leave scheduled without crew confirmed and the day-one call sheet drafted. Automations can move cards on some of those events, but the attachment and the confirmation still come from a person. If a stage is running automations, it shows a bolt in the board header, and every run appears in the Runs tab with a plain-language reason when it fails.

Fields worth carrying on the card: client, deliverable spec, aspect ratios, due date, shoot dates, owner, and must-have shot count. That last one makes the schedule argument factual instead of a difference of opinion.

Access matters when you bring in freelance crew. Guests without the view-all permission see only the cards they are assigned to, so a camera operator can be given the shoot card and its call sheet without opening the whole client roster. The setup is described in how to give freelance editors access to assigned projects, and it works the same for anyone hired for a single job. Files attached to a card are stored in the workspace Drive, so the call sheet and the shot list stay with the work rather than in a chat thread.

Honest tradeoff: a board enforces state, not quality. If the brief was wrong, the board will make it wrong on time, with good version history.

What to do next

Take one job you have not started shooting. Write the five intake fields, split the shot list into must-have and nice-to-have, and run the setups-per-day math before you book anyone or quote a number. If the result is fewer days than you were about to book, you have found margin. If it is more, you have found a conversation to have this week rather than on the shoot day.