<h2>Major Incident Management process</h2><br/><div style="overflow-x:auto"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><meta content="text/html; charset=UTF-8" /><meta name="copyright" content="(C) Copyright 2025" /><meta name="DC.rights.owner" content="(C) Copyright 2025" /><meta name="generator" content="DITA-OT" /><meta name="DC.type" content="concept" /><meta name="DC.title" content="Major Incident Management process" /><meta name="abstract" content="A major incident is a highest-impact, highest-urgency incident that affects a large number of users, depriving the business of one or more crucial services. Given the urgency of the situation, a well-coordinated response process is required to accelerate the resolution and minimize the business impact." /><meta name="description" content="A major incident is a highest-impact, highest-urgency incident that affects a large number of users, depriving the business of one or more crucial services. Given the urgency of the situation, a well-coordinated response process is required to accelerate the resolution and minimize the business impact." /><meta name="DC.relation" scheme="URI" content="../../../product/incident-management/concept/major-incident-management.html" /><meta name="DC.relation" scheme="URI" content="../../../product/it-service-management/reference/r_ITServiceManagement.html" /><meta name="DC.relation" scheme="URI" content="../../../product/incident-management/concept/c_IncidentManagement.html" /><meta name="DC.creator" content="ServiceNow" /><meta name="DC.date.created" content="2023-08-03" /><meta name="DC.date.modified" content="2024-02-01" /><meta name="DC.format" content="XHTML" /><meta name="DC.identifier" content="major-incident-management-process" /><link rel="stylesheet" type="text/css" href="../../../CSS/commonltr.css" /><title>Major Incident Management process</title></head><body id="major-incident-management-process"> <div class="breadcrumb"><a class="link" href="../../../product/it-service-management/reference/r_ITServiceManagement.html" title="The IT Service Management (ITSM) solution provides scalable workflows to manage and deliver IT services to your users all through a single cloud-based platform.">IT Service Management</a> > <a class="link" href="../../../product/incident-management/concept/c_IncidentManagement.html" title="Incident Management restores normal service operation while minimizing impact to business operations and maintaining quality.">Incident Management</a> > </div> <h1 class="title topictitle1" id="ariaid-title1"><span class="ph">Major Incident Management</span> process</h1> <div class="body conbody"><p class="shortdesc">A major incident is a highest-impact, highest-urgency incident that affects a large number of users, depriving the business of one or more crucial services. Given the urgency of the situation, a well-coordinated response process is required to accelerate the resolution and minimize the business impact.</p> <div class="p">The goal of an organization is to have an effective and efficient system for responding to major incidents. The requirements are to:<ul class="ul" id="major-incident-management-process__ul_qqr_sy2_ndb"><li class="li">Minimize the impact of service interruptions.</li><li class="li">Ensure that an appropriate Incident Manager/Major Incident Team/Management Group are in place to manage a major incident.</li><li class="li">Ensure that stakeholders are well-informed of service interruptions, degradations, and resolutions.</li><li class="li">Conduct a review of each major incident once service is restored. Its purpose is to analyze the incident, and understand what can be done to prevent a similar incident in the future. This review also provides an opportunity to evaluate the incident response process and identify areas for improvement.</li><li class="li">Create a problem for root cause analysis.</li></ul> </div> <div class="p">Keeping the goals in mind, a major incident management process can be broadly classified into the following phases:<dl class="dl"> <dt class="dt dlterm">Identification</dt> <dd class="dd">The first step in the process is to identify a potential major incident. A potential major incident can be identified automatically based on trigger rules or an existing incident can be proposed as a major incident candidate. These incidents are classified as major incident candidates and are reviewed by major incident managers who initiate the major incident response process.</dd> <dt class="dt dlterm">Communication and Collaboration</dt> <dd class="dd">Timely communication during a major incident is crucial to ensure that the IT teams, business stakeholders, end users, and customers are informed about the impact and progress of the incident. An occurrence of a major incident requires a comprehensive communication plan that includes who is contacted, the methods and frequency of communication, messaging, and so on. The communication plan enables the incident response team to focus their efforts on the resolution process and sets expectations for any future communications.<p class="p">You can define one or more communication plans based on the type, priority of the incident, or the target audience. For example, communication plans for a P1 major incident could have more frequent communication than a communication plan for a P2 major incident.</p> <p class="p">Throughout the life cycle of the major incident, notifications and status updates are sent to the stakeholders to keep them informed and involved.</p> </dd> <dt class="dt dlterm">Resolution</dt> <dd class="dd">In this phase, the agreed upon path to resolution is followed to resolve the issue. Resolving a major incident resolves all associated child incidents, and the individual callers receive a notification about incident resolution.</dd> <dt class="dt dlterm">Post incident review</dt> <dd class="dd">This is the final phase of a major incident life cycle. After the major incident is resolved, a post-incident review is conducted. Its purpose is to analyze the incident and understand what can be done to prevent a similar incident in the future. This review also provides an opportunity to evaluate the incident response process and identify areas for improvement. <p class="p">To streamline the process, a post-incident report is created when an incident is resolved. The post-incident report can be reviewed and updated during the review process before it is shared with stakeholders.</p> </dd> </dl> </div> <p class="p">A major incident progresses through different states during its life cycle. The following diagram illustrates the different states involved in a major incident management:</p> <div class="p"><div class="fig fignone" id="major-incident-management-process__fig_lvg_gsg_hdb"><span class="figcap"><span class="fig--title-label">Figure 1. </span>Major Incident Management state flow</span> <img class="image" id="major-incident-management-process__image_mvg_gsg_hdb" src="../image/mim-process-flow.png" alt="Major incident management state flow" /> </div> </div> </div> <div class="related-links"> <div class="familylinks"> <div class="parentlink"><strong>Parent Topic:</strong> <a class="link" href="../../../product/incident-management/concept/major-incident-management.html" title="A major incident (MI) is an incident that results in significant disruption to the business. A major incident demands a response beyond the routine incident management process. Major incidents have a separate procedure with shorter timescales and higher priority, so that there is a faster resolution process for incidents with high business impact.">Managing major incidents</a></div> </div> </div></body></html></div>