Before You Reorganise the Newsroom: A Workflow Checklist for Small Teams

Most small newsrooms think they have a speed problem. In my experience on shoots and in edit suites alongside newsroom staff, they have a waiting problem. Footage arrives and sits. A package is finished and sits again, this time waiting for someone to look at it. Before any consultant is called, spend a few days simply noting where a story pauses and for how long.

Pick three recent stories, one fast and two awkward, and trace each from the moment the camera stopped recording to the moment it went out. Write down every hand it passed through. You will usually find that the cutting and shooting take far less time than the gaps between them.

That trace is the most useful thing you can bring to a first conversation. It turns a vague feeling that things are slow into a short list of specific moments you can discuss, and it stops anyone proposing a fix for a problem you do not have.

• Trace three real stories from last record to publication
• Note every handover and how long each wait lasted
• Separate working time from waiting time

Ingest is the first place time leaks away. Ask who is responsible for copying cards or receiving files from the field, where they land, and how anyone knows they have arrived. If the answer depends on one person being at their desk, that is a risk worth naming before a breaking story tests it.

Look at naming and logging too. Clips called by camera numbers and dates are fine for the person who shot them and nearly useless to an editor who was not there. A short, agreed habit at the point of ingest saves far more time later than any piece of software.

Also consider the field end. Can a reporter or operator send material from a location, and does the desk know what has been sent? Daniel-style handheld work on a fast story produces many short clips, and without a simple rule for labelling them the editor ends up scrubbing through everything to find one usable shot.

• Name who owns ingest, and who covers when they are away
• Agree one plain naming habit for clips
• Confirm the desk can see what the field has sent

Approvals are where careful newsrooms lose the most minutes, usually for good reasons. Accuracy matters, and nobody should remove a check just to go faster. The question is whether each check is placed where it can actually be done quickly, and whether the person doing it has what they need in front of them.

List every sign-off a piece currently needs. For each one, ask what it is protecting against, and whether a person can give it from a phone or a shared screen without walking across the room. A script approved before the edit is often cheaper than a finished package sent back for a wording change.

It also helps to decide in advance who can approve when the usual person is unavailable. Many delays on a developing story are not disagreements at all. They are an editor in a meeting and no agreed deputy, with a finished piece waiting on a single reply.

• List every sign-off and what it protects against
• Name a deputy for each approver
• Move checks earlier where wording is likely to change

Archives rarely feel urgent until the day someone needs last year's footage and cannot find it. Ask how a clip from a story eighteen months ago would be located today, and by whom. If the answer is that one long-serving colleague remembers, that is the finding.

Decide what deserves keeping. A small team does not need to store every rushed take, but it does need a clear rule about final packages, key interviews and unique location shots. Storage that nobody can search is only a slower way of losing things.

Think about the practical side as well: where copies live, how they are backed up, and what happens to rights notes and interviewee permissions. A tidy archive supports quicker follow-ups, because the next story on the same subject starts with existing pictures rather than a blank page.

• Test how long it takes to find a clip from last year
• Set a simple keep-or-discard rule
• Record permissions alongside the footage

Good consulting works with how a newsroom already thinks rather than replacing it. Before anyone arrives, write down the habits you value and want protected: the morning conversation, the way a senior editor reads scripts, the house style for graphics and captions. These are not obstacles, they are the newsroom's character.

Be equally clear about constraints. Budget, existing equipment, staff hours and the software you are already paying for all shape what is sensible. A plan that assumes new kit or extra people is not a plan for a small team, and it is better to say so at the start.

Settling this early makes the whole engagement calmer. The consultant knows the edges of the job, your staff know nothing is being done to them, and any change suggested can be judged against a short, honest list of what matters most to you.

• Write down the habits you want to keep
• State budget and equipment limits plainly
• Agree who decides when views differ

When you do talk to someone, ask them to describe a past change in specific terms: what was slow, what they altered, and what the team noticed afterwards. Be wary of answers that are all promise and no detail. Modest, plainly described improvements are more believable than dramatic ones.

Ask how they will learn your newsroom. Will they sit in on a normal day, read your actual stories, speak to the people who ingest and approve? A workflow built from a visit is usually better than one built from a template.

Finally, ask what happens after the first recommendations. Who writes things down, who trains the team, and how will you know in a month whether stories are moving faster? A good answer includes a simple way to measure, using the same story traces you began with.

• Ask for one past change described in concrete terms
• Ask how they will observe a normal working day
• Agree how you will measure progress afterwards