When a ministry or a school calls about a livestream, the request is almost always for equipment. A better camera. A newer encoder. Something to fix the buffering during the part that matters.
The equipment is rarely the cause.
Three things that actually break streams
Signal flow nobody wrote down. Equipment gets added a piece at a time over several years, by several different people, each solving that week’s problem. Nothing is documented. When something fails, troubleshooting starts from zero — usually eleven minutes before service.
A network that was never asked. Streaming was added to a network designed for the office. Upload capacity, switching, and the wireless it competes with were never evaluated together.
One person holding all of it. The system works because a single volunteer knows the sequence by memory. That is not a media team; it is a single point of failure with a family and a day job.
What we do instead
We document signal flow as a deliverable, not a courtesy. We evaluate network readiness alongside AV rather than after it. And we train to the least technical person who will ever have to run the service — because turnover is a certainty, not an exception.
The test
A system is finished when the person who did not attend the install can run it on a Sunday when you are not there. Until then, it is equipment.