What "File as You Go" Means on a Breaking Story

When a producer says "file as you go" to one of our crews, they mean something quite specific: do not wait for the story to finish before sending anything back. Send the first usable piece as soon as it exists, then keep sending as the situation develops. The word "file" is old newsroom shorthand for delivering material to the desk, and it has stuck even though nothing is physically carried anywhere any more. I have spent most of my working life on the editing side of this, and the phrase still sounds to me like a promise between the field and the gallery. The crew promises to send what they have, early and in order. The desk promises to take it without asking for it to be perfect.

It helps to say what the term is not. It is not live broadcasting, and it is not raw footage dumped in a folder. Filing as you go means sending material that has already been shaped enough to be useful: a trimmed clip, a labelled interview, a rough cut with a clear start and end. The desk can then decide what to do with it while the crew moves on to the next shot.

The instinct of many new shooters is to gather everything, then cut one tidy package once the story settles. On a developing story that instinct costs time you do not have. A road closure reopens, a statement is withdrawn, a crowd disperses, and the bulletin has already gone out with nothing from you. A package that arrives after the slot has closed is, in practical terms, not a package at all. Filing in stages changes the risk. If the first piece is a thirty-second cut of the scene with a clean piece to camera, the desk has something to air. Later pieces add the reaction, the detail and the context. Each one stands alone, so if the connection drops or the story turns, nothing already sent is lost.

There is also a quieter benefit. A producer who has seen your first file can tell you what is missing, while you are still standing at the location. That conversation is worth far more than a note about what you should have shot, delivered once you are back at base.

• First file: the scene, short and clean, labelled
• Second file: the voice, an interview or statement
• Third file: the context, wides and cutaways

A file sent from the field should be usable by someone who was not there. That means a plain, consistent name, a short note stating what the clip shows and where it was shot, and the time it was recorded. I have received files called "clip 7" with no note at all; the desk loses minutes working out what they are looking at, and minutes are the whole point. The picture matters too, but not in the way people expect. The first file does not need elaborate grading or a polished soundtrack. It needs correct exposure, steady framing, clear speech and no distracting handling noise. If the sound is poor, say so in the note, so the producer can decide whether to caption it.

Length matters as well. A first file that runs to six minutes is not a first file, it is a second job for the desk. Trim it hard. Keep the strongest moment, cut the false starts, and leave the rest of the material safely on the card or drive for later use if the story grows.

• A plain name: place, subject, order sent
• One line on what it shows and who is speaking
• Time of recording and any known sound problem
• Trimmed to the strongest moment, not the whole take

Speed is the reason for the habit, but accuracy is what keeps it honest. A fast file with a wrongly spelled name in the caption, or a location given loosely, can do more harm than a late one. Our crews are asked to confirm names, titles and place names with the person speaking before they leave the spot, and to write them into the note rather than trust memory. When something is uncertain, the file says so. "Unconfirmed: speaker says she is a resident, not verified" is a perfectly good line to include. The desk would much rather read an honest caveat than discover later that a detail was assumed. Editors can handle uncertainty; they cannot handle surprises discovered after transmission.

Corrections follow the same path as the original. If a later file contradicts an earlier one, the note says which file it replaces and why. That small habit keeps the desk from airing both versions, and it leaves a clear trail for anyone checking the story afterwards.

Filing as you go only works if someone is ready to receive. In our set-up that is often me or another editor, sitting with the project open and the delivery format already chosen. As each file lands, I check it plays, check the sound, and check the note matches the picture. If something is wrong, I tell the crew straight away, while they can still reshoot or re-record a line. The next job is assembly. Early files are cut into a running order that can be updated, so that when the fourth file arrives it slots in without anyone rebuilding the whole package. Captions, graphics and the final delivery format are prepared in parallel rather than at the end.

This is the part clients tend not to see. The speed they notice on air comes from preparation done before the first file was even sent: folders named, templates ready, delivery specifications to hand. A rushed edit is usually a symptom of work that was left until the last moment.

Most failures in this method are ordinary ones. A phone battery dies, a card fills, an upload stalls because no one checked the signal before parking. Crews who file well tend to share a few habits: they check connectivity on arrival, they keep spare power in the vehicle, and they send a short test clip early so that any problem shows up while it is still cheap to fix. Another habit is discipline about order. Number the files in the sequence sent, and keep that numbering even when a file is later withdrawn. Gaps are fine; confusion is not. The desk can see at a glance whether something is missing.

Finally, keep a copy of everything sent, with the original untrimmed material alongside. A story that looked minor at noon can become the lead by evening, and the unused material is often what the follow-up needs. Filing as you go is a way of working, and the archive is part of it.