A Checklist for Judging Live Signal Management Before You Commit

Most conversations about live signal management begin with a list of boxes: encoders, switchers, converters. I would rather begin with a drawing of the route. Ask whoever is quoting you to sketch the path the picture takes from each camera to the point where your broadcaster receives it, naming every hop on the way. A good sketch shows where the signal changes form, where it leaves the building, and where it could be lost. If the person across the table cannot draw it without hesitating, that tells you something before any price does. We draw one for every job at normalvo, even for a single-camera report, because the act of drawing exposes the weak joins early.

Check also who owns each hop. A venue may supply the cabling, a telecoms provider the circuit, and the broadcaster the receiving end. Responsibility that is shared between three parties is, in practice, nobody's responsibility at two in the afternoon on the day of transmission. Write the owner of each stage beside it and get that list agreed in writing.

• Is there a drawn route from lens to broadcaster?
• Does every hop have a named owner?
• Where does the signal leave the venue?

Monitoring is the part of signal management that clients see least and miss most when it is absent. Ask what will actually be watched during the live period: picture, audio levels, loss of the incoming link, temperature of equipment in a hot outside broadcast truck. Then ask who is watching, and whether that person has any other job at the same time. A single engineer who is also rigging cameras cannot give a feed the attention it needs. For anything that cannot afford to go dark, the person watching the signal should be doing nothing else. The screens matter less than the habit behind them: a calm check of each source every few minutes, logged, so that a slow drift is noticed before it becomes a fault.

It is reasonable to ask to see the monitoring layout in advance. You are not judging the technology; you are judging whether the setup has been thought through. Look for a clear view of every incoming source, audio metering that someone can read at a glance, and a way of seeing exactly what the broadcaster is receiving rather than what we are sending.

• Picture, audio and link status all watched
• One person dedicated to monitoring
• Ability to view the return feed

Every live job has a fault somewhere in its chain eventually. What separates a calm day from a bad one is whether a fallback was decided before the fault, not invented during it. Ask for the plan in plain terms: if the main link drops, what takes over, how quickly, and who makes that decision. A second path need not be elaborate. It might be a bonded cellular connection standing behind a fixed circuit, or a recorded copy kept at the venue so that material is never lost even when transmission is. What matters is that the fallback has been tested on site, not merely listed on a sheet. A fallback nobody has switched to is an assumption, and assumptions are what fail first under pressure.

Ask also about the quiet failures: audio that slips out of step with the picture, a frame rate mismatch, a colour range that looks fine on one monitor and wrong on the broadcaster's. These rarely stop a transmission, but they are the faults a producer notices and remembers. A proper check at the start of the job, against the broadcaster's own specification, removes most of them.

• Is there a tested second path?
• Who decides to switch, and how fast?
• Is a local recording kept as well?

Broadcasters differ in what they will accept: resolution, frame rate, codec, audio layout, the way a feed is labelled when it arrives at their desk. Settling these details on the day wastes the quietest and most useful hour of preparation. Ask for the receiving specification from the broadcaster's technical contact and give it to whoever manages your signal, in writing, well before the shoot. If you are supplying more than one outlet from the same event, check whether each wants the same format. Sometimes a single clean output is enough; sometimes separate versions are needed, and that changes the equipment and the number of people. It is far easier to plan for two deliveries from the start than to discover a second requirement during rehearsal.

A short test transmission is worth asking for whenever the schedule allows. Even ten minutes of colour bars, tone and a live picture sent to the receiving end will reveal a mismatch that no amount of paperwork would. Ask who on the broadcaster's side will confirm receipt, because a test that nobody acknowledges proves very little.

• Receiving specification obtained in writing
• One output or several versions needed
• Test transmission arranged before the live period

A signal plan drawn in an office meets the venue only once, and the venue always has opinions. Thick walls kill wireless links, a crowded festival field saturates the mobile network, an old building offers a single power socket behind the stage. Ask whether a site visit or at least a detailed set of photographs and measurements forms part of the preparation. Pay attention to power and to cable runs as much as to the connections themselves. A feed that depends on one extension lead across a walkway is not reliable, however good the encoder. Ask where the equipment will sit, how it will be protected from weather and from people, and whether anyone has checked that the intended uplink actually works at that spot at the time of day you will be live.

Autumn adds its own considerations: damp, early dark, and equipment that has to live outdoors for long hours. Cables and cases that behave perfectly in July can cause trouble in a wet October car park. Ask how the setup copes with rain and cold, and whether spare cables and connectors travel with the crew. The answers should be specific, not general reassurance.

• Site visit or detailed venue information
• Power supply and cable routes checked
• Weather protection for outdoor kit

The last item on my list is the simplest and the one people leave out. On the day, who is your contact, how do you reach them, and how do they reach the broadcaster? Decide this before anything goes live. A producer who has to hunt for a phone number while a picture is breaking up has already lost the minutes that mattered.

Agree a single point of contact on each side and a short, plain way of reporting problems: what is wrong, since when, what is being done. Keep the language calm and factual. Good signal management is quiet by nature, and the clearest sign that it is working is that you hardly hear from the engineer at all until something genuinely needs your decision.