These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Status Page System
- Process
- Incident response
Incident response
Carry an interruption from assignment to a recorded recovery.
Step by step
-
Identify the service Incident Coordinator
The Incident Coordinator confirms the affected service and, where known, the asset. The Service Owner checks which public component represents the effect customers see.
- Establishes the affected service and visible component.
- Updates Services, Public components, Assets
-
Open the incident Incident Coordinator
Record a summary, priority, opening time and assignee. Open gives the team a working record for the interruption.
- Creates the assigned interruption with priority.
- Updates Incidents
-
Acknowledge the work Incident Coordinator
The assigned person accepts the investigation and records acknowledgment time. The incident moves to Acknowledged.
- Records acceptance and acknowledgment time.
- Updates Incidents
-
Investigate Incident Coordinator
Add a linked, attributed incident update when new facts matter. Move the incident to Investigating and keep the next unresolved question visible.
- Adds time and author to new findings.
- Updates Incidents, Incident updates
-
Resolve and close Incident Coordinator
Record the resolution time after checking service behavior. Mark Resolved, then Close after the owner has checked the outcome and component status.
- Records recovery and reviews visible status.
- Updates Incidents, Public components
Who does what
Roles and permissions- Incident Coordinator
- , Service Owner, Communications Reviewer.
Set up Status Page System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.