Multisite Church AV: How to Run Production Across Campuses Without Losing Your Mind

You built a solid production workflow at your main campus. The ATEM is dialed in, volunteers know the routine, and Sundays run smooth. Then leadership tells you to replicate it at a second location — with half the budget and zero additional staff. Sound familiar?

Managing AV across multiple church campuses is one of the hardest scaling problems in church tech. This guide covers how to standardize your gear, train remote volunteers, and keep every campus running reliably — even when you can't physically be there.

The Quick Win: Standardize Your Equipment

The single highest-leverage thing you can do for multisite AV is use the same gear at every campus. Not similar gear. The same gear.

When your main campus runs an ATEM Mini Pro and your second campus has a Roland V-1HD, every troubleshooting call becomes a translation exercise. Your volunteer at campus B says "the effects button isn't working" and you're Googling a switcher you've never touched while simultaneously running your own service.

• Same video switcher — If ATEM Mini Pro works at your main campus, buy another one. Don't "save money" with a different brand. The money you save on gear you'll spend ten times over in training and troubleshooting.
• Same streaming software — If main campus uses OBS, every campus uses OBS. Same scenes, same profiles. Export your OBS profile and import it at the new site.
• Same network layout — Use the same IP scheme at every campus. ATEM is always 192.168.1.10. Encoder is always 192.168.1.30. A volunteer who knows campus A's network already knows campus B's.
• Same cable labels — Use the same naming convention. "CAM1-HDMI" is "CAM1-HDMI" everywhere. When a volunteer texts you "CAM1 is down," you know exactly which cable to check regardless of location.

The goal isn't identical rooms — it's interchangeable knowledge. A volunteer trained at one campus should be able to walk into any other campus and operate without retraining.

Build a Gear Standard Document

Before you buy a single piece of equipment for a new campus, write down your standard. This document becomes the blueprint for every future expansion:

1. Video switcher — Model, firmware version, saved settings
2. Camera(s) — Model, mount type, preset positions
3. Streaming software — Application, version, exportable profile
4. Audio interface — Model, routing from soundboard
5. Network switch — Model, port assignments, IP plan
6. Computer specs — Minimum CPU, RAM, GPU for your streaming workload
7. Cable inventory — Types, lengths, labeling convention

Keep this in a shared Google Doc or Notion page. When you open a third campus, you hand this document to whoever is setting up the room and they order the exact same list. No guessing, no "creative substitutions."

Training Volunteers You Can't Stand Next To

At your main campus, you trained volunteers by standing behind them during service. At a second campus 20 minutes away, that's not an option. You need a training system that works without you in the room.

Create a Runbook, Not a Manual

A manual explains how things work. A runbook tells someone exactly what to do, step by step, in order. Write your runbook as a checklist:

• 30 minutes before service — Power on switcher, boot streaming computer, open OBS, verify stream key, test audio input
• 15 minutes before — Frame cameras on presets, check audio levels, start a test stream for 30 seconds
• Service start — Go live, monitor audio levels, switch cameras per the shot list
• Service end — Stop stream, stop recording, save files, power down in order
• If something breaks — Decision tree: "Is it audio? Go to page 3. Is the stream down? Go to page 4."

Post the laminated runbook next to the console. Every campus gets the same runbook because every campus has the same gear.

Video Walkthroughs Over Written Docs

Record a 10-minute screen share of yourself running through the Sunday workflow. Volunteers will watch a video five times before they read a document once. Host it on a private YouTube playlist or Google Drive folder your team can access.

Shadow Shifts Still Work — Cross-Campus

Send new campus B volunteers to shadow at campus A for two Sundays before their campus goes live. They learn the workflow in person, then execute it on identical equipment at their own location. This builds confidence and creates a personal connection between the teams.

The Real Problem: You Can't Be Everywhere on Sunday

This is the part nobody talks about in the multisite playbook. You're one person. Service starts at the same time at both campuses. When something goes wrong at the campus you're not at, your options are:

1. Hope the volunteer can figure it out from the runbook
2. Take a panicked phone call while you're running your own service
3. Find out after service that the stream was down for 40 minutes

None of these are acceptable — but they're what most multisite churches live with until they solve the monitoring problem.

Remote Monitoring for Multisite Church AV

Tally was built for exactly this scenario. Every campus runs the Tally app on its streaming computer. You see every campus on one dashboard — from your phone, from the booth, from wherever you are:

• Per-campus status — See if each campus's ATEM, encoder, audio, and stream are healthy. Green means good. Red means something needs attention right now.
• Instant alerts — If campus B's stream drops, you get a Telegram notification within seconds — even while you're running production at campus A.
• Auto-recovery — If the stream drops, Tally restarts it automatically. Most of the time the problem is resolved before the volunteer even realizes it happened.
• Pre-service checks — 30 minutes before every service, Tally verifies every device at every campus. You get one summary: "Campus A: all green. Campus B: ATEM offline." Now you have time to call someone.
• Remote control — Switch cameras, start/stop streams, and trigger macros at any campus from Telegram. You don't need to be physically present to fix things.

Think about what this means for your Sunday: instead of hoping both campuses are fine, you know both campuses are fine. And when something goes wrong, you know about it in seconds — not after the service when a volunteer apologetically mentions the stream was down.

Campus Launch Checklist

When you're ready to bring a new campus online, here's the order of operations:

1. Order standard gear — Use your gear standard document. Identical equipment, no substitutions.
2. Set up the network first — Install the AV switch, assign static IPs matching your standard scheme. See our network setup guide for details.
3. Clone your streaming config — Export OBS profiles, ATEM macros, and camera presets from your main campus. Import at the new site.
4. Install Tally — Connect the new campus to Tally so it shows up on your dashboard alongside your other locations.
5. Send volunteers to shadow — Two Sundays at the main campus before the new campus goes live.
6. Soft launch — Run one or two services as a test. Stream to an unlisted YouTube link. Fix issues before you're live to the congregation.
7. Go live with monitoring — First real Sunday. You watch both campuses from one dashboard. Breathe.

FAQ

Do I need a tech director at every campus?

Not necessarily. What you need is at least one trained volunteer per campus who can follow the runbook and escalate problems. With remote monitoring and auto-recovery handling the most common failures, a well-trained volunteer can run production without a dedicated TD on-site. The TD's role shifts from hands-on operator to remote overseer across all locations.

Should each campus stream independently or simulcast?

It depends on your model. If each campus has its own worship and preaching, they stream independently. If you simulcast the sermon from your main campus, the satellite campuses receive the feed and may only need a simpler production setup (one camera, simpler switching). Either way, standardize the gear that each campus operates.

How much does it cost to set up a second campus for streaming?

A solid multisite streaming kit — ATEM Mini Pro, one PTZ camera, a streaming computer, audio interface, network switch, and cabling — runs roughly $2,000–$3,500 depending on camera choice. Add Tally monitoring for visibility across all your campuses. The biggest hidden cost isn't gear — it's the time you'll spend troubleshooting remote problems without proper monitoring.

Start Building Your Multisite Playbook

Multisite AV doesn't have to be chaos. Standardize the gear, document the workflow, train volunteers with repeatable systems, and monitor everything from one place. The churches that do this well aren't the ones with the biggest budgets — they're the ones with the best systems.

Start a free trial of Tally and see every campus on one dashboard. Setup takes about 10 minutes per location.