Most church A/V volunteer training programs do not work. They produce volunteers who know how to use the gear under normal conditions but cannot recover when something goes wrong. The reason is almost always the same: the training is about the equipment, not the workflow.
Why Most Volunteer Training Fails
Training on gear teaches a volunteer what each button does. Training on workflow teaches them what to do in order, what good looks like at each step, and what to check when something does not look right.
Gear-focused training sounds like: “This is the gain knob. Turn it up to make the microphone louder.”
Workflow-focused training sounds like: “When you bring up a new channel, start by setting the gain structure. Here is the level you are aiming for on the input meter. Here is how you know if you are too hot or too low. Here is what you do if the level is wrong before you ever touch the fader.”
The difference is whether the volunteer understands what they are trying to achieve at each step, not just which knob to turn.
The Difference Between Training on Gear vs. Training on Workflow
A volunteer who was trained on gear can operate the system when it works exactly the way it did during training. The moment something is different — a cable is plugged into a different input, a microphone is not responding, the monitor mix is wrong — they are lost.
A volunteer trained on workflow knows what the system is supposed to do at each stage and can diagnose where the chain is broken. They know that if a microphone is not working, they should check the gain, the phantom power, the cable, and the channel assignment before assuming the mic is broken.
The goal of volunteer training is not a volunteer who can operate the console. It is a volunteer who can operate the console and recover from the most common failure modes without calling for help.
How to Document a System So Volunteers Can Self-Recover
Every church audio system should have a document that describes:
- The signal flow from each input to each output, in plain language
- Where each physical cable goes and what it is connected to on both ends
- The normal operating settings for the console (gain, EQ, monitor sends)
- The most common problems and their first-step fixes
- Who to call if the problem cannot be fixed
This document does not need to be long. It needs to be accurate and accessible — printed at the mix position, not stored on someone’s laptop.
If a volunteer cannot find the information they need in under two minutes during a service, the documentation is not useful.
What a Sunday Runbook Should Contain
A Sunday runbook is a step-by-step checklist for opening, running, and closing the audio system for a service. It should be brief enough to actually be used, specific enough to be actionable.
A basic runbook covers:
- Power-on sequence (order matters to avoid pops and speaker damage)
- Scene recall and verification
- Wireless mic checks: battery status, frequency, gain
- Monitor check with each musician or speaker
- Recording or stream verification
- Post-service shutdown sequence
The runbook is not a manual. It is a checklist. Every step should be something the volunteer can verify in under 30 seconds.
When to Bring In Outside Help for Training
Bring in outside help when the system itself is poorly documented or poorly designed and volunteers are being set up to fail. No amount of training makes an unclear signal flow easier to operate.
Bring in outside help when you have a new system that none of your volunteers have used before. An initial training session from someone who knows the equipment saves significant time compared to learning from the manual.
Bring in outside help when the same problems keep happening despite training. Recurring problems are usually system problems — routing that does not make sense, gain structure that was never set correctly — not operator problems.
Heavenly AVI offers remote support and training for church A/V teams.