Broadcast VO Delivery Standard: What to Receive

A broadcaster rejects your file two days before air date. You escalate to your supplier. They confirm the recording was technically correct — clean performance, right talent, no noise. The problem was the delivery format. The file was outside loudness spec for the destination market. Nobody in the chain flagged it, because nobody in the brief specified the destination.

That is not an audio engineering failure. It is a handover failure — and it happens routinely on multi-market campaigns where PMs accept delivery packages without a defined standard to check them against.

Most PMs have never been told what a compliant broadcast voice-over delivery actually looks like. That gap is what creates the problem: not bad recordings, but technically correct recordings delivered in technically non-compliant format. This post defines the standard. If your current supplier isn't delivering to it without being asked, you are doing their QA for them.

Why Broadcast Rejection Happens After a Technically Correct VO Session

The talent did their job. The director approved the take. The engineer mixed it. And two days before air, a broadcaster rejects the file.

Broadcast rejection happens at the technical handover stage — after the creative work is done — and it happens because the file that left the studio was not built to the spec the destination required.

The core issue is a brief gap that occurs dozens of times per week across multi-market productions: the delivery destination was never specified in the original brief. Without a named target market and distribution channel, the engineer defaults to a standard. That standard may be correct for one market and wrong for three others in the same campaign. A file mastered for European broadcast will fail US broadcast QC at the same loudness level — not because the engineer was wrong, but because the two standards differ by a material 1 dB.

There is also a second layer: PMs on multi-market campaigns often receive a consolidated delivery package across 12 or 19 languages and have no technical reference point to verify compliance before passing the files upstream. The assumption is that the supplier has handled it. Whether that assumption is correct is invisible until a broadcaster finds out it wasn't.

The post-mortem on this kind of rejection almost always surfaces the same root cause: nobody in the PM's workflow owned a delivery standard. That is the gap this post closes.

The Delivery Standard Your Files Should Arrive In — By Region

Loudness compliance is the most common reason broadcast voice-over files are rejected. Here are the active standards by region, with the exact numbers your briefs and QC checks should reference.

EBU R128 — European Broadcast Standard

EBU R128 has been mandatory across European broadcast since 2012. It covers television, radio, internet distribution, and cinema — all channels.

Applies to: Germany, UK, France, Spain, Netherlands, the Nordics, and all EU broadcast markets.

ATSC A/85 — US Broadcast Standard

ATSC A/85 is the CALM Act-enforced standard for US digital television. It does not apply to US radio or streaming platforms.

The 1 dB difference that matters

Other Regional Standards

What a Compliant Delivery Package Actually Contains

Loudness compliance is necessary but not sufficient. A professional handover covers the full technical stack the broadcaster and post-production chain will check.

The QC documentation is what turns a delivery package into a verified handover. Without it, a PM receiving files across 19 languages has no basis for confirming compliance beyond listening, which is not a technically reliable method for loudness verification.

When files arrive spec-compliant at the QC gate, revision rounds do not exist for technical reasons. The only revision is a creative one — and creative revisions are the kind a PM can actually manage.

VoiceArchive's Audio Post service delivers to EBU R128 and ATSC A/85 compliance as a default — target confirmed, True Peak verified, loudness report included per language. That is part of what the 9/10 first-pass approval rate reflects: when files arrive spec-compliant at the QC gate, revision rounds do not exist for technical reasons. The only revision is a creative one, and creative revisions are the kind a PM can actually manage.

How to Tell If Your Current Supplier Is Meeting the Standard — Or Assuming You Are

Most suppliers who cause broadcast rejections do not know they caused them. They delivered files. The files failed. The PM absorbed the problem and moved on. No feedback loop closes.

There are four questions that will tell you whether your current supplier is working to a defined standard or working to their own default.

The One Line You Should Add to Every VO Brief Before Production Begins

The most common finding when broadcast rejections are investigated is not a technical failure by the engineer. It is that the brief did not contain the delivery destination information needed to produce the right output.

Engineers default to a standard when one is not specified. In a multi-market campaign, any default is wrong for at least some of the delivery territories. The brief is the only point in the production chain where this can be fixed before it becomes a post-mortem.

The line to add:

One line. It eliminates the most common category of broadcast rejection before production begins. It removes the assumption that the supplier knows what you need. It creates a record — so if a file is rejected, the brief is the first place you look, not the last.

For multi-market campaigns, specify per territory. EBU R128 for European markets. ATSC A/85 for US broadcast. OP-59 for Australia and New Zealand. Streaming targets if digital distribution is in scope. The brief is the only place where all of those can live in a single document before the engineer presses record.