Redundancy: what to ask before you trust a supplier with a live broadcast

Anyone can stream a corporate event when everything goes right. The difference between suppliers shows up when something goes wrong, which is why redundancy is the single most useful thing to ask about before you trust a supplier with a live broadcast. It is not a glamorous conversation, and a supplier who has thought about it properly will not mind having it in detail. A supplier who gets vague or defensive is telling you something too.

Ten redundancy questions to ask before you trust a supplier with a live broadcast

Below are the questions worth asking at the planning meeting, before contracts are signed, along with what a good answer sounds like and what a weak one sounds like.

1. What is your connectivity redundancy?

A good answer names two independent paths to the internet, typically a wired line at the venue plus a bonded mobile backup running on a different mobile carrier, so a single point of failure cannot take out both. A weak answer is "we use the venue's wifi" or a single mobile dongle with no second path.

2. Has that redundancy actually been tested under load?

A good answer describes testing the failover with the stream actually running and other traffic on the network, not in an empty room the day before with nothing else competing for bandwidth. A weak answer assumes it will work because it worked once, somewhere, at some point.

3. What happens if you lose power?

A good answer covers battery backup for the critical path, meaning the encoder, the switcher and the key cameras, long enough to bridge a short outage, plus a plan for a longer one. A weak answer has no answer, because nobody has asked the venue about its power set-up in advance.

4. Is there a local recording, captured separately from the encoder?

A good answer confirms that the event is being recorded to a local device independently of the stream, so that if the live feed drops, the footage itself is not lost and a full recording still exists afterwards. A weak answer treats the live stream as the only copy.

5. Do you carry spare cameras and cables?

A good answer is a straightforward yes, with spares that are actually on site, not back at the office or something that can be sent over mid-event. A weak answer is a single camera per angle with no backup body.

6. What is your comms set-up between crew?

A good answer describes a proper intercom or comms system linking camera operators, the vision mixer and whoever is running the stream, so a problem can be flagged and fixed without anyone needing to shout across a room. A weak answer relies on text messages or hoping someone notices.

7. Who is actually watching the outgoing signal?

This is a subtler point than it sounds. A good answer confirms that someone is monitoring what viewers are actually receiving, not just the encoder's own dashboard, because an encoder can report everything as healthy while the platform on the other end is dropping frames or has stalled entirely. A weak answer only checks the encoder.

8. What exactly is the documented failover process?

A good answer is specific about which system takes over, how the switch is triggered, and how long it takes. A weak answer is "we'd sort it out" with no written process behind it.

9. What is your insurance and liability position?

A good answer confirms appropriate public liability and professional indemnity cover, and is willing to share the relevant detail. A weak answer treats the question as an inconvenience rather than a normal part of commissioning a supplier for a high stakes broadcast.

10. Who makes the call to cut to a holding card, and how fast?

A good answer names a specific role on the crew with the authority to make that decision without waiting for sign off from someone not in the room, and describes what viewers see and hear while a fix is made. A weak answer has nobody clearly responsible, which usually means the decision gets made too late.

• Ask about connectivity redundancy and how it has been tested
• Confirm power backup for the critical broadcast path
• Check for a separate local recording, independent of the live encoder
• Ask about spare cameras, cables and crew comms
• Establish who monitors the outgoing signal, not just the encoder
• Get the failover process in writing, not as a verbal assurance
• Check insurance and liability cover
• Agree who has the authority to cut to a holding card and when

If nobody can tell you what happens in the first thirty seconds after something fails, you have not actually been given a redundancy plan.

None of this is about assuming the worst. Most corporate broadcasts run without incident. It is about the fact that a live audience, unlike an on-demand video, only gets one chance to see the moment as it happens, and a governance meeting, a product launch or a company-wide announcement is not the place to discover that redundancy was a word on a slide rather than a working system.

If you are commissioning a live broadcast and want to see our redundancy set-up in detail before you commit, send us your event date, venue and brief and we will walk you through exactly how it works.

← All twenty guides