Every year, the same thing happens. Around the middle of November, your regular sound person is traveling for Thanksgiving, your livestream lead is home with a sick kid, and the person actually running Sunday morning is someone who has shadowed the booth twice. Then Advent starts, and the crowd doubles.
We have watched this pattern play out at churches of every size. It is rarely a crisis of skill. It is a crisis of documentation. The people who know how everything works are wonderful, and they are also human, and they will not always be in the room. Late September is the moment to fix that, while the calendar is still calm enough to write things down.
Why one page, not a binder
Most church tech documentation dies because it is too ambitious. A fifty-page manual with screenshots ages badly, lives on a server nobody can find, and gets skipped when the pressure is on. What actually survives is a single laminated sheet in the booth, updated once a quarter, that answers the questions a stressed volunteer will ask at 9:47 a.m. on a Sunday morning.
If a page is short enough that a nervous person can scan it in thirty seconds, it will get used. If it is longer than that, it becomes decoration.
What belongs on the page
Think of the runbook as answering four questions in order: how do I turn everything on, what do I check before people arrive, what do I do when the service starts, and who do I call when something breaks. Everything else is a distraction.
Startup sequence, in order. The exact power switches, in the exact order, with a note about the ninety seconds the projector needs to warm up before the input will register. Include the login for the streaming laptop and the Wi-Fi password for the booth. Assume the person reading has never touched the system before.
Pre-service checks. A short list of the five things that most commonly go wrong. For most churches this is: wireless mic batteries, the correct slide deck loaded, the giving QR code pointing to this week's campaign, the livestream preview showing the stage, and the lobby TV showing the welcome loop rather than yesterday's staff meeting.
During-service quick fixes. The two or three things a volunteer can safely do without paging anyone. Muting a hot mic. Switching to the backup camera. Restarting the slides laptop if it freezes. Anything more complicated goes to the next section.
Who to text, and when. A short list of names and phone numbers, in the order to try them. Include what counts as an emergency worth interrupting someone at home for, and what counts as a Monday-morning ticket. The absence of this list is why volunteers freeze when something goes wrong.
The parts most churches forget
A few things are almost never written down, and they are almost always what causes the Sunday panic.
The name of the streaming account and where the password lives. The location of the spare batteries and which brand they are. The channel numbers for each wireless mic, and which one belongs to the pastor. The specific setting on the mixer that gets reset every time someone unplugs the wrong cable. The fact that the sanctuary camera loses its color balance if the sun hits the back window at 10:15.
These are not secrets. They are the tacit knowledge that lives in one person's head. Getting them onto paper is the whole point of the exercise. If your longtime tech lead left tomorrow, the runbook is what you would wish you had built.
How to actually write it
Pick a Sunday in the next two weeks. Ask your regular tech person to run through the morning as if a total stranger were shadowing them, and have someone else write down every step. Do not let the tech person hold the pen. They know the system too well to notice what they are skipping.
Draft the page that afternoon. Print it. Tape it inside the booth. Then, and this is the part most churches miss, hand it to a volunteer who does not usually run the desk and ask them to walk through the startup sequence next Sunday using only the page. Whatever they get stuck on is what your runbook is still missing.
Update it once, right after that trial run. Then leave it alone until Easter.
The faith part of this
Documentation can feel like a joyless topic in a place built around worship. We would push back gently. The point of writing things down is not efficiency for its own sake. It is so that the pastor's spouse who volunteers for the Christmas Eve slides can serve without dread, so that a college student home for break can jump in and be useful, so that a first-time visitor on the biggest Sunday of the year hears the sermon without a squeal from a hot mic. Hospitality has a technical layer, and caring for it is part of caring for the people who walk in.
A church that hands a nervous volunteer a clear page of instructions is a church saying, quietly, we thought about you before you got here.
If you would like help thinking through your church's tech workflow, drafting a runbook that fits your setup, or making your website easier for those Advent visitors to navigate, we would be glad to talk. Reach out through our contact page and tell us a little about your Sunday morning.