How Scripted Drama Post Supervisors Track Network Notes Across Picture, Sound, and VFX

Network notes on a scripted drama episode do not respect departmental boundaries. A single note from a network EP might touch the picture cut, require a sound redesign, and trigger a VFX rework in the same breath. The post supervisor's job is to make sure each department gets the right piece of that note, in the right form, at the right time, and that the resolution of all three pieces gets confirmed before the episode locks.

When I talk to post supervisors tracking network notes across picture, sound, and VFX departments, the biggest complaint is not volume. It is routing. A note arrives. It is clear what needs to happen at the picture level. But the downstream effects on the temp mix, the VFX pull, and the delivery timeline are not automatically visible. Notes get addressed in one department and forgotten in the others. The episode ships with a picture change that the sound department never knew about.

Here is the tracking system that prevents that.

Why Department Silos Break Network Note Tracking

Each department on a scripted drama runs its own note-taking and revision process. The editors have their own cut notes. The sound team has their spotting notes and temp mix comments. The VFX team has their shot review process. In a well-run production, these systems are high-quality within each department. The problem is at the handoff points between departments.

When a picture change is made in response to a network note, that change does not automatically propagate to the sound team's session or the VFX team's pull list. The assistant editor has to remember to notify the sound editor that scene 7 was recut. The post supervisor has to remember to send updated VFX pulls to the VFX coordinator. Under schedule pressure, these notifications get missed. For a targeted solution on one of the most common failure points, see how to prevent a sound designer from working off an outdated cut.

The result is sound work built to a cut that no longer exists, VFX shots pulled from the wrong version of the scene, and a post supervisor who spends significant time chasing departments to confirm they have the right materials.

Build a Cross-Department Note Routing Table

The tool I use is a note routing table: a single document, maintained by the post supervisor or post coordinator, that maps every network note to its downstream departmental impact and tracks resolution status across departments.

The table structure looks like this:

This table is updated every time a note arrives and every time a department marks an item resolved. The post supervisor is the owner. Departments report status to the post supervisor; they do not update the table directly.

Keeping the post supervisor as the single point of record prevents conflicting status updates and ensures that a note is only marked fully resolved when all three departments have confirmed their piece is done.

Handling Notes That Arrive Mid-Department Work

The hardest timing situation for a post supervisor is when network notes arrive while all three departments are already working on previous-round revisions. Sound is in the middle of a temp mix for round three. VFX is rendering updates from round two. Picture is locked at round three waiting for VFX. Then round-four network notes land.

The rule I apply: do not interrupt a department mid-session with a new note round. Collect all round-four notes, complete the routing table, and schedule a formal handoff meeting with each department head before any new work begins. That 30-minute meeting saves four hours of rework that happens when departments start working from partial or mis-communicated notes.

For the picture side of this coordination, how post supervisors manage colorist and editor handoffs without version chaos covers the version discipline that supports clean note routing.

The Picture Change Notification Protocol

Every time the picture editor makes a change in response to a network note, the post supervisor should receive a notification that includes: the timecode of the change, the nature of the change, and which network note it addresses. This is not the editor being micromanaged. This is the post supervisor having the information they need to update the routing table and notify downstream departments.

A shared review platform with version stacking makes this straightforward. When the picture editor uploads a revised version, the version comparison shows exactly what changed and at which timecodes. The post supervisor can see the diff without asking for it.

For sound, the picture change notification should specify whether the change affects: dialogue sync, sound effects cues, temp music edit points, or any existing ADR timing. Most picture changes fall into one of these categories, and knowing which one means the sound editor can estimate the impact and prioritize accordingly.

For VFX, the notification should specify whether the changed cut contains or affects any VFX pulls. Even a small picture change that moves a cut point within a VFX shot can invalidate the pull and require a new turnover.

Centralising the Network Sign-Off Record

When all three departments have resolved their piece of a network note, the post supervisor needs to confirm that resolution to the network. This should not be a casual "I think everything is done" email. It should be a structured sign-off record that states which notes were addressed, which version they were addressed in, and which departments were involved in each resolution.

For productions using a structured video review platform, the version comment thread serves as this record. The post supervisor can leave a summary note on the approved version: "Network notes from round three addressed. Picture: scene 4 tightened 6 seconds (24:12), VFX hallway shot revised (31:07), ADR integrated (18:44). Sound: temp mix updated to reflect picture changes at scenes 4 and 7. VFX: hallway comp revised and cleared. Awaiting network confirmation on this version."

That is a clean record. It is time-stamped, tied to a specific version, and covers all three departments. When the network confirms, their confirmation is also in the same thread.

For related reading on how broadcast editors build this kind of documentation into their delivery workflow, broadcast editors delivering QC-ready cuts with timestamped note trails is directly relevant.

• Note routing table updated immediately on note receipt
• Departmental impact mapped for every note before any work begins
• Mid-session note arrival handled with a formal handoff meeting
• Picture change notification sent to sound and VFX for every edit
• Cross-department resolution confirmed before note is closed
• Network sign-off record documents all three departments' confirmations

Scaling This System Across a Season

For scripted drama post supervisors working on a full season, the note routing table becomes a season-level document with one tab per episode. Locking a fine cut when executive producers are in different time zones is the complementary challenge once the departmental notes are resolved. Version naming conventions need to be consistent across episodes so any department can identify the right materials for any episode without asking.

A centralized video review workspace where each episode has its own review environment, with version stacking and time-coded comments, is the infrastructure that makes this manageable at season scale. PlayPause's approval workflow is designed for exactly this kind of multi-department, multi-round review where each stakeholder has a documented role and every resolution is on record.

For scripted drama teams managing network notes across picture, sound, and VFX on a recurring production schedule, the Agency plan at $19 per month flat covers your entire team with free guest access for network reviewers. See pricing and stop losing notes in the spaces between departments.