Copywriting
AuraScore 81/100

Grid Resilience Outage Notification Copy Specification

Author a behavioral UX copy specification for real-time grid disruption alerts, portal notifications, and resolution updates.

Run this template during storm season preparation or customer experience digital overhauls. It standardizes multi-state incident messaging to manage ratepayer expectations and minimize contact center volume.

Template

Role: Lead Customer Experience (CX) Copywriter and Grid Modernization Communications Architect

Context

  • Grid Operator Entity: {{grid_operator}}
  • Geographic Setting: {{affected_region_type}}
  • Disruption Trigger: {{outage_cause_category}}
  • Restoration Window Target: {{resolution_window}}
  • Self-Service Asset: {{self_service_portal_url}}
  • Contact Center Load Target: {{call_center_mitigation_target}}

Task

Design a comprehensive multi-state outage communication copy specification that provides critical safety guidance, sets realistic estimated restoration times, and proactively deflects inbound telephone inquiries.

Method

  1. Map the emotional and practical trajectory of ratepayers in {{affected_region_type}} experiencing an unplanned service disruption.
  2. Formulate clear incident diagnosis language explaining {{outage_cause_category}} without defensive or ambiguous technical phrasing.
  3. Author Phase 1 (Incident Detected) notifications across SMS, Push Notification, and Outage Map banner states.
  4. Author Phase 2 (Crews Dispatched / Assessing) progress updates incorporating {{resolution_window}} expectation setting.
  5. Author Phase 3 (Power Restored & Verification) messaging with step-by-step guidance on breaker checks and partial outage reporting.
  6. Integrate contextual CTAs routing high-volume queries toward {{self_service_portal_url}} to support {{call_center_mitigation_target}}.
  7. Draft life-safety advisory microcopy for vulnerable ratepayers requiring power for medical equipment.

Constraints

  • MUST maintain an objective, empathetic, and accountability-driven tone representing {{grid_operator}}.
  • MUST NOT provide specific hour-minute restoration commitments unless explicitly flagged as verified crew estimates.
  • SMS message strings MUST adhere to strict multi-part SMS standards with clear opt-out commands.
  • Safety warnings regarding downed lines and generator usage MUST appear in all primary disruption alerts.

Output format

1. Incident Communication State Machine Copy (Phase 1 Initial Alert, Phase 2 Crew Update, Phase 3 Restoration Confirmed)

2. Multi-Channel Copy Spec (SMS Text Tranches, Mobile Push Alerts, Web Outage Map Header Banners, Automated IVR Script)

3. Safety & Vulnerable Customer Warnings (Life-support equipment, downed power line warnings)

4. Deflection Microcopy & Self-Service Guide (Clear navigation prompts linking to {{self_service_portal_url}})

Self-review

  • Confirm that every alert state includes direct life-safety warnings and actionable next steps.
  • Check that tone appropriately mitigates panic while avoiding corporate evasiveness regarding {{outage_cause_category}}.
  • Verify that digital touchpoint copy clearly supports the quantitative goal in {{call_center_mitigation_target}}.
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-copywriting
energy-utilities
copywriting
utilities
crisis-communications