A digital mixer can hold hundreds of decisions, and most church sound problems trace back to those decisions being made differently by every person who sits behind the desk. A consistent setup turns a powerful console into a predictable one. This guide lays out the exact framework The Penn Group uses when commissioning consoles for houses of worship, from the first input list to the last locked scene.
Key Takeaways
- Plan the console on paper first: input list, output list, bus plan, and control plan.
- Lock a fixed channel order and one color legend across every console in the building.
- Build a service layer of eight to twelve faders so volunteers never hunt for channels.
- Start every scene from a protected master template and back up show files weekly.
Start on Paper, Not on the Console
The most common setup mistake happens before a single cable is patched: the team starts pressing buttons without a plan. Every well-organized console begins as a spreadsheet with four documents.
- Input list. Every source on stage, numbered, with microphone or DI type, stage box port, and whether phantom power is required.
- Output list. Every destination: main left and right, subwoofers, front fills, monitor wedges, in-ear mixes, livestream feed, lobby, and recording.
- Bus plan. Which mixes are pre-fader monitor sends, which are post-fader effects sends, and which are groups.
- Control plan. Which faders, DCAs, and SoftKeys a volunteer will touch during a normal service, and which settings should never move.
Print the input list and tape a copy at front of house and at the stage box. When the paper, the patch, and the console agree, troubleshooting takes minutes instead of an entire rehearsal.
Build a Channel Order That Never Changes
The single best habit for any church console is a fixed channel order that stays the same week after week, even when the band changes. Musicians rotate. The console layout should not. A proven order for a contemporary worship setup runs from the back of the stage forward and from low to high:
| Channel Block | Sources | Typical Color |
|---|---|---|
| 1 to 8 | Kick in, kick out, snare top, snare bottom, hi-hat, toms, overheads | Red |
| 9 to 12 | Bass DI, bass mic, keys left and right | Orange |
| 13 to 18 | Electric guitars, acoustic guitars, auxiliary instruments | Yellow |
| 19 to 24 | Worship leader vocal, background vocals | Green |
| 25 to 28 | Pastor headset, handheld spares, lectern | Blue |
| 29 to 32 | Playback, tracks, click, video audio, ambient room mics | Purple |
Leave unused channels in place rather than closing the gaps. A permanently empty channel 17 is far less confusing than a guitar that moves to a new fader every month.
Name Channels for the Role, Not the Person
Label a channel “WL Vox” or “BGV 1” rather than with a volunteer’s name. Names change; roles stay consistent. The exception is the pastor channel, where a clear label such as “Pastor HS” prevents the most expensive mistake on a Sunday morning: a muted sermon.
Use Color as a Language
Color coding works only when the colors mean the same thing on every console in the building. Choose one palette and publish the legend at every mix position: drums red, bass and keys orange, guitars yellow, vocals green, spoken word blue, playback purple, effects returns white. Allen & Heath consoles such as the Qu-6 and the SQ Series carry those colors onto channel displays and meters, so a volunteer can find the vocals from across the room.
Design Fader Layers Around the Service, Not the Stage
Input channels belong on one layer. The faders a volunteer actually rides during a service belong on another. The Penn Group typically builds a “Service” custom layer that holds exactly what a typical Sunday requires:
- Pastor headset and backup handheld
- Worship leader vocal
- A DCA for background vocals
- A DCA for the band
- A DCA for drums
- Playback and video audio
- Reverb and delay returns
- Main mix master
The result is a console that a newer volunteer can run from eight faders, while an experienced engineer can still flip to the full input layers for detail work. Modern Allen & Heath Qu models support customizable channel strip layers precisely for this approach.
Structure Buses and DCAs With Intention
Monitor Mixes
Set monitor and in-ear sends to pre-fader so a change in the house mix never shifts what a musician hears. Name each mix after the position (“Drum IEM”, “Keys Wedge”) and keep the same bus number for each position permanently. When a personal mixing system is in use, route a consistent set of stems rather than every channel. Sixteen well-chosen stems create less confusion on stage than forty raw inputs.
Effects
Two reverbs and one delay cover nearly every worship service: a short plate or room for drums, a larger hall for vocals, and a tempo-synced delay for moments of emphasis. Send to effects post-fader so effect levels follow the channel faders.
DCAs Over Groups for Most Churches
DCAs control levels without passing audio, which keeps processing simple and avoids latency or phase surprises. Reserve audio subgroups for situations that genuinely need shared processing, such as compressing all background vocals together. A clean worship layout usually lands at six to eight DCAs: drums, bass and keys, guitars, BGVs, lead vocal, spoken word, playback, and effects.
Set Gain Structure Once, Then Protect the Settings
Gain staging is the foundation every other setting relies on. During soundcheck, have each musician play at performance volume, not warm-up volume, and set preamp gain so peaks land comfortably below clipping with headroom to spare. A good working target on most digital consoles is peaks around the upper yellow section of the meter, leaving roughly 10 to 15 dB of room above.
Once gains are set, a volunteer should rarely touch the gain controls. Faders handle the mix. Gain handles the input. When those two jobs blur, feedback and distorted vocals follow.
Build Scenes as Templates, Not Snapshots
A scene library should start from one master template. That template holds the complete patch, names, colors, gains for the regular band, EQ starting points, monitor routing, and effects. Every other scene inherits from that template.
| Scene | Purpose |
|---|---|
| 00 Master Template | Locked reference. Never used live, never overwritten without approval. |
| 01 Sunday Full Band | Standard weekend service. |
| 02 Sunday Acoustic | Reduced band, drums muted and hidden. |
| 03 Spoken Word Only | Midweek meetings, funerals, and classes. |
| 04 Special Event | Christmas, Easter, and guest artists. |
| 99 Safe Reset | Known-good fallback when something goes wrong. |
Use recall filters, sometimes called recall safes, to protect settings that should never change when a scene loads. Main output EQ and system processing almost always belong in that safe list, so a scene recall cannot accidentally undo the tuning of the room.
Back Up Everything, Off the Console
Export show files to a USB drive and to a shared cloud folder after every significant change. Date the file names. A console failure should cost a church a few minutes of reloading, never a rebuilt mix from memory.
Lock Down Permissions for Volunteers
Most professional digital consoles offer user profiles with restricted access. Create at least two:
- Admin. Full access for the technical director or integrator.
- Volunteer. Access to faders, mutes, the service layer, and scene recall, with patching, system EQ, and output processing locked.
Permissions are not a statement about trust. Permissions protect volunteers from the stress of accidentally breaking a system minutes before a service.
Plan for Recording and the Livestream From Day One
The most reliable stream feed starts from the main mix. Route the main left and right into a matrix dedicated to the stream, blend in ambient room microphones to carry congregational singing, and add stream-only processing on that matrix: gentle EQ, compression, and a limiter set just below clipping. The stream then follows every decision the front-of-house engineer makes, with no separate mix for a volunteer to forget during transitions. The Penn Group explains the method in 3 things that improve a live stream for free. Most current consoles record multitrack directly to SD card or over USB, which allows a team to rehearse virtual soundchecks on Tuesday using Sunday’s real performance.
Document the System and Train to the Document
Finish every setup with a one-page quick start sheet placed at the mix position:
- Power-on order for the console, stage box, and amplifiers.
- Which scene to load for each service type.
- Where the pastor fader lives and how to unmute the main mix.
- What to do when a microphone fails.
- Who to call, with a phone number.
Training sessions then teach the sheet, not the entire console. Volunteers gain confidence fast when the job is defined, and technical directors spend Sundays leading teams instead of fixing settings.
Quick Setup Checklist
- Input list, output list, bus plan, and control plan documented
- Fixed channel order with reserved empty channels
- One color legend used across every console in the building
- Custom service layer with eight to twelve faders
- Pre-fader monitor sends, post-fader effects sends
- Six to eight DCAs aligned to the service
- Gain staging set at performance volume
- Master template scene plus service-specific scenes
- Recall safes on system and output processing
- Dated show file backups off the console
- Volunteer user profile with restricted access
- Stream matrix fed from the main mix, with room mics and a limiter
- One-page quick start sheet at the mix position
Professional Console Commissioning From The Penn Group
The Penn Group is an authorized Allen & Heath dealer and authorized repair center that configures consoles for churches every week, from compact Qu systems to full dLive installations. Commissioning includes show file design, volunteer user profiles, scene libraries, training, and documentation tailored to the way each church actually runs a service.
The Penn Group
Plan the next upgrade with an integrator who services what gets installed.
Design, installation, volunteer training, and authorized service for churches and venues across Ohio and beyond.
Schedule a Free ConsultationFrequently Asked Questions
How long does a proper digital mixer setup take?
A complete commissioning for a typical worship console, including show file design, scene library, and volunteer training, generally takes one to two days on site plus planning time beforehand.
Should every service use the same scene?
Every service should start from the same master template, with separate scenes for different service formats. Any change to the master template should require approval from the technical director.
What is the difference between a DCA and a group?
A DCA adjusts the level of the channels assigned to the DCA without carrying any audio. A group combines audio from several channels into a new signal that can be processed and routed. Most church mixes benefit from DCAs for control and use groups sparingly.
How often should show files be backed up?
After any meaningful change, and at minimum once a week. Keep at least three dated versions so a team can roll back to a known good setup.