It usually happens on a Tuesday. A text, an email, a quiet word after the service: the person who has run sound for three years is moving, or burned out, or just done. Nobody is angry. Nobody did anything wrong. But Sunday is five days away, and the one person who knew which channel the pastor's mic lives on, how loud the room can run before it starts to feed back, and which cable in the closet is the flaky one — that person is no longer coming.
This is not really a story about sound. It is a story about what happens when a whole function of church life sits inside one head. A church can lose a greeter and barely feel it. It cannot lose its only sound tech without every single person in the room noticing, immediately, out loud.
The job was never one job
What looks like “running sound” is actually a stack of small, specific decisions made over months or years: the gain on each channel, the order to power things on in, which monitor mix the worship leader likes, the workaround for the wireless mic that drops out near the back wall. None of that is written anywhere. It lives in one person's hands and habits. When they leave, it does not get handed off — it simply stops existing, and whoever steps in has to rediscover all of it, usually live, usually on a Sunday morning.
Why this role in particular breaks loudly
Every small church runs on volunteers doing more than one person's share, and most of those single points of failure fail quietly. The treasurer who is the only one who understands the books. The one small group leader who has been running the same group for six years. Those gaps show up slowly, as a program that fades or a task that gets missed.
Sound is different because the failure is public and immediate. A treasurer's absence can go unnoticed for a month. A missing sound tech is noticed by two hundred people the second the sermon starts and the pastor's voice cuts out, or the band is too loud, or the mic feeds back through the monitors. There is no quiet version of this gap. That is exactly why it deserves attention before it happens rather than after.
The Sunday after they leave
Most churches respond to the gap the same way: someone willing but untrained steps up under pressure, on a live mic, in front of the whole room. Sometimes it goes fine. Often there is feedback, a dropped wireless mic, a sermon nobody in the back three rows can quite hear. None of that is a reflection on the volunteer who stepped in — it is what happens when knowledge that lived in one person's head has to be reinvented under pressure with an audience watching.
The deeper cost is what it does to whoever steps in next. A rough first Sunday, done alone, with everyone watching, is a fast way to talk someone out of ever trying the booth again. The volunteer who might have become your second sound tech quietly decides it is not worth the risk of embarrassment, and the single point of failure stays exactly as narrow as it was.
Two people who can run it alone, not one plus a helper
The fix is not a bigger team. It is a second person who can run a full service start to finish without the first person in the room. A helper who has only ever assisted is not a backup — they are still one unplanned absence away from the same crisis. The target for a church of 60 to 250 is two people who can each run sound alone, and ideally a third who is partway there. That third person matters more than it sounds: without them, your backup becomes the new single point of failure the moment they take a vacation.
Getting there rarely means recruiting a stranger with audio experience. It usually means noticing who already fiddles with settings on their own gear, or which teenager is comfortable behind a soundboard-shaped interface, and asking them something much smaller than “can you run sound.” “Come sit next to Dave this Sunday and just watch” gets a yes far more often than an open-ended ask for a new volunteer role. This is the same widening of the base that matters for any serving team that is quietly resting on too few people.
Write down what is in one person's head, before they leave
The best time to document the sound booth is while the person who knows it is still around to be asked questions. A one-page checklist — power-on order, where levels usually sit, what to do first if feedback starts — is more useful than it sounds, because it turns a crisis into a procedure. A five-minute phone video of an actual Sunday setup covers what is hard to write down: where a hand goes, what a loose cable connection looks like before it fails. Neither needs to be polished. It only needs to exist before the gap opens, not after.
This is worth doing for every role that lives in one person's memory, not only sound. The same instinct — write it down while the person who knows it is still here — is behind getting a church's records out of one person's spreadsheet and into something anyone can open.
Seeing the gap before it opens
A church that only thinks about its sound team when the booth goes empty will keep having this Tuesday. A church that can look at its serving teams and see, at a glance, who is the only trained person in a role — not just for sound, for anything — can start recruiting a second person months before the first one burns out or moves. SundayBridge keeps roles and assignments in one view, so a role with exactly one name against it is visible instead of invisible until the day it is empty.
What it cannot do is have the conversation, or record the training video, or sit next to the new volunteer on their first live Sunday. That part is still on the people. Once you can see who is scheduled and who isn't backed up, the same discipline that fixes the sound booth applies to scheduling any team that is really the same few people every week.
The interview questions worth asking before someone leaves
Exit conversations in a small church tend to focus on gratitude, which is right and good, but they skip a practical opportunity. Before your sound tech's last Sunday, sit down with three questions: what do you check first every week that nobody told you to check, what has gone wrong before and how did you fix it, and what would you want the next person to know that you never got asked. The answers are rarely dramatic. They are things like “the wireless pack on channel four eats batteries fast” or “the drummer's in-ear mix always needs to come down after the second song.” Small facts, but they are exactly the facts a new volunteer has no way to guess.
The same three questions are worth asking of any volunteer in a role nobody else can currently do — the treasurer, the one group leader who has run the same group for years, whoever holds the keys to the building. A departure is uncomfortable to plan for in advance. It is far less uncomfortable than losing the knowledge along with the person.
None of this needs a form or a formal process. A leader can ask the three questions over coffee, jot the answers on a phone, and hand the note to whoever ends up in the booth next. The point is not thoroughness. The point is that the answers exist somewhere other than one person's memory, so the next Tuesday text does not also cost the church a bad Sunday.
What to do this month, not just this Sunday
If your booth still has two trained people, use this month to find and start training a third — not because two is unsafe, but because two with no one behind them is one departure away from being one again. If your booth has one person right now, the honest move is to say so out loud this Sunday, to the whole church if needed, and ask for a name. It is an uncomfortable ask. It is far more comfortable than the Sunday the mic goes silent and there is no one in the room who knows why.