Are Your Editors Waiting for Files? A Guide to Raw Asset Handoffs

When the Edit Stops Before It Starts

Imagine your editor sits down to begin cutting a wedding ceremony. They sync the footage from the two main cameras but find the audio is unusable—just ambient noise from the in-camera mics. They search the project folders for the separate audio files from the lapel microphones on the couple and the feed from the officiant's sound system. The folders are empty. Work grinds to a halt. The editor messages the project channel, but the audio technician who worked the wedding is now on a different shoot and doesn't respond for two days. The project is already behind schedule.

This scenario is a direct consequence of a process failure, not a personal one. When a studio’s handoff process is simply “upload all the files,” it treats all assets as one monolithic block. This informal approach breaks down as soon as you add specialized roles like drone operators, audio technicians, or second shooters using different gear. Without a specific record of what was supposed to be delivered, there's no way to know what's missing until it's too late.

From a Single Task to a Specific Checklist

The solution is to stop thinking about the raw footage handoff as a single task. Instead, break it down into a checklist of its component parts. For each project, you should be able to list every type of media you expect to receive. The handoff is not complete until every item on that list is checked off.

A typical wedding film project might have a raw asset list that includes:

• A-Cam Footage (Full day)
• B-Cam Footage (Ceremony and reception)
• Gimbal Footage (Key moments, portraits)
• Drone Footage (Establishing shots)
• Ceremony Audio (Lapel mic 1, Lapel mic 2, Soundboard feed)
• Reception Audio (Speeches feed)
• Ambient Audio Recorder

Assign Ownership at the Source

A checklist is a good start, but it lacks accountability without ownership. A reliable way to verify a file gets uploaded is to assign the responsibility to the person who created it. The drone pilot is responsible for the drone footage. The audio technician is responsible for the audio files. The lead shooter is responsible for the A-Cam footage.

This makes the post-shoot process clearer for everyone. Instead of a vague directive to a group, each crew member has a specific, limited list of duties. This clarity is especially important for hybrid teams that rely on freelancers who move from one studio's project to the next. Their job for you isn't finished when they pack their gear; it's finished when their specific assets are successfully uploaded and verified.

Building an Internal Deliverable System

Many studio management systems are designed to track project phases. In Dubsado, for example, you can create custom project statuses like "Post-Production Handoff" or "Awaiting Raw Files" to categorize projects and see which ones are stuck. You can also build an automated workflow that sends a reminder email on a due date, as you can with Studio Ninja.^[1][2]

This phase-based tracking is useful, but it doesn't solve the problem of knowing *which specific file* is missing. To do that, you need to track these internal handoffs with the same precision you use for final client deliverables.

In RevePod, you can adapt the deliverable system for this purpose. A project in RevePod is built around events, crew roles, and deliverables. While you typically use deliverables for client-facing items like the 'Highlight Film' or 'Ceremony Edit,' you can create internal deliverables for 'Drone Footage Upload' or 'Reception Audio Upload.' You then assign each of these tasks to an assignee. The Post Production dashboard collects these deliverables from all your projects, showing each item's assignee and status. This gives a post-production manager a single screen to see which raw assets are ready and which are not, without having to poll the entire team.

Is This Overcomplicating Things?

For a small, co-located team working on a simple, two-camera shoot, this level of tracking might seem like extra work. If the editor can turn to the shooter in the same office and ask for a missing file, the problem is solved in minutes. The informal method works when communication is instant and memories are fresh.

This system becomes necessary when that informal process fails. With freelance or remote team members, the person you need to reach might be on a flight, on another job, or in a different time zone. What was a five-minute question becomes a two-day delay. By the time you reach them, they may have worked multiple other jobs and struggle to remember specifics about your project. A formal checklist and clear ownership reduce the risk of delays and ambiguity, allowing your post-production process to scale with the complexity of your shoots and your team.

Checklist: Pre-Edit Asset Audit

Before assigning any project to an editor, the post-production manager should be able to answer yes to every question on this list. Use it as a template for your own studio's verification process.

• Have all expected camera cards (A-Cam, B-Cam, etc.) been uploaded and files verified?
• If applicable, is drone footage present, correctly labeled, and playable?
• Are all external audio sources (lapel mics, board feeds, ambient recorders) accounted for?
• Have specialty shots (e.g., gimbal, Super 8, slow-motion) been uploaded and noted?
• Has the lead shooter provided a log or notes on key moments or technical issues?
• Does the total file size and clip count seem reasonable for the duration of the event?
• Is there a confirmation from each assigned crew member that their upload is complete?