Managing Versioned Cuts Across Network, Studio, and Streaming on One Show

On some shows, the same episode has to exist in three different versions simultaneously. The network wants a 42-minute broadcast cut. The streaming platform wants a 48-minute extended version. The studio has its own deliverable requirements. All three are being worked on at the same time, all three have different stakeholders reviewing them, and an editorial change in one version may or may not apply to the others.

Managing versioned cuts across network, studio, and streaming on a single show is one of the more demanding version control problems in post-production. Here is how to do it without losing your mind.

Why this gets complicated so fast

Three versions sounds manageable until you realize that each version has its own stakeholder chain, its own review cycle, and its own delivery spec. The network broadcast cut has network S&P notes. The streaming version has additional content that the network version does not include. The studio is reviewing both and has notes that apply to one but not the other.

The editorial team is trying to track which change applies to which version. The post supervisor is managing three separate QC and delivery tracks. The editor is working on Sequence A, Sequence B, and Sequence C in the same Premiere timeline and trying not to inadvertently apply a network edit to the streaming version.

The version naming and isolation framework

First principle: each version is a separate project in your review platform. Not a separate upload in the same project. A separate project with its own name, its own stakeholder access, and its own approval chain.

Project naming that works:

• SHOW_TITLE_S01E04_NETWORK_BROADCAST_V[n]
• SHOW_TITLE_S01E04_STREAMING_EXTENDED_V[n]
• SHOW_TITLE_S01E04_STUDIO_MASTER_V[n]

Each has its own version counter. Network Broadcast might be on V5 while Streaming Extended is on V3 because they started at different times and have different revision cadences.

Tracking which changes apply where

The most error-prone part of managing three versions is tracking whether an editorial change from one version needs to be replicated in another. This requires a decision log that explicitly flags cross-version applicability.

For every editorial change made in response to notes:

• Network cut: dialogue trim at 00:28:14 (does NOT apply to streaming, which keeps the extended version)
• Network cut: broadcast language substitution at 00:33:02 (DOES apply to streaming as the baseline language standard)
• Streaming cut: additional scene insert after 00:41:00 (NOT in network version by definition)

The editor needs to make these distinctions explicit in the project notes, not just in their head. I recommend a simple change log format maintained by the assistant editor:

• Change description and timecode
• Which version(s) it applies to
• Whether it was cross-applied and confirmed
• Who authorized the cross-application

Without this log, changes bleed between versions accidentally and you end up with a network cut that contains streaming content or a streaming version that has network censorship applied incorrectly.

The review workflow for three simultaneous versions

Each version needs its own review link for its own stakeholders. The network executive should never be reviewing a streaming link and vice versa. This is not just about access control; it is about avoiding note contamination. A network executive who sees the streaming extended content will start giving notes based on content that should not be in their version.

In PlayPause, you upload each version to its own workspace and set access accordingly. Network executive gets the network broadcast workspace. Streaming platform contact gets the streaming workspace. Studio gets its own workspace with whatever the studio needs to see. Guest access is free, so adding a new reviewer to the appropriate workspace costs nothing.

For the studio workspace, where legal and business affairs are often also reviewing, the approval workflow feature gives you a documented sign-off record per version. That matters for deliverables where the studio needs to formally clear a cut.

Handling editorial conflicts between versions

Sometimes the network wants a change in the broadcast version that, if cross-applied, would alter the streaming version in a way the showrunner does not want. This is an editorial conflict that requires an explicit decision.

The worst outcome is the post supervisor or editor making a quiet judgment call and applying the change to one version but not the other without documenting it. That comes back to bite you when the streaming platform asks why their version has a different scene structure than the network version.

Every cross-version decision needs to be documented and attributed. "Network note at [timecode]: cross-applied to streaming with showrunner approval on [date]." Or: "Network note at [timecode]: NOT cross-applied to streaming. Streaming version retains original cut per showrunner decision on [date]."

For shows managing even more version complexity, see how post houses handle simultaneous notes from multiple network executives, how multi-stakeholder sign-off on TV drama episodes runs cleanly with the right gate structure, and how locked cut confirmation works without chasing email chains.

What the platform cost looks like

Running three separate workspaces for one show across a broadcast series is exactly the use case the Agency plan at $19 per month is designed for. Flat workspace pricing means you are not paying per network executive or per streaming contact who reviews a cut. The whole team, all the external reviewers, all the versions, for a single monthly fee.

Managing versioned cuts across network, studio, and streaming is not glamorous work. It is precision work. Get the isolation and the change log right, and it becomes routine. Start PlayPause free and set up your version workspaces before the first review request comes in.