Shot Review Workflow for a Small VFX Studio With No Pipeline Team

Most shot review workflow advice is written for studios with a pipeline team, a farm render manager, a dedicated review tool admin, and a team of TDs to wire it all together. If that is not you, if you are running a boutique VFX studio with six artists and one coordinator who also does scheduling, then most of that advice is useless.

Here is a shot review workflow for small VFX studios with no pipeline team, built around tools you can actually set up in an afternoon.

The Core Problem: No Structure Means Duplicate Work

Without a defined review structure, here is what typically happens: an artist finishes a comp and uploads it to a shared drive folder. The supervisor watches it during lunch and makes a few notes in a Slack message. The artist misses the Slack message, sees the file in the shared drive, and assumes it is approved. The supervisor follows up three days later. Everyone is annoyed, time was wasted, and the comp still has the problem.

This cycle repeats for every shot, every pass. The fix is not a $50k pipeline. It is a clear process where the review happens in one place, comments are attached to the footage, and there is no ambiguity about whether a shot is approved.

Step One: Define Your Review Stages

Even without a pipeline, you can define review stages. For a typical VFX shot, that is:

• Previs or layout pass: the rough animated camera and blocked geo, reviewed for composition and timing.
• Lighting and lookdev pass: the shading and lighting direction, reviewed before full renders.
• Comp v01: the initial composite, reviewed for integration, colour, and grade.
• Final comp: the near-deliverable version, reviewed for all details before QC.

You do not need a database to track these. You need a naming convention and a rule: one review link per stage per shot. Never reuse links. When a shot moves from comp v01 to comp v02, the v02 gets its own link, even if v01 only had two comments.

Step Two: One Review Platform, Not a Folder

The single most damaging habit in small studios is the shared folder review. Someone drops a file in Google Drive and the supervisor opens it in VLC and sends notes in a Slack thread. Two problems: the notes are not attached to the frames, and there is no record of which file was reviewed.

Switch to a video review platform where the artist uploads the render, shares a link, and the supervisor leaves frame-pinned comments directly in the browser. PlayPause works for this without any IT setup: no installation, no admin configuration, no per-seat fees for the artists and the client who needs to see the finals. The supervisor and client are free guest reviewers on the Creator plan.

For a studio of six, a single PlayPause workspace covers everyone. One coordinator manages the workspace, artists upload their shots, and the supervisor reviews in the browser. The whole thing is running in 20 minutes.

Step Three: Naming Conventions That Actually Hold

Small studios skip this and pay for it. Here is a naming format that works:

Use this as the video title in PlayPause when you upload. When the supervisor opens the review link, the title tells them exactly what they are looking at. When you are tracking VFX pulls from offline through delivery, that naming convention is also the thread you follow through the whole pipeline.

• One review link per shot per pass
• Name every upload with project, shot, pass, and version
• Guest reviewers never need to log in
• Set a 24-hour note deadline per round
• Supervisor consolidates notes before artist sees them

Review_Cut_v4.mp4In Review

212160p · ProRes

00:34 / 02:18

SR

Sarah 0:34

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

Step Four: The Supervisor Review Loop

Here is the loop that works in a small studio:

1. Artist uploads completed pass, titles it correctly, shares the review link in the project channel.
2. Supervisor has a 24-hour window to leave frame-pinned comments. No rolling notes after the window closes.
3. If there are client stakeholders, they get the same link. Their notes come in during the same window.
4. After the window closes, the supervisor does a five-minute consolidation pass: merge duplicates, resolve conflicts, mark which notes are from the client versus internal.
5. Artist gets one clean list of timestamped notes. No hunting through Slack.

This loop is the difference between a shot taking three revision rounds and taking one-and-a-half. The consolidation step is where most studios bleed time without realising it.

Step Five: Approval Is a Deliberate Act, Not an Assumption

In small studios, approval often means "I haven't heard anything back, so I guess it is fine." That is how shots get locked that should not be, and how rework happens at the worst possible moment.

In PlayPause, the supervisor can mark a version as approved. That approval is timestamped and logged. When you are creating an audit trail for every note given on a feature film, this matters. For episodic work especially, you want a record of who approved what and when, because when a client comes back six weeks later saying a shot was not approved, you can show them the logged sign-off.

For boutique VFX studios handling episodic work, the audit trail is also useful when handing off shots to a finishing house. You can show the full comment history and the approval timestamp as part of the handoff documentation.

Handling Client Reviews in the Loop

Small studios often have clients who are involved in review. The client might be a director, a production company, or a streaming platform exec. None of them should need a login to see your VFX renders.

PlayPause lets you share an expiring, password-protected link with a client. They open it in their browser, watch the comp, leave comments at the exact frame, and submit. You see their notes alongside the internal supervisor notes in the same review. No email attachments, no "can you resend the file" messages.

For clients who are reviewing VFX shots before the online session, this matters because the turnaround window is tight. Every hour spent waiting for an email with notes attached is an hour of potential rework time lost.

What You Do Not Need

“

The best shot review workflow is the one that runs on its own without you having to remind anyone what to do.

Let me be specific about what a small VFX studio does not need to run a solid shot review workflow:

• You do not need a dedicated pipeline tool like ftrack or Shotgun. Those are powerful, but they are overkill and expensive for a six-person shop. Build up to them if you need them.
• You do not need a custom render viewer. Standard review tools handle all common VFX formats.
• You do not need a pipeline TD to set up review routing. A coordinator can manage PlayPause in an afternoon.
• You do not need per-seat licenses for every artist who uploads. PlayPause's flat workspace pricing means one subscription covers the whole studio.

For small studios comparing options, the PlayPause pricing page shows the flat workspace structure. It is designed so that scaling your team does not mean your review costs scale with it.

Keeping the Workflow Alive as You Grow

The risk with any small-studio workflow is that it collapses when you land a bigger project and bring in two freelance artists. The new artists do not know the naming convention, they upload to the wrong folder, and the review structure falls apart.

The fix is documentation. Write down the five steps above. Put them in a one-page onboarding doc for every new artist or freelancer. When they join, they get the doc before they touch a project file. It takes 20 minutes to write and saves hours of confusion per project.

PlayPause works on this kind of scale, whether you are a two-person studio or a 20-person studio without a pipeline team. Start free on the pricing page and see how quickly your shot review cycle tightens up.