How long does a newsroom workflow review actually take?

The question we are asked first

When an editor or newsroom manager rings about workflow advice, the first thing they ask is rarely about price. It is about time: how long will this take, and will it get in the way of the bulletin? That is a fair worry. A newsroom in mid autumn is already stretched, with budget coverage, early dark evenings and the run-up to winter weather desks all pulling on the same people.

The honest answer is that a review usually runs over a few working days spread across a fortnight, not a block of weeks. We do not close desks, ask staff to stop filing or require a special meeting room. We sit where the stories already move, watch them travel from tip to transmission, and keep out of the way when a deadline is close. Most of the disruption people expect never arrives.

What the first day looks like

The first visit is mostly listening. We ask to follow two or three real stories from the moment someone flags a tip through to the moment the finished item goes to the gallery. We note who touches it, where it waits, which files are renamed, which messages are repeated and which approvals happen by shouting across the room rather than by any agreed route.

We also talk to the people who do the work: the producer who assigns crews, the editor who receives rushes, the person who checks captions. Their account of a normal day often differs from the process written down, and the gap between the two is where most lost minutes hide. We take notes, we do not grade anyone, and we keep names out of the written findings unless you ask otherwise.

• Follow two or three live stories end to end
• Speak with producers, editors and desk staff separately
• Note waits, repeats and informal approvals

Where the time usually goes missing

In our experience the delays are seldom dramatic. A shoot is finished but nobody has said where the card should go. Footage arrives in a format the edit suite must convert before cutting. A caption is written twice because two people did not know the other had started. Each of these costs ten or fifteen minutes, and on a busy day they add up to a bulletin slot.

Another common pattern is the handover between shooting and editing. Crews describe what they filmed in a phone call, the editor writes it down, and details such as which interview is the usable take are lost on the way. A short shared note, agreed in advance and kept to a few lines, often saves more than any new software could.

• Unclear file destinations after a shoot
• Format conversions that could be avoided at source
• Duplicate captioning and unlogged handovers

The days between visits

After the first visit we go away and work through what we saw. This stretch is quiet from your side. We map the route each story took, mark where it paused and note which pauses were necessary, such as legal checks or editor sign-off, and which were habit. Some waits are there for good reason and we say so plainly.

We then return for a second, shorter visit to test our reading against a fresh story. If the same pauses appear, we are confident they are real. If they do not, we adjust before putting anything on paper. This second look is what separates a useful report from a list of guesses, and it is the part we would never skip to save a day.

What you receive at the end

The result is a written report in plain language, usually a handful of pages, with a short list of changes ordered by how much time they are likely to save and how easy they are to try. We prefer small changes that a desk can adopt in a week over a grand redesign that needs months and a committee.

We go through it with you in person or by phone, and we answer questions about anything that is unclear. If you want help putting a change into practice, such as a naming convention for files or a one-page shoot brief, we can say what that would involve before you decide. Nothing in the report commits you to further work, and the findings are yours to use as you see fit.

• A short written report in plain English
• Changes ranked by effort and likely time saved
• A walk-through with your editors and producers

What can lengthen or shorten a review

Several things change the timetable. A newsroom with a single desk and one edit suite is quicker to understand than one spread over two sites with separate regional teams. A big breaking story during our visit gives us excellent material but may delay conversations, and we simply return another day.

How much written process already exists also matters. If your team keeps a run sheet, a shot log or a shared folder structure, we read these first and spend less time reconstructing events. The most useful thing you can do beforehand is to name one contact who knows how stories really move and who can open doors for us. A review that starts with that person runs more smoothly.