How VFX Coordinators Can Keep Shot Review Notes Organized Across a Full Season

A VFX coordinator on a full season of episodic television might be tracking 200 to 500 active shots at any given time, each at a different stage of completion, with notes from multiple supervisors, a production schedule that shifts weekly, and a delivery pipeline that does not care about any of it.

VFX coordinator shot review notes need a system that is rigid enough to prevent chaos but flexible enough to survive the reality of production. The three things that consistently go wrong are: notes that are not tied to a specific version of a shot, notes from multiple reviewers that contradict each other, and shots that get re-reviewed after a fix without the reviewer knowing what the previous note said.

Here is how to build a system that handles all three.

The Version Problem

The single most common failure I see in episodic VFX review is a note that is not attached to a version. For productions with large-file deliverables like crowd simulations, see reviewing crowd simulations with a VFX supervisor when the renders are huge files for how proxy review fits into a system like this. "The fire simulation looks low-res" is not a useful note if the artist does not know whether it applies to v003 or v007. By the time a shot reaches v010 on a complex effects sequence, the v003 note might have been addressed and then reintroduced in a subsequent change. If you cannot track which version a note applies to, you cannot know whether it has been resolved.

Every note in your tracking system needs to include:

• Shot code (e.g., EP3_VFX_220)
• Version number the note applies to (e.g., v006)
• Timecode or frame reference
• The actual note
• Reviewer name
• Status (open, in progress, resolved, won't fix)

PlayPause handles this automatically: each uploaded version of a shot has its own comment thread, so notes from v003 are visually separate from notes on v007. When an artist uploads v008, the reviewer can compare it directly against v007 and see which comments were resolved.

The Multi-Reviewer Problem

Episodic VFX typically has at least two layers of review: the internal VFX supervisor and the show's executive producer or director. Sometimes there is a third layer from a studio-side visual effects producer. Each reviewer has different priorities and different technical vocabularies.

The coordinator's job is to consolidate notes from multiple reviewers before passing them to the artist. This means:

1. Reviewing all notes on a shot after each review session.
2. Identifying conflicts between reviewers.
3. Escalating conflicts to the VFX supervisor (or show supervisor if needed) for resolution.
4. Documenting the resolved direction before the artist starts work.

With a shared review link on PlayPause, all reviewer comments appear in one thread with attribution. The coordinator can see immediately if the VFX supervisor and the director have different opinions on the same frame. That conflict gets resolved at the coordinator level before it ever reaches the artist.

Building a Seasonal Shot Tracking System

The master tracking document for a full season lives outside the review tool, usually in a spreadsheet or production management platform. The review tool handles per-shot notes; the master tracker handles aggregate status.

Here is a working column structure:

Update this daily. The review tool handles the notes; the tracker handles the production status. These two systems should always be in sync.

Handling Review Session Cadence

On a full season, daily review sessions are common during heavy production periods. The coordinator's role in each session is not just to facilitate, but to prepare.

Before each session:

• Confirm which versions are being reviewed
• Pull the outstanding notes from previous versions so the reviewer knows what was already requested
• Note any shots that need special context (e.g., "This version addresses the density note from Tuesday's session")

The reviewer should not come into a session cold. They should know what the previous note was and whether it was addressed. When PlayPause shows the comment history on previous versions, this context is available without any prep work from the coordinator.

Common Coordinator Mistakes to Avoid

Passing notes before consolidating. If two reviewers commented on the same shot and you have not resolved the conflict, do not send notes to the artist yet. You will be generating rework.

Marking a shot approved too early. A supervisor saying "looks good in the session" is not an approval. The formal approval happens when they confirm on the review link. Do not update your tracker to approved until that confirmation exists.

Losing note history after a shot is approved. Approved shots still need their comment history. QC issues can be caught after approval, and the VFX producer may need to understand what changes were made between v001 and the final version.

Keeping Notes Actionable at Scale

When you are tracking 300 shots, note quality becomes a production issue. Vague notes on 10 shots create 10 rounds of clarification. At 300 shots, that is a management crisis.

For a smaller studio context with fewer shots in flight, shot review workflow for a small VFX studio with no pipeline team has a lighter-weight version of this process. For a full guide on what makes a VFX note actionable, the how to give notes on a comp pass that the artist can act on immediately post has the framework. As coordinator, you are in a position to enforce note quality standards. When a reviewer leaves a vague note, it is your job to follow up and get the specific frame reference and expected result before it reaches the artist.

For teams managing visual effects turnover alongside an active edit, the how to keep a VFX turnover tight when editorial is still cutting picture post covers the handoff coordination side of this problem.

• Every note must include shot code, version number, frame reference, and expected result
• Consolidate multi-reviewer notes before passing to artists
• Escalate reviewer conflicts before revision work begins
• Update master tracker daily with current version and approval status
• Preserve comment history on approved shots
• Set explicit review deadlines for each session and enforce them

If your current season-level VFX tracking is living in email threads and shared spreadsheets without a connected review tool, you are creating coordination overhead that the coordinator role should not have to carry. PlayPause connects shot-level notes to version history so the two systems actually talk to each other. Start a free workspace and try it on a single episode before rolling it out to the full season. See pricing for studio plans.