Conform and Online Finishing Handoff Process That Does Not Break Between Facilities

The conform online finishing handoff process between facilities is one of those workflows that looks simple on paper and then absolutely does not work in practice. The offline editor sends an EDL and a drive, the online facility receives it, and somewhere between those two moments a version confusion problem quietly takes root.

I have seen this break in every direction. Wrong cut version handed to conform. VFX pulls missing from the EDL. Color notes attached to an outdated lock. The technical pipeline between facilities is usually solid. The communication layer is where it falls apart.

Here is how to build a handoff process that actually holds.

Why Handoffs Break Between Facilities

The root problem is that facilities communicate by sending files and hoping the other side received the right version. There is no shared context, no single location where all parties can see what is current, and no record of what was approved before the handoff happened.

The offline editor is working in their NLE. The online facility is working in theirs. The producer is in email. The client sign-off exists as a message somewhere in a thread nobody can find when the conform supervisor asks "was this locked?"

The conform and online finishing handoff breaks at exactly that moment. Not because the EDL was wrong, but because nobody can verify what was approved.

What Has to Be Locked Before You Hand Off

I am a strong believer in not handing anything to an online facility until the offline lock is documented. Not verbally confirmed. Documented, with a timestamp, and ideally with a sign-off record attached to the actual cut. If this applies to your setup, picture lock documentation for editors is worth reading alongside this.

Here is what that means in practice:

• The locked cut exists as a specific version in your review system, not just a file with "LOCK" in the name.
• The producer, director, and any executive stakeholders have reviewed that specific version and their approval is recorded.
• The approval is attached to the cut version itself, not living in a separate email chain.

PlayPause's approval lock feature does exactly this. Once a cut is approved, it is marked as locked in the review session. Anyone who pulls that session later can see who approved it and when. That becomes your documentation for the conform handoff.

When the online facility asks "are we working from the picture lock?" you send them a link to the locked version with the approval timestamps visible. That is a different conversation than forwarding an email chain.

Building the Handoff Package

Once the lock is documented, the handoff package itself is a technical checklist. The specific files will vary by facility and delivery spec, but the structure should always include: If this applies to your setup, the picture lock to sound design handoff checklist is worth reading alongside this.

The locked cut reference with burned-in timecode is not optional. The online editor should be able to check any frame in their conform against that reference without calling anyone.

For productions where the color session happens simultaneously with online finishing, the colorist feedback workflow becomes part of this same package. Notes on color passes need to be traceable back to the same review session so the colorist and the online editor are not working off conflicting information.

Review_Cut_v4.mp4In Review

212160p · ProRes

00:34 / 02:18

SR

Sarah 0:34

Frame-accurate note, everyone sees the exact same thing.

Keeping Both Facilities On the Same Version

The most common failure point I see after the initial handoff is a late change that goes to one facility and not the other. A producer sends a revised EDL for a picture fix to the offline editor but forgets to tell the online facility. The conform has already started. Now someone is working off the wrong version.

The fix is centralizing change communication. Any change after picture lock, no matter how small, goes through the same review link that documented the original approval. The change is flagged as a post-lock revision, the time stamp is captured, and all parties get notified.

This sounds like process overhead. It is actually far less work than the alternative, which is a conform supervisor stopping work mid-session to figure out whether the version they have is current.

Handling VFX Handoffs Within the Larger Conform

This is where most handoffs have a second, parallel failure. VFX shots coming back from vendors often arrive on a rolling basis, sometimes after the conform has started. Without a clear protocol, the online editor is either holding the conform for VFX or trying to incorporate new shots without a clear handoff process.

I recommend treating each VFX delivery as its own mini handoff within the larger conform session. Each shot delivery includes:

• Shot name and TC in/out matching the EDL
• Version number (VFX vendors rarely deliver once)
• VFX supervisor approval status

PlayPause's time-coded commenting handles this well because you can leave shot-specific notes on the incoming VFX delivery and have the VFX supervisor approve individual shots before they are incorporated into the conform. For a detailed look at keeping VFX notes organized, how to track VFX pulls from offline through delivery covers the full chain.

Protecting Against Last-Minute Changes

The most difficult scenario in any conform handoff is the late-breaking client change. The conform is underway, the online editor is working, and a note comes in that requires an offline change before online can continue.

The protocol here is simple but has to be agreed before production starts:

• Any offline change after handoff triggers a full version check before work continues in online.
• The revised lock goes through the same approval and documentation process as the original.
• The online facility does not incorporate any change until they have a signed-off revised EDL.

This feels bureaucratic. It is actually the thing that prevents a $50,000 conform session from having to be partially redone because a change came in mid-session and the communication broke.

For teams dealing with multiple cut versions across different deliverables, managing multiple cut versions without version confusion runs through how to keep the version hierarchy clean so the conform facility always knows which is current.

• Document picture lock with approval timestamps before handoff
• Include burned-in timecode reference cut in every package
• Centralize post-lock change communication through the review system
• Treat each VFX delivery as its own mini handoff
• Agree on change protocol with all facilities before production starts

Making the Handoff a Normal Part of the Process

The facilities that run these handoffs cleanly are the ones that build the documentation process into their normal workflow, not as an add-on when things get complicated. The approval record is not extra paperwork. It is the thing that makes the conform go smoothly.

If you are running online finishing on a regular basis and your current handoff process relies on emails and file names with "FINAL" in them, it is worth building something better before the next project. Post houses managing multiple active projects face this across every job simultaneously, and the answer is the same: one source of truth for what is locked, documented, and ready to hand off.

For further reading, how a post supervisor manages colorist and editor handoffs digs into this from a related angle.

For further reading, online edit conform checklist before the finishing house digs into this from a related angle.

PlayPause starts free and the Agency plan at $19/mo gives you the approval documentation, version control, and guest reviewer access to build a handoff process your online facilities will thank you for.