The Ultimate Sunday Morning Tech Checklist for Church AV Teams

The teams that never seem to have Sunday morning surprises aren't the ones with the best equipment. They're the ones running the same checklist, in the same order, every single week, until it's muscle memory. Here's a checklist built around actual arrival-to-doors timing, not just a vague list of "things to check."

90 minutes before doors: power and connections

This is the window for anything that needs time to boot, sync, or fail safely before people start arriving.

• Power on all AV equipment — boards, projectors or displays, streaming encoder, cameras.
• Confirm the internet connection is up and check actual upload speed, not just "connected." A weak connection is far easier to fix at 90 minutes out than at 5 minutes out.
• Check that wireless mic packs are charged or have fresh batteries, and that receivers show a clean signal.
• Open your streaming software and confirm scenes/sources load correctly, including any browser source used for graphics.
• Log into your scripture, lyrics, and lower-thirds tool and confirm it's pushing to the correct screen output — not just visible on the control laptop.

60 minutes before doors: content load and sound check

• Load today's setlist into your lyrics tool and spot-check two or three songs for correct formatting and slide breaks.
• Confirm the sermon's scripture references (if provided ahead of time) are ready to pull up, and that your default Bible translation is set correctly.
• Load any lower thirds needed today — guest speaker names, series titles, announcement slides.
• Run a full sound check with live vocals and instruments, not just a line check with no one singing.
• Test stream output end-to-end: watch the actual public stream link on a separate device, not just the local preview window. This step catches problems nothing else will.

30 minutes before doors: full run-through

• Walk through the service order start to finish with whoever's operating each role, cueing actual transitions — welcome, worship set, announcements, sermon, response.
• Confirm hand signals or headset cues for cutting to specific cameras or triggering graphics.
• Test the "clear screen" function specifically. Operators drill pushing content constantly; clearing it cleanly gets forgotten and shows on stream more than people realize.
• Check battery levels one more time on anything wireless.
• Confirm a backup plan is understood by everyone present: what happens if the stream drops, what happens if a mic cuts out, who makes the call.

10 minutes before doors: final pass

• Do a final scan of every screen output — sanctuary displays, lobby screens, livestream — confirming they all show what they're supposed to, not leftover content from rehearsal.
• Confirm volunteers are in position and know their first cue.
• Silence phones and notifications on any device connected to the production system, since a notification popup during a screen share has ruined more than one livestream.

During the service: the ongoing checklist

The checklist doesn't stop when the service starts. Keep a light version running throughout:

• Glance at stream health (viewer count, connection quality) every 10-15 minutes rather than only at the start.
• Confirm each transition between segments — worship to announcements, announcements to sermon — actually happened cleanly on screen, not just in the room.
• Keep scripture and lyrics tools open and ready for anything unplanned; sermons go off script more often than people expect.

This is where a centralized dashboard earns its keep. AllStreamHub's Real-Time Dashboard is designed for exactly this kind of ongoing, in-service checking — pushing scripture, lyrics, and lower thirds from one place, so an operator running the mid-service checklist isn't juggling five separate tools while also trying to catch an unplanned Bible reference.

After the service: five minutes that save next week

• Note anything that went wrong or felt shaky, even minor things, in a shared log.
• Power down equipment properly rather than just walking away.
• Flag any hardware issue (a flickering cable, a mic that cut out) immediately rather than trusting yourself to remember it by Thursday's prep.

A checklist like this looks long written out, but in practice it's mostly muscle memory after a few weeks — five to ten minutes of focused checking spread across ninety minutes, not a heavy new burden. The teams that run it consistently are the ones who stop having "surprise" problems, because most Sunday morning tech failures are really just a checklist step that got skipped the week it mattered.