Editing & rewrite
AuraScore 81/100

Grid Incident Customer Communication Modernization Blueprint

Produce a step-by-step editing plan to transform technical outage notices into clear, empathetic customer alerts.

Use this template when critical grid failures or planned maintenance notifications require urgent editorial restructuring. It establishes an actionable plan to convert engineering jargon into transparent public advisories.

Template

Role: Senior Utility Crisis Communications Editor specializing in customer-facing emergency notifications.

Context

  • Utility Name: {{utility_provider_name}}
  • Incident Type: {{outage_event_type}}
  • Impacted Audience: {{impacted_customer_segment}}
  • Source Draft Copy: {{current_draft_text}}
  • Target Reading Level: {{target_reading_grade_level}}
  • Regulatory Notice SLA: {{regulatory_sla_window}}

Task

Develop a comprehensive editorial revision plan to rewrite the technical grid incident draft into an accessible, empathetic, and compliant multi-channel public notification sequence.

Method

  1. Audit {{current_draft_text}} against engineering terminology, identifying operational terms that require translation for {{impacted_customer_segment}}.
  2. Calculate the baseline readability score of the source copy and map the delta to {{target_reading_grade_level}}.
  3. Establish an editorial hierarchy prioritizing safety precautions, estimated time to restoration (ETR), and resource access points.
  4. Draft three tailored rewrite variations spanning SMS alerts, email bulletins, and social broadcast copy.
  5. Align the revised messaging with dispatch milestones governed by {{regulatory_sla_window}}.
  6. Integrate targeted localized mitigation guidance specific to {{outage_event_type}}.
  7. Review revised content for tone balance, eliminating defensive phrasing while preserving legal accuracy.
  8. Formulate a post-incident editorial sign-off matrix for the corporate communications and grid operations leads.

Constraints

  • MUST eliminate internal system operational codes and substation naming conventions.
  • MUST NOT make non-committal restoration promises outside verified operational guidance.
  • Keep reading level strictly within {{target_reading_grade_level}}.
  • Plan must cover SMS, email, and web portal touchpoints.

Output format

  • Section 1: Readability & Jargon Defect Audit (table format, 4-6 identified issues)
  • Section 2: Channel-Specific Revision Matrix (SMS, Email, Portal variants with word counts)
  • Section 3: Phased Rollout & Review Sequence (chronological timeline within {{regulatory_sla_window}})
  • Section 4: Operational Editorial Quality Gate Checklist (5 sign-off criteria)

Self-review

  • Verify all operational acronyms from {{current_draft_text}} have plain-language equivalents.
  • Confirm every channel variant contains explicit safety instructions.
  • Check that the implementation timeline respects the constraints of {{regulatory_sla_window}}.
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 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 efficiency7/10 · Adequate

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-editing
energy-utilities
crisis-communications
grid-management
plain-language