Handling Distributor Version Notes on Top of Broadcaster Notes in the Same Edit

Getting distributor version notes on top of broadcaster notes in the same edit is one of the most disorienting situations a post supervisor can walk into. Two sets of stakeholders, both with contractual authority over the final deliverable, giving notes that may directly contradict each other on the same cut. The editor is caught in the middle. Without a system, someone's notes get lost or overridden without the right person knowing, and the deliverables end up wrong for at least one party.

Here is a clear-headed way to handle it.

Understanding Why the Notes Conflict

The distributor and the broadcaster want different things from the same content, and that difference is structural. The broadcaster has specific editorial and compliance requirements tied to their platform and audience. The distributor is thinking about international licensing, marketing cuts, and sometimes entirely different running times for different territories.

Those are legitimate differences. The problem is that when both sets of notes arrive in the same inbox on the same day, the editor has no clean way to separate them. A broadcaster note to cut a scene and a distributor note to expand the same scene are not a creative disagreement. They are two valid instructions for two different deliverables that happen to live in the same timeline.

The first step is always to determine whether the production is creating one master cut with alternates, or genuinely two separate versions. That decision has to come from the showrunner or the executive producer before notes are distributed. If the editor is making that call themselves, the process is already broken.

Separating the Note Streams Before They Hit the Edit

The practical fix is to route broadcaster notes and distributor notes into separate review streams from the start. Both parties watch the same cut, but their notes go into different places.

With PlayPause, I would set this up as two separate review links for the same version. The broadcaster gets a secure expiring review link shared only with their reviewing team. The distributor gets their own link. Both sets of notes land on the same timeline, but they are visually separated by reviewer identity. The editor can filter by reviewer and see broadcaster notes only, or distributor notes only, without the two sets bleeding into each other.

This separation matters most during the revision pass. When the editor is addressing broadcaster notes, they should not be looking at distributor notes for the same sequence. Mixing them produces a hybrid cut that satisfies neither party.

Building Two Deliverable Tracks in the Same Post Workflow

If the production has confirmed that two separate versions are needed, the post workflow needs to accommodate that from picture lock forward. Here is how I would structure it.

Lock one master. Start with a single picture lock that both parties have reviewed. Get the broadcaster and distributor both to sign off on the structural cut before any version-specific changes are made. This gives you a clean foundation and prevents one party from later claiming the baseline was wrong.

Branch at lock. After the master is locked, create two branches in your versioning system. The broadcaster version and the distributor version are now separate editorial tracks. Changes to one do not affect the other.

Route notes by version. Every note from the broadcaster goes on the broadcaster version link. Every note from the distributor goes on the distributor version link. There is no shared note space between them once the versions are branched.

Review each version independently. The broadcaster approves the broadcaster cut. The distributor approves the distributor cut. Neither party reviews the other's version unless there is a specific reason to do so.

When Notes Actually Conflict on the Same Version

Sometimes the production is only delivering one version and the distributor and broadcaster both want to make changes to it. In that case, the conflicts need to be surfaced and resolved before the editor touches anything.

The post supervisor's job here is to act as a translator. Pull up both sets of notes in PlayPause and look for overlapping timecodes. Any note from the broadcaster that touches the same range as a note from the distributor is a potential conflict. Flag those ranges and bring them to the executive producer for a decision.

Do not let the editor try to reconcile conflicting notes. That is an editorial decision that belongs with the people who have contractual authority, not with the person implementing the cut. An editor who chooses between a broadcaster note and a distributor note without explicit direction is making a decision they should not own.

For productions managing similar multi-stakeholder conflicts, the post on managing multiple cut versions for a broadcaster, festival, and streaming delivery addresses a closely related scenario.

The Delivery Documentation Problem

When you are delivering two versions, you need to be able to show what was approved for each. The distributor should not be able to look at the delivered version and claim it includes a change they never approved. The broadcaster should not be able to say the version they received does not reflect their sign-off.

PlayPause's approval records solve this cleanly. Each version has its own approval history. The broadcaster's sign-off is attached to the broadcaster version. The distributor's sign-off is attached to the distributor version. When there is a delivery dispute, you pull up the relevant approval record and the dispute is resolved by the record, not by memory.

For the broader QC documentation picture, the post on how broadcast editors deliver QC-ready cuts with timestamped note trails covers how to carry the note history through to delivery in a format QC teams can actually use. And for productions managing offline and online approvals on the same versioned deliverable, syncing offline and online edit approvals across a broadcast series addresses that layer.

Protecting the Edit Team

The distributor-versus-broadcaster note problem has a cost beyond the administrative hassle. Editors who are given conflicting instructions and no process for resolving them burn time, make wrong calls, and sometimes produce deliverables that neither party accepts. That is a waste of skilled labor and post budget.

A clear note routing system, version branching, and documented approvals protect the edit team from being asked to solve problems that belong at the executive level. The editor implements decisions. The platform keeps the record. The EP makes the calls.

If your production is still managing broadcaster and distributor notes in the same email thread, try PlayPause free on your next project. Set up separate review links for each stakeholder group on the same cut and see how much cleaner the note conversation becomes.