What to Do When the Tech Person Quits With No Notice

It's rarely a clean resignation. Usually it's a text message, or a conversation after service that starts with "I need to talk to you about something," or the person just quietly stops showing up. Whatever the form, the result is the same: the one person who knew where the show file lived, which input the pastor's mic was patched into, and how to fix the thing that breaks every third week is suddenly gone, and Sunday is still coming whether the team is ready or not.

First, get through this Sunday, don't try to solve the whole problem by Saturday night

The instinct is to panic-recruit a permanent replacement in four days. Don't. That's a recipe for putting an unprepared person in a high-pressure seat and burning them out before they've even started. Instead, figure out the minimum viable service: what absolutely has to work (mic on the pastor, lyrics on the screen, livestream if that's a weekly commitment) versus what can be simplified or dropped for a few weeks (fancy camera cuts, a full lighting cue list, multi-platform streaming). A simpler service that runs smoothly beats an ambitious one that falls apart mid-song.

Find out what's actually in that person's head, while you still can

If there's any window at all where the departing volunteer is still reachable, even briefly, get as much out of their head as possible: where show files and presets live, what quirks the gear has that aren't written down anywhere ("the wireless mic on channel 3 drops if it's within ten feet of the router"), login credentials for streaming platforms and ProPresenter accounts, and who else has touched the booth before, even casually. This conversation is uncomfortable to have quickly, but it's far better than trying to reverse-engineer three years of undocumented tribal knowledge from scratch.

Look for the person who's already halfway there

Most churches have someone who's helped occasionally, filled in once, or hovered near the booth out of curiosity, even if they've never been "the" tech person. That person is worth more right now than someone brand new, because they already have some context, even if it's thin. Ask around specifically, don't just wait for a volunteer sign-up sheet to fill itself, because the person most capable of stepping in is often the last one to assume they're qualified to.

This is exactly the scenario cross-training exists to prevent, so build it now even though it's late

If your church had one single person who knew how everything worked, that's the actual root problem, not the fact that they left. People leave. Churches move, families relocate, life circumstances change, and a volunteer team built around one irreplaceable person is a team one phone call away from this exact situation happening again. The fix isn't finding a new single point of failure to replace the old one, it's making sure at least two or three people can run sound, run ProPresenter, and handle basic livestream troubleshooting, even if none of them are the expert.

Start documenting as you rebuild. A simple run sheet, a labeled patch list, a one-page "if this breaks, try this" cheat sheet taped inside the booth. None of this has to be elaborate. It just has to exist somewhere other than one person's memory.

Don't let this become a bigger spiral than it needs to be

A tech gap left unaddressed doesn't stay contained to tech. A rough few Sundays creates frustration, which makes the remaining volunteers less likely to stick around, which makes the gap worse, which creates more frustration. Naming the situation honestly to the team, "we lost someone unexpectedly, here's the plan for the next few weeks," does more to keep people calm and engaged than pretending everything's fine while scrambling behind the scenes.

The real lesson isn't "vet volunteers better"

It's tempting to treat a sudden departure as a hiring or commitment problem. Sometimes it is, but often it's just life happening to a volunteer, the same as it happens to anyone. The actual lesson is structural: build a team where no single absence, planned or sudden, can take the whole system down with it. That's not a one-time fix, it's an ongoing habit of cross-training and documentation that pays off exactly on the week you hoped you'd never need it.

If this happened and it feels like scrambling, that's the normal response to a genuinely hard situation, not a sign of poor leadership. Follow along for more real-world volunteer team tips, or grab the free Sunday Checklist so whoever's running the booth this week has a clear list to follow instead of guessing. See also: why tech teams burn out and training a new volunteer fast.