How to Prepare Your Studio for a Written Technical Audit

Before anyone opens a rack door, write down the question you want answered. Some studios ask for an audit because a fault keeps returning on air, others because a new presenter, a second set or a change of building is coming. The reason shapes the review. A studio chasing an intermittent audio dropout needs the signal paths followed closely, while a studio planning to add a camera position needs the power and cabling capacity checked first.

I find it useful to put the question in one or two plain sentences and attach it to the request. Keep it modest and specific: "We lose the return feed to the presenter about once a week" is far more useful than "we want everything checked". The written review covers cabling, power, signal paths and risks, so your question tells us which of those deserves the most time on site and which can be treated as a general pass.

• The fault or change that prompted the audit
• Which programmes depend on the studio and when they go live
• Anything already tried and what happened

Most studios have more documentation than they think, scattered across email threads, shared drives and the back pages of a notebook. Collect whatever exists: signal flow drawings, patch lists, equipment inventories, power distribution notes, and the manuals for anything unusual. Drawings do not need to be tidy or current. A sketch that is two years out of date still tells the auditor what the studio was meant to be, and the differences from what is actually installed are often where the useful findings sit.

If nothing is written down, say so plainly. An audit can still go ahead, and the review will then include a record of what we find so that the next person has a starting point. It also helps to name the person who knows the room best, whether an engineer, a floor manager or a long-serving operator, and to make sure they are available on the day to answer questions.

• Signal flow diagrams and patch lists, however rough
• Equipment inventory with approximate ages
• Fault logs or notes of past on-air problems

A short walk through the studio and gallery before the visit costs nothing and often turns up the obvious items. Look at the floor along the walls and behind the desks. Loose cable run across walkways, power strips daisy-chained into one another, labels that have peeled or faded, and connectors held in place with tape are all common, and all worth noting before an outside eye arrives.

Take photographs of the back of the main racks and of any cabinet you are not sure about. Note anything that feels warm to the touch, any fan that sounds different from last month, and any socket that is used by more than one thing. None of this needs to be solved in advance. The aim is simply to arrive at the audit with your own observations written down, so that the conversation starts from what you have seen rather than from a blank page.

• Cables crossing walkways or tucked under carpet
• Extension leads feeding other extension leads
• Missing, faded or contradictory labels

The visit itself is mostly looking, measuring and asking questions, and it can usually be arranged around a quiet part of your schedule. We trace the main signal paths from source to output, check how the gallery is powered and whether any single point of failure would take the whole studio off air, and inspect the cable runs and patching. Where it is safe and sensible, we test rather than assume.

We try not to interrupt live work, so we will agree in advance which areas are off limits during transmission. Expect to be asked why things were set up the way they are. Often there is a good reason that never made it into the documentation, and capturing it is part of the job. By the end of the visit you should know roughly what we have seen, even though the written review follows afterwards in full.

• Signal paths traced from source to output
• Power distribution and single points of failure
• Cabling condition, routing and labelling

The written review ends with a prioritised action list, and how you read it matters as much as what it says. Items are ordered by the risk they pose to live output, not by how easy they are to fix. A cheap job near the top, such as replacing a failing connector on a feed that carries the programme, deserves attention before an expensive tidy-up lower down. Read the top section first, then decide what can be handled by your own engineers.

Some items will be quick: relabelling, re-routing a cable, separating circuits. Others need planning, a budget conversation or a gap between programmes. It is perfectly reasonable to act on only part of the list and keep the rest for later. The review is written so that it still makes sense in six months, with the reasoning for each item set out rather than just a verdict.

• Start with items that threaten live output
• Separate quick fixes from jobs needing a planned gap
• Keep the full review as a record for future changes

An audit loses value quickly if it sits in a drawer. After the review arrives, hold a short meeting with whoever runs the studio day to day and agree who owns each item and roughly when it will be looked at. Record the outcome next to the original item, even if the answer is that you have chosen not to act on it. That small habit makes the next audit faster and keeps arguments about past decisions short.

When changes are made, update the drawings and patch lists as you go rather than in a batch later. A studio whose documentation matches its wiring is easier to fault-find at short notice, easier to hand over to a new engineer and easier to extend. Treat the audit as the point where that discipline starts, not as a one-off exercise to be filed away.