PRACTICAL OPERATOR GUIDE

Church sound team
training & handoffs.

Use this free web guide to build a checklist for your church’s sound system. It is general guidance, not instructions for your specific system. For instructions written around your room, equipment and saved settings, ask about system documentation and operator training.

Train operators on your own system.

A channel controls a source, a bus combines signals for a destination, and a scene stores a set of mixer settings.

  1. Trace the signal path. Follow one microphone from the stage input through the preamp, channel, buses and outputs. Identify which controls affect the room, monitors and livestream.
  2. Start from a known scene. Keep a protected starting scene and document how to recall it. Mute outputs before making patch changes and follow the system’s documented power sequence.
  3. Check inputs one at a time. Confirm labels, gain, routing and monitor sends before balancing the full band. Use a short spoken-word check as well as music.
  4. Listen to the broadcast separately. A livestream needs its own listening check. Room microphones and acoustic instruments reach the audience differently from the stream; document the broadcast bus and its level controls.
  5. Practice the handoff. Have another volunteer follow the checklist without coaching. Update unclear steps and record approved changes after rehearsal.

Leave a clear handoff for the next engineer.

  • Startup and shutdown: power order, safe output levels, scene name and the location of the reference copy.
  • Input patch: stage socket, console channel, source, phantom-power requirements and the matching physical label.
  • Outputs: main PA, monitor mixes, assisted listening and livestream destinations, with clear ownership of each level.
  • Visiting engineers: a current patch, system overview, access instructions and a contact for questions. Note which settings must remain unchanged.
  • Troubleshooting: a short signal-path check for a missing source, with the last known working scene and a recovery procedure.

Keep the guide beside the console and date revisions. Use labels and screenshots from your own system so the next operator can follow it.

For an engineer to cover services while volunteers learn, explore church service coverage. For a guide written for your actual room and console, explore system documentation and operator handoff.

Plan training for your team