Five-stage control flow
Each stage has a clear decision, record and ownership expectation.
Detect
Capture the alarm or report, affected service and first observable symptoms.
Qualify
Confirm scope, severity, customer effect and the team accountable for action.
Stabilise
Open the record, set priority, assign coordination and preserve diagnostics.
Coordinate
Engage technical, vendor, carrier or field resources and maintain updates.
Close
Confirm restoration, customer acceptance, chronology and follow-up actions.
Severity and cadence
| Level | Typical impact | Coordination | Updates |
|---|---|---|---|
| P1 | Critical service unavailable or widespread high impact | Immediate ownership and senior escalation | Every 30 minutes or agreed cadence |
| P2 | Major degradation with material operational impact | Priority technical and vendor engagement | Every 60 minutes or agreed cadence |
| P3 | Limited degradation or non-critical service issue | Standard queue ownership and tracking | At 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 question | Required handover evidence | Failure prevented |
|---|---|---|
| What is affected now? | Current impact and last verified service state | Working from stale assumptions |
| Who owns the next action? | Named team or person, action and target time | Unowned waiting time |
| What has already been tried? | Tests, outcomes and supporting timestamps | Repeated troubleshooting |
| What must the customer hear next? | Latest update, next update time and open questions | Communication gaps |
This sample demonstrates the Respond, Coordinate and Document pillars of DDANEP.
Explore the full framework