Multi-Campus Church AV

Not everything should be identical. These are the things to fix across campuses and the things to let vary with the room.

There are two models and they have very different requirements. Live simulcast sends the service from a broadcast campus to receiving sites in real time, which is technically demanding and unforgiving: an outage happens during the service and there is no recovery. Recorded delivery sends the message as a file to be played at each site, which is dramatically more robust and is what most multi-campus churches actually do for good reasons.

If you are sending live, plan the bandwidth honestly. A 1080p60 stream is about 6,800 kbps of video plus 160 of audio, which is roughly 6.96 Mbps. The working rule is that a stream needs about double its bitrate in measured upload, because the building also carries Wi-Fi, phones and the office, so the originating campus needs about 14 Mbps of genuine upload and will use about 3.1 GB per hour. A 1080p30 stream halves the video requirement to about 4.66 Mbps, needing roughly 9.3 Mbps of upload. Measure this on a wired connection at service time rather than trusting a plan figure, using the livestream bitrate calculator.

Whichever model you choose, audio is what viewers judge. A campus receiving a feed with poor audio will disengage regardless of picture quality, so take a dedicated mix from the console rather than camera microphones and build it for someone listening without the acoustic contribution of the originating room. That is covered at church livestream audio setup and how to mix for livestream.

The hardest problem in multi-campus AV is that faults happen where the expertise is not. Three things make remote support workable. Identical systems, so the person on the phone can visualise exactly what the volunteer is looking at. Thorough labelling, so both parties can name the same cable. And a saved default console scene that a volunteer can always recall to get back to a known working state, which resolves a substantial share of Sunday morning problems without any diagnosis at all.

Build a written fault card for each campus covering the five most likely problems and their first response: no sound from a microphone, feedback, the stream not starting, the projector showing no signal, and a wireless channel dropping. Most Sunday faults are one of those, and a volunteer with a card resolves them faster than a phone call would. Pair it with the routine at church sound checklist for Sunday.

Then build the maintenance rhythm, because multi-campus operations fail slowly rather than suddenly. Batteries, cable checks, lamp hours, firmware and a physical inspection at each site on a schedule, covered at church AV maintenance schedule. A central team that visits each campus on a rota catches the problems nobody reported because they had learned to work around them.

Multi-campus buying has one large advantage and one large trap. The advantage is volume: standardising means buying the same console, wireless and microphones repeatedly, which is worth a genuine conversation with a supplier and makes a shared spares pool viable. The trap is that campuses acquired at different times drift onto different equipment generations, and within a few years the standard exists only on paper.

Handle that by writing the standard down as a specification document and reviewing it deliberately rather than per project, and by planning replacement in waves so a campus is not left three generations behind. Each campus also needs its own annual operating budget for batteries, cable and replacement, at roughly 5 to 10 percent of system value. The framework is at building a church AV budget and the vendor questions at church sound system RFP questions.