A brand publishing on social platforms has an invisible problem. Every vertical, whether it's a Reel, a Short or a TikTok, looks like a self-contained project, with its own request, its own date, its own approval. Over the course of a year, it's actually a series production, and that's the scale you have to treat it at.
"Shoot on demand" — where each idea triggers an isolated day of filming — looks like the natural answer. Someone asks, you film, you edit, you publish. The trouble is that at six or seven different channels with several posts per month on each, that mode makes production materially impossible to sustain with an in-house team. Organization cost explodes, and the calendar fills up with shoot days that leave no room for anything else.
Batching — grouping several videos onto a single shoot day — is the answer to that saturation. Three to ten videos per session, depending on context. In every multi-channel or multi-brand setup that holds up over time, batching is the common practice.
Three reasons for it, one of them much heavier than the other two.
Three shoots means three logistics machines
The first reason, and by far the main one, is coordination overhead.
Setting up a shoot day isn't about planting a camera on a tripod. The actual filming hours are a fraction of the work. What takes time is everything that makes them possible: lining up the calendars of four to six people, alerting reception and site security, booking an available room at the agreed time, sending the brief to the interviewees and chasing them so they actually read it, negotiating slots when someone moves a meeting, dealing with day-of surprises when the room you booked turns out to be taken.
Three separate shoots over three different weeks means going through that machinery three times. One big session that covers five videos means going through it once. The difference doesn't show up on the gear rental invoice. It shows up in the weeks of meetings you didn't have, the emails you didn't send, the follow-ups you didn't have to chase.
It's also the strongest argument for defending batching to someone commissioning the work who sees it as red tape. Asking two months ahead for a contributor's availability for a session that will produce seven deliverables isn't a sign of heavy process. It's what lets the team exist.
Film wide first, frame in the edit
The second reason has to do with the nature of certain shoots, which are really long captures you slice up afterwards.
A day spent at an event, an internal seminar, a workshop, a product launch, actually contains six to ten potential subjects that surface as the hours go by. The operating rule is to film more than you think you'll use and to sort it out in post. A fifteen-minute talk can yield three different Shorts if it's framed for it.
It's documentary logic applied to brand production. You accept filming too much, because the marginal cost of an extra hour of capture is low once the crew is on site, and because the best moments are rarely the ones that were scripted in the brief.
This second reason only holds because the first one does. If every shoot required its own coordination cycle, you'd never have the luxury of filming wide.
Shooting stops being the bottleneck
The third reason is the most mechanical of the three, and it's what makes batching unavoidable rather than optional.
A team producing for social platforms spends most of its time in post-production, as covered in detail in the previous article. If shooting takes up four or five days a week, there's not enough time left to edit, and the pile of unprocessed footage stacks up until deliverables fall behind. Conversely, if shooting fits into a day and a half per week, the remaining three and a half days are enough to absorb the post-production flow.
That balance is what batching protects. Shooting three videos in one day is the equivalent, in shoot load, of half a day per video, compared with the full day each one would demand in separate mode. The factor of three on shooting is what makes the post-production cadence sustainable.
Once that balance is found, post-production becomes the only real bottleneck, and that's good news. Shooting, once compressed, becomes predictable. Post-production, measurable. The cadence, steerable.
Where batching doesn't hold
Not everything batches. Three cases break the logic.
The first is subjects tied to a one-shot moment. A corporate announcement that can't wait, a hot-take reaction, a capture that will never happen a second time. These subjects justify an isolated shoot, and you have to accept that they consume a disproportionate organization cost relative to their output. The rule is that they stay the exception.
The second case is contributors with one-off availability. An executive who has only an hour in the quarter, an external partner passing through, a client you won't see again. Batching here means stacking everything you can get them to say during that hour, rather than going at it on demand for a single format.
The third case, more structural, is the absence of an editorial pipeline. Batching requires knowing several weeks ahead what you'll want to publish. A team that only films on demand, without a consolidated calendar, can't group. It reacts, it doesn't plan, and every video arrives with its own urgency. The entry condition for batching isn't material, it's editorial: you need a calendar that plans ahead, by channel and by theme, and someone commissioning the work who accepts looking at production three months out rather than three days out.
Batching changes the unit
Batching isn't an efficiency trick. It's a production mode that changes what the team can do in a week. It shifts the shoot unit from "one video" to "one session," and as a consequence makes post-production sustainable. As long as you reason at the video level, the calendar collapses. As soon as you reason at the session level, it breathes.
One last subject remains, which is the client-side counterpart of everything just laid out: how many channels can a given team serve, and at what point do you have to grow the team to hold the promised frequency?