What a Studio Workflow Review Actually Covers, Step by Step

The question we are asked most often

Almost every first conversation begins the same way: what do you actually do when you review our studio? It is a fair question, because the phrase workflow consulting can mean anything from a quick chat to a month of paperwork. At premixra it means something specific. We follow the path of a programme through your building, from the cameras on the studio floor to the control room, through the signal chain, and out to whatever carries your output.

The answer matters to producers and engineers alike, because each of them sees only part of that path. A producer notices that the gallery feels slow to react. An engineer knows which patch bay is awkward. Nobody holds the whole picture at once, and that gap is where most avoidable delays and repeated faults hide. Our review exists to close it, and to put the result on paper.

Before we arrive: what we ask you to send

The review starts at a desk, not in your studio. We ask for whatever documents already exist: signal flow diagrams, patch lists, rack layouts, a rundown from a recent show, and any fault log your team keeps. Most studios have less of this than they fear, and we work with what is there. A hand-drawn sketch of the control room is perfectly useful.

We also ask for a short note from each role that touches the output. Vision mixer, sound operator, director and floor manager each tell us in their own words what slows them down. These notes are often the most valuable part of the preparation, because they point us towards problems that no diagram would show. Nothing in this stage requires you to stop production or reorganise anything.

• Signal flow diagrams or rough sketches
• Patch lists and rack layouts
• A recent rundown from a typical show
• Any fault or incident log
• A short note from each operating role

On site: following one programme through the building

We usually spend one to two days in the studio, depending on its size. The most useful thing we can do is watch a real rehearsal or a live production from the gallery and from the floor, rather than a staged demonstration. We stand behind the operators, listen to the talkback, and note where people wait, repeat a request or work around a limitation.

Alongside that we trace the signal paths physically: which camera feeds which input, where audio is embedded or separated, how timing is handled and where the programme leaves the building. We check labelling, cable routes and the order in which a crew powers things up in the morning. Small habits count for a lot here. A tidy, consistent start-up sequence prevents more faults than any new piece of equipment.

What we look for, and what we leave alone

Our attention goes to handovers: the moments where responsibility or signal passes from one person or device to another. Those are the places where delays, mislabelled sources and timing drift tend to appear. We look at how cues are called, how graphics and playout are triggered, and whether the people involved agree on who does what.

Equally important is what we do not do. We do not insist on replacing kit that works, and we do not rewrite your editorial decisions. If an item of equipment is genuinely the limit, we say so plainly and explain why, but most improvements in a review come from sequence, labelling, documentation and communication. Where a deeper investigation is needed, for instance a persistent lip-sync fault, we say so and treat it as separate work.

• Handovers between people and between devices
• Start-up and shutdown routines
• Labelling and documentation gaps
• Cue calling and talkback habits

The written plan you receive

The output of a review is a written report, not a presentation. It describes the workflow as it currently runs, sets out each finding with the observation behind it, and proposes changes in a sensible order. Quick adjustments that cost nothing come first, then changes that need a planned slot off air, then any longer items worth budgeting for.

Each recommendation is written so that your own engineers can act on it without us in the room. We include revised diagrams where the existing ones were missing or out of date, and a short checklist for the daily routine. Helen Marsden, who leads the reviews, goes through the report with your team afterwards and answers questions, so that the document does not simply sit in a shared folder.

How long it takes and what you need to provide

From the first enquiry to the written report, a review normally runs for a few weeks, shaped mainly by when your studio can offer us a rehearsal or a transmission to observe. The on-site days are the shortest part. Most of the elapsed time is spent writing carefully and checking our notes against what your team told us.

Your side of the work is modest: send the documents you have, make a named contact available, let us sit in on real production, and give us honest access to the people who operate the room. We do not need a quiet studio or a perfect one. The cost and what it covers are set out on the prices page, and you can start with a simple enquiry through the contact page.

A workflow review is a structured look at how your programme travels through your own building, followed by a plan you can act on. It asks for a few documents, a day or two of your team's attention and honest answers. In return you receive a report that names the delays, explains the reasons and puts the fixes in order, written for the people who will carry them out.