zoryli
Blog Distribution

Content Distribution: Mistakes We See and How to Avoid Them

Priya Nair

6 min read

Priya Nair, who coordinates deliveries at zoryli, lists the slips that most often delay a finished feed on its way to a broadcaster, and the small checks that prevent them.

Content Distribution: Mistakes We See and How to Avoid Them

Starting from the wrong format

The most common slip I see in my work as Distribution Coordinator is assuming that every broadcaster wants the same file. A news programme may ask for one container, frame rate and audio layout, while a television broadcaster commissioning a festival highlight asks for another. When the format is guessed rather than confirmed, the feed arrives, gets rejected at the ingest desk, and someone has to re-export it under pressure.

The fix is dull and reliable: ask for the delivery specification in writing before the event, not after it. That means resolution, frame rate, codec, audio channel order, loudness target and the file naming the receiving team expects. We keep these requests on record so that a repeat delivery to the same programme does not depend on anyone's memory.

If the broadcaster has no written specification, we write one back to them and ask them to confirm it. A short reply saying yes is enough to protect everyone later.

  • Ask for the written specification early
  • Confirm frame rate and audio channel order
  • Keep each broadcaster's requirements on file

Leaving the check until handover

Another mistake is treating the final check as something that happens at the moment of delivery. By then there is no time to correct a missing audio track, a black frame at the head of the file or a clock that does not match the programme's rundown. I check formats before each handover, but a check at the last minute only tells you that you have a problem, not how to solve it calmly.

We prefer to test early with a short sample sent ahead of the main delivery. The broadcaster's ingest team opens it, plays it through their own system and tells us if anything looks off. It costs a few minutes in the days before and often saves an hour on the day.

For live events the same idea applies to a rehearsal feed. A signal that has already travelled the full route once is far less likely to surprise anyone the second time.

Sending without a named contact

Deliveries go wrong in small ways even when preparation is good, and the question then becomes who can answer. A frequent error is sending a feed to a general mailbox or a shared drop point with no person attached on either side. When a file will not open at half past six in the evening, nobody knows whom to ring.

Before any delivery we agree one named contact at the broadcaster and one at our end, with a direct phone number for each. The contact on our side is usually me, and the details sit on the delivery note alongside the file list.

This sounds minor, but a ten minute call between two people who already know each other settles most problems. A chain of unanswered emails to a department does not.

  • One named contact on each side
  • A direct phone number on the delivery note
  • Agree who decides if a re-send is needed

Skipping a record of what was sent

Producers sometimes ask a week later whether a particular version was delivered, and which one. Without a record, the honest answer is a search through folders. A quiet mistake in distribution is failing to log what left, when, in which format and to whom.

Our delivery log is a plain list kept for every job: file names, formats, the time each was sent, and the time the receiving side confirmed it. It is not sophisticated, and that is the point. Anyone on the team can read it and answer a question without guessing.

Where a broadcaster requests a corrected version, the log also shows which one replaced which, so nobody airs the older file by accident. Version confusion is far more common than technical failure, and a log removes most of it.

Forgetting the backup delivery route

A single delivery path is a single point of failure. I have seen a transfer stall because the one connection chosen was congested, with no alternative prepared. The mistake is not that the connection failed; it is that nothing else was ready when it did.

For anything with a fixed air time, we arrange a second route in advance, whether that is a different transfer method or a physical copy that can be sent on request. The broadcaster is told which route is primary and which is held in reserve, so there is no confusion about which file counts.

This works alongside the backup signal routes Daniel Whitcombe maintains on the live side. The principle is the same in both places: assume one thing will fail and decide beforehand what happens next.

  • Name a primary and a reserve route
  • Tell the broadcaster which one counts
  • Keep a copy ready for fixed air times

Treating late changes as someone else's problem

Rundowns move. A segment is cut, a running time shifts, a broadcaster asks for an extra version in the autumn when schedules are crowded with seasonal programming. The mistake is to carry on delivering to the original plan and hope the change is noticed.

When a change arrives, I write it into the delivery note and repeat it back to the person who asked, so both sides read the same thing. If the change affects format or timing, I tell the rest of our team straight away, since the camera and signal staff may need to know too.

Calm handling matters here. A producer under time pressure wants a short, clear answer about what is possible, not a long explanation. If a request cannot be met, saying so early is more useful than a late apology.

Most distribution problems are not technical failures but small gaps in agreement: a format assumed, a contact missing, a change not repeated back. None of the remedies here need special equipment, only a habit of writing things down and confirming them before the day. If you are planning a delivery to a news programme or broadcaster, tell us the specification you have been given, and we will check it against the feed before anything is sent.

Written by

Priya Nair

Distribution Coordinator

Priya schedules deliveries to broadcasters and checks formats before each handover.

You may also like

Ask for a quote

Email: hello@zoryli.com