Six Studio Workflow Mistakes We Keep Finding, and How to Avoid Them

Reviewing the plan before the cables

Most workflow problems we are asked to look at were not caused by faulty equipment. They were caused by decisions made in the wrong order. A studio buys a new mixer, a new set of cameras or a new routing layer, and only afterwards asks how the pieces will behave together. By then the room is built, the patch bay is full and nobody remembers why a particular path was chosen.

When I work through a studio for Studio Workflow Consulting, I begin on paper. I ask for the signal path from each camera to the vision mixer, from the mixer to the recorder and the output, and the same for every audio source. Gaps in that drawing nearly always point to the faults the crew has been living with for months.

Mid autumn is a sensible time for this, because many teams are planning winter schedules and still have room to change things before the busy weeks begin.

Mistake one: nobody owns the whole signal path

In a typical studio, the camera crew knows the cameras, the audio team knows the desk and the engineer knows the router. Each group is competent, yet nobody holds the picture from lens to transmission. When a fault appears, every group proves its own section is fine, and the problem sits quietly in the joins between them.

The fix is modest. Name one person who is responsible for the complete chain, and give them a single current diagram to maintain. It does not need to be elegant. It needs to show every device, every conversion between formats and every point where delay can be added.

In our reviews, this one document often settles arguments that had run for weeks, simply because everyone can finally point at the same line.

• Keep one diagram, dated, in the control room
• Mark every format conversion and frame store
• Review it whenever equipment is added or moved

Mistake two: treating latency as someone else's problem

Video processing adds delay, and audio paths add delay of a different size. If nobody records those figures, lip-sync drifts as soon as a new device joins the chain. Crews then compensate by ear, which works until a different operator sits at the desk and makes a different adjustment.

Write down the delay of each stage when it is installed, even if the number is approximate, and note who measured it. When a device is replaced, measure again rather than assuming the new one matches the old.

A short sync check at the start of each production day, using the same test source every time, catches drift before the audience does. It takes minutes and gives the team a shared reference instead of a matter of opinion.

Mistake three: changing things without a record

Studios evolve through small changes. A cable is moved for one show and never moved back. A preset is altered for a guest and left that way. Within a year, the room no longer matches its documentation, and the people who knew why things were set up as they were have moved on.

A simple change log solves most of this. Each entry needs a date, the person, what changed and the reason. It should live next to the diagram, not in someone's inbox.

This is also the cheapest form of training you can offer. A new vision mixer or sound operator who can read six months of changes understands the room far faster than one who is told to ask around.

• Log every patch, preset and routing change
• Record the reason, not only the action
• Review the log monthly with the whole crew

Mistake four: skipping the rehearsal of failure

Crews rehearse the show but rarely rehearse what happens when something breaks. Which camera is the fallback if the main one loses its feed? Who calls it, and how does the director hear about it? When these answers exist only in people's heads, a fault during a live programme becomes a scramble.

Choose two or three likely failures and walk through them during a quiet slot. Lose a camera, lose a microphone feed, lose the talkback to one position. Time how long recovery takes and note where the team hesitated.

The goal is not to remove every risk. It is to make sure the response is agreed beforehand, so that the people involved are following a plan and not inventing one under pressure.

Mistake five: writing the plan once and filing it

After a review, we write up a practical plan for improving the studio. The most common way for that plan to fail is that it is read once, agreed with and then left in a folder. Weeks later, the daily pressure of production has pushed it aside.

Break the plan into small steps that can be done between shows, and give each step an owner and a rough week. A change that fits inside a single quiet afternoon is far more likely to happen than a project that needs the room closed.

Come back to the plan after a month and mark what has been done. Unfinished items usually reveal a real obstacle, such as a missing part or a scheduling clash, and that is worth knowing early.

• Split the plan into afternoon-sized tasks
• Assign one named owner to each task
• Check progress after the first month

None of these mistakes needs new equipment to correct. They need a shared diagram, recorded delays, a change log, rehearsed failures and a plan that people actually return to. A studio that does those five things can usually absorb new technology without losing its footing. If you would like a second pair of eyes on your own signal path, the contact page is the place to start.