The Batch Shoot Day Playbook: 100 Files In, 15 Videos Out
How to run a batch shoot day that actually turns into published videos: how many concepts to book, what to slate, what inserts to name in the brief, and what happens after everyone goes home.
The Batch Shoot Day Playbook: 100 Files In, 15 Videos Out
A good batch day looks like this on the calendar: 9am call, 4pm wrap, 15 deliverables. It looks like this on the drive: 94 files named C0031.MP4 through C0124.MP4, 340GB, no structure, and one person who has to make sense of them before anyone can edit.
Here’s how to run that day, including the part that happens after everyone goes home.
Why batch filming wins
One setup. One lighting check. One wardrobe. One mental mode.
The setup tax on a talking-head shoot is fixed: 45–90 minutes for lights, sound, camera, framing, and a test record you actually watch back. Film once a week and you pay it 52 times a year. Film twice a month and you pay it 24. Same footage volume, half the overhead.
The bigger win is cognitive. Performing on camera means energy, presence, and not caring whether the take is perfect. Editing means judgment, patience, and caring about frames. Teams that do both on the same day do both badly.
Separate the days. The only thing that should happen at the end of a shoot day is a backup.
Plan the day before you plan the shots
Concepts per session. For a single-location, single-talent setup, a realistic number is 8–15 concepts in a 6-hour day. That assumes 15–25 minutes of camera time per concept including resets, and a hard break every 90 minutes because on-camera energy degrades faster than people expect. Below 8 you’re wasting the setup. Above 15 and the last three concepts are visibly worse than the first three. You’ll cut them anyway.
Shooting for multiple brands in one day? Cut that to 6–10 and block them: all of Client A, then reset, then all of Client B. Do not interleave.
Scripts vs. bullets. Use both, deliberately.
- Full script for anything with a specific claim, a legal-sensitive line, a product spec, or a number. Teleprompter, clean takes, and you don’t discover in the edit that they said “40%” when it’s 34%.
- Bullet-point brief for opinion, story, and reaction content. Three to five bullets: hook, two supporting beats, close. Scripted delivery here sounds scripted, and audiences hear it.
Most teams land around 30% scripted, 70% briefed. Write the hook line verbatim either way. That’s the one sentence worth controlling.
A repeatable shot list. Build it once, then run it per concept:
| Slot | What | Time |
|---|---|---|
| A-roll | Concept, 3 takes minimum | 8–12 min |
| Hook takes | 3–5 opening variations | 3–5 min |
| Cutaway | Talent silent, listening / nodding / working | 1 min |
| Concept b-roll | 2–3 specific inserts named in the brief | 3–5 min |
Decide your deliverable count before you roll. Not “we’ll see what we get.” Write it on the call sheet: 15 shorts, 3 longer-form, 1 client sizzle. Every concept maps to a specific slot. If you can’t name the slot, cut the concept. You just bought back 20 minutes.
On the day
Shoot each concept three times. Don’t chase the perfect take.
The instinct is to reset and go again until one take is clean. That’s slow. Rolling straight into take two while the energy is up costs about 90 seconds. Stopping, discussing, re-centering, and going again costs five minutes and usually produces a stiffer read. Three complete takes per concept, back to back. You pick in the edit, take two wins about half the time.
Shoot 3–5 opening takes per concept while the setup is live. The highest-leverage 4 minutes of the day. Different first lines, different energy, one straight and one punchy. At capture the marginal cost is near zero, lights on, talent warm, frame matched. Two weeks later, when the edit is done and the open is soft, that same variation costs a full reshoot: a calendar slot, a rebuild, wardrobe continuity, and talent who no longer remembers the concept.
Capture b-roll deliberately, not “just in case.” Generic b-roll is why edits look stock. Name the inserts in the brief, “hands on keyboard,” “product close, rotating,” “walking into frame from left”, and shoot 10–15 seconds of each. Ten specific inserts beat 40 minutes of ambient wandering, and they’re findable later because you know what you asked for.
Verbal slates between every concept. Roll, then say out loud: “Concept 4, hook variant B, take 2.” Two seconds. Almost nobody does it. It makes concept boundaries findable by ear or by transcript, which matters enormously when 94 files come back with no other structure.
The part nobody plans for
Wrap at 4pm. Backup runs. Everyone feels good.
Monday morning, someone opens a folder holding 94 files with camera-generated names, 5–7 hours of runtime, and no indication of where concept 3 ends and concept 4 begins. Before a single cut happens, that person has to:
- Scrub every file to find out what’s in it
- Work out where each concept starts and ends
- Group the three takes of each concept together
- Identify the usable take, and where inside it the restart happened
- Match b-roll to the concept it belongs to
- Create 15 separate projects with the right media in each
That is 4–8 hours on a 94-file day. It produces nothing publishable, appears in no production plan or budget, and is usually done by the most senior person available, because they’re the only one who knows what the deliverables are supposed to be. Agencies that contract it out pay $250–400 per project for a selects-and-string-out pass; at 15 deliverables that’s $3,750–6,000 for one day of footage, before editing starts.
Every editing tool on the market starts after this step. Opus Clip, Submagic, and Captions need a finished file. Descript wants one file at a time. Mosaic and Palmier want the node graph built up front. Eddie AI gets closest, raw footage into one rough cut, but that cut goes to a professional editor, not to a published deliverable. Sorting is assumed to be already done, by a human, for free.
This is the step Clik removes: point it at the day’s folder and it separates the batch into concepts, groups the takes, and sets up each deliverable as its own project. You never sort a file.
Naming and folder conventions (and where they break)
If you’re doing it by hand, these help:
2026-08-05_ClientName/
01_CONCEPT-pricing-objection/
A-ROLL_t01.mp4
A-ROLL_t02_SELECT.mp4
HOOK_vB_t01.mp4
BROLL_keyboard.mp4
02_CONCEPT-onboarding-myth/
Date-first folders sort chronologically. Concept numbers match the call sheet. _SELECT marks the chosen take. B-roll lives with its concept, not in a shared bin.
Now the honest part. This only works if someone renames files at capture, and nobody does. The camera op is framing the next setup, the producer is watching the clock, talent is waiting. Renaming 94 files afterward takes 60–90 minutes and requires re-watching most of them, which means you’ve already done the expensive part manually.
Conventions scale to roughly one shoot day, one client, one person. Past that, two cameras, multiple brands, a shoot every week, the folder structure becomes a description of work someone already did rather than a way to avoid it.
A realistic time budget
For a 94-file day producing 15 short-form deliverables:
| Stage | Hours | Notes |
|---|---|---|
| Prep, briefs, shot list, scripts | 3–5 | Mostly the week before |
| Setup | 1–1.5 | Lights, sound, test record |
| Shooting | 5–6 | 8–15 concepts, 3 takes each |
| Backup + ingest | 1–2 | Unattended, but blocked |
| Sorting and project setup | 4–8 | The invisible line |
| Editing | 11–22 | 45–90 min each |
| Internal review + revisions | 3–5 | 12–20 min each |
| Client review round | 2–4 | Plus 1–3 days of calendar |
| Publishing prep | 1.5–3 | Copy, thumbnails, uploads |
Total: 32–57 hours across 5–10 calendar days, for one 7-hour shoot.
Look at the ratio. The shoot is 6 of those hours. Everything after it is 26–51. And the largest non-editing line, sorting, never appears on a call sheet, never gets quoted to a client, and is almost always absorbed by whoever cares most.
Plan the shoot day. Then plan the four days after it, because that’s where the deliverables actually get made.
Run your next batch through Clik and see how much of that sorting line disappears.