The VFX Production Checklist Before Sending Shots to a Finishing House
A solid vfx production checklist before the finishing house prevents costly recalls. Here is what to verify on every shot before you hand off.
Before you send a single shot to the finishing house, you need a locked, verified package. Not a rough pass. Not a "good enough" export. A complete, documented handoff where every shot is confirmed, every note is resolved, and every stakeholder has signed off. I have seen productions burn days and real money because something slipped through at the transfer stage. This checklist is what I would run through every time.
Recalls from finishing houses eat time you do not have and money you did not budget for. A ten-minute checklist now beats a two-day recall later.
Why This Matters More Than You Think
The finishing house is not your safety net. They are the final stage, and their job is to take clean, approved shots and prepare them for delivery, not to catch problems your team should have caught earlier. When a shot arrives with unresolved notes, a wrong version, or a missing element, the best-case scenario is a delay. The worst case is a costly recall that blows your delivery schedule and your relationship with the facility.
A solid vfx production checklist treats the finishing house handoff as a hard gate, not a soft suggestion. Every item has to clear before the package goes out.
Step One: Confirm Shot Approvals Are Locked
This is the single most important step and the one most often skipped under deadline pressure. Before anything else, every shot in the package needs a documented approval from the appropriate decision-maker. Not a verbal okay. Not a Slack message. A formal sign-off that is tied to the specific version of the shot being sent.
With PlayPause, you get approval locks that attach to a specific video version. The approver clicks approve, and the record is timestamped and permanent. That record travels with the shot. If a dispute comes up later about which cut was approved, you have the answer in seconds.
If you are using a structured approval workflow for your VFX rounds, this step should already be done before the shot even reaches the checklist phase. The finishing house receives only shots that cleared the gate.
Step Two: Verify Version Numbers and File Names
Version confusion is the quiet killer of VFX handoffs. You have v14 internally. The approval was on v13. The finishing house gets v14 because it was in the folder labeled "Final." Nobody catches it until the colorist calls to say the grade does not match the client's approved reference.
Before handoff, do a one-to-one match between your approval records and the actual files going into the package. Match the timecode, the frame count, and the file name. If there is any discrepancy, stop and resolve it. Sending the wrong version is worse than sending nothing, because it looks like you sent the right thing.
This is also where your cut version naming conventions matter. If your internal naming is inconsistent, the finishing house will struggle to interpret your package, and that friction becomes your problem.
Step Three: Check Notes Status on Every Shot
Run through your active note log. Every note that was raised during the review process should be either resolved and confirmed, or formally deferred with an explicit "hold for pickup." There should be no orphaned notes sitting open on shots you are about to send.
This is where a frame-accurate VFX note system pays off. If your team has been logging comments at the frame level throughout the review process, generating a final notes-cleared report is straightforward. If your notes are spread across emails, Slack threads, and hand-written lists, you are going to miss something.
What hurts
What is better
Step Four: Run a Technical QC Pass
Approval is about creative intent. Technical QC is about delivery specs. Both have to pass before the package goes out. Here is what to check:
- Frame rate matches the delivery spec (29.97, 23.976, 25, etc.)
- Resolution is correct for the finishing house's pipeline (2K DPX, EXR, ProRes, etc.)
- Color space is tagged correctly and matches what was agreed on (ACEScg, log C, etc.)
- Audio tracks are either absent or correctly labeled if included
- Handles are the right length as specified by the facility (usually 8 to 16 frames on each end)
- No burned-in timecode or watermarks on shots intended for finishing (unless requested)
- Slate information is accurate on each clip
This is the kind of check that belongs in a dedicated QC session, not a quick scan before the upload. If you have a VFX coordinator on the project, this is their primary job at this stage.
Step Five: Prepare the Shot Delivery Document
Every shot package should ship with a written delivery document. At minimum this should include:
| Item | What to Include |
|---|---|
| Shot list | All shot identifiers with timecodes |
| Version reference | Which version of each shot is in the package |
| Approval record | Who approved each shot and when |
| Notes resolved | Summary of open notes cleared before handoff |
| Technical specs | Format, frame rate, color space, handle length |
| Deferred notes | Anything intentionally held for a pickup pass |
| Contact info | Who at the production to call if the facility has questions |
The delivery document is your paper trail. If anything goes wrong after the handoff, it is what protects your production from blame.
Step Six: Communicate Directly With the Finishing House
Do not just drop files into a shared folder and assume the facility has everything they need. A short email or call with the finishing house's VFX supervisor confirming the package contents, flagging any unusual elements, and confirming their expected turnaround is worth the five minutes it takes.
If you are sending a large package, confirm the file transfer method they prefer. Some facilities want everything via Aspera. Others use their own FTP. Dropping 2 TB onto a random Google Drive link is a recipe for a bad first impression.
Step Seven: Lock Down Revisions After Handoff
Once the package is out, any additional notes or change requests need to go through a formal revision process, not an informal message to the colorist. This is especially important on productions where creative stakeholders are still in the loop after the finishing house has started work.
Make sure your approval chain documentation makes it clear that changes after handoff are a new revision cycle, not a free correction. Otherwise you will spend the rest of post putting out fires that started because someone sent a note directly to the facility without going through production.
- Confirm shot approvals are locked to correct version
- Verify file names and timecodes match approval records
- Check notes log for any unresolved items
- Run technical QC against delivery spec
- Prepare and attach the shot delivery document
- Confirm transfer method and timeline with the facility
Putting It All Together
A good vfx production checklist is not a bureaucratic burden. It is the thing that lets you hand off with confidence, knowing your finishing house has exactly what they need to do their best work. It is also what protects your production if anything comes back wrong, because you have the receipts.
PlayPause is built for exactly this kind of structured review workflow. Frame-accurate comments, approval locks, version stacking, and a full audit trail mean your shots do not arrive at the finishing house with a cloud of uncertainty around them. They arrive clean, approved, and documented.
If you want to see how it fits your VFX pipeline, start PlayPause free or check out the plans at /pricing. The Agency plan at $19/mo is what most VFX teams reach for, and guest reviewers are always free.
Rohit K. writes about creative operations for PlayPause. He focuses on how agencies and production teams run review and approval at scale without scope creep, missed deadlines, or version chaos.
Related resources
Keep reading
Bring your team into one review space
Centralize feedback, lock approvals, and deliver faster, start free today.
Sign Up for Free