Shot Turnover Process for a Boutique VFX Studio Handling Episodic Work
A solid shot turnover process is what separates boutique VFX studios that thrive on episodic work from those that drown in version confusion and missed deliverables.
Episodic VFX work is a different beast from feature work, and the shot turnover process that works for a single film often breaks down completely on a 10-episode series with 200 shots per episode. The pace is faster, the review cycles are shorter, the client is often a broadcaster with strict delivery requirements, and there is no slow ramp-up period. Episode one is due before episode four has even been turned over.
For a boutique VFX studio handling episodic work without a full pipeline team, the shot turnover process is either the engine that keeps everything moving or the source of constant firefighting. Here is how I would build it.
What Shot Turnover Actually Means in Practice
Shot turnover is the process by which visual effects shots are formally handed from the editorial department to the VFX department, worked on, reviewed, and handed back. For a boutique studio, this involves several moments:
- The editorial team delivers the offline cut with VFX pulls marked.
- The VFX coordinator logs each shot, assigns a shot number, and creates the review infrastructure for that shot.
- Artists receive the shot brief and source plates.
- The shot goes through internal review rounds.
- Approved shots go through client review.
- Locked shots are delivered to online/finishing.
Every one of these steps is a handoff. Every handoff is a potential point of failure if there is no documented process.
The Turnover Package: What You Need From Editorial
Before a single artist touches a shot, the editorial team owes you a complete turnover package. Many boutique studios accept incomplete turnovers because they are eager to start work. This is a mistake that costs you double.
A complete turnover package includes:
| Item | What it is | Why it matters |
|---|---|---|
| Offline EDL or AAF | Edit decision list with timecode | Establishes sequence timecode for all shots |
| VFX pulls list | Shot numbers, sequence, frame range | Official shot list to work from |
| Source plates | High-res original camera files | What the artist actually composites onto |
| Scene reference | On-set stills, lighting notes | Integration reference |
| Production notes | Any known issues with the plate | Saves time finding problems that already exist |
| Delivery spec | Resolution, format, frame rate, colour space | Non-negotiable technical parameters |
Do not start work without the delivery spec in writing. For studios also managing network broadcast compliance notes and tracking which changes were made, having the delivery spec attached to the review record from day one is essential. On episodic work, a broadcaster might change specs between season one and season two. If you are working from memory or a verbal instruction, you risk delivering to the wrong spec for an entire episode.
Building the Review Infrastructure Before Artists Start
For each episode, the VFX coordinator should set up the review infrastructure before any renders exist. This means:
- Creating a naming convention for every shot: EP03-SH054-COMP-v00 is a placeholder, not yet a render.
- Creating a review folder or project in PlayPause for that episode, with each shot as a named slot.
- Setting up the client review link for the episode, which will be used for final client approvals once shots are ready.
Doing this upfront means that when an artist finishes the first pass of a shot, the infrastructure exists to upload, name correctly, and route it to the internal review without any coordinator overhead.
- Complete turnover package received before work starts
- Naming convention applied to every shot before any render exists
- Internal review infrastructure set up per episode
- Client review link prepared and access-controlled
- Delivery spec confirmed in writing
The Internal Review Loop for Episodic
On a feature, you might have days between review rounds. On episodic, you have hours. A one-day internal review turnaround is not unusual on a series with weekly broadcast delivery.
The loop I would use for a boutique studio:
- Artist submits render by end of local business day.
- VFX supervisor reviews in the evening using frame-pinned comments in PlayPause. Notes are left on the specific frame, not in Slack.
- Notes are available to the artist at the start of the next morning.
- Artist completes revisions and submits new version.
- If supervisor approves, shot moves to client review queue. If not, another morning review happens.
This loop keeps artists working during business hours and supervisors reviewing in off-hours. For studios managing dailies review when a director and supervisor are in different time zones, this same after-hours review approach is the only sustainable model, which is not glamorous but it is how episodic VFX gets made at boutique studios. The key is that the notes are already attached to the frames when the artist opens their workstation in the morning. No email to check. No Slack thread to parse. The review link has the notes, right on the frames.
Client Review on Episodic: Managing Multiple Episodes Simultaneously
The client review phase on episodic is where most boutique studios lose control. You might be pushing shots for client review on episode two while episode one is still receiving network notes. The same client contact is reviewing both. Without clear version separation, they will leave a note on an episode two shot that references what they saw in episode one, or vice versa.
The fix is episode-segregated client review. Episode one has its own client review link. Episode two has its own. They are never combined. When you send the client a weekly update, you send two links: "Here is the episode one update, please review shots SH023, SH031, and SH044. Here is the episode two update, please review shots SH007, SH015, and SH022."
The client knows exactly which episode and which shots they are reviewing. Their notes apply to specific shots in specific episodes. No drift, no cross-episode confusion.
For managing per-episode approval status across a streaming series, this episode-segregated structure is the baseline requirement.
Handling Network or Broadcaster Notes on Delivered Episodes
On episodic work, delivered episodes sometimes come back with network notes. This is normal. What is not normal is receiving network notes with no clear timecode reference, applying them to the wrong version, or delivering revisions to a shot that was already in the next-episode pipeline.
The PlayPause review trail handles this. When the network sends notes on episode three, you open the episode three delivery review, find the note, and can verify exactly which version the network watched. If you need to pull that version back and make a revision, you have the original source in the system.
For handling distributor version notes on top of broadcaster notes in the same edit, the same version-locking principle applies at the content level, and it is worth reading for the broader delivery context.
Protecting Unreleased Episodic Content
Episodic VFX work often involves content that is under strict NDA. A single leaked still from an unaired episode can cause real damage to a client relationship and a future contract.
PlayPause supports password-protected and expiring review links. Every client-facing review link for a boutique VFX studio should be:
- Password protected with a unique password per episode.
- Set to expire after the review window closes (usually 72 hours for client reviews).
- Shared only through a secure channel, not in a public Slack channel.
This is basic security hygiene that costs nothing to implement and protects everyone.
Set the expiry when you create the link, not as an afterthought.
Delivery and Archiving
When an episode is fully approved and delivered, the review infrastructure for that episode should be archived, not deleted. On a long-running series, you will inevitably receive a note six months later from a distributor requesting a technical revision to a delivered episode. If you have archived the approved review links, you can immediately pull the approved version, verify what was delivered, and confirm whether the revision is valid.
For archiving approved course video versions so rollback is always possible, the same archiving logic applies, and a boutique VFX studio should treat episode archives the same way.
The Pricing Reality for Boutique Studios
For a boutique studio, per-seat pricing on review tools is a problem. You have artists, supervisors, a coordinator, and multiple client contacts per episode. Per-seat tools charge for each of them. On a busy season with eight active episodes, the seat cost adds up quickly.
PlayPause's flat per-workspace pricing means one workspace covers the whole studio. Guest reviewers (including the network contact and the production company) are always free. The pricing page has the full breakdown, and the Agency plan at $19 per month per workspace is the right fit for a boutique studio handling episodic at volume. Start with the free tier to build your turnover process and upgrade when the volume justifies it.
Priya Menon writes about video marketing and content workflows for PlayPause. She covers how marketing teams, brands, and creators review video, approve campaigns, and ship content faster.
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