Sanitised practice example 01

Incident Control & Escalation Runbook

A practical control model for turning a service-affecting signal into an owned, coordinated and fully documented response.

Representative working method · no confidential operational data
ObjectiveRestore service while maintaining technical and customer control.
Primary ownerAssigned incident coordinator until formal transfer or closure.
Required evidenceImpact, timestamps, diagnostics, decisions, updates and restoration proof.

Five-stage control flow

Each stage has a clear decision, record and ownership expectation.

01 · SIGNAL

Detect

Capture the alarm or report, affected service and first observable symptoms.

02 · IMPACT

Qualify

Confirm scope, severity, customer effect and the team accountable for action.

03 · CONTROL

Stabilise

Open the record, set priority, assign coordination and preserve diagnostics.

04 · RESPONSE

Coordinate

Engage technical, vendor, carrier or field resources and maintain updates.

05 · EVIDENCE

Close

Confirm restoration, customer acceptance, chronology and follow-up actions.

Severity and cadence

LevelTypical impactCoordinationUpdates
P1Critical service unavailable or widespread high impactImmediate ownership and senior escalationEvery 30 minutes or agreed cadence
P2Major degradation with material operational impactPriority technical and vendor engagementEvery 60 minutes or agreed cadence
P3Limited degradation or non-critical service issueStandard queue ownership and trackingAt milestones and agreed review points

Minimum incident record

  • Service and customer impact
  • Detection and acknowledgement times
  • Priority and ownership
  • Diagnostic evidence
  • Escalations and vendor references
  • Customer-update chronology
  • Restoration confirmation
  • Follow-up owner and due date

Handover quality gate

A handover transfers control—not just information.

Control questionRequired handover evidenceFailure prevented
What is affected now?Current impact and last verified service stateWorking from stale assumptions
Who owns the next action?Named team or person, action and target timeUnowned waiting time
What has already been tried?Tests, outcomes and supporting timestampsRepeated troubleshooting
What must the customer hear next?Latest update, next update time and open questionsCommunication gaps

This sample demonstrates the Respond, Coordinate and Document pillars of DDANEP.

Explore the full framework