How a workflow review actually runs, from first walk-through to show day

It starts with watching, not with a checklist

When a studio manager asks us to look at their workflow, the first thing we do is turn up and watch a normal working day. We do not bring a template or a list of faults to find. We bring a notebook, a pair of headphones and a lot of patience, and we sit near the people who actually do the work.

Most delays come from small things that nobody has written down. A producer waits for a file because it was named differently from last time. An operator switches a source by memory because the label on the panel wore off. These habits grow up around busy teams, and they are only visible when someone stands quietly in the corner and follows a programme from the first cue to the last.

Our notes at this stage are plain observations with times beside them. We record how long a task took, who waited and what they were waiting for, so that later we can talk about real minutes rather than impressions.

• One full working day observed where possible
• Notes kept as times and names, not opinions
• No changes suggested during the first visit

Tracing the signal from camera to screen

Next we follow the picture and the sound through the building. We start at the source, a camera or a microphone, and walk the path through patch bays, routers, mixers and converters until it reaches the output. We write each step on a single sheet and ask whoever knows the room best to correct us.

This is usually where the surprises turn up. A feed passes through an old converter that nobody remembers adding. A return signal travels the long way round because of a cable run chosen years ago for a different layout. None of it is dramatic, but each extra hop adds delay, a place for a fault to hide and one more thing a new operator has to learn.

By the end we have a drawn map the whole team can read. Often it is the first time the studio has had one that matches what is really plugged in, and people tend to start marking it up on the spot.

• Every device on the path listed by name and location
• Delays and conversions noted at each stage
• Unlabelled or undocumented links flagged for checking

Following the files after the show ends

Live signal is only half of the picture. The other half is what happens to recordings, graphics and audio once they exist. We ask where a file is written, who moves it, what it is called and how long it takes before somebody else can use it. Then we ask what happens if the person who normally does that is away.

Studios are often surprised by how much time is lost between a recording finishing and an editor being able to open it. A drive is carried across a room, a transfer runs overnight because nobody wanted to interrupt it, or two people keep their own copies and quietly disagree about which one is current.

We trace one real recording from end to end and time each handover. That single example usually explains more than a long discussion about storage, because everyone can see the same gaps in the same place.

• Naming habits compared between shows and between staff
• Copies counted: where they live and who owns each
• Handover times measured on one real recording

Show-day procedures and the cue sheet nobody updates

We also read the paperwork a team already uses, and we compare it with what we saw. Running orders, call sheets and fault procedures tend to describe the studio as it was a few years ago. The gap between the page and the room is where mistakes happen at the worst moment.

Mid autumn is a good time to do this. Many teams are settling into a new season of programmes or preparing for winter events, and they would rather fix a routine now than discover its weakness live. We ask what happens when a camera drops out, when a guest arrives late, when the lead engineer is ill.

Where an answer lives only in one person's head, we write it down in short, plain steps. The aim is not a thick manual. It is a single page by each desk that a competent stranger could follow in a bad moment.

• Running orders checked against what really happens
• Fault steps written in short, numbered lines
• One owner named for each procedure

What we hand back, and how it is used

The result of a review is a written report in ordinary language, with the signal map, the file path and the procedures attached. Findings are ordered by how much time or risk they involve, and each comes with a note of what it would take to fix. Some are an afternoon with a label printer. A few need equipment or a change in how the team works.

We do not expect everything to be done. Studios have budgets and calendars, and a sensible list is one the team can work through over several months. We sit down with the managers and agree which items matter most before the first rehearsal of the new season.

If the studio wants help carrying changes out, we can join the crew for that work. If not, the report stands on its own, and the team keeps the drawings and checklists whether or not they ever call us again.

• Report written in plain English with drawings attached
• Findings ranked by time lost and risk
• Quotation given separately if you want help with changes

Small changes that tend to pay off first

Across the reviews I have led since 2011, the early gains are rarely glamorous. Consistent labelling on panels and cables cuts the time operators spend hesitating. One agreed file naming rule removes a surprising amount of searching. A shared, current signal map means a new freelancer can be useful in an hour rather than a week.

A short rehearsal of the fault procedures helps just as much. Teams that have practised losing a feed once are calmer when it happens live, and the practice often shows a missing cable or a vague instruction while the cost of finding out is still small.

None of this needs new technology. It needs somebody to look closely, write down what they saw and give the team something they can keep using after the visit is over.

A workflow review is mostly careful looking, followed by plain writing. We watch a normal day, draw the signal path, follow the files and read the procedures against reality, then hand back a ranked list your own team can act on. If delays in your studio or on your event days feel hard to pin down, get in touch and we can talk through what a review would involve.