Delivering Broadcast Masters for Approval: What Post Supervisors Need to Know

Broadcast master delivery is where post production meets financial and contractual reality. Missing a broadcast delivery, delivering a non-compliant master, or failing to get the required approvals before submission can have real consequences: penalty clauses, rescheduled broadcast slots, or in the worst cases, rejected deliverables that require expensive remediation.

Post supervisors who manage this well do not rely on memory or informal communication. They build a structured broadcast master delivery approval process that makes every step visible, documented, and tracked. Here is what that process should look like.

Understanding What Broadcasters Actually Need

Before you can build an approval workflow, you need to understand what you are delivering. Different broadcasters have significantly different technical and content requirements.

Technical requirements typically include: video codec and container format, frame rate, resolution, audio channel configuration, loudness normalization target (LUFS), dynamic range, and color space. Content requirements may include: clean versions (M&E tracks), dubbed versions, subtitles, closed captions, and textless elements.

Get the broadcaster's delivery specifications in writing before post begins, not a week before delivery. Every broadcaster has a technical delivery guide or specification document. Some have online portals where you submit materials and they run automated QC. Others use third-party QC houses. Know which process your broadcaster uses and build your approval workflow around it.

The Post Supervisor's Approval Checklist

Broadcast master delivery approval involves multiple distinct sign-off categories. A complete checklist covers all of them:

Each of these requires a documented sign-off. Not a verbal agreement. A documented approval from the right person at the right stage.

For productions where the sound mix approval involves multiple stakeholders, the structured approach described in our guide on sound mix approval workflow for narrative films with multiple stakeholders applies directly here.

Building the Delivery Timeline

Broadcast delivery deadlines are not negotiable. The post supervisor's job is to build a timeline that accounts for every approval stage with enough buffer that a delay in one area does not cascade into a missed delivery.

Work backward from the delivery date:

• Delivery date: Day 0
• Technical QC and corrections: Days -5 to -3 (allow at least 3 days for QC issues)
• Online session and mastering: Days -10 to -6
• Color lock: Days -15 to -11
• Sound mix lock: Days -20 to -16
• Picture lock: Days -30 to -21

These are minimums. Longer productions or complex deliveries (multiple versions, multiple languages) need more buffer at each stage.

If any approval stage slips, the post supervisor needs to know immediately so they can assess whether the delivery date is at risk and communicate that risk to the producer and broadcaster as early as possible. Broadcasters generally prefer to know about potential delivery issues early, not the day before the deliverable is due.

Managing Technical QC Against Broadcaster Specs

Technical QC is a distinct step that often gets compressed or skipped when the delivery timeline is under pressure. This is a mistake. A technically non-compliant delivery that gets rejected by the broadcaster's QC system costs more time than a proper QC pass would have.

The technical QC pass should check:

• Video: codec, container, frame rate, resolution, color space, aspect ratio
• Audio: channel configuration, loudness (LUFS), dialogue level, dynamic range
• Captions: format, accuracy, timing alignment
• Metadata: file naming, program information, episode numbers
• Legal elements: clearance cards, copyright notices, broadcast legal lines

If you are using a third-party QC facility, build their turnaround time into your delivery timeline. Most facilities need 24 to 48 hours for a QC pass on a feature-length program. If they find errors, you need time to correct them and re-QC.

For productions using PlayPause for the approval workflow, the timecoded comment system is useful during QC: the QC facility's notes can be entered as timecoded comments on the review version, the post house addresses them, and the corrections are verified against the same version without anyone having to reconcile separate documents.

Review_Cut_v4.mp4In Review

212160p · ProRes

00:34 / 02:18

SR

Sarah 0:34

Frame-accurate note, everyone sees the exact same thing.

Tracking Clearances and Legal Sign-Off

Broadcast delivery for a factual or documentary program almost always requires legal clearances: music licenses, archive footage licenses, E&O (errors and omissions) insurance clearances. These need to be coordinated with the legal team and incorporated into the delivery package.

The post supervisor needs to track clearance status for every licensed element in the program. A running clearance log that ties each element to its timecode, the license obtained, and the clearance sign-off date is the minimum. A missed clearance on a broadcast delivery is a serious problem.

For programs with significant archive footage, the structured approach described in our guide on keeping archive documentary footage approvals organized across a year-long edit provides a useful framework for the clearance tracking side.

Delivering Multiple Versions

Many broadcast deliveries include multiple versions: the program cut, a clean version without music and effects on certain tracks, a textless version for international use, subtitled versions, and dubbed versions. Each of these is a distinct deliverable with its own approval requirements.

The post supervisor needs to track approval status for each version independently. A table like this in your project management tool keeps it manageable:

Do not mark any version as ready to deliver until all four columns are confirmed.

Coordinating the Final Approval Before Submission

Before you submit anything to the broadcaster, get a final explicit confirmation from the producer (and the EP if required by your agreements) that the delivery package is complete and approved. This is not a formality. It is protection.

Post supervisors who have received a delivery confirmation from a producer only to be told later that the EP had not actually reviewed the final version know exactly how important this step is. The formal approval record that PlayPause's workflow creates is valuable here: when you have a timestamped sign-off from the producer and the EP on the final broadcast master version, you have documentation of what was approved and by whom.

For productions where the broadcaster version and a separate streaming or festival version are being managed simultaneously, the version isolation approach described in our guide on managing multiple cut versions for a broadcaster, festival, and streaming delivery is directly relevant.

After Submission

Once the delivery is submitted, the post supervisor's job is not done. Confirm receipt from the broadcaster's technical team. Follow up on QC results. If the broadcaster's QC raises issues after submission, you need to be available to address them quickly.

Keep a record of the submission: what was submitted, when, the version numbers and file specifications, and who confirmed receipt. This documentation is valuable if there are any disputes about what was delivered and when.

Getting the Workflow in Place

Broadcast master delivery is high-stakes, and the approval workflow that supports it needs to be more rigorous than what most productions run. PlayPause's structured review and approval tools give post supervisors the visibility and documentation they need: version-specific review links, formal approval locks with timestamps, and a full record of who approved what and when.

The Agency plan at $19 per month covers your full post production team with free guest seats for your director, DP, sound mixer, legal contact, and broadcaster representative. If your current delivery approval workflow is held together by email and spreadsheets, get a more structured system in place before your next broadcast master deadline. Start PlayPause free and build the workflow before your next delivery cycle.