Getting Rushes and Archives in Order Before the Winter News Season

Why autumn is the time to tidy delivery habits

Each year the same pattern arrives with the dark evenings. Storms, flooding, road closures and long holiday schedules push more footage through a newsroom than at any other time, and the weaknesses in how rushes travel become obvious in the first bad week. I cut news packages every day, and most of my lost minutes come not from the edit itself but from waiting for files, hunting for the right clip or guessing which version is final.

Mid autumn is a quiet enough moment to fix that. Crews are busy but not yet stretched, and a newsroom can still agree how material should be named, sent and kept without doing it under pressure. A small change made now, such as a shared naming rule or a named person who confirms receipt, will save far more time than it costs once the winter stories start arriving.

This note looks only at the delivery and storage side of our work: moving rushes and finished items to you securely, and keeping them organised afterwards if you ask us to. It is practical advice for the coming months, not a general guide to shooting or editing.

Agree how files are named before the first storm

A clip called with a camera number and a string of digits tells an editor nothing at eleven at night. Before the weather turns, agree a plain convention with us: story slug, location, date and a take or card number, in the same order every time. It sounds fussy, yet it is the single habit that lets a producer find the right interview in seconds rather than scrubbing through a folder.

Decide too who owns the slug. In a developing story the working title often changes three times, and files named under the old title become orphans. We suggest the newsroom issues the slug and we keep to it for the whole story, adding a short suffix only for versions. That way rushes, graphics and the finished item all sit under one name.

Write the convention down on a single page and share it with every crew and editor involved. When Owen or another operator is on a roadside at dusk, the last thing anyone wants is a debate about what to call the card.

• Story slug first, then place, then date
• One suffix style for versions, such as v1 and final
• No spaces or odd symbols in file names
• Keep a single page of the rules where crews can see it

Choose your transfer route and a fallback

Secure transfer is only useful if everyone knows which route to use and what to do when it fails. Decide with us in advance how rushes reach you: a direct transfer to your ingest point, a shared secure folder, or a physical drive for very large shoots. Each suits a different situation, and none is right for everything.

Winter tests connections. A live position in a coastal car park or a village hall with poor signal may not manage a large upload at all. Agree a fallback now, for example sending a compressed selection first so your producer can start work, followed by the full-quality files when the connection improves or the crew is back at base.

Test the route before you need it. Send a short dummy clip through the exact path you plan to use, confirm it arrives intact and note how long it took. A ten-minute check in October is far cheaper than discovering a permissions error during a breaking story.

Confirm receipt so nothing is assumed

The quietest failures in this work are the ones nobody notices: a transfer that stopped at ninety per cent, a folder shared with the wrong address, a card handed over and then wiped on the assumption it had been copied. Every delivery should end with a clear confirmation from the person receiving it, not a hopeful silence.

We ask newsrooms to name one contact per shift who acknowledges arrival and checks that files open and play. It takes a minute and removes the doubt. For finished items, the same person confirms the version that goes to air, so that an earlier cut is not played by mistake.

Crews on our side keep their original cards until receipt is confirmed. It is a simple rule, and in a busy week it has more than once let us resend a clip that would otherwise have been gone.

• One named receiver per shift
• Check that files open and play, not just that they arrived
• Hold original cards until receipt is confirmed

Decide what is kept, for how long and where

Organised storage is available on request, and the useful question is what you actually need to keep. Raw rushes from a minor story rarely need to be held for long, while footage from a major local event may be wanted for anniversaries, follow-ups or legal reasons. Sorting this before the winter rush stops decisions being made in a hurry later.

Work out a simple tiering with your editor: what stays easily reachable for recent stories, what moves to slower storage once a story is closed, and what is cleared altogether. Write the rule down, with who may ask for material to be restored and how that request reaches us.

Tag material while it is fresh. A story slug and a short note on who appears and where it was filmed cost seconds at the time and save hours in a year when nobody remembers the detail. Archives become useful through the notes attached, not just the files held.

A short list to settle in the coming weeks

None of this needs a long meeting. Most newsrooms can settle the essentials in a single conversation with their producer and editor, then send us the result in writing so every crew works the same way. We will adjust our side to match.

Go through the points below in order, since each one depends on the last. Naming comes first because everything else, transfer, receipt and storage, relies on files being identifiable. If you only have time for two items before the weather turns, make them the naming rule and the fallback route.

We are happy to talk any of it through by phone or through the contact page, and to run the test transfer with you so the first real use is not also the first trial.

• Agree the naming convention and who issues slugs
• Pick a main transfer route and a fallback
• Name one receiver per shift
• Decide retention, tiers and restore requests