Case study · Central Church · 2026

Worship Center Audio System

I configured the entire audio system for Central Church's new 1,800-seat worship center. Construction delays squeezed the schedule, but leadership kept the opening date, and the room opened on that date with no glitches.

At a glance

RoleAudio Lead; I owned 100% of the system configuration
OrganizationCentral Church, Sioux Falls, SD (4,000–5,000 weekly attendance)
SpaceNew 1,800-seat worship center
TimelineSpring 2026 to grand opening, August 29–30, 2026
Scale120 console channels, about 50 networked audio devices, 10 connected subsystems
PartnerREACH (main speaker design, hanging and tuning)
OutcomeOpened on the fixed date with no glitches and strong feedback on the sound

The challenge

The new room had to work perfectly on its first weekend, with less setup time than planned. Construction ran late, but the August 29–30 grand opening held, so every day of delay came straight out of system setup and testing.

The system also had to serve many groups at once from one network:

  • The congregation hears the main mix in the room.
  • The band and worship leaders each control their own in-ear monitor mix.
  • The broadcast and recording teams get separate mixes for online services and archives.
  • Production staff talk on intercom, and can talk privately to the worship leader during a service.
  • The lobby and other spaces get their own feeds.

If one connection was wrong, a mic could go silent or a private talkback channel could reach the whole band. I had to get each one right, document it, and prove it matched the plan before the first full rehearsal on August 20.

My role

I owned the configuration of the entire system, from each microphone to every place its sound goes. REACH, an outside audio contractor, designed, hung and tuned the main speakers, and brought me into those decisions.

AreaWhat I did
Mixing consoleSet up the 120-channel console: inputs, labels, groups, mix buses and custom fader layouts
Stage I/OPlanned and labeled every stage box connection, down to the individual cable
WirelessPlanned 16 wireless mic channels and coordinated their frequencies
In-ear monitorsConfigured the 64-channel personal monitor system the band and leaders mix themselves
Building routingRouted audio to the lobby, video control and other rooms, and set what each space receives and how it's mixed
Broadcast and recordingDesigned the audio paths for the video router, recorders and a 62-channel multitrack recording rig
Intercom and talkbackDesigned two-level talkback so production can speak to the whole band or only the worship leader
NetworkDocumented and checked about 50 networked audio devices, including naming and which device keeps them in sync
DocumentationBuilt and maintained the master planning workbook everyone worked from

Approach: one master plan

I built one master planning workbook and made it the single source of truth. Everything was documented in it, and the console, network and install labels were checked against it. Its 12 linked tabs cover:

  • What we own: every audio device, with model, channel count, location and status, plus a naming registry for networked hardware
  • What comes in: all 120 console inputs, the 16 wireless channels and the physical stage box ports, mapped to each cable
  • Where it goes: 48 mix buses, 12 matrix outputs, monitor mixes, effects and output zones
  • Everything else: intercom, speaker processing, broadcast and video, recording, and background audio

Automation. Using AI-assisted tools, I wrote Python scripts that generate and update the tabs. When something changed, I updated the source data once and regenerated the affected tabs, which kept 12 tabs and about 1,000 rows consistent without retyping.

Key design decisions

  • Organized for the operator. The 120 channels sit in 10 banks of related sources, with spare slots where growth is most likely, so new gear has a home without renumbering.
  • Private talkback. Two talkback levels: one reaches every musician's in-ears, the other only the worship leader, so production can redirect a service without the whole band hearing.
  • Live and rehearsal modes. Two named network presets: LIVE runs from the stage mics; PLAYBACK runs from recorded tracks, so the team can rehearse and tune the mix with no band in the room.
  • One-button vocal changes. Saved scenes move whoever is leading into the lead vocal processing and fold everyone else into backing vocals with one press.
  • A reliable clock. The network follows one timing source: a stage box that stays powered 24/7, not the console, which gets shut down.

Verification: checking the plan against reality

I didn't assume the plan matched the installed system. I read the console's own show file and compared successive network backups device by device, then found and fixed six differences before opening weekend.

What I foundRisk if missedWhat I did
A network backup saved in rehearsal mode, with the console listening to recorded tracksRestoring it on a weekend would have silenced every live micCaught it before it was restored; set up named LIVE and PLAYBACK presets
In-ear feeds built on different mix buses than first plannedDocumentation would point techs to the wrong placesRebuilt the bus plan to match the console exactly
Private talkback on a different output than documentedMid-service troubleshooting would start in the wrong placeCorrected the docs and mapped network to console numbering
One stereo input patched to the same side twiceA silent right channel in the live mix and recordingsTraced the exact connections and fixed them in the re-patch
Intercom channels renamed and moved on the consoleLabels and documentation no longer matchedUpdated the input plan and console map
Two devices still set up for the temporary gym systemBroadcast talkback and the tracks computer would fail after the moveMoved them over during swap-over week, settings documented in advance

Results

The worship center opened on schedule on August 29–30, 2026, with no glitches and strongly positive feedback, including on the sound.

  • Met a fixed deadline through the August 20 mock rehearsal, the August 26 prayer service and opening weekend.
  • Caught problems early: six plan-versus-reality differences fixed before they could reach a live service.
  • Left a usable reference: staff can trace any signal from microphone to destination, and the scripts keep it current.

Documentation and training

Beyond the engineering workbook, I wrote guides so staff and volunteers run the system the same way every week, each written for the person who will use it:

  • Front of House Audio Guide (26 pages) for operators: gain structure, loudness targets measured with Smaart, tonal balance against an RTA target curve, EQ and compression, scenes and recall, a service-day checklist and troubleshooting. Each standard explains the reasoning, not just the number.
  • FOH computer assignments (1 page) for staff: which software runs where, the network plan, and a go/no-go checklist before buying a $499 plugin license.
  • In-ear mixing quick start (1 page) for band members: running your own mix from an iPad, tips, and who to call when something's wrong.
Cover and contents page of the Front of House Audio Guide
Front of House Audio Guide.
One-page FOH computer assignments sheet
FOH computer assignments.

Technical appendix

Signal flow: stage, wireless, video and intercom sources pass through a Dante network and DM7 console to speakers, in-ears, broadcast, recording and talkback
Every source joins the Dante network once; each system takes what it needs from there.
SubsystemHardwareRole
MixingYamaha DM7-EX120 inputs, 48 MIX, 12 Matrix, 24 DCAs, custom fader layers
Stage I/O3× Rio1608-D2, 1× Rio3224-D2Stage boxes; one is Dante Preferred Leader (powered 24/7)
WirelessShure Axient + QLXD via AD-TQ16 mic channels
In-ear monitorsKlang:vokal (64 ch) + Shure PSM12 stereo personal mixes from raw splits plus console stems
IntercomClear-Com Arcadia6 COM + 2 stage announce channels; two-tier talkback
LoudspeakersQ-SYS Core + NEXO amplifiersMains, subs, front fill, lobby and other zones
Video and broadcastRoss Ultrix + 2× AJA Ki Pro20 audio channels into the console; SDI embeds on the recorders
RecordingREAPER on Dante Virtual Soundcard62-channel multitrack and virtual soundcheck
PluginsWaves SoundGridFX processing with returns into the console