A soundcheck can feel like a test with an audience. Musicians are waiting, someone is asking for more in a monitor, and a new operator is trying to remember where everything lives on the desk. I want the process to give that operator a way forward.
Confidence grows when the next step is clear and someone can explain why it matters. A simple, repeatable sequence is more useful than a fast demonstration that leaves a volunteer afraid to touch anything.
Explain the plan before asking for sound
Tell the team what you will check and in what order. Agree on a way to ask for monitor changes. Give the volunteer one manageable responsibility at a time: verifying inputs, making a rough vocal balance, or listening for the words in a chorus.
When coaching, I would rather ask, “What are you hearing?” than reach across someone and change three controls. If I need to intervene, I explain the reason and hand control back when the immediate problem is settled.
Separate the line check from the mix
First establish that each expected source reaches the expected channel. Check labels, patching, input level, and the routes you intend to use. Do not let a complete absence of signal become a ten-minute EQ experiment.
Work at controlled levels. Verify routing and mute states before opening unfamiliar channels, especially when they could feed stage monitors. A line check proves that a path works; it does not prove that a band sounds balanced.
Ask for a useful performance
Have people sing and play at a realistic level. For a vocalist, a few words of conversation may verify a connection, but a representative musical phrase is more useful for gain and monitor decisions. Explain the request kindly: you are trying to avoid making the team repeat the work once rehearsal begins.
After checking individual inputs, listen to a section with the full group. A source that sounds impressive alone can occupy too much space in the arrangement. Give the volunteer a listening goal: follow the lead vocal, hear the rhythm clearly, or notice whether the piano masks the words.
Make one change and listen again
Choose one issue, make a measured adjustment, and repeat the same passage when practical. Ask whether the change helped. That connection between hearing and action is the lesson.
Avoid teaching every feature of the console during one rehearsal. A volunteer who understands one successful decision has something to repeat next week. A volunteer who watches a blur of settings may only remember that the desk is complicated.
Finish with the handoffs
- Check speaking microphones with the people who will use them.
- Test playback through its intended route.
- Confirm monitor needs with the musicians.
- Check the stream or recording path separately if it is in use.
- Review mutes, transitions, and who owns the next cue.
Save the agreed starting point using the team’s normal scene or show-file process. Before recalling anything later, check recall scope and safe settings; a saved scene can change more than the fader positions you remember.
After rehearsal, ask two questions: what became easier, and what still feels uncertain? Keep the next practice goal small enough to act on.
A good soundcheck prepares the service and develops the person running it. The team should leave knowing what is ready, what still needs attention, and how to ask for help.