MINIMVisit Website →
← Back to blog

Broadcast Deliverables: 5 Essentials for Broadcaster Acceptance

October 13, 2026
Broadcast Deliverables: 5 Essentials for Broadcaster Acceptance

The minimal survival set for broadcaster acceptance is a picture-locked final master, a music-and-effects (M&E) track, closed captions, a metadata manifest, and proof of chain-of-title with an E&O insurance certificate. Before picture lock, confirm the buyer's exact delivery spec and schedule: that single step prevents most redeliveries. Loudness and caption errors cause the majority of rejected masters, so build QC into the schedule rather than treating it as a final checkbox.

TL;DR:

  • Streamers may require IMF packages, while broadcasters often specify MXF OP1a; confirm resolution, frame rate, color space, and timecode before export.
  • Send full mix and M&E WAV files at 24 bit depth and 48 kHz; add separate stems when the contract requires them.
  • When buyers set no loudness target, U.S. broadcast practice commonly uses around 24 LKFS; submit integrated loudness and true peak measurements with the files.
  • Caption files should match the platform format, and teams should verify timing, spelling, speaker labels, and placement against the final graded picture.
  • Schedule chain of title, insurance, and cue sheets alongside postproduction, and run final QC after color and encoding because either can reintroduce errors.
MINIM
Get Broadcast Deliverables Right
MINIM partners with creative teams to produce cinematic campaigns from concept through final delivery, without expanding internal headcount.
Explore MINIM’s production support

Table of Contents

The Master Deliverables Checklist Every Broadcaster Expects

Every broadcaster or streamer publishes its own delivery spec, but most requests cluster around the same core set of files. Building your package against this list first, then adjusting for the buyer's specific document, saves time and avoids the most common gaps.

  • Final picture-locked master: a mezzanine file (high-bitrate ProRes or DNxHR) for archiving and regrading, plus one or more air-ready files matching the buyer's wrapper and codec requirements.
  • Audio deliverables: a full mix, a complete M&E track with no dialogue, and stems or trackouts when the contract calls for them, all delivered as WAV files at broadcast specification.
  • Captions and subtitles: sidecar files in the broadcaster's preferred format, plus embedded captions where the spec requires them for air-ready masters.
  • Textless masters: a version of the program with no burned-in titles or lower-thirds, used for international versioning and promos.
  • Support and marketing assets: key art, poster images, trailers, and promos sized to the platform's published specifications.
  • Metadata manifest: a document listing title, runtime, language, rating, and technical contact information for every file in the package.
  • Legal deliverables: chain-of-title documentation, an E&O insurance certificate, music cue sheets, and any licensing agreements tied to footage or music.

Naming conventions matter more than teams expect. A consistent pattern, such as ShowTitle_EpisodeNumber_Version_Resolution, applied across every file in the package, reduces ingest confusion and speeds up QC on the broadcaster's side.

For teams working under tight budgets or compressed timelines, the minimum survival set still holds: final master, M&E, captions, and chain-of-title. Everything else can often follow under a short grace period, but confirm that in writing with the buyer rather than assuming it. Picture lock is not the finish line. Legal and marketing assets like chain-of-title and cue sheets need their own line item in the schedule, not a scramble after the edit wraps, a point echoed in discussions of IMF packaging workflows. Our own breakdown of mezzanine-first delivery specs walks through how to structure these files so later versioning doesn't require a full re-export.

Choosing the Right Video Format, Codec, and Color Space

Picking the wrong wrapper or color space is one of the most common reasons a technically sound edit still fails ingest. The format decision depends entirely on who is receiving the file and what they do with it next.

  • IMF (Interoperable Master Format): increasingly required by streamers for multi-version masters, since it separates picture, audio, and subtitle components for efficient versioning and archival, as referenced in AMWA's AS-11 specification alongside other packaging standards.
  • MXF OP1a (AS-11): a constrained, play-out-ready package widely used by broadcasters for finished programs, built to carry metadata and captions in a single file.
  • ProRes: common for mezzanine masters and internal handoffs, favored for its editing flexibility rather than for final delivery to air.
  • Resolution and frame rate: confirm whether the buyer wants 1080i, 1080p, or UHD, and whether the project needs to be delivered in the original shooting frame rate or converted; interlaced versus progressive mismatches are a frequent rejection cause.
  • Color space and bit depth: Rec. 709 remains standard for broadcast SDR delivery, while Rec. 2020 and higher bit depths apply to HDR and UHD masters; legal video-level checks (keeping luma and chroma within broadcast-safe range) should happen before export, not after.
  • ACES workflows: useful for productions grading in a wide color gamut and needing a consistent pipeline from camera to final master; our practical guide to ACES color management covers the handoff points that most often introduce errors.

File-naming, timecode continuity, and metadata tagging deserve the same rigor as the picture itself. A master with correct color and audio but mismatched timecode between picture and caption files will still bounce at QC. Confirming the buyer's preferred wrapper and ingest workflow during pre-production, not after the cut is locked, avoids a costly re-wrap later. Encoding choices also affect playback compatibility across platforms, a detail covered in Kudoflix's notes on H.264 and AAC delivery rules.

Getting Loudness and Audio Deliverables Right

Audio masters should arrive as 24-bit, 48kHz WAV files: one full mix and one complete M&E track, with stems delivered separately if the contract specifies them. Getting the loudness target wrong is one of the fastest ways to trigger a rejection, and it's entirely preventable with the right workflow.

  • Default loudness target: in the United States, broadcast audio follows the CALM Act and ATSC A/85 practices, with a target around −24 LKFS commonly used when the buyer doesn't specify otherwise.
  • Measurement and documentation: generate a loudness report showing integrated LKFS and true-peak values, and include it in the delivery manifest alongside the audio files.
  • Normalization order: mix correctly first, then apply file-based scaling before falling back on real-time processing, a sequence outlined in AES guidance on loudness management.
  • Common pitfalls: inconsistent loudness between dialogue and music beds, clipped peaks on sound effects, and missing M&E stems for international versioning.

ATSC A/85 outlines recommended practices for measuring and maintaining loudness across production and distribution, giving production teams a documented method rather than a guess. Including the loudness report and LUFS measurements with the final package, rather than waiting for the broadcaster to ask, shortens the QC cycle considerably. Our guide on audio mix standards for mixers goes deeper into stem preparation for teams handling the mix in-house.

Meeting Caption and Accessibility Requirements

The FCC requires captions to be accurate, synchronous, complete, and properly placed, and video programmers share responsibility with distributors for making sure captions actually reach the viewer. Programming that aired on television with captions generally needs those captions when the same content is distributed online.

  • Deliver caption files in the broadcaster's preferred format, typically CEA-608/708 for traditional broadcast and IMSC1 for streaming platforms.
  • Avoid placing captions over lower-thirds, titles, or other essential on-screen graphics; follow title-safe and action-safe guidelines when positioning them.
  • Provide a plain-text transcript alongside caption files when the buyer's spec requests one.
  • For live or near-live content, expect slightly lower caption accuracy and build in a review pass before the content moves to any on-demand platform.
  • Run a captions QA pass checking timing, spelling, and speaker identification, and attach a certification statement if the delivery spec calls for one.

Pro Tip: Check captions against the final color-corrected picture, not an offline cut; timing drift between versions is a frequent, easily missed error.

Packaging, Naming, and Transferring Files Without Errors

Once every file is finished, how you package and send them matters almost as much as the files themselves. Broadcasters reject clean masters regularly simply because the package arrived incomplete or mislabeled.

  1. Choose the right transfer method: Aspera for large mezzanine files, SFTP for smaller packages, or the buyer's own vendor portal when one is specified.
  2. Build the metadata manifest with every field the buyer requests: title, runtime, audio language, closed-caption flag, content rating, and a technical contact.
  3. Structure folders and file names consistently across picture, audio, captions, and artwork so an ingest operator can identify every asset without opening it.
  4. Generate checksums (MD5 or SHA) for each file and include them in the manifest so the receiving team can verify nothing was corrupted in transit.
  5. Package textless masters, poster art, and trailers as clearly labeled supplemental folders rather than mixing them into the main delivery.

Structured metadata and localization packaging become especially important on multilingual deliveries; tools like Arkian's semantic metadata generation can help smaller teams produce delivery-ready language files without building a full localization pipeline. Our guide to avoiding redelivery through IMF and IMSC1 workflows covers the packaging decisions that most often get revisited after a rejection.

Running QC That Catches Problems Before the Broadcaster Does

Quality control is the actual gatekeeper. A creatively strong cut with illegal color levels, a dropped frame, audio clipping, or mistimed captions will still bounce, regardless of how the final program looks on a monitor.

  • Check frame integrity, program start and end black, and full-roll continuity against the spec's required duration.
  • Verify color legality with a waveform and vectorscope, confirming luma and chroma stay within broadcast-safe range.
  • Scan the full mix and M&E for pops, clipping, and loudness drift, cross-checked against the loudness printout.
  • Confirm caption timing, format, and placement against the final locked picture, not an earlier cut.

A QC report should document scope, the tools used, waveform and vectorscope snapshots, the loudness printout, and caption timecode verification, giving the ingest team everything they need to approve the package on the first pass. Run QC after color and after final encode, never before, since either step can reintroduce an error that passed an earlier check.

Pro Tip: Lock the delivery schedule inside a Post Milestone Calendar and require signoffs at each stage; late creative changes are a leading cause of last-minute QC failures.

How We Structure Deliverables to Avoid Costly Redeliveries

Locking deliverables into the statement of work before production starts prevents the scope drift that turns a clean project into a change order. When the final package, the formats, and the schedule are defined up front, nobody is negotiating captions or stems after picture lock, a practice we detail in our piece on locking TV commercial deliverables into the SOW.

A typical package we build out includes a mezzanine master, two air-ready files matched to the buyer's spec, audio stems, caption files, and a complete metadata manifest, assembled as one unit rather than stitched together at the last minute. We run this against a Post Milestone Calendar established at a delivery kickoff meeting, with governed file transfer through Box or Aspera and signoff checkpoints at each stage. Using IMF and IMSC1 packaging where the streamer requires it has reduced the back-and-forth that normally follows a first submission, a workflow we expand on in our post-production deliverables guide.

What Most Delivery Advice Gets Wrong

What Most Delivery Advice Gets Wrong — overview diagram

Most delivery checklists treat the technical spec as the hard part and the paperwork as an afterthought. In practice, chain-of-title, E&O insurance, and music cue sheets cause as many delivery delays as a bad color pass, because they get scheduled last instead of alongside post-production. The technical side is also more forgiving than teams assume: a mezzanine-first workflow with clearly documented loudness and caption QC will satisfy nearly any buyer's spec with minor conversion, not a full rebuild.

The real point of failure is process, not technology. Teams that skip the delivery kickoff meeting, or treat the Post Milestone Calendar as optional, end up guessing at requirements mid-post and paying for it in redeliveries. If there's one thing to prioritize before anything else, it's getting the buyer's actual delivery document in hand and building the schedule around it, not around an assumed standard. Everything else on the checklist is easier to get right once that document exists.

— Steven Reina

Let Us Manage Your Deliverables From Kickoff to Final QC

We offer integration with agency creative teams to handle commercial production end-to-end, including the technical packaging, loudness compliance, and legal paperwork that broadcaster deliverables require, without adding headcount to your team.

MINIM

If your next campaign needs a clean path from picture lock to broadcaster acceptance, reach out to set up a delivery kickoff and let us build the Post Milestone Calendar around your actual spec.

FAQ

What are campaign deliverables?

Campaign deliverables are the finished assets a client or broadcaster requires at the end of a production, typically including the final video master, audio files, captions, and supporting marketing materials like key art or trailers. The exact list varies by contract and platform, so confirming the buyer's specific delivery document early in production avoids gaps later.

What are the audio standards for broadcast?

In the United States, broadcast audio loudness follows the CALM Act and ATSC A/85 recommended practices, with −24 LKFS commonly used as the target when a buyer hasn't specified otherwise. Deliverables typically include a full mix and M&E track as 24-bit, 48kHz WAV files, along with a loudness report showing integrated LKFS and true-peak measurements.

What are deliverables in film?

In film and television production, deliverables are the complete set of finished files and documents handed over to a distributor or broadcaster, covering picture, audio, captions, metadata, and legal paperwork like chain-of-title and E&O insurance. The specific requirements are defined by the buyer's own delivery specification, which should be confirmed before picture lock.

How to use deliverables in a sentence?

"Deliverables" refers to the finished assets a production owes to a client or broadcaster, as in: "Our deliverables for this project include the final master, M&E track, and closed captions." The word is used across production and business contexts to describe any agreed-upon output due at a project milestone.

Sources