Post-Production Workflow: Stages, Handoffs and Review Loops

A post production workflow is the ordered chain of stages, handoffs and review loops that moves a project from camera files to delivered masters. Each stage receives defined inputs, produces defined outputs, and passes a review before the next team starts. When those handoffs are clear, post runs on schedule. When they are vague, it stalls.

This guide walks through a typical film and TV workflow stage by stage, with the exact materials that change hands at each point, where the review loops sit, what a good turnover package contains, and where AI tools are starting to take on repetitive work without taking over creative decisions.

What is a post-production workflow?

A post-production workflow is the documented path that media, metadata and decisions follow from the end of the shoot to final delivery. It answers three practical questions for every step: who does the work, what do they need to start, and who says it is done.

Three things travel through that path together, and a workflow fails when any one of them gets lost:

• Media. Camera originals, proxies, audio, VFX plates, renders, stems and masters.
• Metadata. Timecode, reel and clip names, color information, script notes and edit decision lists that let each department find the exact frames it needs.
• Decisions. Notes, approvals and version history, which record why the program looks and sounds the way it does.

Teams usually plan the first two carefully and improvise the third. That is backwards, because the decisions layer is where schedules slip.

Five steps or three phases? Simplifying the model

There is no single official number of post-production steps. Different schools and companies group the same work differently, so it helps to know the common simplifications.

A five-step version often looks like this: editing, visual effects, color grading, sound and music, then finishing and delivery. A three-phase version groups the work by what is being finished: picture (edit and VFX), sound (editorial, music and mix), and finishing (conform, color, QC and deliverables). Some people also use “three phases” to mean the whole production cycle of pre-production, production and post-production.

The model you choose matters less than making sure every stage in it has a named owner, a defined handoff and a named approver. A five-step plan with fuzzy approvals will run worse than a ten-step plan with clear ones.

The post production workflow at a glance

The table below maps a common scripted film or series workflow. Unscripted, commercial and corporate projects compress some rows, but the handoff logic is the same.

Stage by stage: what happens and what gets handed off

Every stage below ends with a handoff. The quality of that handoff decides whether the next team starts working or starts asking questions.

Ingest, DIT and dailies

On set or at a near-set lab, a digital imaging technician or data manager copies camera cards with checksum verification, makes multiple backups and logs every clip. The dailies team syncs picture to production sound, applies a viewing look and creates proxies for editorial. The handoff to the edit room should include clip names that match the camera originals exactly, because every later conform depends on that match.

Offline edit

The editor and assistants build scenes from proxies, usually while shooting continues. Cuts move through assembly, director’s cut and producer or studio cuts. Assistants manage bins, temp music and temp effects so that screenings feel close to finished without committing to expensive final work.

Picture lock and turnover

Picture lock is the moment the timing of every shot is frozen. The assistant editor then prepares turnovers: edit decision lists or project exchange files, reference video with burned-in timecode, VFX pull lists and audio exports. Changes after lock are still possible, but each one ripples into several departments, so they should go through a formal change note.

Visual effects

VFX vendors receive plates pulled from the camera originals plus a brief for each shot. They return numbered versions for review, and approved finals are cut back into the timeline. Keeping version numbers visible in the file name and in the review tool prevents the classic mistake of approving v7 while v6 goes into the conform.

Conform and color

The online editor relinks the edit to full-resolution media and checks it against the offline reference. The colorist then grades within whatever color pipeline the project defined in prep. Many productions use ACES, which ACESCentral describes as “the global standard for interchanging digital image files, managing color workflows and creating masters for delivery and archiving.” The point for workflow planning is that the color pipeline must be agreed before the shoot, not discovered in the grading suite.

Sound, music and mix

After a spotting session, dialogue editors clean production audio and plan ADR, Foley and effects editors build tracks, and the composer scores to picture. The re-recording mixers combine everything into the final mix, stems and alternate versions. Mixes must hit the loudness targets in the delivery spec; for US television, the reference is ATSC’s recommended practice A/85, “Techniques for Establishing and Maintaining Audio Loudness for Digital Television”.

QC and deliverables

Quality control checks the finished program against technical and editorial requirements, and the deliverables team builds each master in the format the buyer specifies. Delivery formats are increasingly standardized. The DPP notes that on 1 October 2014, every UK broadcaster made the switch to the AS-11 UK DPP file format for programme delivery. Standard formats make QC more predictable, but they also mean a failed check sends the file straight back.

Where post-production review loops happen, and why they stall

A post-production review happens at nearly every handoff: dailies, each cut, each VFX version, color sessions, mix playbacks and QC fixes. Each loop has the same shape (share a version, collect notes, make changes, confirm the fix) and fails in the same few ways.

• Notes live in too many places. Email, chat threads, marked-up PDFs and verbal comments in a screening all compete. Someone has to merge them, and something gets dropped.
• Nobody knows who has the final word. Five reviewers give notes of equal weight, two conflict, and the editor waits for a decision that no one owns.
• Versions are compared from memory. A producer watches v5 and tries to recall whether the fix requested in v4 happened. Small regressions slip through.
• Notes are not tied to a frame. “The color in the kitchen scene feels off” costs an hour of searching; a note at a timecode costs a minute.

This is the specific problem PeakView was built around. It plays two versions of the same media side by side, synced to the frame, so a reviewer can point at a difference instead of remembering one. Notes sit at the exact frame and timecode, can be resolved and checked off inside the workspace, and export with timecodes or as JSON for the editorial pipeline.

A turnover checklist for every handoff

A turnover is complete when the receiving team can start without asking a single question. Use this as a baseline and add to it per department:

1. Reference video with burned-in timecode and a clear version label.
2. Edit list or project exchange file that matches the reference exactly.
3. A shot, cue or reel list showing what is new or changed since the last turnover.
4. Source media or pull requests with names that match the camera originals.
5. Technical specs: frame rate, resolution, color space, audio channel layout and target loudness.
6. Open notes carried over from the last review, with timecodes, so nothing resolved gets reopened by accident.
7. The approver for this department’s work, and the date their sign-off is due.

Items six and seven are the ones most often missing, and they are the ones that turn a two-day loop into a two-week loop.

How AI is entering each stage

AI is arriving in the post-production workflow as a set of assistants inside existing stages, not as a replacement for the stages themselves. The pattern is consistent: automate the measurable, repetitive part and hand the result back to a person to judge.

• Dailies and editorial: transcription, face and scene search, and assistance with syncing and logging.
• VFX: faster rotoscoping, cleanup and object removal, with artists reviewing each shot. Big Idea lets teams upload footage they shot and add, edit or enhance VFX elements with text prompts, while keeping characters and environments consistent across shots.
• Sound: dialogue cleanup and noise reduction as a starting point for the dialogue editor.
• Deliverables: reformatting finished programs for other aspect ratios and resolutions. Our guide to converting horizontal video to vertical without losing quality covers what that step involves.
• Review and QC: frame-accurate comparison of versions to confirm that only the intended changes were made.

If you are deciding where machine assistance belongs in your own pipeline, our framework for classifying work as human generative or machine generative is a useful test for each stage.

Building a workflow your team will follow

A workflow document only works if people use it under deadline pressure. Keep it short: one page per stage listing inputs, outputs, owner, approver and the review tool. Run a test before the shoot, from camera card to a sample conform and a short QC pass, and fix what breaks. Then protect the review loops, because that is where the calendar is won or lost.

If your team’s reviews still depend on scrubbing through two exports and comparing them by eye, try running your next VFX or color round in PeakView’s side-by-side QA workspace and measure how long it takes to close the notes.