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
- Public status cycle
Public status cycle
Review incident-linked wording and record its intended audience.
Step by step
-
Check the incident Communications Reviewer
The Communications Reviewer reads the current incident state and the latest attributed incident update. The Service Owner confirms the affected component condition.
- Establishes current operating facts.
- Updates Incidents, Incident updates, Public components
-
Draft the message Communications Reviewer
Describe the observed customer effect and the next expected update. Keep the message linked to the incident it explains.
- Connects customer wording to the incident.
- Updates Public updates, Incidents
-
Approve the wording Communications Reviewer
The Communications Reviewer decides whether the text is suitable for the selected audience and is named on the update.
- Names the decision maker for the message.
- Updates Public updates, People
ApprovalA person approves before the work moves on. -
Record the update Communications Reviewer
Select Public or Subscribers, retain the message and publication time, and check its external destination.
- Retains audience, text and publication time.
- Updates Public updates
-
Follow through Incident Coordinator
As the incident changes, record a later message for the same incident and review component status against actual recovery.
- Keeps later status aligned with recovery.
- Updates Incidents, Public updates, Public components
Who does what
Roles and permissions- Communications Reviewer
- , Incident Coordinator, Service Owner.
Set up Status Page System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.