Studio Workflow Review: On-Site Visit or Remote Desk Review?
Two ways to review a studio and control room workflow, compared on what each can see, what each costs in time, and which one we would recommend for most small teams.
Two ways to look at a workflow
When a team asks us to review how their studio and control room run, we offer two routes. The first is an on-site review, where one of us spends a working day in the building, watching a real rehearsal or recording. The second is a remote desk review, where the team sends documents, run sheets, signal diagrams and short recordings, and we report from our office in Cambridge.
Neither route is the grown-up version of the other. They answer different questions, and the mistake we see most often is picking one by habit rather than by the problem in front of the team. This note sets the two side by side, with a plain recommendation at the end for the kind of small production team that tends to write to us.
Both routes finish in the same way: a written report that names where time and quality are being lost, ordered by how much each item matters, with a suggested fix beside each.
What an on-site review can see
Standing in the control room is the only reliable way to see the things nobody thinks to mention. A producer calls a shot change and the vision mixer waits for a second confirmation. A talkback channel is shared by three departments, so everyone shouts over each other. A tally light is hard to read from the graphics desk. None of this appears on a run sheet, and people who work in the room every week stop noticing it.
On site we also see the physical layout: how far the floor manager has to walk to reach the camera operators, where cables cross walkways, how the lighting desk position affects communication with the gallery. We talk to each person at their own position, briefly, while they work.
The cost is calendar time. A visit needs a day when the studio is genuinely in use, travel, and the willingness of the crew to be observed.
- Best for timing, communication and layout problems
- Needs a live rehearsal or recording day
- Involves the whole crew for part of a day
What a remote desk review can see
A desk review works from evidence the team already has. We ask for the signal flow diagram, the usual run order, the equipment list, a few minutes of recorded programme with the control room audio if it exists, and a short written account from the producer and the engineer of where they believe things go wrong.
This route is good at spotting structural faults: a routing arrangement that forces an extra conversion, a naming scheme for sources that two people read differently, a checklist that was written for last year's kit. Because we read at our own pace, we can compare documents line by line and notice gaps that a busy day on site might hide.
What it cannot do is observe behaviour. If the real trouble is hesitation, unclear calls or a crowded room, the paperwork will look fine while the programme still runs late.
- Best for routing, documentation and equipment questions
- Needs documents and recordings sent in advance
- No disruption to the working day
Where the two differ in practice
The simplest way to compare them is to ask what the team suspects. If the suspicion is technical, such as sync drift, awkward routing or a patching habit that causes errors, the desk review usually reaches the answer with less fuss. If the suspicion is human or spatial, such as slow decisions, confusion between departments or a room that fights its operators, only a visit will show it.
There is also a question of honesty. People write about their own workflow the way they wish it ran. On site, we see the version that actually happens on a tired Thursday. Remote work relies more on the team's own account, which is useful but never neutral.
Finally, the report differs. A site report carries observations with timings and quotes from the crew. A desk report is more document-based and tends to be shorter, with fewer remarks on behaviour and more on structure.
Our recommendation
For most small teams, we recommend starting with the desk review and adding a site visit only if the report points to something it could not settle. The desk review is quicker to arrange, interrupts nobody, and often removes the cheap, obvious faults first. That leaves the visit, if it is still needed, with a narrower question and a shorter day.
The exception is a team that already knows the trouble is in the room itself: a new gallery layout, a recent change of crew, or a programme that has grown beyond the space it was built for. There, go straight to the visit, because the paperwork will not show what is wrong.
If you are unsure which describes you, say so when you write. We would rather talk it through for ten minutes than sell the wrong route.
- Unclear cause or technical suspicion: desk review first
- Room, crew or timing problems: on-site review
- Both can be combined in a single report
Preparing for either route
Good preparation shortens both. For a desk review, gather the current signal diagram even if it is hand drawn, and mark anything that has changed since it was made. Include the usual run order, a list of who sits where, and a note of the last three problems that cost you time on air or in the edit.
For a visit, pick a day that is typical rather than calm. Tell the crew in advance that a consultant will be watching the process, not judging individuals, and ask them to work as they normally do. Keep a quiet corner available so we can speak to people for a few minutes each.
In both cases, tell us what you would like the report to help you decide. A review aimed at a purchase, a restructure or a training plan reads very differently from one without a stated purpose.
Both routes have a place, and the choice should follow the suspected cause rather than habit. For most small studios, a desk review is the sensible first step, with a visit held back for questions it cannot answer. If you already know the room itself is the problem, book the visit directly. Whichever you choose, the result is a written report you can act on, in plain language, with the largest losses of time and quality listed first.