Six Common Mistakes in Live Workflow Reviews and How to Avoid Them

Reviewing the paperwork instead of the show

The most frequent mistake is treating a workflow review as a desk exercise. A signal flow diagram, a rundown and a kit list are useful, but they describe the show as it was planned, not as it runs on the night. Diagrams drift from reality within a few weeks: a spare converter gets patched in, a monitor is moved, a temporary cable becomes permanent. If the review starts and ends with documents, it tends to confirm what everyone already believes.

Our written reviews begin with the documents and then move to observation. We ask to see a rehearsal or a live transmission, and we note what operators actually do between cues: who they call, which screens they look at, where they improvise. Those small habits often reveal the real workflow, and the real weak points, far better than any drawing of the system.

• Compare the diagram with what is physically patched
• Watch at least one full run, not only the quiet moments
• Ask operators what they do when something goes wrong

Asking only the people at the top

A producer or studio manager can describe the intent of a workflow very well, but the people who feel its friction are usually the vision mixer, the sound operator, the camera crew and the person running playback. When a review collects views from one level only, the recommendations tend to reflect management priorities and miss the small daily frustrations that cause late cues and dropped moments.

We try to speak with every role that touches the programme, in short conversations rather than a formal survey. People are more candid when they are asked about a specific moment, such as the last time a feed arrived late, than when they are asked what could be improved. The written review then credits the observation to the role, not the person, so nobody is exposed for being honest.

Chasing every finding at once

A thorough review can produce a long list, and the second common mistake is trying to act on all of it together. Teams that change the routing, the intercom plan and the audio chain in the same fortnight cannot tell which change helped and which caused the new fault that appears on Friday. Recorded and live work both suffer, because nobody has a stable baseline to return to.

This is why our reviews are prioritised rather than simply listed. Each recommendation is placed in an order based on risk to the programme, effort to put right and how much it depends on other changes. Items that protect the transmission come first, and cosmetic tidying comes last. Where two changes interact, the review says so, and suggests doing them on separate production days.

• Rank findings by risk to the programme first
• Change one connected area at a time
• Keep a note of the settings you can return to

Forgetting the recorded side of the workflow

Teams who mostly work live often review only the path to air and overlook what happens to material afterwards. Recordings, iso feeds, clean audio and logging may be handled informally, and the review misses the places where files are named inconsistently, timecode is not shared or a second audio mix is made by hand. These gaps are rarely visible on the night and become expensive in the edit.

A good review follows the material from the moment it is captured to the moment it is delivered or archived. We ask where each recording is written, who checks it and how long it takes to find a particular segment. Often the useful recommendation is modest, such as agreeing one naming pattern and one person responsible for checking recordings before the crew leaves.

Vague recommendations nobody can act on

A review that says the audio chain should be tightened or the gallery communication improved gives a team nothing to do on Monday. Vague findings are easy to write and easy to agree with, which is exactly why they change nothing. The same is true of recommendations that name a problem without naming who should look at it or what a fixed version would look like.

We write each recommendation so that it can be picked up by a named role. It states what we saw, why it matters, what to change and how you would know it had worked, for example that the delay between camera and sound stays constant across a full show. If a finding needs further measurement before a decision, the review says that plainly and describes the measurement.

• State what was seen, not only what to fix
• Name the role responsible for each action
• Describe how success would be checked

Treating the review as a one-off event

The last mistake is filing the report and moving on. Workflows change with every new presenter, venue, camera or format, and a review written in one season can be out of date by the next. Teams that read the document once, agree with it and never return to it lose most of its value within a few months.

We suggest keeping the written review as a working document. Tick off completed items, add a line when something new is introduced, and revisit the priority order before a major production or a change of crew. A short follow-up conversation after the first changes have bedded in is often more useful than a second full review, because it shows which recommendations held up in practice.