How to Prepare Your Newsroom for a Workflow Review
A practical guide to getting ready for a review of how stories travel from first tip to broadcast: what to gather, who to involve and what to expect on paper afterwards.
Start with one story, followed end to end
The easiest way to prepare for a workflow review is to pick a single recent story and trace it from the first phone call or message to the moment it went to air. Choose something ordinary rather than your best or worst night. A council meeting, a road closure or a court report will do. Write down every handover in order: who took the tip, who decided it was worth sending a crew, who briefed the camera operator, who logged the footage, who cut it, who checked it and who pushed it to the gallery.
This simple trace shows more than any diagram of how the newsroom is supposed to work. You will usually find two or three points where the story sat waiting for someone, and one or two where it moved backwards because information was missing. Keep the notes short and factual, in plain sentences. They become the backbone of the conversation with the reviewer and save a great deal of time on the first day.
- Pick an ordinary story, not an exceptional one
- List each handover in the order it happened
- Note where the story waited and for how long
Gather what people already use
Before anyone visits, collect the documents and tools your staff genuinely rely on, not the ones that sit in a folder. That means the running order template, the shared spreadsheet or whiteboard photo used for assignments, any shot-logging sheet, the naming rules for files and the checklist, if there is one, for sign-off before transmission. Include the messy versions. A crumpled printout with handwriting on it tells a reviewer more than a tidy policy nobody follows.
Also note which systems feed which. If a producer retypes details from an email into a rundown, or a camera operator renames files by hand after a shoot, say so. These small manual steps are rarely written down, yet they are where errors and delays tend to gather. Do not tidy any of this up beforehand. A review works best on the real picture, and the people who made those workarounds usually had a good reason for them.
- Running order and assignment templates in current use
- File naming habits and any shot-logging sheets
- Manual retyping or renaming steps staff have invented
Decide who should be in the room
A review that only hears from the editor tends to describe the intended process. One that also hears from the people at each handover describes the actual one. Aim for a short list: an editor or duty producer, someone who takes tips or manages the desk, a camera operator or reporter who goes out on stories, and the person who edits or finalises packages. Half an hour each is usually enough if they know the questions in advance.
Tell people plainly that nobody is being assessed. Staff who fear blame will smooth over problems, and those problems are exactly what you are paying to find. Ask the reviewer to speak to people individually as well as together, since a junior producer may say things in a one-to-one chat that they would never raise in front of a senior editor. Agree beforehand who can approve any change that follows.
Agree what you want answered
Vague aims produce vague recommendations. Before the review begins, write down two or three questions you want answered in everyday terms. How long does a story sit between a tip arriving and a crew being sent? Why do packages sometimes reach the gallery with captions missing? Where do duplicate copies of footage come from? Concrete questions let the reviewer focus on observation and gives you recommendations you can act on within a week rather than a general report that nobody reads.
It also helps to say what is out of bounds. If you cannot change the editing software this year, or the shift pattern is fixed by an agreement, tell the reviewer at the start. Recommendations that ignore those limits waste everyone's time. A good written review works within the constraints you actually have and ranks its suggestions by effort, so your editors can begin with the quick wins.
- Write two or three plain, specific questions
- State fixed limits such as software or shift patterns
- Ask for suggestions ranked by effort
What the written recommendations should look like
Expect a short document written for editors and producers, not for a boardroom. It should describe what was observed, say what is causing the delay or error, and propose one change for each finding. Each proposal should name who would do it and roughly how long it would take to put in place. If a recommendation reads as a general principle, ask for it to be rewritten as a step someone could take on Monday morning.
Good recommendations are small and sequenced. Renaming rules, a clearer handover note at the point where crews return, or a single agreed place for approved captions often removes more friction than a new system would. Ask for the findings in the order you would tackle them, and for a plain list of anything the reviewer was unable to check, so you know where the picture is still incomplete.
- Each finding paired with one proposed change
- A named owner and rough time for every step
- A clear note of anything that could not be checked
Keep the habit after the visit
A review is a snapshot, and newsrooms change as staff, formats and equipment change. The simplest way to keep the benefit is to repeat the single-story trace every few months. Pick another ordinary story, follow it through, and compare the handovers with the last time. If a step the review removed has crept back, you will see it quickly, and you can deal with it while it is still a small habit rather than a standing practice.
Share the results with the whole desk, including the things that improved. People are far more willing to change how they work when they can see the effect of the last change. Pin the one-page list of agreed steps where the team will see it, and revise it when something stops working. Autumn is a sensible time to do this, before the winter run of weather and travel stories puts extra pressure on every handover.
A workflow review pays off in proportion to the preparation behind it. Trace one real story, collect the documents people actually use, bring in the staff at each handover, and ask questions that can be answered plainly. Then expect recommendations small enough to start on straight away. Keep tracing a story every few months and the desk keeps improving, long after the written report has been filed.
Gareth Pritchard
Senior Camera OperatorGareth shoots breaking stories on location and runs our camera technique workshops.
More from the News Desk
What a Breaking-News Camera Crew Costs and What Moves the Price
A plain account of how a day rate for a camera crew is built, what it covers, and which parts of a developing story push the final figure up or down.
Preparing Your Newsroom Workflow for the Darker Months
Part two of our look at workflow reviews: what to check in how stories move from tip to broadcast before early dusk, winter weather and holiday rotas change the pace.
Getting Your Edit Desk Ready for the Dark Evenings Ahead
Early sunsets, weather alerts and busy bulletin slots change how same-day edits behave. Rhian Hughes sets out how to prepare your turnaround routine for the coming months.