General support
AuraScore 81/100

Vulnerable Consumer Life-Support Grid Continuity Blueprint

Deliver a proactive support and escalation framework for medically dependent utility customers.

Use this template to establish robust customer service procedures when managing planned outages or emergency curtailments affecting critical-care customers. It ensures strict regulatory adherence and zero-harm outcomes.

Template

Role: Vulnerable Customer Program Director and Regulatory Support Strategist.

Context

  • Grid Operator: {{utility_operator}}
  • Vulnerability Category: {{customer_vulnerability_tier}}
  • Outage Advance Notice: {{outage_notification_timeline}}
  • On-Site Backup Status: {{backup_generation_status}}
  • Primary Engagement Channel: {{escalation_channel}}
  • Regulatory Framework: {{compliance_jurisdiction}}

Task

Design a critical care customer support framework that guarantees reliable contact, emergency mitigation, and direct case management for medically vulnerable consumers during maintenance shutdowns or grid stress events.

Method

  1. Establish registry verification requirements according to {{compliance_jurisdiction}} standards for {{customer_vulnerability_tier}}.
  2. Construct an omnichannel outreach cascade through {{escalation_channel}} aligned with {{outage_notification_timeline}}.
  3. Formulate positive confirmation protocols that mandate documented human-to-human contact before work proceeds.
  4. Assess the customer's {{backup_generation_status}} to determine emergency battery or generator deployment triggers.
  5. Define secondary emergency escalation paths with local community services if the customer cannot be reached.
  6. Detail special operational coordination between {{utility_operator}} dispatch and frontline priority support teams.
  7. Create a post-event check-in protocol to confirm normal operation of medical equipment upon grid re-energization.

Constraints

  • MUST mandate 100% positive contact confirmation before any planned service disruption.
  • MUST NOT permit automated robocalls as the sole notification method for life-support households.
  • Privacy and sensitive health data handling must strictly follow relevant privacy statutes.
  • Guidance must include explicit fail-safe steps for unanswered contact attempts.

Output format

Deliver the operational framework across 4 defined components:

  1. Critical Care Verification & Registry Standards (eligibility and documentation rules)
  2. Escalating Notification Cascade (chronological timeline and channel mapping)
  3. On-Site Emergency Assistance & Backup Assessment (action checklist)
  4. Regulatory Audit & Incident Logging Standards (mandatory documentation fields)

Self-review

  • Does the framework strictly enforce human confirmation prior to power interruption?
  • Are the specific mandates of the regulatory jurisdiction fully incorporated?
  • Are backup power assessment actions clearly outlined for frontline staff?
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.

support-success
support-general
energy-utilities
vulnerable-customers
medical-baseline
utility-compliance