It is Thursday. The one person who knows how everything works just told you they are moving, or starting a job with Sunday hours, or that they are just done.
Sunday is in three days.
Nobody else knows the password to the streaming account. Nobody knows which cable goes where. There is a laptop backstage that only they ever touch.
I have watched churches lose their entire online presence in a single week over this, and never really get it back. So let me give you two things: what to do between now and Sunday, and then the fix that makes sure you are never here again.
The next three days
Get the keys before you get anything else. Today. Not Saturday. YouTube account, streaming software license, the church's Google account, the graphics computer login, wifi password, whatever they use to schedule. This is the part churches forget, and it is the part that is genuinely hard to recover. Get it in writing, in a document, in the church's own account. Not theirs.
Do it kindly and do it now. Someone leaving on good terms will hand it all over gladly. Someone leaving on bad terms will stop answering texts, and then you are on a support line trying to prove your church owns an account registered to a personal Gmail.
Ask them to write down Sunday. Not a manual. One page. What they touch, in order, from arriving to shutting down. Fifteen minutes of their time is worth more than anything you will figure out on your own by Saturday night.
Record them doing it once. Walk behind them with a phone this Sunday if you still can. A shaky ten minute video of someone plugging things in and clicking things is the single most valuable training asset your church can own. It costs nothing.
Then cut the scope. Hard. Whoever picks this up cannot do what your volunteer did. Do not ask them to. Pick the one thing that matters, and it is almost always this: the message gets recorded with clean audio. Not three cameras. Not the lower thirds. One camera, one good audio feed, one person.
A simple stream that happens beats an ambitious one that does not. Every time.
The One-Deep Rule
Now let me tell you what this actually was:
Any job only one person can do is a job your church is about to lose. Not might. Is.
Nobody volunteers forever. People move, have babies, get promoted, get tired, get hurt by something at church. Every one of your one-deep roles has an expiration date. You just cannot see it.
This was never a volunteer problem. It was a structure problem that had been waiting quietly for its moment.
The same resignation hits both teams on a Thursday
One person deep
✕ Tyler just told you he is moving
With a named second
✕ Same Tyler. Same Thursday.
The actual fix
Own your accounts. Every login in a church-controlled email, in a shared password manager, today. This is the cheapest insurance in ministry and almost nobody buys it until after it hurts.
Write the one-pager for every role. Not a binder nobody reads. One page per job: what you touch, in what order, who to call when it breaks. If a role cannot fit on one page, the role is too complicated, and that is its own problem.
Name a second for every position. Not "train someone eventually." Name them this month. The four steps are shadow, assist, solo with help, then train the next one. That last step is what turns a rotation into a team.
Simplify until a new person can run it. If your setup needs its inventor in the room, you do not have a system. You have a dependency. Every layer you remove is a layer that cannot break on a Sunday when the only person who understood it is gone.
Give people a Sunday off on purpose. A volunteer who can never miss is a volunteer counting down. Scheduled rest is not a luxury. It is what makes the role survivable for years instead of months.
One more thing, and I mean it
Before you fix any of this, go thank the person who left.
They served for years in a dark room at the back while everyone else worshipped. Most of the church has no idea what they did. The only feedback they ever got was when something broke.
Do not let the last conversation be about passwords.
Build it so it survives the person
Somebody is going to find your church this week on a screen, because that is how people find churches now. Whether that still happens next month should not depend on one person's life circumstances staying exactly as they are.
Building it so it survives the person is not a lack of faith in your volunteers. It is respect for them. It means the ministry does not quietly become a weight only they can carry.
Team structure and systems are two of the twelve tracks inside the DiDio Media Academy, including the role one-pagers and the bench rotation this post describes. If you want somewhere free to start, the Channel Launch Checklist covers the setup a new person can actually pick up.
