The most common VFX production failures aren’t creative. They’re administrative. A delivery comes back in the wrong color space. The handles are too short for the editor to extend the cut. The channel naming doesn’t match the comp pipeline. The frame range is offset by one. Each of these by itself sounds trivial. Each one of them, on a real project, can cost a week of recovery.
The reason these failures happen isn’t laziness. It’s that the documents that would prevent them — the spec sheet, the pipeline test, the handles convention — are the unglamorous part of VFX production. They don’t show up in the creative review. They don’t get talked about in the kickoff meeting. They sit in a folder somewhere, and either both sides reference them or one side assumes everyone knows.
This post is about treating those three documents as load-bearing. They are the production layer underneath the creative layer. When they’re solid, the creative layer can move. When they’re not, every creative decision has to fight through a fog of preventable confusion.
The Spec Sheet: The Document That Should Exist Before Anything Else
A spec sheet — sometimes called a tech spec, a delivery spec, or a delivery requirements document — is a single source of truth for every technical parameter a VFX delivery has to meet. Resolution, frame rate, color space (working and delivery), codec, container format, channel assignment, naming convention, frame range, handles count, slate format, and any project-specific requirements.
The spec sheet is what every department references when there’s a question about what a delivery should look like. The vendor uses it to format outputs. Editorial uses it to verify deliveries match what they expect. The DI house uses it to confirm the pipeline they’ve built will receive the work cleanly.
A project without a spec sheet is a project where every department is making decisions in isolation. The vendor delivers EXR with their preferred channel layout, editorial expects ProRes 422 in a specific aspect ratio, the DI house is in ACES, and nobody is wrong because nobody has agreed on anything. The fixes are expensive because they happen after the fact.
A project with a clear spec sheet — written before the engagement starts, signed off by the production team, the VFX vendor, and the DI house — saves a remarkable amount of pain later. The discipline is to write it once, distribute it, and reference it. Don’t change it mid-engagement without re-signing it.
A good spec sheet specifies, at minimum:
- Working resolution (what the vendor will work in) and delivery resolution (what’s expected on delivery) — these are not always the same
- Color pipeline: ACES, sRGB, Rec.709, Cineon log, with explicit IDT/ODT/RRT references when ACES is involved
- Codec and container: ProRes 422 HQ in a QuickTime container, EXR with PIZ compression, DPX in a specific bit depth — be specific
- Channel assignment: RGB only, RGBA, with embedded matte, with separate mattes — the comp pipeline downstream will fail if this is wrong
- Naming convention: shotID_versionID_artistInitials_handles or whatever your editorial system expects — vendors will follow it if it exists, and guess if it doesn’t
- Frame range and handles: starting frame, ending frame, frames of head and tail handles
- Slate: yes or no, format if yes
- Audio: yes or no, format if yes (relevant for some advertising work)
A good spec sheet also has a “questions for vendor” section. The vendor’s first task on receiving the spec sheet is to confirm they can meet it, flag any incompatibilities, and ask the questions that the spec sheet didn’t cover.
The Pipeline Test: The Single Shot That Verifies Everything
Once the spec sheet is signed off, the pipeline test is the practical verification. One shot — typically a simple one from the breakdown — goes through the vendor’s full process: ingest, work, internal QC, render, naming, packaging, delivery. The result is checked by every downstream department against the spec sheet.
What the pipeline test catches: incompatibilities between the spec on paper and the actual integration of the vendor’s pipeline with yours. Color management drifts. Naming conventions that look right but break the editorial system’s auto-import. Channel assignments that the vendor’s pipeline produces correctly but the comp software downstream interprets differently. Handle counts that match the spec but don’t match the editor’s actual cut length.
The pipeline test is a small, deliberate friction at the start of the engagement. It costs the vendor a shot’s worth of work that doesn’t go directly into the show. It costs the production a few days of waiting before main production starts. It saves an enormous amount of pain later because the integration problems are caught in week one, not week eight.
Vendors who don’t run pipeline tests are vendors who haven’t been burned often enough to know better. The discipline is industry-standard for a reason. If a vendor proposes skipping the pipeline test to save time on a tight schedule, the right response is to insist anyway. The time saved by skipping is much smaller than the time lost when something breaks in the main delivery.
Handles: The Convention That Saves the Edit
Handles are the extra frames on either end of a VFX shot — frames that aren’t in the cut but are delivered anyway, so the editor can extend the shot in either direction without re-rendering.
The standard handle count is 8 frames per side, but it varies by project. Some productions use 12 or 16. Some use as few as 4. The number isn’t important; what’s important is that the convention is defined in the spec sheet and applied consistently across every shot.
What goes wrong when handles are inconsistent: the editor needs to extend a shot by 2 frames, and the handles aren’t there, so the shot has to be sent back for re-rendering with extended handles. On one shot this is annoying. On a project with hundreds of VFX shots, it’s a re-rendering catastrophe that drags the delivery schedule.
What goes wrong when handles are too generous: the vendor renders 24 frames per side on every shot, multiplying the render time and storage cost across every delivery. Storage and render farm overhead aren’t free.
The right convention sits in the middle and matches the editorial workflow. Editors who do a lot of late-stage trim work need more handles. Editors who lock the cut early can work with fewer. Ask editorial what they want, write it in the spec sheet, and stick to it.
The other detail that matters: handles need to be conformed to the cut’s actual frame range, not the original plate. If a plate was shot from frame 1001 to frame 1100, but the cut only uses frames 1020 to 1080, the handles run from 1012 to 1088 (with 8-frame handles) — not from 1001 to 1100. Vendors sometimes get this wrong, and the wrongness is easy to miss in QC.
The Three Documents Together
Each of these documents — spec sheet, pipeline test, handles convention — is useful on its own. Together they form the production foundation that the creative work sits on top of.
The flow looks like this: the spec sheet defines the technical parameters. The pipeline test verifies that the vendor’s actual delivery matches the spec. The handles convention is one specific element of the spec that gets its own attention because it interacts with editorial in a way that none of the other parameters do.
Projects that get all three right are projects where the creative work can actually move. Notes are about the shot, not the format. Revisions are about the look, not the channel layout. Delivery is about timing, not file naming.
Projects that miss one or more of these documents are projects where the creative team and the production team are constantly fighting through preventable noise. The notes that should be about the shot end up being about why the delivery came back in the wrong color space.
How FXiation Digitals Treats These Three Documents
A spec sheet is the first document we ask for in any new engagement. If one doesn’t exist, we’ll help draft it before any other work starts. The cost of building it is small and one-time; the cost of not having it is paid every week.
The pipeline test is standard procedure on every engagement at FXiation Digitals. One shot, full chain, verified against the spec sheet, signed off before main production starts. We’ve never regretted running one. We have, on rare occasions, regretted skipping one for a project that pushed for speed and learned the same lesson the slow way.
Handles are part of the spec sheet, applied consistently across every shot, conformed to the cut’s actual frame range. We deliver test shots in the early days of any engagement specifically to verify the matchmove and compositing handles handoff to your editorial system before we’re ten weeks in.
If you’re starting a project and the spec sheet, pipeline test, and handles convention aren’t yet defined, send us the brief. The first thing we’ll do is help you build them. The producers who run smoothly are the ones who treated these three documents as load-bearing — and the work that comes after is straightforward because of it.
Common Questions