Getting Second Unit Footage to the Main Editor the Same Day It's Shot

Second unit footage has a strange habit of arriving late even when it was shot early. The main unit wraps a car chase insert at 10am, the stunt team's second unit grabs the wide crash angle across town by noon, and yet somehow the editor doesn't see any of it until three days later because it landed on a different drive, got backed up by a different DIT, and nobody thought to merge it into the same project until someone specifically asked where it was. If you've ever watched an assistant editor spend half a morning hunting down footage that was technically shot on schedule, you know exactly how much time that gap actually costs, and it's almost never a shooting problem, it's a pipeline problem.

Why Parallel Units Create a Data Bottleneck

The moment a production splits into a main unit and a second unit, whether that's a stunt team, an aerial crew, or just a smaller B-camera group grabbing coverage on a different part of the location, you've effectively created two separate data pipelines that both need to converge somewhere before an editor can actually cut. On a lot of mid-size productions that convergence point is still a shared drive that someone manually reconciles at the end of the week, which works fine right up until the editor needs second unit footage for a scene that's cutting this week, not next week. We've heard the same story from post supervisors on productions running three or four units at once, a shared drive that gets updated Friday afternoon might as well not exist to an editor who needed a specific pickup shot on Tuesday, because by the time that drive gets touched the assembly cut has already moved past the point where the shot would have slotted in cleanly.

What Same-Day Delivery Actually Requires

We built PlayPause's project structure around the idea that a shooting day, not a unit, should be the organizing principle, so that a main unit DIT and a second unit DIT can both upload proxies into the same reviewable project without needing to coordinate a folder structure over text message at 11pm. That single project view is what actually lets an editor open one link and see everything shot that day, tagged by scene and unit, instead of toggling between two separate delivery systems that happen to be running in parallel.

Tagging Matters More Than Speed

Uploading fast is only half the job, because footage that lands in the same project untagged is nearly as unusable as footage that hasn't arrived yet. An editor scanning through fifty second unit clips with generic filenames from a stunt team's camera card has basically the same problem as an editor who has no footage at all, they can't find what they need without opening every file. This is exactly where a disciplined naming and metadata approach earns its keep, and it pairs directly with what we cover in our piece on building a DIT report that actually helps editors find the right take, because the same tagging discipline that makes a DIT report useful is what makes a multi-unit project navigable.

When Second Unit Is a Drone Crew, Not a Camera Department

Aerial second units complicate this a bit further because they're often running on entirely different gear, a DJI Inspire or a cinema drone rig recording to its own memory cards in its own file container, with no genlock or jam-sync connection back to the main unit's timecode at all. That means aerial footage frequently can't be timecode-matched to ground footage the way two ground cameras can, and the drone operator also has to keep a separate FAA flight log alongside the footage for compliance reasons, which is its own piece of paperwork that has nothing to do with the edit but still needs to travel with the footage. The practical fix is the same tagging discipline applied a little more loosely, scene number and rough time-of-day noted on each aerial clip even without frame-accurate sync, so an editor cutting in an establishing aerial shot can at least find the right pass over the right location without needing exact timecode alignment to make it usable.

Coordinating DITs Across Units

On productions big enough to run parallel units, you usually also have parallel DITs, and getting them working off the same system, right, rather than two competing ones, is most of the battle.

That last step is one people underestimate, the ability for an editor to flag a problem, wrong lens, missing slate, unusable audio, back to the second unit while they're still on location and can potentially grab another take, rather than discovering the issue in an assembly cut two weeks later when the second unit has already wrapped and gone home.

A Real Scenario: Stunt Coverage on a Commercial Shoot

Picture a commercial with a hero car sequence, main unit shooting the actor's coverage in a controlled lot while a stunt second unit is out on a closed road grabbing the actual high-speed pass. The agency wants to see a rough assembly by end of week, which means the editor genuinely cannot afford for that stunt footage to trickle in whenever the second unit gets around to backing it up. On a shoot like this, we typically see the editor start cutting main unit coverage the same afternoon it's shot, and by the time the second unit's footage lands in the shared project a few hours later, tagged to the same scene, it drops straight into the timeline instead of triggering a scramble to figure out what take goes where. Say the second unit wraps their closed-road pass at 4pm and their DIT has proxies uploaded and tagged to "Scene 14, Second Unit" by 6, the editor who's already built a rough assembly of the actor's coverage from that morning can drop the stunt pass straight into the same sequence before dinner, rather than waiting until the next production meeting to even find out the footage exists.

This is also where continuity checking benefits from a unified project, because if a script supervisor is trying to confirm that a stunt double's jacket matches the hero actor's jacket from an earlier setup, that comparison only works if both units' footage lives in the same reviewable place. We go deeper on that specific workflow in our piece on script supervisors catching continuity mismatches same-day, and the short version is that a fragmented pipeline makes continuity checking across units nearly impossible, while a unified one makes it almost trivial.

Organizing Volume Without Losing the Editor's Trust

A second unit on a busy day can easily generate as much footage as the main unit, sometimes more if it's a stunt or aerial team running multiple takes on a single setup, and that volume needs somewhere sane to land. This is where batch uploads matter more than people expect, because a second unit DIT shouldn't be manually dragging in one clip at a time between setups, the whole card should go up in one pass while they move on to the next task. And once it's up, it needs to live inside multi projects structure that keeps each shooting day, each unit, and each scene distinct, because an editor who has to guess which project a clip belongs to stops trusting the system and starts asking for footage to be sent directly again, which defeats the entire point.

Reliable media storage underneath all of this is what makes the trust actually stick, because if footage occasionally goes missing or takes hours to appear after upload, editors revert to the old habit of texting DITs directly to confirm footage exists, which is exactly the bottleneck a shared review project is supposed to eliminate.

What Breaks Without a Shared System

We hear the failure mode from productions pretty often, and it's rarely dramatic, it's just slow attrition. A second unit's footage sits on a card for two extra days because nobody was assigned to offload it that night. It gets backed up to a personal drive instead of the shared storage because the second unit DIT wasn't looped into the same system as the main unit. It arrives untagged, forcing the assistant editor to spend an afternoon just figuring out what scene each clip belongs to. None of these are catastrophic on their own, but stacked together they can turn same-day footage into a week-late delivery, which on a tight post schedule is the difference between hitting a client deadline and asking for an extension.

• Put both units on the same upload system before day one, not after a delay happens
• Assign a named DIT or PA per unit responsible for same-day uploads
• Require scene and unit tags on every upload, no exceptions
• Give the editor visibility into the shared project, not a request-and-wait system
• Flag unusable takes back to the unit while they can still grab a replacement

Making the Handoff Actually Flat-Rate

One thing that trips up productions running multiple units is pricing, because a lot of review platforms charge per seat, which gets expensive fast once you're adding a second unit DIT, a stunt coordinator, an editor, and an assistant editor all needing access to the same project. A flat-price workspace means adding a second unit to the review pipeline doesn't come with a per-person bill attached, which matters on productions where units scale up and down week to week depending on what's being shot. If you're building out a camera-to-cloud pipeline for a multi-unit shoot and trying to figure out what's actually worth paying for, our cost breakdown for camera-to-cloud on an indie budget is a useful next stop, since a lot of the same infrastructure decisions apply whether you're running one unit or three.

As production workflows keep shifting toward on-set connectivity, outlets like IBC have documented how camera-to-cloud has moved from a big-budget novelty into something mid-size productions expect as standard practice, and multi-unit coordination is one of the areas where that shift pays off fastest, because the alternative, manual reconciliation between units, scales badly the moment you add a second camera department.

Getting Every Unit Into One System

If your production runs multiple units and the editor is still waiting on second unit footage that was technically shot on time, the problem isn't your crew, it's the pipeline connecting them. PlayPause gives every unit, main or second, the same shared project link so footage lands tagged and ready the moment it's uploaded, no separate systems to reconcile. Take a look at PlayPause pricing to see how one flat workspace scales across as many units as your production needs without adding a per-seat cost for every DIT and stunt coordinator you bring on.