Olympic sized preparedness

You don’t judge how prepared a team is by the show that goes right; you judge them by the recovery when it goes wrong.

When the lights went out in Cortina, the PA system (likely on a separate emergency circuit) allowed officials to inform the crowd. Information kills anxiety.

Let me guide you through the journey to resilience, and break it down into a useful framework. We will move beyond the audio focus of the Cortina blackout (in part 1) to explore the leadership that ensures your show is built to withstand the storm.

This will work if it’s a global broadcast to millions, or an in-person event for hundreds.

It’s more than just “having a backup.” We are going to explore the physics of why your backup failed last time, the network topology that ensures it won’t fail next time, and the theology of why it matters in the first place.

Welcome to the Winter Guide to Bulletproof Production.

1 Removing the Distraction

Most would agree that technology in an event or worship service should be transparent. Its purpose is to carry the message. When the system fails, the mic feeds back, the screen goes blue, or the lights go out, the technology becomes a distraction. The congregation’s focus shifts from the message to the medium.

Stewardship of the Moment

A backup plan is not a lack of faith; it is stewardship of the opportunity to gather. By investing in a redundant computer for lyrics or a UPS for the sound board, the technical team is protecting the congregation’s ability to engage without distraction.

Excellence vs. Perfection

No system is perfect. The goal is an excellence of doing the absolute best with the resources available. A small church or studio might not afford a whole building generator setup, but they can afford a spare $50 backup microphone and a written plan for what to do if the power fails.

2 The Complexity Factor

Unlike the paid engineers at the Olympics, churches rely on volunteers. Complexity is the enemy of volunteer success.

The “Panic Button” Design:

Systems should be designed so that the “panic” state is safe. For example, backup profile on a USB stick for the audio console that has no effects or fancy routing. Or, if the external effects or eq hardware dies, the signal flow automatically bypasses the broken unit and goes straight to the amp with safe volume levels preset into it.

Training for Failure:

Most training focuses on how to make things work. My advice is to train for when things break.

In addititon to your team’s normal instruction, do occasional failure drills:

• Drill 1: “The pastor’s mic battery died. Go.” (Target: <10 seconds to swap to the handheld backup).
• Drill 2: “The graphics computer froze. Go.” (Target: Switch video output to the “Logo” or “Black” instantly).
• Drill 3: “Power outage. Go.” (Target: Flashlights on, acoustic guitar ready).

3. The Disaster Run Sheet

Just as you have a run sheet for the order of service, you need a Disaster Run Sheet.

• IF Livestream drops THEN switch to local recording, post “Technical Difficulties” graphic to chat.
• IF Fire Alarm triggers THEN cut all audio, bring up house lights, announce evacuation.
• IF Pastor collapses THEN cut livestream feed, fade to black, medical team go.

Implement it

Whether you are broadcasting to billions from the Italian Alps or livestreaming to fifty people from a basement sanctuary, the mandate is the same: Build it strong, have a plan, and when the darkness comes, be ready to shine.