Severe Weather Energy Supply Resilience and Curtailment Contingency Plan
Formulate a risk-indexed crisis contingency plan for extreme weather power supply shortfalls and emergency load shed.
Use this template during pre-season storm preparedness or when hardening utility emergency operations. It delivers structured curtailment tiers, critical infrastructure protection protocols, and regulatory crisis communication timelines.
Role: Chief Energy Risk Officer and Supply Continuity Strategist
Context
- Utility / Grid entity: {{utility_entity}}
- Anticipated winter/summer peak demand: {{peak_demand_forecast_mw}}
- Upstream fuel and interconnect constraints: {{fuel_supply_vulnerabilities}}
- Protected load designations: {{critical_infrastructure_loads}}
- Emergency curtailment thresholds: {{curtailment_tier_thresholds}}
- Mandatory compliance reporting interval: {{regulatory_reporting_window}}
Task
Design an operational emergency preparedness and load-shed contingency plan for {{utility_entity}} to maintain systemic grid integrity under extreme climate stress, mitigating {{fuel_supply_vulnerabilities}} while defending {{critical_infrastructure_loads}}.
Method
- Establish early-warning weather trigger criteria and day-ahead gas/power trading protocols to secure physical generation capacity.
- Quantify the supply deficit across operating reserve tranches when load reaches {{peak_demand_forecast_mw}} under extreme weather scenarios.
- Map automated rotational load shedding circuits, ensuring 100% isolation and defense of {{critical_infrastructure_loads}}.
- Define operational trigger metrics for shifting through each phase of {{curtailment_tier_thresholds}}.
- Formalize blackstart generation procedures, fuel switching routines (e.g., dual-fuel diesel/gas), and cold-weather line de-icing schedules.
- Standardize executive incident command escalation pathways and public emergency broadcast protocols.
- Detail mandatory regulatory and regional transmission notifications required within {{regulatory_reporting_window}}.
- Construct a 72-hour post-event restoration, feeder re-energization sequencing, and root-cause audit methodology.
Constraints
- Critical assets identified in {{critical_infrastructure_loads}} MUST NOT be placed on automatic shedding rotation circuits.
- Incident declaration timelines MUST NOT violate {{regulatory_reporting_window}}.
- Load-shed stages must explicitly match the operational criteria defined in {{curtailment_tier_thresholds}}.
- Must provide explicit human-in-the-loop override procedures for manual breaker trips.
Output format
- Readiness & Trigger Threshold Matrix (table: Alert Level, Weather Threshold, System Reserve MW, Command Action)
- Fuel Assurance & Generation Hardening Protocol (250-350 words addressing {{fuel_supply_vulnerabilities}})
- Controlled Curtailment & Rotational Shedding Scheme (step-by-step procedure mapped to {{curtailment_tier_thresholds}})
- Critical Infrastructure Protection Plan (bulleted list of isolation and uninterruptible power requirements)
- Emergency Communications & Compliance Schedule (time-based checklist complying with {{regulatory_reporting_window}})
- Post-Event Restoration & Audit Procedure (numbered chronological sequence)
Self-review
- Confirm no circuit in {{critical_infrastructure_loads}} is subject to unmanaged blackout or shedding.
- Verify that total curtailment volumes correspond accurately to {{peak_demand_forecast_mw}} deficit scenarios.
- Check that all regulatory reporting workflows strictly observe {{regulatory_reporting_window}}.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.