Rundown Mistakes That Slow a Newsroom, and How to Avoid Them

Why the same errors keep returning

I spend much of my time with newsroom teams who say their mornings feel harder than they should. When we sit down and trace a late bulletin or a muddled crew call, the cause is rarely a single dramatic failure. It is usually a small habit that everyone has quietly accepted, such as a rundown that lives in two places or a schedule that only the producer fully understands.

These habits survive because each one seems harmless on its own. A spare copy of the rundown on someone's laptop saves time on a quiet Tuesday. A verbal change shouted across the gallery is quicker than editing a document. The trouble arrives on the day the story breaks, when the quick fixes pile up and nobody is certain which version is current.

This article walks through the mistakes I meet most often in newsroom production coordination, and what a calmer alternative looks like in practice. None of it needs new people or a larger budget, only a clearer agreement about where the truth lives.

Keeping more than one version of the rundown

The most common mistake is also the easiest to spot: two or three rundowns in circulation. The producer has one, the director has a printed copy from an hour ago, and the autocue operator is working from a file that was exported before the lead story changed. Everyone believes they are looking at the plan.

The fix is unglamorous. Agree on a single shared rundown and treat every other copy as disposable. Print only at the moment it is needed, mark the print with a time, and tell the crew that anything older than the latest timestamp should be binned. A shared workspace makes this far easier, because a change made by the producer appears for the director and the technical crew at once.

It also helps to decide who is allowed to edit. Wide-open editing sounds collaborative but tends to produce silent overwrites. Give a small number of people the right to change running order, and let everyone else comment or flag, so the order stays readable under pressure.

• One live rundown, with older copies treated as out of date
• Time-stamp every printed copy
• Limit editing rights to the people who own the running order

Leaving the technical crew out of the loop

Producers think in stories and directors think in shots, but camera, lighting and sound crews think in setups. A frequent mistake is sharing the editorial rundown without the technical detail attached, so the gallery learns about a standing interview or a remote guest only minutes before transmission.

A better pattern is to put the technical needs on the same page as the story they serve. If item four needs a second microphone and a change of lighting for a seated guest, that note sits beside item four, visible to the sound and lighting leads when they plan their morning. Nobody has to chase a producer for a verbal briefing.

This is where bringing producers, directors and technical crew into one shared schedule earns its keep. It does not remove conversation, it removes the guesswork that makes conversation urgent. The crew arrives knowing what the studio has to do, and the early part of the day goes to preparing rather than asking.

Treating crew calls as an afterthought

Crew calls are often written last and read first, which is the wrong way round. A call sheet built from memory on the previous evening tends to miss the person who swapped a shift, or the engineer needed early for a rig change. The result is a studio that is short of a pair of hands at the one moment they matter.

Build the call from the rundown rather than from habit. Once the running order is settled, work backwards: what has to be ready, who has to be in, and by when. Share the call in the same place as the rundown so the two cannot drift apart, and ask each department lead to confirm rather than assuming silence means agreement.

Where a change happens late, say so plainly and name the person affected. A short, specific message beats a general broadcast that everyone skims. The aim is that no one learns their start time from a colleague in the corridor.

• Derive the call from the settled running order
• Ask department leads to confirm, not merely to read
• Name the person affected when a late change is made

Changing the plan without recording why

Bulletins change constantly, and that is fine. The mistake is changing the plan without leaving a trace of what moved and why. When a story is dropped, the technical crew may have already built a set or cued a graphic for it, and a bare deletion tells them nothing about whether to stand down.

Keep a short note against each late change: what was removed or moved, who decided, and what the crew should do about preparation already under way. This takes seconds and prevents the awkward gallery conversation about whether the item is still happening.

It also gives you something useful afterwards. A week of these notes shows where the plan tends to wobble, whether that is a regular guest who cancels or a live link that is often late. Patterns like these are far easier to plan around once they are written down rather than half remembered by whoever happened to be on shift.

Skipping the review once the day is over

After a long shift nobody wants a meeting, so the review is the first thing to go. Yet a five-minute look back is where small errors get caught before they become habits. Without it, the same late graphic or the same missed cue repeats for weeks.

Keep the review short and specific. Ask what slowed the gallery, which change caused the most confusion, and whether any information arrived too late to use. Write down one or two items and assign a person to each, rather than collecting a long list that nobody owns.

Over a month, those small corrections add up to a noticeably quieter studio. The point is not to find fault but to make the next bulletin a little easier than the last, using the evidence the team already has in front of it.

• Hold the review the same day while details are fresh
• Limit it to one or two actions with a named owner