Five Delivery Mistakes That Cost Newsrooms Time, and How to Avoid Them

Why delivery is where good footage gets lost

A crew can shoot a clean, well-framed story and still lose it in the last twenty minutes. In my years running productions I have watched strong material miss a bulletin because the files were in the wrong place, named in a way nobody could read, or sent in a format the edit suite refused to open. Shooting gets the attention, yet delivery decides whether the footage is used.

At ordivix, footage delivery and archive means secure transfer of rushes and finished items to your newsroom, with organised storage on request. This note takes one slice of that work: the mistakes that recur, and how we avoid them. These weeks, with darker evenings and more incidents on wet roads, the pressure on late transfers is higher, so it is a good time to check your own habits.

None of the mistakes below needs special equipment to fix. Most come down to agreeing a few things before the camera is switched on, and holding to them when the story moves quickly and everyone is tired.

Mistake one: sending before agreeing the format

The most common fault is simple. A crew shoots in one frame rate and codec, the newsroom ingests another, and the first twenty minutes of a deadline go on conversion. Nobody did anything wrong, because nobody asked. The editor assumes the files will match the house standard, and the operator assumes the desk will take whatever arrives.

The fix is a short written line agreed before the first job: resolution, frame rate, file type and whether you want proxies as well as full-quality rushes. We keep this on file for each client and check it against the camera settings before the crew leaves the building. If a story changes mid-shoot, the operator tells the desk at once rather than hoping the difference will not matter.

It also helps to agree what happens when the standard cannot be met, for example when a phone clip from a witness is the only footage available. Say in advance how that material should be flagged so the editor knows what quality to expect.

• Confirm resolution, frame rate and codec in writing
• Ask whether proxies are wanted alongside full rushes
• Flag any off-standard material as soon as it is taken

Mistake two: file names that mean nothing at 6am

Camera-generated names such as a string of letters and numbers are fine for the operator and useless to everyone else. When a producer is searching a folder for the shot of the road closure, a name that says nothing about location, subject or time costs minutes the desk does not have. The problem multiplies when several crews feed one story.

We name every delivery with the story slug, the location, the shooter's initials and a running number, and we add a plain text note listing what each clip contains and any pieces that need care, such as a face that should be blurred or a sound bite that is uncleared. It takes the operator a couple of minutes on location and saves far more at the other end.

The same discipline applies to finished items. A package sent without its version number invites the wrong cut being broadcast, which is a far more serious problem than a slow search.

• Use story slug, place, initials and number in every name
• Send a short clip list with each delivery
• Mark version numbers on every finished item

Mistake three: treating transfer as a single attempt

Mobile connections drop, upload links time out, and a large file that stalls at ninety per cent can sit unnoticed until someone asks where it is. Sending once and assuming it arrived is a risk, especially from a location with weak coverage, which in South Wales includes plenty of valleys and coastal edges.

Our approach is to send in smaller segments where we can, confirm receipt with a named person on the desk, and keep the originals on the crew's drives until the newsroom has checked the files and said they are complete. We do not wipe a card or clear a drive on the strength of an upload bar alone.

Where a story is live and the connection is poor, the operator sends the most important clips first, so the editor can start cutting while the rest follows. Agreeing that priority order before the crew leaves is quicker than arguing about it during the shoot.

• Confirm receipt with a named contact
• Keep originals until the desk says the files are complete
• Send the most important clips first on weak connections

Mistake four: leaving the archive as an afterthought

Newsrooms often realise they need old footage only when a story returns, and by then nobody remembers which drive it lives on. An archive built in a hurry tends to be a folder of folders, with dates in one style on one disk and another style on the next. Finding the shot from last winter's flooding then becomes a half-day task.

Where clients ask for organised storage, we file rushes by story, then by date, with the clip list and any usage notes kept beside the material. We agree in advance how long items are kept and who may request them back, so nothing is deleted or retained by accident. Storage is on request rather than automatic, because not every client wants it.

A modest, consistent structure beats an ambitious one that nobody follows. Decide the folder pattern once, write it down, and apply it to every job, including the small ones that seem too minor to bother with.

• Agree a folder pattern once and keep to it
• Store notes and usage restrictions beside the footage
• Decide retention periods before the material is filed

Mistake five: no one owns the handover

The last mistake is organisational. When a crew, an editor and a desk producer all assume someone else is checking the delivery, nobody does. Footage then goes out with missing audio channels, a clip cut short, or an interview with no release noted, and the problem surfaces only when it is already on air.

We give each job one named person responsible for the handover, usually the producer on the day. They check that every clip plays, that audio is present on both channels, that the clip list matches the files, and that the newsroom contact has confirmed receipt. It is a five-minute check, and it is written into how we plan each deployment.

If you take only one habit from this note, make it that one. A named owner and a short checklist prevent more delivery problems than any piece of technology.