Review in Place or Review Remotely: Two Ways to Audit a Newsroom Workflow

Two ways to look at how stories move

When a newsroom asks us to review how a story travels from tip to transmission, there are two sensible ways to go about it. The first is to send someone to sit in the building for a few shifts and watch. The second is to work from a distance, using the planning documents, the running orders, the file logs and a handful of recorded conversations with the people who handle each stage.

Both approaches end with the same thing: a short written set of changes that save time without asking anyone to learn a new system. The difference lies in what each method is able to notice. I have used both over the years at verbmelo, and this article sets them side by side so an editor can pick the one that fits the problem they actually have.

I will say now where I land. For most television newsrooms, a short visit followed by remote follow-up works better than either method alone. But the reasons matter, and there are cases where one of the two is clearly the right call on its own.

What an on-site review shows

Sitting in the room, you see the things nobody thinks to mention. A producer walks across the floor to ask a question that a shared note could have answered. A reporter waits for a file to finish copying because the only fast drive sits on someone else's desk. A duty editor keeps a second list on paper because the main system does not show what has been cleared for air.

These are small frictions, and they rarely appear in a written description of the process. People describe the workflow as it is meant to run, not as it runs at ten past six with a late interview coming in. Being present lets you time the real gaps between hand-offs and see which ones repeat from one day to the next.

An on-site review also makes it easier for staff to speak plainly. A conversation at a desk, with the story still open on the screen, tends to be franker than a scheduled call. The cost is real, though: it needs our time and theirs, and a visitor in the gallery can change how people behave for the first day or so.

• Shows unrecorded workarounds and paper lists
• Lets us time hand-offs as they actually happen
• Easier to hear honest views from staff at their desks

What a remote review shows

Working from a distance has its own strengths. The paperwork tells a steady, unhurried story: how long items sat between filing and approval, which formats caused re-exports, how often a package was rebuilt after a change of running order. If the newsroom keeps decent logs, a week of them can reveal a pattern faster than a week of watching.

It is also easier on the people involved. Nobody has to give up a corner of the desk or explain the room to a stranger. We can read the material in our own time, come back with specific questions, and speak to individuals one at a time rather than catching them in the middle of a bulletin.

The weakness is what the documents leave out. Logs record what was entered, not what was avoided. A remote review can tell you that approvals are slow; it often cannot tell you that they are slow because one person is the only one allowed to sign off and is also the person filing the lead story. That kind of cause tends to surface only when someone is in the room.

Cost, disruption and speed compared

On time and money the remote route is lighter. There is no travel, no days given over to observation, and the written findings can follow within a few working days of receiving the material. For a small regional desk with a tight budget and one clear complaint, such as late captioning, that is often enough.

The on-site review takes longer to arrange and asks more of the newsroom, because managers must tell the shifts we are coming and make someone available to answer questions. In return, the recommendations tend to be more specific and easier to act on, since we have seen the actual room, the actual desks and the actual routes between them.

Disruption cuts both ways. A visit can feel intrusive for a day. A remote review can feel remote in a different sense: staff may not see the point of it and answer questions briefly. I would weigh how settled the team is, how much trust there already is, and whether the problem is one of paperwork or of people and layout.

• Remote: lower cost, quicker start, less disruption
• On site: higher cost, richer detail, more specific advice
• Either way the output is a short written list of changes

When each option is the right choice

Choose the remote review when the question is narrow and the records are good. If you want to know why items miss a particular delivery slot, or whether a naming convention is causing lost files, the documents will usually answer it. The same goes for a newsroom that is stretched thin and cannot spare anyone to host a visitor for several shifts.

Choose the on-site review when the trouble is hard to describe. If editors say stories simply feel late, or if the same arguments recur between the field, the edit suite and the gallery, something in the way people and equipment are arranged is probably at fault, and that is best seen in person.

If the problem is genuinely unclear, start with a short visit of a day or two. It costs less than a full residency and gives enough to decide whether more is needed. Then let the remote work fill in the detail from the logs, with the visit telling us which logs to read first.

The recommendation

My advice for most television newsrooms is the combined route: one short visit, followed by a remote review of the records and a written summary. The visit finds the causes that documents hide, and the records confirm which of them cost the most time, so nobody ends up fixing a daily irritation that turns out to affect two minutes a week.

Whatever is agreed, ask for the findings in plain language and in an order you can act on. The first change should be something your team can try within a week, using the people and tools already in the building. If a recommendation needs a large purchase or a restructure before anything improves, it deserves a second look.

I would also keep the scope small. A review that tries to cover every stage of production at once tends to produce a long list that nobody finishes. Pick the stretch between tip and first edit, or between final cut and transmission, and look hard at that one.

• Start with a one or two day visit
• Follow with a remote read of logs and running orders
• Ask for the first change to be testable within a week