Managing Rundown Changes and Video Package Updates in the Same Review Session

Here is a scenario every producer knows: you are 90 minutes from air. The rundown changes. A segment gets dropped, another gets expanded, and now two packages need to be re-cut to fit the new durations. While that is happening, a reporter calls in with a new line for the script that changes the B-roll sequence. The overnight editor is juggling three cuts. And no one is quite sure which version of the lead package is the one that just got approved.

Managing rundown changes and video package review sessions simultaneously is the most chaotic part of live news production. And most teams handle it with a combination of shouted hallway updates, Slack messages, and a lot of trust that the right version ends up on the server.

That trust fails. Regularly.

The Core Problem: Rundown and Review Are Treated as Separate Workflows

In most newsrooms, the rundown lives in a newsroom system. Package review happens over email, screener links, or someone walking the producer's office with a laptop. These two workflows do not talk to each other. When the rundown changes, the review process does not automatically know about it. When a package gets updated after approval, the rundown does not flag that the reviewed version is now outdated.

This disconnection is where errors live. The same gap causes broadcast editors to struggle with delivering QC-ready cuts with timestamped note trails and makes locked cut confirmation from showrunners so unreliable. An approved version of a package gets replaced by a late-breaking update that was never formally reviewed. The producer thinks the package is good to go because they approved something. They just did not approve this version.

What a Unified Review Session Actually Looks Like

A unified session means the producer is reviewing packages inside the same tool where approval status is tracked, and that tool is updated in real time as packages change. When a new cut lands, the old approval is automatically flagged as applying to a previous version. The producer knows they need to re-review.

This sounds obvious. Almost no newsroom actually does it.

The closest most teams get is a Slack channel where the editor posts "package updated" messages and hopes the producer sees them before air. That is not a system. That is hope with a chat interface.

With a proper video review tool, the workflow looks like this:

The key feature is version-locking. When a producer clicks approve, they are approving a specific file, not the package concept in general. If the editor makes another change, the approval from 40 minutes ago does not automatically carry over. The producer has to confirm the new version.

Handling Rundown Changes Mid-Session

Rundown changes create two specific problems for package review:

Duration changes. A package cut for 1:45 now needs to be 2:10 or 1:15. The editor re-cuts it. Is the newly timed version considered a new version requiring re-review? Yes. Always. Even a five-second trim can remove or alter a key editorial claim.

Slot changes. A package moves from the A block to the C block. This may seem like a production issue rather than an editorial one, but slot changes often mean the package needs a different cold open or different tag copy. Which means the editor touched the cut. Which means re-review.

Build both of these into your standing policy. Any editorial change to a package after it has been approved requires a new review pass, however brief. The review can be fast. But it cannot be skipped.

For newsrooms also dealing with the compliance dimension of these changes, the guide on news standards compliance review when a story breaks overnight covers how to keep that layer of oversight running even under time pressure.

The Version Labeling Convention That Actually Works

One of the fastest improvements a news team can make is adopting a consistent version label format. Here is a simple one:

The label that matters most is the last one: the version that went to air. That is your record. That is what you pull when a viewer complaint comes in three weeks later asking what was in the package at the time of broadcast.

If you are tracking this in a review tool that attaches approvals to specific file versions, the AIR label becomes a formality because the tool already has the record. But even then, naming conventions matter because humans read file names and make assumptions. Clear labels reduce the chance that someone grabs the wrong file off the server.

Keeping the Producer Out of the Weeds

The producer's job during the final 90 minutes before air is not to chase package statuses. It is to make editorial decisions. The more time a producer spends asking "is that package approved yet?" the less time they have to actually produce the show.

A review system with a live status dashboard flips this. The producer sees at a glance which packages have pending reviews, which are approved on the current version, and which have been updated since their last approval. They pull attention only where the status is yellow or red.

This is exactly what I built PlayPause to do for teams dealing with exactly this kind of multi-stream coordination. The tool shows every reviewer's status in real time. If the editor uploads a new version, the producer sees it immediately flagged as needing review. No Slack message required. No hallway shout.

For newsrooms thinking about how this fits into a broader approval audit trail, see the post on audit trails for news package approvals when editorial decisions are challenged. The review session is not just about getting the package to air. It is about having a defensible record of what happened.

When the Rundown Freezes and Packages Do Not

There is a window, usually 20 to 30 minutes before air, when the rundown should be frozen. No new slot changes. No new segments. The producer calls the rundown locked and everything from that point is execution, not planning.

Packages, however, keep getting updated right up to the last minute. A reporter calls in a correction. A legal note comes back. A graphic needs a title card change.

During the frozen rundown window, any package update needs an explicit fast-track review. One person. Two minutes. A documented approval. Not a conversation.

Build this fast-track review into your pre-air checklist. When the rundown freezes, your review tool should show every package's current approval status. Anything without a green approval on the current version is a flag that needs to be resolved before air.

PlayPause is priced flat per workspace, so your entire production team, producers, editors, legal, and however many reviewers you need, works inside one plan without adding per-seat costs every time someone new joins the review. The Creator plan starts at $9/month for smaller operations and the Agency plan at $19/month covers larger teams. Free guest reviewers mean your on-call legal counsel can jump in for a fast review without you needing to add a license.

If you want a review process that actually keeps up with your rundown, set up a free PlayPause workspace and see what a live-status review dashboard does for your pre-air workflow.