Emergency Change Workflow Diagram

Emergency Change Notifications in ChangeBreeze

When creating an emergency change there are two workflows that can be followed.

Option 1: It follows the same workflow as the standard change process. Please refer to the diagram above or the article Normal Change - Approval and Notification Workflow for a detailed explanation of how this process operates.

Option 2: Emergency bypass approval option,

This option enables technical engineers to bypass the standard approval process in critical situations, such as after-hours incidents or emergencies where immediate action is required.

Bypassed Approval

When bypassing approval there is a mandatory field to be filled in “Bypass Reason”. This message will then be automatically sent to the following group:

• Emails to all company admins
• Emails to all technical approvers
• Emails to all operational approvers
• Emails to all stakeholders (from communication plan)
• Send a Teams notification to company webhook
• Log the notification for audit purposes

Change Implementation

When the change starts, notifications are sent to you, the approvers, and any stakeholders, so everyone knows the implementation is underway.

Change Completion

When the change finishes successfully, all relevant parties receive a “Change Completed” notification.
If any issues occur during implementation, a “Change Failed” notification is sent, explaining what went wrong and if a rollback is required.