Docs & technical writing
AuraScore 81/100

Dangerous Goods Transport Spill Response Protocol Script

Draft an interactive read-aloud emergency dispatch and driver guidance script for hazardous freight incidents.

Use this template when designing voice-guided standard operating procedures for logistics dispatchers managing active hazmat transit emergencies. It produces an imperative, high-clarity spoken script to guide drivers and emergency services through immediate spill containment.

Template

Role: Principal Transport Safety Technical Author with deep expertise in hazmat transit documentation and emergency response procedures.

Context

  • Logistics carrier network: {{carrier_network}}
  • Hazardous materials class: {{hazmat_class}}
  • Containment escalation tier: {{containment_tier}}
  • Dispatch console tool: {{dispatch_console_tool}}
  • Regulatory reporting agency: {{regulatory_agency}}
  • Maximum notification window: {{notification_timeframe}}

Task

Develop an interactive, read-aloud dispatch response script that transport controllers use to verbally guide drivers and coordinate first responders during a {{hazmat_class}} transit spill across the {{carrier_network}}.

Method

  1. Define immediate verbal verification steps to determine driver safety, wind direction, and exact GPS coordinates.
  2. Script unambiguous spoken diagnostic questions to identify container breach type and run-off direction.
  3. Provide step-by-step read-aloud containment directives aligned with {{hazmat_class}} emergency response guides.
  4. Script exact phrases for instructing the driver to establish perimeter exclusion zones.
  5. Outline the simultaneous digital inputs required within {{dispatch_console_tool}} while maintaining call contact.
  6. Draft the official notification read-out required when placing the emergency call to {{regulatory_agency}}.
  7. Detail the handover dialogue script for transitioning command to arriving municipal hazardous incident commanders.
  8. Script the post-containment call logging script to guarantee compliance within {{notification_timeframe}}.

Constraints

  • Dispatcher voice prompts MUST use the NATO phonetic alphabet for all license plate and placard references.
  • The script MUST NOT offer unverified neutralization instructions; focus strictly on evacuation and isolation.
  • Spoken lines must be visually distinct from console software logging instructions.
  • Critical life-safety instructions must be scripted in short, active-voice sentences under 15 words each.

Output format

  • Phase 1: Immediate Triage Call Script (Driver Dialogue, Immediate Protective Actions).
  • Phase 2: Containment & Isolation Protocol (Read-aloud safety commands categorized by {{containment_tier}}).
  • Phase 3: Statutory Agency Relay Script (Verbatim voice template for reporting to {{regulatory_agency}}).
  • Phase 4: Dispatch Console Logging Checklist (System timestamps and data fields).

Self-review

  • Confirm that the script accounts for the critical time constraint of {{notification_timeframe}}.
  • Ensure safety commands match standard chemical response protocols for {{hazmat_class}}.
  • Validate that script formatting clearly differentiates between what dispatchers SAY and what they DO.
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-docs
transport-logistics
hazmat
dispatch
emergency response