Emergency changes bypass parts of the standard change process when there is insufficient time for the usual assessment, approval, and scheduling. Urgency is exactly what makes emergency changes risky.
The emergency change control process exists to keep speed from turning into chaos: a lighter, faster route through Change Management that still keeps structure, accountability, and a way to roll things back if the fix makes matters worse.
Here's how that process works, what ITIL recommends, and the practices that stop emergency changes from becoming a habit.
Change in ITIL
Change management is a process used to ensure that a change within the IT infrastructure is handled with the least disruption to IT services and the least impact on the business processes. From an ITIL perspective, change can be anything from migrating to a different service desk solution or a shift from on-premise infrastructure to cloud.
There are different change categories with different steps, starting with submission, where change requests are made and tickets are created, and ending with closure, where the change is marked as successful, failed, or incomplete. After submission is the planning stage, where the expected time, service disruptions, etc. are calculated and conveyed to the stakeholders. The plan is further approved by the change advisory board in the next stage, following which the change is implemented. After this comes the review stage where any issues that arose during implementation are fixed out, following which comes the closure stage.
Since ITIL 4, change management became change enablement. The name change signified how the responsibility for the change was shared among all the employees of the organization and how instead of managing the change, employees were empowered to make the change themselves.
When does a change become an emergency change?
An emergency change is a change that cannot wait for the standard change process without creating unacceptable risk or impact. A major service outage, an actively exploited vulnerability, or a failed deployment affecting a critical service can all require immediate action.
ITIL generally distinguishes three types of change:
- Standard change: A low-risk, routine change with a known outcome and a documented, repeatable procedure. Examples include routine software patches, hardware replacements, and other recurring maintenance.
- Normal change: A change that requires assessment, planning, and authorization because it is not routine and carries risks that need to be evaluated. Normal changes can range from relatively low-impact changes to major changes with significant risk or business impact.
- Emergency change: A change that must be implemented quickly because delaying it could cause significant service disruption, security exposure, or other serious impact. The process is accelerated, with appropriate controls maintained where time allows and a review conducted afterward.
Emergency changes may involve less testing or a shorter approval path because there is no time for the full process. That increases the risk, which is why organizations need clear criteria for declaring an emergency change and a defined process for handling and reviewing it.
What does ITIL recommend for handling emergency changes?
According to ITIL, the process for emergency change should begin just like any other change - by creating a request for change. The change manager will bring this to the attention of the ECAB or Emergency Change Advisory Board. This will be composed of members of the Change Advisory Board who are available and have the expertise and authority to make decisions regarding the change.
The ECAB members are responsible for weighing the risks of implementing the proposed change as an emergency change and the risks of delaying the change and implementing it as a normal one. In some cases, if the risks outweigh the benefits, the ECAB may decide to proceed with the change as a normal one.
If ECAB approves the change, the change owner will plan and design the change. They’re also responsible for building and testing the change if required. Once tested, the change owner will coordinate the implementation of the change. The configuration management database is updated to reflect the changes during the implementation phase.
Once implemented, the change owner will review to mark it as a success or a failure.
If failed, the change owner will initiate the back-out process. Back-out is an element that is rather unique to emergency changes. It is used to bring the systems back to the initial state if the change fails, or if the change presents new risks or issues.
In practice, this means that the emergency change is handled like an accelerated version of a normal change. Since it won’t be expected or routine, you’ll need unique approaches to tackle the change. But because of the time constraint, the approval and testing will be limited. And often a higher level of risk will be accepted by the ECAB, as the delays may prove costly.
How to handle an emergency change in InvGate Service Management
The process above is the theory. Here's how it plays out in practice when the tool is doing the work of moving an emergency change from request to resolution — with the ECAB approval kept fast without losing the paper trail.
-
1Log the change. Create the change request with the details of what needs to happen and why. There's no need to pre-label it as emergency here; the workflow will make that call a step later, based on evidence rather than the requester's judgment.
-
Run the Risk and Impact Assessment. The workflow's assessment step scores the change on how much risk it carries and how much is at stake if it's delayed. AI Hub's predictive risk and impact analysis can feed this step, giving a faster read on likely blast radius so the score reflects more than a manual guess.
- Let the conditional route it. Based on the assessment result, a single conditional branches the change down one of two paths: a high-risk, can't-wait result routes it to the Emergency Change Advisory Board (ECAB); anything below that threshold goes to the standard Change Advisory Board (CAB) on the normal path.
- Implement and record the work. Once approved, the change owner carries out the fix and the workflow moves into implementation. As they go, the request keeps the record — what was done, by whom, and when — so the account of the change stays complete even though testing and planning were compressed for speed.
- Review, then roll back if needed. After implementation, the change is marked a success or a failure in the review step. If it failed or created new problems, the back-out plan returns systems to their previous state — the safety net that matters most when testing was cut short for speed.
Best practices for handling emergency change
Effective emergency change management requires clear criteria, defined responsibilities, and a process that allows teams to act quickly without losing control. The following best practices can help organizations manage emergency changes while keeping risks in check.
1. Set standards for classifying changes as emergency or normal
One of the main challenges in Change Management is deciding when a change qualifies as an emergency. Some cases are straightforward: mitigating an active cyberattack is clearly an emergency, while deploying a routine feature update is generally a normal change.
The distinction becomes less clear when a feature update is blocking a key business process, for example. Organizational practices can also blur the boundaries. If the Change Advisory Board (CAB) meets only once every two months, requesters may start submitting every change as an emergency to avoid long approval delays.
Since emergency changes prioritize speed, they carry additional risks. Establish clear criteria for what qualifies as an emergency and communicate them across the organization. This helps prevent the emergency process from becoming a shortcut for bypassing normal Change Management.
2. If there are way too many emergency changes, you need to understand why
A high volume of emergency changes can expose the organization to unnecessary risks. Over time, the cost of those risks may outweigh the benefits of implementing changes quickly. Monitoring change activity across the organization helps identify whether emergency changes are being used appropriately.
Track the number of normal, standard, and emergency changes, their success rates, and how many emergency requests genuinely met the criteria. Also assess whether the risks taken were justified by the situation.
If emergency changes are too frequent, investigate the underlying causes. The organization's culture may reward speed at the expense of risk assessment, or a temporary situation, such as a series of targeted cyberattacks, may be driving the increase.
The long-term goal should be to reduce unnecessary emergency changes without discouraging their use when they are genuinely needed. Treating every change as normal can also be costly if it delays the restoration of critical services.
3. Make sure the ECAB team has the expertise and authority for approving the change
It’s relatively easy to build a CAB with members having the relevant expertise and authority for the change, but it requires a bit more effort for ECAB. When speed is important, it may not be easy to get all the members of CAB to discuss and approve the change - hence the ECAB. But this does not mean people without the expertise should make the decision.
It may be a good idea to form a clear picture of the chain of command and field of expertise among the CAB so that everyone knows who is absolutely necessary to form the ECAB for the specific emergency. For example, in the case of isolating a network to mitigate a cyberattack, network engineers may be important.
And at the same time, it would be prudent to not rely on one single person for expertise on a subject. Emergency changes should not be delayed just because of the absence of one person.
4. Fix first, but document the change afterward
When delays can cause significant damage, teams need to identify and deploy a solution as quickly as possible. Although documenting the change and assessing its impact are important, the immediate priority is to contain the problem and restore services.
Focus first on defining the solution, assessing the most immediate risks, and planning its implementation. Once the change is in place, document what was done, why it was necessary, and which components were affected.
Keeping these records up to date supports ongoing maintenance, future troubleshooting, and coordination among IT support teams.
5. Don’t forget to communicate
During an emergency, teams naturally prioritize implementing the fix and restoring services. Communication can seem secondary when every minute counts, but neglecting it can create additional problems. Employees may keep reporting an issue that is already being addressed, stakeholders may make decisions based on outdated information, and support teams may struggle to handle questions from affected users.
Keep relevant stakeholders informed throughout the process, even if updates are brief. Explain what prompted the change, what is being done, which services may be affected, and when users can expect further information. Once the emergency is resolved, share the outcome and document any remaining impact.
“Your approach to managing the change shouldn't be drastically different than your typical change management process. The major difference is how quickly communication of a change needs to take place.Communicate as early as possible. Communicate clearly. Communicate in a way that provides context as to WHY the change is urgent, and WHY the change is necessary. And finally, be sure to communicate when the change is complete and the emergency is mitigated.”
Ema Roloff, Director at Naviant, expert in Change Management and digital transformation
Frequently Asked Questions
What are the different types of change according to ITIL?
The three types of changes are normal, standard, and emergency changes. Standard changes are carried out often, they’re predictable and often follow a set of repeatable steps. Normal changes are planned changes, but require a specific and unique approach, and are not routine. Emergency changes are similar to normal changes but are in response to something that requires immediate attention, such as security issues. They’re often executed on a shorter timeframe compared to other changes.
When does a change become an emergency change?
When a change has to be executed in a short time frame, when delays can be costly to the business, the change becomes an emergency change. They’re necessary to ensure service continuity and uninterrupted service delivery.
What is the ECAB?
The Emergency Change Advisory Board (ECAB) is a group authorized to assess and approve emergency changes when there is not enough time to follow the normal Change Advisory Board (CAB) process. It typically includes the people needed to make a rapid decision based on the change’s urgency, risk, and potential impact.