Inside a Newsroom Workflow Review: How We Trace a Story from Pitch to Air
Helen Marsden walks through how a workflow review actually runs: the days spent watching desks, the maps we draw, and the small changes that give producers back minutes on every package.
Starting with a day on the floor
A workflow review at newflare does not begin with a questionnaire. It begins with someone from our team sitting in your newsroom for a full working day, usually Callum Reid, with a notebook, a stopwatch and no laptop open. We want to see the real pipeline, not the one in the procedures document, because the two rarely match. A pitch that should go from editor to producer in a minute may travel through a chat thread, a whiteboard and a shouted question across the room before anyone owns it. We ask permission to follow one or two stories from the morning meeting through to transmission, noting who touches each one and how long it waits between touches. Waiting is where most of the time goes. Shooting and cutting are usually quick; it is the gaps between them that stretch a bulletin deadline.
We keep the observation quiet and unhurried. Staff are told in advance why we are there, and that we are reviewing the process rather than the people in it. That matters, because a newsroom that feels inspected will tidy up its habits for the day and show us nothing useful. By mid afternoon, as a rule, people have stopped noticing us, and we start seeing the workarounds they have built over the years: the spreadsheet nobody admits to, the folder with the unofficial name, the editor who checks a script twice because the first version never carries the final shot list.
Drawing the map of how a story really moves
After the observation we draw the pipeline on a single large sheet: every handover, every tool, every approval, in the order a story actually meets them. We use plain boxes and arrows, not diagrams that need a legend. The map goes up on a wall or onto a shared screen and the people who work the process correct it. Someone nearly always says that is not quite how it goes, and that correction is often the most valuable moment of the whole review. Once the map is agreed, we mark three things on it: where a story waits, where information is typed in more than once, and where a decision sits with someone who is rarely free. These are not criticisms. They are simply the places where a minute saved is a minute saved on every story that passes through, every day of the week.
We also note what works well, and we say so. Several newsrooms we have worked with had a handover between camera crew and edit that was already clean, and the sensible advice was to leave it alone and copy its habits elsewhere. A review that only finds faults tends to produce a long list nobody acts on. A review that shows what is already sound, and why, gives a newsroom something to build from and makes the suggested changes feel like an extension of its own good practice.
- Where a story waits between hands
- Where the same detail is entered twice
- Where one person's availability holds up the rest
Choosing changes small enough to survive a busy week
The report we write is short, and its suggestions are ranked by effort as well as by saving. A newsroom in the middle of a heavy news cycle will not adopt a new system, but it will adopt a renamed folder structure, a single shared rundown, or a rule that a shot list travels with the footage instead of arriving later. We favour changes that can start on a Monday without a training day, and we say plainly when something would take longer and what it would need. Each suggestion states what we saw, what we propose, who it affects and roughly how much time we think it frees per story. We are careful with that last figure. We give a range, based on what we timed, and we do not promise it. Newsrooms differ, and a saving that holds on a quiet morning may shrink when three breaking items land at once.
We also try to propose changes in a way that respects how people already work. An editor who has run a bulletin the same way for years will resist a process that feels imposed, and quite fairly. So we bring the proposals back to the people involved before they reach the final report, adjust them where their objections are sound, and drop the ones that do not survive the conversation. The recommendations that remain have usually been argued over once already, which makes them far likelier to hold.
What the written report contains
The report is usually a dozen pages or fewer, written in plain language for editors and producers rather than for a technology department. It opens with the map of the pipeline as it stands, followed by the points where time is lost, each tied to something we watched rather than something we assumed. We include short quotations from the staff we spoke to, with their permission, because a colleague's own words about a bottleneck carry more weight than ours. The second half sets out the proposed changes in order, with the quickest wins first. For each one we describe how it would work on an ordinary day, what could go wrong, and how the newsroom would know it had made a difference. We do not pad the document with general advice on newsroom culture or industry trends. If a point would apply to any newsroom in the country, it does not belong in a report about yours.
We deliver the report in person where we can, walking the editor and senior producers through it and answering questions on the spot. A document read alone at a desk invites a skim; a conversation tends to turn up the objection or the missing detail that changes a recommendation. Afterwards the written version stays with you as a reference, and Callum remains available to talk through any point that proves harder in practice than it looked on paper.
- A map of the pipeline as it actually runs
- Time lost, tied to what we observed
- Ranked changes with effort and likely saving
- A note of what is already working
Following up once the changes are in use
A review that ends at the report is only half useful, so we offer a short follow-up some weeks later. By then the newsroom has lived with the changes through a handful of ordinary days and at least one awkward one, and that is when we learn which suggestions took hold. We ask the same people the same plain questions: what is faster, what is no different, what has become an irritation. Sometimes a change that looked sensible on paper turns out to add a step nobody wanted, and we say so and revise it. That is not a failure of the review; it is the review doing its job. A workflow is a working thing, and the aim is a pipeline your own staff are content to keep using after we have gone home, not one that only looks tidy in a report.
The follow-up is also a good moment to look again at the map. Newsrooms change: a new presenter, a different bulletin slot, a shift in how much arrives from the field. A pipeline that suited last spring may need small adjustments by now. We redraw only the parts that moved, note what has improved, and leave you with a lighter second document. Most newsrooms find that second look takes far less time than the first, because the vocabulary and the habit of looking for waiting time are already theirs.
A workflow review is, in the end, careful watching followed by modest, well-argued changes. Nothing in it is dramatic, and that is deliberate: newsrooms rarely have the spare hours for upheaval, but they can usually find the minutes that small fixes return. If you would like to see how a day on your own floor might look from the outside, the contact page is the place to start.