Respond to a live broadcast failure

---
name: respond-to-a-live-broadcast-failure
category: media
description: Respond to a live broadcast failure through audience safety, scoped diagnosis, alternate transmission, clear communication, and verified recovery. Use when a real-time program loses signal, content, control, accessibility, or distribution.
---

# respond-to-a-live-broadcast-failure

Protect people and editorial integrity first, then restore the smallest trustworthy audience experience.

## When to use

- Use when live video, audio, captions, contribution, control, platform distribution, moderation, or recording fails during a program.
- Use routine technical troubleshooting before air when no live audience or safety consequence exists.

## Preconditions

- Confirm producer, director, technical, editorial, safety, accessibility, platform, communications, and recording authority.
- Gather program and return feeds, multiview, encoder, network, platform, caption, chat, intercom, logs, backup media, and audience reports.

## Procedure

1. Declare the incident and establish **failure scope** across program, source, audio, video, captions, platform, regions, audience, recording, and time.
2. Protect **audience safety** by removing harmful output, stopping unsafe activity, and displaying an accessible holding state.
3. Use independent confidence monitoring to distinguish production, contribution, distribution, and audience failure.
4. Choose **alternate transmission** through backup source, encoder, network, platform, prerecorded segment, audio-only, or verified holding channel.
5. Keep one decision log for switches, edits, delays, moderation, accessibility, and recording.
6. Publish **recovery communications** that state observed impact, available alternatives, and next update without speculation.
7. Diagnose power, signal, sync, control, credential, capacity, platform, and configuration boundaries.
8. Test the recovered path off-air or in a controlled preview, then return gradually.
9. Preserve local recordings and reconcile what audiences received across platforms and regions.
10. Complete participant, audience, archive, caption, rights, and post-event follow-through.

## Failure plan

- If content or participant safety is uncertain, cut to the approved safe state immediately.
- If full video cannot be trusted, prefer verified audio, captions, or holding information over repeated unstable switching.
- Never expose backstage feeds, credentials, private chat, or unapproved content during recovery.
- If no safe path exists, end the broadcast clearly and preserve recording plus audience communication.

## Worked example

During a medical conference, the primary encoder freezes while platform preview still shows an old frame and captions continue. The producer cuts to an accessible holding slate, confirms the local program is healthy, and sends backup encoder output over a second network. An independent audience device verifies video, audio, and captions before return. The decision log records a four-minute affected window, regional audience reports, archived local recording, communications, and a later encoder configuration finding.

## Done

- A broadcast incident timeline records failure scope, audience safety, signals, decisions, alternate transmission, and uncertainty
- A continuity and decision log records holding states, accessibility, editorial actions, platform checks, communications, and recording
- A recovery and post-event report verifies audience playback, archive completeness, affected scope, participant follow-through, and prevention work