A Checklist Before You Commission a Newsroom Workflow Review
Questions worth answering inside your own newsroom before you ask anyone to review how stories travel from pitch to air, so the review starts from facts rather than impressions.
Start with the delay you can name
Most newsrooms that ask for a workflow review can feel the problem before they can describe it. Stories seem to wait somewhere, but nobody agrees where. Before you contact a consultant, pick one recent story that aired later than it should have and trace it by hand. Note when the pitch was made, when it was approved, when a crew was assigned, when the footage came back, when the edit began and when it went to transmission.
You will rarely find that everything was slow. Usually one or two handovers account for most of the lost time, and they are often ordinary ones: a producer waiting for a sign-off, a file waiting for a transfer, a script waiting for a legal read. Naming even one of these gives a review a starting point, and it stops the conversation drifting into general opinions about how busy everyone is.
If you cannot trace a single story, that is useful information too. It tells you the process is not recorded anywhere, and that mapping it is the first piece of work, not a side task.
- Choose one late story, not an average week
- Write down each handover with a time beside it
- Mark where the story sat still, not where people worked hard
Know who actually decides at each step
A pipeline on paper and a pipeline in practice often differ on one point: who has the authority to say yes. The organisation chart may show an editor approving every item, while in practice a senior producer waves things through and the editor only hears about them afterwards. Neither arrangement is wrong, but a review built on the wrong one will suggest changes nobody can carry out.
Write down, for each stage, the person who can approve, the person who is usually asked and the person who covers when both are away. Gaps appear quickly. Overnight shifts, weekends and bank holidays tend to reveal approvals that depend on one individual answering a phone. Those single points of dependence are exactly where a small change, such as a clear deputy or a pre-agreed rule for routine items, saves the most time.
Be ready to say honestly where the written rule and the daily habit part ways. A consultant can work with either, provided they are told which is which.
- List approver, usual contact and cover for every stage
- Include nights, weekends and public holidays
- Separate the written rule from the daily habit
Gather the paperwork and tools people really use
Collect the items that shape a day: the running order template, the assignment sheet, any shared calendar, the naming convention for files, and the checklist a crew takes into the field if there is one. Include the unofficial ones too, such as the spreadsheet a producer keeps because the official system is awkward. These private tools usually exist for a good reason and often point to the real need.
Also note how footage moves. Is it carried on cards, sent over a network, uploaded from the field? Which machine receives it, and who tells the editor it has arrived? Small friction here, a missing label or an unclear folder, can cost more minutes than a slow edit.
You do not need to tidy any of this before sharing it. A review is more honest when it sees the working documents as they are, with the crossings-out and the workarounds, than when it sees a version prepared for a visitor.
- Running order and assignment templates
- File naming rules and where footage lands
- Any private spreadsheet or list people rely on
Decide what you want to be different afterwards
A review can end in a tidy report that changes nothing. The way to avoid that is to agree, in advance, what a useful result looks like. It might be a shorter gap between a crew returning and the first cut, fewer stories held over for a missing script, or a handover document a new producer can follow in their first week. Pick one or two outcomes and be specific about them.
It also helps to say what you are not willing to change. If your transmission system is fixed for the next year, or your union agreements limit shift patterns, say so at the start. Suggestions that run into those limits waste everyone's time, whereas suggestions designed around them are the ones that get used.
Think about who will carry the changes through once the review is finished. A proposal without an owner inside the newsroom tends to fade within a month or two.
- Name one or two outcomes you can observe
- State constraints that cannot move
- Choose an owner for the follow-up
Be clear about time, access and the people involved
A useful review needs access to the people who do the work, not only to those who manage it. Reporters, camera crews, editors and the person who runs the gallery each see a different part of the pipeline, and each will have a view on where it stalls. Decide beforehand who can spare an hour, and tell them plainly that the purpose is to understand the process, not to assess them.
Think about timing as well. Observing a quiet fortnight gives a flattering picture, while observing a week with a running story shows the pressure points. If you can, allow some time on a busy day, accepting that people will have less patience for questions.
Finally, check that your colleagues know it is happening. A review that arrives as a surprise is read as criticism, and people become guarded. One short message from the editor explaining the aim usually settles that.
- Offer access to crews and editors, not only managers
- Include at least one busy day if possible
- Tell the team what the review is for in advance
Questions to put to any reviewer
Ask how they intend to find out what really happens, as opposed to what is supposed to happen. A sound answer involves watching, tracing real stories and talking to people at every level. Ask what you will hold at the end: a list of practical changes in order of effort and benefit is more useful than a long document of observations.
Ask what they will need from you, how much of your team's time it takes, and how they handle material that is sensitive or unpublished. Ask what happens if a suggestion turns out not to suit your newsroom, and whether they will revisit it with you.
Finally, ask for the price and what it covers in writing before anything starts, along with what would change it. If the answers are plain and specific, you can compare them calmly. If they are vague, that tells you something as well.
- How will you observe the real process?
- What will we hold at the end, and in what form?
- What does the quotation include, and what would change it?
A workflow review is most useful when the newsroom arrives with a traced story, a list of who decides, its own working documents, a clear outcome and a team that knows what is happening. None of this takes long, and much of it is worth doing whether or not you ever commission outside help. If you would like to talk it through, the contact page is the place to start.