General writing
AuraScore 81/100

Critical Outage Incident Messaging Framework

Structure a multi-channel crisis communication framework for severe utility disruptions.

Use this template during widespread service interruptions caused by severe weather or equipment failure. It creates a unified messaging hierarchy for crisis communicators balancing operational reality with customer reassurance.

Template

Role: Senior Emergency Operations Communications Director with extensive field experience in electric transmission crisis response and public safety reporting.

Context

  • Provider entity: {{utility_provider}}
  • Incident trigger: {{hazard_type}}
  • Scope of disruption: {{affected_customer_count}}
  • Projected restoration timeframe: {{estimated_restoration_window}}
  • Critical infrastructure focus: {{priority_infrastructure_sites}}
  • Compliance oversight standard: {{regulatory_reporting_standard}}

Task

Design an operational crisis messaging framework and update cadence that delivers clear, empathetic, and legally compliant communications across all emergency broadcast channels during an active power restoration lifecycle.

Method

  1. Assess the operational impact of {{hazard_type}} across the impacted service footprint.
  2. Establish a tiered incident classification level mapped against {{regulatory_reporting_standard}} obligations.
  3. Create primary safety instructions prioritizing life-support customers, downed lines, and generator precautions.
  4. Formulate contextual restoration messaging detailing field triage protocols for {{priority_infrastructure_sites}}.
  5. Structure interval-based communication schedules (T-0, T+2h, T+6h, T+12h, restoration completion).
  6. Draft channel-specific adaptation guidelines for press releases, digital outage maps, SMS notifications, and media briefings.
  7. Establish misinformation containment protocols for addressing speculative outage causes on social channels.

Constraints

  • MUST state restoration times strictly as estimated intervals subject to safety and field condition assessments.
  • MUST NOT guarantee restoration times for specific individual feeders before physical field verification.
  • All critical safety warnings must appear above the fold in every communication tier.
  • Language must balance operational gravity with calm, authoritative transparency.

Output format

  1. Incident Triage & Situation Overview Statement
  2. Channel-by-Channel Core Messaging Architecture (SMS, Social, Media Briefing, Web)
  3. Restoration Phase Playbook (Immediate Assessment, Active Repair, Final Mopping Up)
  4. Priority Facility Protocol Explainer (Covering {{priority_infrastructure_sites}})
  5. Public Safety Advisory Template

Self-review

  • Verify that the estimated restoration phrasing complies with regulatory disclaimer rules.
  • Confirm clear prioritization of public life-safety hazards over property damage updates.
  • Ensure channel templates maintain consistent facts without contradictory time stamps.
AuraScore breakdown
81/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 engineering12/12 · Strong

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.

writing-content
writing-general
energy-utilities
crisis-communication
utilities
emergency-response