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 the list to collect no matter where you are in this, what to do between now and Sunday, and the fix that makes sure you are never here again.
Who should own your church's media accounts?
The ministry should, and at least two or three trusted people should be able to get into every one of them. Set that up before anyone leaves, because not everyone leaves on good terms, and the person walking out the door may not be willing to help you move anything.
Most people who serve in a booth for years will hand everything over gladly. Some leave hurt, and they stop answering texts. You do not get to choose which kind of goodbye you get, so do not build a setup where your church's YouTube channel depends on it.
What to collect, whether they have left, are leaving, or are staying
The list is the same in every case: every login, the email and phone number that receive password resets, the two-step verification backup codes, and access to the YouTube channel and Facebook Page, all moved into accounts the ministry controls. What changes is how fast you need it and how you ask.
MINISTRY ACCOUNT CHECKLIST
The ministry owns it. At least two people can get in.
Do this now if nobody is leaving. Do it today if someone is.
[ ] YouTube channel: owned by the ministry's Google account, with 2 to 3 people
added as Managers (YouTube Studio, Settings, Permissions, Invite).
If a volunteer's personal account owns it today, have them invite the
ministry's account and two leaders as Managers.
[ ] The Google account itself: password, recovery email and recovery phone
all belong to the ministry, not one person
[ ] Two-step verification backup codes saved in the shared password manager
[ ] Facebook Page: at least two leaders with full Page access
[ ] Instagram and any other social accounts: logins in the shared password manager
[ ] Streaming service or software: login, license and stream keys
[ ] Church website and domain registrar login
[ ] The email inbox that receives every password reset
[ ] Graphics and slides computer login (ProPresenter or similar) and the Wi-Fi password
[ ] Scheduling tool admin access (Planning Center or similar)
[ ] CCLI account login and license numbers
[ ] Cloud storage where the sermon files live
[ ] A one-page "how Sunday runs" sheet and a phone video of it
- Nobody is leaving yet. This is the best time you will ever get, so do it this month, in one sitting, with the person who runs it. Tell them plainly that it protects them too: nobody will be calling them at midnight two years from now to ask for a password.
- Someone is leaving. Get it today, not on their last Sunday. Sit down together, get the ministry's account and your leaders added everywhere while they are still answering texts, and thank them while you do it.
- They already left. Ask once, kindly and in writing, with the exact steps spelled out. Some people who will not have a conversation will still click one button. If the channel or Page sits on their personal account and they do not respond, you are on a support line trying to prove your church owns an account registered to a personal Gmail, and there is no guaranteed way back. That is the whole reason to do this before anyone leaves.
What to do in the next three days
Between now and Sunday, do four things in this order: get the keys, get Sunday written down, record it once, and cut the scope to one camera and clean audio. A simple stream that happens beats an ambitious one that does not.
- Get the keys before you get anything else. Today. Not Saturday. Work through the checklist above and get the ministry's account added everywhere while they are still answering. Do it kindly and do it now. This is the part churches forget, and it is the part that is genuinely hard to recover.
- 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.
If they are already gone, steps two and three are off the table, so the last one matters even more.
The One-Deep Rule
The One-Deep Rule. 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.
The rule applies to logins, too. An account only one person can get into is a one-deep role, and it is the one that costs the most to lose, because you can borrow a camera on Saturday and you cannot borrow a YouTube channel.
This was never a volunteer problem. It was a structure problem, and the resignation is just the day you found out.
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.
How to make sure you are never one person deep again
Make every role and every account at least two people deep before anyone leaves. The ministry owns the logins, every role has a one-page instruction sheet and a named second, and the setup stays simple enough that a new person can run it on their first Sunday.
- Own your accounts. Every login lives under a ministry-owned email, not a volunteer's personal Gmail, and sits in a shared password manager (1Password and Bitwarden both do this) that at least two or three trusted people can open. On YouTube, the channel should be owned by the ministry's Google account, with your people added as Managers. YouTube's own help page on channel permissions says owners can't transfer ownership to other users, which is exactly why the owner has to be the church from day one. On Facebook, give at least two leaders full Page access. Save Google's two-step verification backup codes in the same vault, so one volunteer's phone is never the only way in. 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. If the accounts were settled long before anyone left, it never has to be.
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, or on how one goodbye goes.
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.
Sources
- YouTube Help: Add or remove access to your YouTube channel with channel permissions (the roles, where to invite someone, and that owners can't transfer ownership)
- Facebook Help: Give, edit or remove Facebook Page access
- Google Account Help: Sign in with backup codes (the 10 codes for two-step verification)
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.
