What a Written Audit Found in One Regional Studio's Signal Chain

Marcus runs a small regional studio that produces an evening news bulletin and a weekly interview programme. He rang us in the middle of October, a few weeks before his winter schedule filled up. Nothing had gone badly wrong. What worried him was a feeling, shared by his two engineers, that the gallery worked because certain people happened to be in the building, not because the system was sound.

We hear that sentence more often than any other when a studio asks for a workflow and reliability audit. Systems grow in layers. A router is added in one year, a replacement monitor the next, and a backup path gets patched in during a bad night and never documented. After several years nobody can say with confidence what would happen if one box failed.

So we agreed a plain scope with him: a written review of the signal chain, the backup paths and the run sheets, with fixes ranked by priority. He did not want a rebuild, and he said so twice.

I spent two days on site. The first morning I did nothing but follow cables. Starting at each camera, I traced the path through the wall boxes, the patch bay, the router and the vision mixer, and out to the transmission feed, noting every connector, adaptor and power source along the way. Marcus's engineers helped, and several of them learned things about their own gallery that nobody had ever written down.

The method is unglamorous. I draw the chain as it really is, not as the original drawings claim, and mark every point where a single failure would stop pictures or sound reaching air. A diagram on paper makes weak points obvious in a way that standing in a hot gallery does not.

By lunchtime I had a drawing that Marcus pinned to the wall. He told me it was the first time the whole system had existed on one sheet.

• Every cable path traced and labelled on one drawing
• Single points of failure marked in red
• Undocumented adaptors and splitters listed

Three things stood out. First, the intercom and the programme audio shared one power distribution strip, so one tripped breaker would have silenced both at the same moment. Nobody had noticed because it had never tripped during a broadcast.

Second, the backup path for the main camera feed existed, but it ran through the same patch panel as the primary. It looked like redundancy and behaved like a single path. A loose connector there would have taken out both.

Third, the run sheet for the evening bulletin assumed a particular person would know to switch to the standby graphics machine. That instruction lived in one engineer's head. None of these problems was exotic. They are ordinary results of a studio that has grown steadily and been kept running by good people doing their best.

A list of twenty findings is no use to a manager with a schedule to keep. The written report put every item into one of three bands: fix before the next broadcast week, fix within the quarter, and note for the next planned upgrade. The shared power strip and the false backup path went into the first band, because both could be solved with a few hours of work and modest parts.

The standby graphics procedure was a documentation job, not an engineering one, so it sat in the first band too. Written down and rehearsed once, it cost almost nothing.

Larger items, such as replacing an ageing router, went into the later bands with a rough indication of cost. Marcus could see which expenses were urgent and which could wait for budget. That ranking is the part clients tell us they value most.

• First band: power separation, true backup path, written standby procedure
• Second band: labelling and patch panel tidy
• Third band: router replacement planning

Marcus's own engineers carried out most of the first-band fixes over a weekend, using my notes. I came back for half a day to check the work and rehearse a failure with them. We pulled a power feed during a mock bulletin, and the intercom stayed alive while programme audio carried on from the separate circuit. We then forced the camera feed onto its backup path, and this time it genuinely arrived by a different route.

The rehearsal was the part he had not expected to need. A fix that has never been tested is only a belief. Watching his team recover calmly from an induced fault told him more than any report could.

He has since added a short monthly test to his own checklist, taking about twenty minutes, in which one backup path is exercised and logged.

The case shows what an audit is for. It does not promise a studio that never fails. It gives a manager an accurate picture of how the system behaves when something goes wrong, and a sensible order in which to improve it.

Most of the value came from drawing the chain honestly and writing the run sheet so that it no longer depended on memory. The equipment changes in Marcus's gallery were small. The change in how his team understood their own system was larger, and it will last longer than any single piece of hardware.