Newsroom workflow checklist: what to settle before you decide

File naming sounds dull until two editors cut the same story from different clips because nobody could tell which was which. Check whether your current names carry the date, the story slug, the camera or source, and a clip number. If they depend on one person's memory, they will fail the first time that person is off shift.

The decision to make is a convention short enough that a crew will use it on location, with cold hands and little time, and clear enough that a producer can read it without opening the file. Test it on last week's stories. If you cannot reconstruct what each clip was from its name alone, the convention needs another pass before it goes anywhere near a crew.

Ingest is where speed and care pull against each other. Ask how long a typical card takes to be copied, checked and made available, and whether anyone confirms the copy is complete before the original is wiped or reused. I have seen good footage lost at exactly this point, and it is never the fault of the person standing there; it is the absence of a rule.

Work out what a second copy costs you in minutes and whether you can afford the minutes. Ask too where the checking happens: at the desk, in the van, or not at all. Decide what a clip must pass before it is called ingested, and write that down in plain words rather than keeping it as habit.

Most workflow trouble sits in the hand-overs. The crew believes the desk knows what was shot; the desk believes the editor has the notes; the editor is guessing. Look at what travels with the footage: a short shot list, anything sensitive that was said off the record, notes on audio problems, and which clips are the strongest.

As the person who hears the sound problems first, I would add one thing: if a clip has a fault, such as wind, a noisy location or a weak radio mic, say so at hand-over, not at the edit. A line of text saves an editor from discovering it under deadline. Decide the minimum note that must accompany every delivery and keep it short enough to be written.

A checklist is only as good as the shifts that have to follow it. Ask who covers when your usual producer is ill, whether the overnight team has the same access as the day team, and what the plan is when a transfer link drops during a live story. Ours has dropped at awkward moments, and the teams that coped best had a second route agreed in advance.

Then ask a harder question: what do you want support to change, and what should stay as it is? Good advice on workflow fits the way your team already works. If a change would need everyone to behave differently overnight, it will not hold. Smaller adjustments, adopted by the whole room, beat a perfect scheme that nobody follows.

When you do speak to someone about workflow support, bring your own list. Ask what they would look at first, how they would observe your current process, and what you would have in your hands at the end: a written convention, a diagram of the route, a short guide for crews. Ask what they need from you and your engineers.

Ask, too, how they handle the moment after set-up, when habits slip. Support that ends on the day of handing over a document tends to fade within weeks. You want to know who you can ring when a shift finds a gap, and how quickly someone who understands your set-up will pick up the phone.