Handoff Checklist From Picture Lock to Sound Design Without Miscommunication

The picture lock handoff to sound design is one of the highest-stakes transitions in post-production. Get it wrong and your sound designer spends two days working on an OMF from the wrong sequence, discovers the problem when they try to sync to the locked cut, and suddenly you have a schedule problem that nobody budgeted for.

This handoff is not complicated to do well. It just requires being deliberate about what you are delivering, confirming that the recipient has everything they need, and not assuming anything is obvious.

Here is what that looks like in practice.

Why Handoffs Go Wrong

The most common reason a picture lock to sound design handoff fails is not that someone forgot something obvious. It is one of these:

• The OMF or AAF was exported from a different sequence than the locked cut
• The frame rate of the exported file does not match the locked picture
• Temp music is not labeled clearly and the sound designer does not know whether to keep or replace it
• Timecode burn-in or slate information is missing, so the sound team has no reference frame
• The locked cut delivered to sound is not actually the same version the director signed off on

All of these are avoidable with a checklist that covers what to deliver, how to verify it is the right version, and what information to communicate alongside the files.

The Core Handoff Package

Every picture lock to sound design handoff should include the following:

The locked picture file A reference video, typically an H.264 or H.265 export with timecode burn-in and audio reference mix. Resolution is usually 1080p for the reference file. The timecode in the burn-in should match the sequence timecode in the NLE, so that when the sound designer calls out a cue at 01:24:15:03, your editor can find the same frame.

The OMF or AAF for the audio session This is what the sound designer will actually import into Pro Tools or their DAW of choice. Export it from the exact same sequence as the locked picture file. Confirm that the audio track layout makes sense: dialogue on its own tracks, temp music on its own tracks, sound effects separated. The cleaner the track layout, the faster the sound team can get into the work.

A sequence summary A short document that covers: total running time, frame rate, starting timecode, intended delivery specs (stereo mix, 5.1, Atmos, etc.), and any notes about the audio that the sound designer needs to know. This includes things like: "The dialogue in scene 3 has a wardrobe noise we could not remove in production. It is flagged on the timeline."

The approved version record This is the one most people skip. Document which version of the cut was approved, who approved it, and when. If you are using PlayPause's approval workflow, you can export this record directly. If you are not, you should at minimum have an email or message thread where the director or producer confirmed picture lock.

Why does this matter? Because if the sound designer is three weeks into the mix and the editor reopens a scene, the sound team needs to know whether the picture is actually locked or whether changes are still possible. An explicit approval record sets a clear line.

The Checklist

• Export reference video with timecode burn-in from the locked sequence
• Export OMF or AAF from the same locked sequence
• Verify frame rate matches between video and audio export
• Prepare sequence summary with specs and flagged audio issues
• Attach the approved version record
• Confirm the sound team received and can open all files before marking handoff complete

Temp Music: The Hidden Handoff Risk

Temp music is where a lot of handoffs create unexpected problems. Editors drop in temp tracks from Spotify, YouTube, or music libraries to give the cut a feel. For more on managing the sound mix approval process after the handoff is done, sound mix approval workflow for narrative films with multiple stakeholders covers the downstream process. The sound designer needs to know, for every piece of temp music: is this being replaced by an original score or licensed track, or is this a track we are licensing and the mix should be built around its structure?

Do not leave this ambiguous. Include a simple cue sheet that lists every temp music track, its start timecode, its source, and its status: to be replaced, licensed and staying, or TBD.

If temp music is not documented and the composer or music supervisor is not aware of what was cut in, you end up with original music scored to a slightly different pacing than the temp and a sound designer who has to bridge a gap nobody told them about.

Confirming the Handoff Is Complete

Sending the files is not the handoff. The handoff is complete when the sound designer has confirmed they can open everything. Using video proofing tools with explicit approval steps makes this confirmation part of the process rather than a separate conversation., it plays in sync, and they have the information they need to start working.

This is a simple check-in: "We have received the files. The OMF opens in Pro Tools, it is in sync with the reference video, and we have the cue sheet. We are starting on the dialogue clean tomorrow."

If you do not get that confirmation, follow up. Do not assume everything is fine because you sent the files. File transfer issues, codec incompatibilities, and missing stems are common enough that confirmation is worth the five-minute follow-up.

For projects where multiple departments are involved simultaneously, the broader tracking challenge is covered in how post production coordinators keep track of approval status across five deliverables.

After Handoff: Managing Changes Without Chaos

Picture lock should mean the picture is locked. In practice, changes sometimes happen after handoff, even after sound has started. The way you document picture lock determines how you handle those requests. For more on this, picture lock documentation: how editors prove a cut was approved is worth reading before your next project. When that happens, the sound team needs to know immediately, and the new version needs to be delivered to them with a clear change note.

This is where having a documented picture lock approval record is critical. When the director asks for a scene change after handoff, you can go to the record and say: "The picture was locked and approved on [date]. This change is going to require a new export and a note to sound about the affected timecodes. It will add time to the schedule." That is not an argument. That is just information the director needs to make an informed decision.

For the post supervisor's perspective on managing these kinds of handoff complexities across the full post schedule, how a post supervisor manages colorist and editor handoffs without version chaos covers the same principles applied to the color pipeline.

Make It a Template

If you do a significant number of narrative or commercial projects, make this checklist a template. Not a different document every time, but a shared template that the post coordinator or assistant editor fills in for each project. The template ensures nothing is forgotten and creates a consistent handoff experience for the sound team you work with regularly.

The sound team will appreciate it. Sound designers who work with organized post teams take better care of those relationships, which matters when you need a favor on a tight turnaround.

For the review and approval infrastructure that supports a clean handoff record, start PlayPause free and run your next picture lock through an explicit approval step. The record you create at lock becomes the documentation the sound team needs to know they are working on the final cut.