How to Plan a Newsroom Handover So Nothing Gets Lost Between Shifts

Most handover problems begin long before anyone says goodbye at the end of a shift. They begin when a story enters the day without a clear plan. A usable story plan is short: what the item is about, who is filming it, what the intended length is, which bulletin it feeds and who has the final say on the cut. If any of those five answers is missing, the editor who picks it up later has to guess, and guessing costs minutes that a news day rarely has to spare.

In the training sessions I run with editors and producers, we write the plan on a single line before a camera leaves the building. It sounds fussy until the first story changes direction at three in the afternoon. Then the line becomes the reference point everyone returns to, and arguments about what the item was meant to be disappear quickly.

• Subject in one sentence
• Intended length and bulletin slot
• Named shooter and named editor
• Who signs off the final version

Ingest is the least glamorous part of a newsroom and the place where most avoidable delays hide. The aim is simple: every card, file and clip arrives in the same place, with the same naming pattern, and nobody has to ask where it went. Agree one folder structure for the whole team and keep it for months. Changing it every time someone has a better idea is worse than living with a slightly clumsy layout.

A good ingest routine includes a quick check before the card is cleared: does the file play, does the audio sit on the right channels, is the clip count what the shooter expects. That check takes under two minutes and saves the far more painful discovery, hours later, that a key interview has no sound on one side.

• One shared folder structure
• Date, story and shooter in every file name
• Playback and audio check before clearing cards

An edit queue works best when everyone can see it. A whiteboard or a shared sheet is enough; the tool matters far less than the habit. Each line shows the story, the editor currently on it, its status and the deadline. When a breaking item arrives, the producer moves it up and says aloud what has been pushed down, so the person whose edit was interrupted knows exactly where they stand and is not left wondering.

Queues go wrong when priorities live in someone's head. If only one producer knows that the council story can wait until the evening, the plan falls apart the moment that producer leaves for lunch. Put the reasoning on the list in a few words, next to the story, so any colleague can follow the logic without a conversation.

• Story, editor, status and deadline on every line
• Say aloud what is bumped when something urgent arrives

The handover note is where a day's work either carries forward or evaporates. Keep it to a page at most. For each open item, state what is finished, what remains, which files hold the latest version and any decision still waiting on someone. Avoid phrases such as nearly there or just needs a polish; they mean different things to different people and tell the next editor nothing about the actual state of the timeline.

I ask trainees to imagine the reader has just walked in with no briefing and ten minutes before a deadline. Could they pick up the first item and carry on? If the answer is no, the note needs another line or two. Naming the exact sequence, the version number and the missing shot is far more useful than a general reassurance.

• What is done, what is left, where the latest version sits
• Pending decisions with a named owner
• Anything that must not be deleted or overwritten

Handover is a skill, and like any skill it improves with practice. Choose a quiet afternoon and run a mock changeover with a real story from the previous week. One person plays the outgoing editor and writes the note; another plays the incoming editor and works only from that note and the shared folders. Afterwards, compare what the note said with what the receiver actually needed to ask.

The gaps this exercise reveals are usually small and fixable: a missing file path, an unclear label, an assumption about who owns the captions. Mid autumn is a sensible time to try it, with the busier winter schedule and early darkness approaching, and before staff leave and holiday cover begins to blur the usual roles.

• Use a real story from last week
• Receiver works only from the note
• List every question the receiver had to ask

A workflow that needs perfect conditions is not a workflow. The test of any newsroom routine is how it behaves when two stories break at once, a colleague is off sick and the main server is slow. Anything that depends on everyone remembering six separate steps will be skipped under pressure, so cut the routine down to the few actions that matter and make those unmissable.

Review the system every few months and remove what nobody uses. Each form, field or checkbox should earn its place by solving a problem someone actually had. Smaller routines are followed more often, and a routine followed every time beats an elaborate one followed when there is leisure to do so.

• Fewer steps, followed every time
• Remove fields nobody reads
• Review a few times a year