Docs & technical writing
AuraScore 81/100

Substation Emergency Protocol Documentation Architecture

Design a technical documentation framework for high-voltage substation emergency response procedures.

Use this template when building critical hazard response guides and emergency operating frameworks for electrical substations. It ensures frontline clarity during high-risk utility incidents.

Template

Role: Senior Energy Safety Technical Author specializing in high-voltage utility emergency response procedures.

Context

  • Facility Operator: {{utility_operator}}
  • Asset Type: {{asset_category}}
  • Primary Hazard Domain: {{hazard_classification}}
  • Oversight Authority: {{regulatory_body}}
  • Response Roles: {{field_crew_roles}}
  • Lifecycle Stage: {{document_lifecycle_stage}}

Task

Design an emergency response technical documentation framework for {{utility_operator}} that standardizes fast-action procedures for {{hazard_classification}} events occurring at {{asset_category}} facilities, meeting {{regulatory_body}} incident mitigation mandates.

Method

  1. Define immediate threat containment triage criteria customized for {{hazard_classification}}.
  2. Map emergency command hierarchy and communication channels across {{field_crew_roles}}.
  3. Structure step-by-step containment procedures with immediate 60-second, 5-minute, and 30-minute milestones.
  4. Design graphical hazard perimeter and isolation zone specification rules.
  5. Standardize personal protective equipment requirements and secondary hazard triggers.
  6. Create handover protocols for municipal first responders and transmission dispatchers.
  7. Establish post-incident event timeline reconstruction and evidence capture templates.

Constraints

  • MUST distinguish clearly between actions authorized for field personnel versus certified hazardous response teams.
  • MUST NOT use ambiguous temporal phrases; all response times must have numeric thresholds.
  • Highlight life safety imperatives ahead of asset preservation actions.
  • Maintain format alignment with {{document_lifecycle_stage}} revision control rules.

Output format

Provide a technical framework structured as:

  1. Incident Classification and Threat Assessment Matrix (3 threat tiers with threshold criteria)
  2. Immediate Action Playbook (numbered sequential steps grouped by time horizon: 0-60s, 1-5m, 5-30m)
  3. Role-Based Responsibility Matrix (RACI format covering {{field_crew_roles}})
  4. First Responder Coordination Protocol (concise handover script and site-entry checklist)
  5. Post-Event Reporting and Debrief Framework (6 required data fields and evidence requirements)

Self-review

  • Confirm that life-safety priorities explicitly supersede asset preservation.
  • Check that role handoffs between {{field_crew_roles}} are gap-free.
  • Ensure all emergency thresholds strictly adhere to {{regulatory_body}} benchmarks.
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-docs
energy-utilities
technical-writing
emergency-response
substations