Workflow reviews: common mistakes and how to avoid them

Starting with the kit instead of the route

Most workflow reviews begin when something has already gone wrong: a feed that dropped during a rehearsal, a file that would not open, a presenter waiting on a confidence monitor that stayed black. The first mistake teams make is to answer that single failure by buying or swapping equipment. A new converter or a longer cable may fix the symptom, but the cause is usually further upstream, in how the signal was meant to travel from source to screen.

From the lighting side I see the same pattern with control data. A desk, a node and a run of fixtures are only as dependable as the route between them. A review that starts with a drawn route, every source and destination on one sheet, tends to find the weak joint within an hour, where a shopping list would only hide it.

• Draw the route from source to screen before naming any equipment
• Mark every conversion point, because each one can fail
• Note who owns each stage of the route

Leaving names and labels to memory

A surprising amount of lost time comes from things nobody wrote down. Inputs on a vision mixer called by the name of whoever patched them last year, files saved as final, final2 and final_real, cables with no tag at either end. On a quiet day the team copes because the people who know are in the room. On show day, with a freelancer covering a shift, it falls apart.

The fix is dull and effective: one naming convention, agreed once and written where everyone can see it. Sources, folders and cable runs all follow the same pattern. When I plot a lighting rig I label fixtures and channels the same way each time, so a stranger can read the plot. A studio team deserves the same courtesy from its own paperwork.

• Agree one naming pattern for sources, files and cables
• Tag both ends of every cable run
• Keep the list where freelancers can find it

Treating file handling as an afterthought

Teams often plan the live signal carefully and leave the files to chance. Recordings land on whichever drive was free, graphics arrive by e-mail in three formats, and nobody is sure which copy is current. The delay shows up later, in an edit suite or a playout queue, when someone has to hunt for material that was captured perfectly well.

A sound review of file handling asks plain questions. Where does each recording go, and who checks it arrived? Which format does the next person in line expect? How long are files kept, and who may delete them? Answering these on paper takes an afternoon. Answering them during a deadline takes much longer and usually involves raised voices.

• Decide where every recording is stored and who confirms it
• Agree formats with the people downstream
• Write down retention and deletion rules

Skipping the rehearsal of the dull parts

Rehearsals tend to cover the visible moments: the opening, the guest entrance, the big lighting change. The dull parts are left alone, such as switching to a backup feed, restarting a device mid-show, or handing over between two operators. Those are precisely the moments where delays appear, because nobody has practised them.

I suggest a short run of deliberate small failures during a rehearsal in these autumn weeks, when schedules loosen after the summer events. Pull one source, drop one link, and see who knows what to do. Keep notes. The point is not to catch anyone out but to find the steps that live only in one person's head, and give them a place on a shared page.

• Rehearse the backup route as often as the main one
• Practise operator handovers
• Note every step that only one person knows

Changing too much at once

Once a review turns up a list of weaknesses, the temptation is to fix everything in one push. A new naming scheme, a rebuilt patch bay, fresh file rules and a different show-day script, all introduced the week before a broadcast. When something then misbehaves, nobody can say which change caused it, and the team loses trust in the whole exercise.

Better to rank the findings by how often they cause a delay and how easy they are to correct, then introduce them in small steps between productions. Labelling and file rules cost little and help straight away. Rebuilding cabling belongs in a quiet period with time to test. A modest, ordered plan is more likely to survive contact with a busy schedule.

• Rank findings by frequency and effort
• Introduce changes between productions, not before one
• Test each change before adding the next

Forgetting to write it up for the next team

The last mistake is finishing a review with a good conversation and nothing on paper. Within a few months the agreed habits fade, a new technician arrives, and the studio drifts back to how it worked before. A review is only useful if its results can be picked up by someone who was not in the room.

A short document is enough: the signal route drawing, the naming pattern, the file rules and the show-day order of events, each on a page or less. Review it after a few productions and correct what no longer matches practice. Treated as a living reference rather than a report, it keeps working long after the consultant has gone.

None of these mistakes needs expensive equipment to correct. They come from habits that grew up under time pressure, and they yield to patient, ordinary work: draw the route, label what exists, settle where files go, rehearse the dull parts, change things in order and write it all down. A studio team that does this finds that show days become quieter, and the delays that remain are easier to trace and fix.