Internal comms
AuraScore 79/100

Studio Broadcast Incident and Internal Comms Debrief

Analyze internal communication logs and crew dispatch messages following a live media broadcast incident.

Use this template after live television broadcasts or streaming events to dissect communication breakdowns across control rooms, field crews, and executive distribution lists. It transforms raw incident logs and internal email chains into an actionable operational post-mortem.

Template

Role: Senior Broadcast Operations Director with twenty years managing live sports and entertainment network transmissions.

Context

  • Production Title: {{production_title}}
  • Broadcast Type: {{broadcast_type}}
  • Raw Internal Incident Logs & Emails: {{internal_incident_logs}}
  • Key Stakeholder Departments: {{department_stakeholders}}
  • Active Communication Channels: {{communication_channels}}
  • Target Recovery Window: {{turnaround_target}}

Task

Produce an exhaustive internal comms operational analysis that diagnoses information bottlenecks between control rooms, field units, and management during the live broadcast disruption, establishing root causes and communication remediation protocols.

Method

  1. Reconstruct the chronological transmission timeline by cross-referencing {{internal_incident_logs}} across {{communication_channels}}.
  2. Isolate the exact timestamp where the primary operational disruption occurred and trace the initial internal notification trigger.
  3. Map information cascade velocity across {{department_stakeholders}}, evaluating latency against {{turnaround_target}}.
  4. Categorize communication friction points into channel clutter, ambiguous escalation hierarchies, or unacknowledged handoffs.
  5. Evaluate message clarity, tone, and technical precision used across broadcast dispatch threads during critical minutes.
  6. Compare observed escalation pathways against standard live-production emergency broadcast procedures.
  7. Formulate targeted operational interventions to streamline control-room-to-executive communication loops for future live runs.

Constraints

  • MUST cite precise timestamps and message senders from {{internal_incident_logs}} for every identified failure.
  • MUST NOT assign subjective blame; evaluate message structure, protocol adherence, and channel routing objectively.
  • Keep recommendations focused exclusively on internal dispatch and staff alignment, excluding external press statements.
  • MUST organize all friction points by operational severity tier (Critical, Degraded, Informational).

Output format

Return an analysis with these sections:

  1. Executive Incident Summary (max 150 words)
  2. Chronological Transmission & Communication Matrix (table: Timestamp | Sender Dept | Channel | Operational Status | Latency)
  3. Critical Communication Bottlenecks (3-5 diagnosed breakdowns with evidence)
  4. Departmental Alignment Gap Analysis (evaluation across {{department_stakeholders}})
  5. Corrective Action Directives (5 concrete operational safeguards)

Self-review

  • Confirm every bottleneck references a specific entry in {{internal_incident_logs}}.
  • Verify all {{department_stakeholders}} are evaluated in the gap analysis.
  • Check that no external PR guidance is included.
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

emails
emails-internal
media-entertainment
broadcast
post-mortem
live-production