Start with the stories that slipped, not the tools
Before looking at any software or process diagram, I ask a newsroom to pull out the last handful of stories that went out later than anyone wanted. For each one, mark where the clip actually waited: in an edit queue, in someone's inbox for sign-off, or in a folder nobody had told the delivery desk about. That small exercise tells you more than a week of interviews, because delays cluster in the same two or three places.
Write the findings on one sheet, in plain words. Avoid blaming people; a clip that sat for forty minutes usually sat there because the route to the next person was unclear. If the sheet shows the same handover appearing again and again, you have found the part of the workflow worth redesigning first, and you can leave the rest alone for now.
This is the first item on the checklist because it stops a redesign from becoming a tidy-up of things that were never the problem.
- List the last stories that ran late
- Mark the exact handover where each one waited
- Note whether the wait was people, files or unclear ownership
Map who approves what, and what happens when they are away
Approval is where most newsroom workflows quietly fail. Check whether every kind of output has a named approver: bulletin packages, online clips, captioned versions, interview extracts. Then ask the harder question: who signs off when that person is on leave, in a meeting or on location? If the honest answer is that the clip waits, that is a gap to close before you change anything else.
Look at how many sign-offs a routine clip needs. Some newsrooms collect three approvals out of habit when one editor and one duty producer would be enough for a standard package. Sensitive or legally awkward stories deserve a longer route, but the ordinary ones should not travel it.
A good approval step is short, written down and has a deputy. Agree this with the people who actually do the signing, because a rule they did not help write is the first one they will route around under deadline.
- Name one approver and one deputy per output type
- Separate routine clips from sensitive stories
- Write the rule where editors will see it
Check how files move from camera to edit to delivery
Follow one piece of footage physically, or as physically as a file can be followed, from the camera card to the transmission server or online channel. Count the times someone copies, renames or re-exports it. Each manual step is a place for a wrong version to go out or for a clip to be mislaid, and in a busy hour those small errors cost more than the minutes they appear to cost.
Check that naming is consistent. If three editors label clips three different ways, the delivery desk spends its time guessing. A short naming convention, agreed once and used by everyone, removes a surprising amount of friction.
Also confirm the delivery formats you actually need: broadcast, web, captioned, vertical. Knowing which are standard and which are occasional lets the edit step export the right versions in one pass rather than being asked again after the clip is finished.
- Count every copy, rename and re-export
- Agree one naming convention
- List the formats each destination really needs
Be honest about what your team will keep using
A workflow only works if the people on shift follow it at six in the evening with a story breaking. When reviewing a proposed change, ask whether each step is something a tired editor will do without being reminded. If a step relies on someone remembering to update a spreadsheet, expect it to be skipped within a fortnight.
Include the freelancers and occasional crew in the question. They meet the process less often and need it to be obvious. A one-page guide that fits next to the edit station is more useful than a long document stored somewhere out of sight.
Think about training time too. A change that needs a day of instruction for every editor has a real cost on a rota that is already thin. Prefer small adjustments that people absorb during normal shifts, and phase the larger ones across quieter weeks, which in mid autumn often means before the run-up to the busy winter schedule.
- Test each step against a tired shift
- Include freelancers and visiting crew
- Prefer changes that need little training
Decide how you will know it has improved
Agree the measure before the work starts. It does not need to be elaborate: the typical time from footage arriving to clip delivered, and the number of clips returned for correction, are usually enough. Record them for a couple of weeks as they are now, so that later you are comparing against a real baseline rather than a feeling.
Be cautious about promising a figure in advance. Newsrooms differ, and a quiet fortnight can flatter any change. Compare like with like, and look at the slow days and the frantic ones separately.
Set a date to review. A workflow is not finished when the new steps are written down; it is finished when the team has used them under pressure and told you where they chafe. Build in one short review session a few weeks in, with the people who do the work in the room, and be ready to loosen a step that is not earning its place.
- Record current turnaround before changing anything
- Count clips returned for correction
- Fix a review date with the team present
Questions to put to whoever redesigns it
If you bring in outside help, ask how they will learn your newsroom before proposing anything. Be wary of anyone who arrives with a finished diagram. Ask who will be on the floor during the work, what they will need from your staff and how long your editors will be pulled away from live output.
Ask what stays in your hands afterwards. You should end up with steps you can maintain yourselves, written in language your team uses, not a system that only the people who built it can adjust.
Finally, ask what they would leave unchanged. A sensible answer shows that the redesign is aimed at the delays you found in the first step, rather than at replacing everything because it can be replaced. That restraint is usually the best sign that the proposal has been thought through for your newsroom specifically.
- Ask how they will learn your newsroom first
- Ask who works on the floor and for how long
- Ask what they would deliberately leave alone
A workflow redesign is worth deciding on when you can point to the handovers that cause delay, name the approvers and their deputies, and say how you will measure the result. Work through these questions with the people who run your shifts, and the decision usually becomes clear. If it is useful, I am happy to look at your list with you before anything is committed.