Why packages go wrong after the shoot
A news feed package is meant to be ready to air: a feed or a set of clips, with the metadata a desk needs, delivered quickly. When one causes trouble, the picture is rarely the problem. The trouble usually sits in the small things around the pictures, such as a vague title, a missing note about who is speaking, or a file that arrives in a format the receiving desk did not expect.
I have run outside broadcasts since renyzo's early years, and the pattern holds across mid autumn storms, council meetings and evening bulletins alike. Mistakes cluster at the handover points: between the camera and the editor, between the editor and distribution, and between distribution and the news desk. Each handover is a place where an assumption goes unchecked.
What follows are six mistakes, each with a plain way to avoid it. None of them needs new equipment. Most need a short conversation before the work starts and a habit of checking at the end.
Mistake one: sending a brief that leaves the desk guessing
The commonest slip is an order that says what the story is but not how the package will be used. A desk that wants a thirty-second clip for a lunchtime bulletin needs something different from a desk building a longer evening item with room for natural sound. If we are not told, we guess, and a guess costs a second round of changes.
Avoid it by stating the running time, the programme slot, the deadline and whether the clip will be cut further on your side. Tell us whether you want clean pictures with no graphics, or a version with captions burned in. Two sentences at the enquiry stage save a good deal of back and forth later.
It also helps to name one person at your end who can answer questions while the package is being prepared. A feed is often built under time pressure, and a question that waits an hour for a reply can push the whole delivery past its slot.
- Running time and programme slot
- Deadline and delivery format
- Clean pictures or captioned version
- One contact who can answer quickly
Mistake two: thin or inconsistent metadata
Metadata is the part nobody sees on air and everybody misses when it is wrong. A clip called final_v3 tells an editor nothing. A good package carries a clear title, the location, the date of recording, the names and roles of anyone interviewed, and a note of any restrictions on use.
The mistake is treating this as paperwork to be done last. By then the shoot is a blur and details are remembered wrongly. Our crews note names and spellings at the time, and the person preparing the package checks them against what was written down, not against memory.
Agree a naming pattern with the receiving desk once, and keep to it. A consistent pattern lets an archive search find the right clip months later. If your desk already has a convention, send it to us at the start and we will follow it exactly, including how dates and slugs are written.
Mistake three: ignoring file standards until delivery day
Every broadcaster and streaming partner has its own requirements for frame rate, codec, audio levels and file wrapper. A package that looks perfect on our monitors can still be bounced at the other end for a mismatch no one mentioned. Discovering this an hour before air is the most avoidable stress in the trade.
Ask the receiving desk for its delivery specification before the shoot, not after the edit. Ewan Campbell, our Distribution Manager, keeps the standards for each regular partner on file, so repeat work rarely hits this problem. For a new partner, we ask for the specification in writing and test a short sample first.
Audio deserves its own check. Levels that suit a stage feed may be too hot or too quiet for a bulletin, and a missing stereo channel is easy to overlook on a quick listen. A short sample file sent ahead settles these questions cheaply.
- Frame rate and codec
- Audio levels and channel layout
- File wrapper and naming
- A short test sample for new partners
Mistake four: no plan for the late change
News moves. A name is corrected, a figure is withdrawn, or an interviewee asks for a line to be removed after the clip has gone out. Packages built as one locked file are hard to amend, and a fix made in a rush is where new errors creep in.
We keep the clean pictures, the separate audio and the version notes together, so a correction means changing one element rather than rebuilding everything. Tell us early if a story is still developing and likely to change; we will hold the package in a form that is easy to update and say plainly how long an update takes.
It is also worth agreeing who may approve a change. When two people on your side send conflicting instructions, the crew has to stop and ask, and the time lost is usually the time you did not have.
Mistake five and six: skipping the check and the review
The fifth slip is delivering without a final watch-through of the finished file, start to end. Dropped frames, a frozen last second or a stray audio pop only show up when someone plays the whole thing. Our rule is that a different person from the editor reviews every package before it leaves us.
The sixth is never looking back at what happened. After a busy run of stories, a short note on what the desk liked, what needed changing and what arrived late tells both sides how to improve the next order. We are glad to take that feedback by phone or through the contact page.
None of this is complicated. It asks for a little preparation, a named contact and a habit of checking. Most of the packages that cause grief did so because one of those three was missing, not because the story was difficult.
Good news feed packages come from ordinary habits: a clear brief, tidy metadata, known file standards, a plan for corrections and a second pair of eyes before delivery. If you would like to talk through how your desk orders feeds, or what a first package would involve, the contact page is the place to start, and I will make sure the right person replies.
