Drafts escalation communications for operational incidents, service failures, and compliance breaches. Produces structured escalation notices with incident classification, impact assessment, timeline of events, immediate actions taken, and required management decisions with appropriate urgency framing.
The Escalation Drafter skill produces structured, professional escalation communications for operational incidents, service degradations, compliance breaches, and other events requiring management attention. It ensures that escalation notices contain all necessary context for decision-makers to act quickly, including severity classification, business impact quantification, chronological event timelines, and clearly stated asks. The skill enforces consistent formatting and urgency calibration so that critical issues receive proportionate attention without desensitising recipients through overuse of high-priority framing.
Classify the incident severity. Determine the appropriate severity level (Critical, High, Medium, Low) based on the scope of impact, number of affected users or systems, revenue exposure, and regulatory implications. Apply the organisation's severity matrix if one is referenced in the input.
Identify the audience and escalation tier. Determine whether this is a Tier 1 (team lead / on-call manager), Tier 2 (department head / VP), or Tier 3 (C-suite / board) escalation. Adjust the level of technical detail, business context, and formality accordingly.
Construct the incident timeline. Build a chronological sequence of events from first detection through to the current state. Include timestamps, key actions taken, personnel involved, and any decision points. Use UTC timestamps unless a specific timezone is indicated.
Assess and quantify business impact. Document the measurable effects of the incident: affected customer count, revenue at risk, SLA credit exposure, data records involved, or regulatory reporting deadlines triggered. Use concrete figures where available and clearly label estimates.
Document immediate actions taken. List all remediation, containment, or mitigation steps already completed or in progress. Include the responsible party for each action and its current status (completed, in progress, pending).
State required decisions and asks. Clearly articulate what the escalation recipient needs to do: approve a workaround, allocate additional resources, authorise customer communications, engage external vendors, or invoke a disaster recovery plan. Frame each ask with its deadline and consequence of inaction.
Draft the escalation notice. Assemble the communication using the standard escalation template with clearly labelled sections. Ensure the subject line conveys severity and topic at a glance. Keep the executive summary to three sentences maximum.
Calibrate urgency and tone. Review the draft to ensure the urgency level matches the severity classification. Remove inflammatory language, unsupported speculation, and blame attribution. Confirm that the tone is factual, direct, and action-oriented.
The escalation notice is produced as a structured document with the following sections:
[SEVERITY] - Brief description of incident