Types of Changes
Emergency
Standard
Normal
A change that must be implemented as soon as possible
A change that is very low to no risk
A change that is planned and implemented
+ info
+ info
+ info
Patching
Unauthorized
Informational
A change created to record the activity of routine maintenance patching
A change that is performed outside of logging a Change Request
A change created when we need to keep track of changes
+ info
+ info
+ info
Patching
A change created to record the activity of routine maintenance patching of customer or internal devices. These changes are raised by submitting a Patching catalog request from the Service Now request catalog. This catalog request suppresses alerts during the change window and creates a change request to record the CIs affected. There is no required lead time, and no approvals are required.
Emergency
A change that must be implemented as soon as possible to resolve a P1 or P2 Incident. These are the only changes permitted to be logged after the work is completed, so the focus can be on resolving the P1 or P2 Incident. There is no required lead time, and it requires approval from only 1 member of the Emergency Change Approval group.
Standard
A change that is very low to no risk, is very common, so they are performed frequently, and are easily reversible should it cause an issue. There is no required lead time, and no approvals are required.
Unauthorized
A change that was performed outside of logging a Change Request, and did not receive proper authorization to implement. There is no required lead time, and it requires approval only from the Change Manager.
Informational
A change created when we need to keep track of changes our customers report to us (such as changes made in a shared colocation) or when a vendor is making a change that could impact our customers or our internal environments, and we do not want to suppress the alerts.
Normal
A change that is planned and implemented within the appropriate lead times of two days. This Change Type goes through the full approval process. A Normal change can also be expedited faster than the required two day lead time if necessary.
Types of Changes
Stacy
Created on April 21, 2026
Start designing with a free template
Discover more than 1500 professional designs like these:
View
Akihabara Agenda
View
Akihabara Content Repository
View
Momentum: Tools Tutorial
View
Mind Map: The 4 Pillars of Success
View
Big Data: The Data That Drives the World
View
Internal Guidelines for Artificial Intelligence Use
View
Correct Concepts
Explore all templates
Transcript
Types of Changes
Emergency
Standard
Normal
A change that must be implemented as soon as possible
A change that is very low to no risk
A change that is planned and implemented
+ info
+ info
+ info
Patching
Unauthorized
Informational
A change created to record the activity of routine maintenance patching
A change that is performed outside of logging a Change Request
A change created when we need to keep track of changes
+ info
+ info
+ info
Patching
A change created to record the activity of routine maintenance patching of customer or internal devices. These changes are raised by submitting a Patching catalog request from the Service Now request catalog. This catalog request suppresses alerts during the change window and creates a change request to record the CIs affected. There is no required lead time, and no approvals are required.
Emergency
A change that must be implemented as soon as possible to resolve a P1 or P2 Incident. These are the only changes permitted to be logged after the work is completed, so the focus can be on resolving the P1 or P2 Incident. There is no required lead time, and it requires approval from only 1 member of the Emergency Change Approval group.
Standard
A change that is very low to no risk, is very common, so they are performed frequently, and are easily reversible should it cause an issue. There is no required lead time, and no approvals are required.
Unauthorized
A change that was performed outside of logging a Change Request, and did not receive proper authorization to implement. There is no required lead time, and it requires approval only from the Change Manager.
Informational
A change created when we need to keep track of changes our customers report to us (such as changes made in a shared colocation) or when a vendor is making a change that could impact our customers or our internal environments, and we do not want to suppress the alerts.
Normal
A change that is planned and implemented within the appropriate lead times of two days. This Change Type goes through the full approval process. A Normal change can also be expedited faster than the required two day lead time if necessary.