The six things that break a corporate livestream
Bandwidth, audio, the venue's promises, remote presenters, redundancy, and the run of show. What actually goes wrong on event day and how to plan around it.
Corporate livestreams do not usually fail dramatically. They fail quietly, in a way where the event feels fine in the room and the remote audience has a bad hour and never says anything.
Six things cause almost all of it. In rough order of how often they bite.
1. The venue's internet is not what the venue said
This is the most common one and it is not close.
The number a venue quotes is the number on their circuit, measured at 3am, not the number you get in the ballroom at 2pm with four hundred phones camped on the same access points. "Dedicated" often turns out to mean a VLAN on the guest network. "Hardwired" sometimes means there is a jack in the wall that nobody has tested since the building opened.
The fix is boring: test it yourself during a site survey, with your own encoder, at roughly the time of day the event runs. Then bring a bonded cellular uplink anyway. On corporate campuses we now default to bringing our own connection as the primary rather than the backup, because getting IT to open outbound ports on the day of an event is not a plan.
2. Audio
Viewers forgive a soft picture. They will not sit through bad sound, and here is the part that makes it dangerous: they do not complain. They just leave, and your view count looks like a retention problem when it is an audio problem.
A room mic at the back of a ballroom picks up HVAC, chairs, the coffee service in the hallway, and a speaker who is thirty feet away. What you want is either lavaliers on the presenters or a clean board feed off the house system, mixed by somebody who is listening.
If you take one thing from this: get the audio right and you can be forgiven almost everything else.
3. Nobody is watching the stream
An encoder can be publishing a black frame, or frozen video, or audio with no picture, while the room looks completely normal. The production is going great. The stream has been dead for twenty minutes.
The only way anyone finds out is a viewer emailing someone in the room, which takes a while, and by then you have lost the audience.
Somebody has to be looking at the actual outbound stream, on a separate device, on a separate network, for the whole event. It feels like a waste of a person until the first time it saves you.
4. Remote presenters were an afterthought
Bringing someone in over Zoom or Teams is easy. Bringing them in so they look like part of the broadcast is a pipeline.
Without it you get a presenter who is lit by their laptop, framed from the chin up, out of sync with their own audio by half a second, in front of a kitchen. Next to an in-room speaker shot on a broadcast camera, the contrast is brutal, and the remote person reads as less important than the people in the room. Which is usually the opposite of the intent, because the remote person is frequently the CEO.
Handle it in advance: a tech check with each remote speaker on the actual device they will use, on the actual connection, at least a few days out. Not the morning of. You want time to ship someone a webcam and a light if it comes to that.
5. No redundancy anywhere
One encoder. One internet connection. One recording. Any single failure takes the whole event.
Redundancy is invisible when things go well, which is exactly why it is the first line cut from a budget. A second encoder running in parallel, a bonded cellular uplink alongside the hardwired, and a local recording that keeps rolling regardless of what the stream is doing. That local recording has saved more corporate events than any other single item on the list, because it means a failed stream becomes a delayed video rather than a lost one.
6. The run of show does not exist
Not the agenda. The run of show: who is on camera at what minute, when the deck goes full screen, when the video roll happens, who cues it, what the lower third says and how their name is spelled.
Without one, the director is guessing in real time. You get late cuts, missed graphics, and the wrong name on screen for the general counsel. With one, a four-camera show runs itself.
Write it down. Send it to the crew the day before. Then walk it once in the room before doors.
The pattern
Look at the list and notice that five of six are planning failures, not equipment failures. The cameras almost never let you down.
That is the argument for treating a livestream as a production rather than a service you order. The equipment is the easy part and it is what everybody quotes on. The site survey, the tech checks, the run of show, and the person watching the outbound stream are what actually decide whether the remote audience had a good hour.
If you are planning something and want a second set of eyes on the plan, send us the details. Even if we are not the right fit, we will tell you what we would check.
Anthony Valentine
Founder and Executive Producer, AVP.Live
Anthony runs live production for AVP.Live out of Freehold, New Jersey. He has produced multi-camera corporate broadcasts, memorial livestreams, and sports pay-per-view events across New Jersey, New York City, and Philadelphia, and holds an FAA Part 107 remote pilot certificate.