The incident management process is how IT teams restore a disrupted service as fast as possible and keep the business impact small. It runs in eight steps: identify, log, categorise, prioritise, assign and escalate, investigate and diagnose, resolve, and close. An impact and urgency matrix sets the priority of each incident, and SLA targets for that priority decide how fast each step must happen. Below you will find the full workflow, a process flow, a priority matrix with example SLA targets, a worked example and the metrics to track.
The 8 steps of the incident management process at a glance
Incident management is the ITIL practice for handling unplanned interruptions to a service, or a drop in its quality. The goal is restoring normal service, not finding the root cause; that is the job of problem management. Here is the workflow most IT teams follow.
| Step | What happens | Who owns it | Output |
|---|---|---|---|
| 1. Identify | The incident is detected by monitoring, a user report, email, phone, chat or the self service portal | Service desk, NOC, monitoring tools | Incident raised |
| 2. Log | A ticket is created with a unique ID, time, source, caller, affected service and description | Service desk agent | Incident record |
| 3. Categorise | The incident is classified by type, service and affected configuration item | Service desk agent | Category and subcategory |
| 4. Prioritise | Impact and urgency set the priority (P1 to P4), which sets the SLA clock | Service desk agent, incident manager for P1 | Priority and SLA target |
| 5. Assign and escalate | The ticket goes to the right group or technician; it escalates if SLA thresholds are near or the fix needs specialists | Service desk lead, resolver groups | Owner assigned |
| 6. Investigate and diagnose | The resolver checks known errors and knowledge articles, gathers detail and finds a fix or workaround | Level 2 or 3 support, vendors | Diagnosis and fix plan |
| 7. Resolve | Service is restored and the resolution steps are recorded | Resolver group | Service restored |
| 8. Close | The user confirms, the closure category is set, and the ticket is closed or linked to a problem record | Service desk | Closed incident, knowledge captured |
Incident management process flow
The flow below shows the main path and the three branches that decide how an incident moves. Use it as a starting point for your own diagram.

Branch 1, major incident: At the prioritise step, a P1 that affects a critical business service moves to the major incident path: an incident manager takes charge, a bridge call starts, and stakeholders get updates on a fixed schedule.
Branch 2, escalation: At assign or diagnose, the ticket escalates functionally (to a more skilled group or a vendor) when first line cannot fix it, or hierarchically (to management) when the SLA is at risk or the impact grows.
Branch 3, not fixed or recurring: At closure, if the user does not confirm the fix, the ticket reopens. If the incident is recurring or the root cause is unknown, it is linked to a problem record for root cause analysis.
Incident workflow vs process. People search for both terms. The process is the set of steps and rules above. The workflow is how those steps run inside your ITSM tool: the states (new, assigned, in progress, on hold, resolved, closed), who can move a ticket between them, and what automation fires at each change.
A worked example: email outage at 9:05 am
Here is how the eight steps play out for a common incident.
- Identify. At 9:05 am, monitoring raises an alert that the mail server is not responding. Within minutes, users start emailing and calling the service desk.
- Log. The first report creates incident INC1042 with the time, source (monitoring alert), affected service (corporate email) and the linked configuration item (mail server). Later user reports are linked to it instead of opening duplicates.
- Categorise. Category: Software, subcategory: Email. Affected service: Corporate email.
- Prioritise. Impact is high (the whole company) and urgency is high (no workaround), so it is P1. The SLA clock starts: response in 15 minutes, resolution target 4 hours.
- Assign and escalate. The ticket routes automatically to the messaging team. Because it is a P1, the incident manager is notified and a bridge call opens.
- Investigate. The engineer finds the mail server’s disk is full after a failed log rotation.
- Resolve. Logs are archived, disk space is freed and mail flow resumes at 10:20 am. Steps are recorded on the ticket.
- Close. Users confirm email works. The ticket closes with closure category ‘Capacity’. Because log rotation failed before, a problem record is raised to fix the root cause, and a knowledge article captures the workaround.
Incident priority matrix and SLA examples
Priority is set from two inputs. Impact is how many users, services or business functions are affected. Urgency is how quickly the business needs it fixed, and whether a workaround exists.
| Impact \ Urgency | High urgency | Medium urgency | Low urgency |
|---|---|---|---|
| High impact (whole organisation or critical service) | P1 Critical | P2 High | P3 Medium |
| Medium impact (a department, site or important service) | P2 High | P3 Medium | P4 Low |
| Low impact (one user or a non critical service) | P3 Medium | P4 Low | P4 Low |
Example SLA targets by priority
These are example targets only. Set yours with the business, based on service hours, contracts and what each service is worth to the organisation.
| Priority | Example | Example response target | Example resolution target | Update frequency |
|---|---|---|---|---|
| P1 Critical | Core banking, ERP or email down for everyone | 15 minutes | 4 hours | Every 30 minutes |
| P2 High | A branch or department cannot work; no workaround | 30 minutes | 8 hours | Every 2 hours |
| P3 Medium | Single service degraded or a workaround exists | 4 hours | 2 business days | Daily |
| P4 Low | One user affected, minor issue | 1 business day | 5 business days | On change |
Major incident management
A major incident is a P1 with serious business impact, such as a full outage of a customer facing service. It needs its own path because normal queues are too slow.
- Named incident manager. One person owns coordination, not the fix.
- Bridge call or war room. Resolvers, vendors and service owners join one channel.
- Scheduled communication. Status updates go to stakeholders and users at a fixed interval, even when there is no news.
- Clear decision rights. Agree in advance who can approve emergency changes or failover.
- Post incident review. Within a few days, review the timeline, what worked and what to change, and raise a problem record for the root cause.
Roles and responsibilities
Clear ownership is what keeps incidents from bouncing between teams.
| Role | Responsibility |
|---|---|
| Requester or end user | Reports the incident, gives details, confirms the fix |
| Service desk (Level 1) | Logs, categorises, prioritises, resolves known issues, routes the rest |
| Resolver groups (Level 2 and 3) | Investigate and fix technical issues; work with vendors |
| Incident manager | Owns the process, major incidents, escalations and reporting |
| Problem manager | Takes recurring or unexplained incidents and finds root causes |
| Service owner | Agrees SLA targets and priority rules for their service |
Incident management vs incident response vs problem management
These three terms are often mixed up. They work together but have different goals.
| Incident management | Security incident response | Problem management | |
|---|---|---|---|
| Goal | Restore service fast | Contain a security threat and preserve evidence | Find and remove the root cause |
| Trigger | Any unplanned disruption or degradation | A suspected security breach or attack | Recurring incidents or one major incident |
| Measure of success | Time to restore, SLA met | Threat contained, impact limited | Fewer repeat incidents |
| Typical owner | Service desk and incident manager | Security team | Problem manager |
Incident management metrics to track
Track a small set of metrics and review them every month. Use the MTTR impact analyzer and the incident response calculator to estimate what faster resolution is worth to your business.
| Metric | What it tells you |
|---|---|
| Mean time to acknowledge (MTTA) | How quickly someone picks up a new incident |
| Mean time to resolve (MTTR) | How long it takes to restore service, by priority |
| SLA compliance rate | Share of incidents responded to and resolved within target |
| First contact resolution | Share fixed by the service desk without escalation |
| Reopen rate | Share of incidents closed too early or fixed badly |
| Incident volume by category | Where recurring issues and problem candidates sit |
| Backlog age | How many open incidents are older than their target |
| Customer satisfaction | How users rate the experience after closure |
Incident management best practices
- Give users one easy way in. A self service portal, email to ticket and a phone line all landing in the same queue.
- Use templates and categories that people understand. Keep the category list short enough that agents pick the right one.
- Agree the priority matrix with the business. Then automate it so priority is not left to each agent’s judgement.
- Route automatically. Rules based on category, location or service send tickets to the right group the first time.
- Build escalation into the SLA. Notify and reassign before a breach, not after.
- Link incidents to configuration items. Knowing the affected asset speeds up diagnosis and shows the impact of changes.
- Turn fixes into knowledge. Save resolutions as articles and suggest them when similar incidents are logged.
- Hand recurring incidents to problem management. Fixing the same incident every week is a cost, not a process.
- Review major incidents. Every P1 gets a short post incident review.
See how Infraon ITSM automates logging, routing, SLA escalation and knowledge suggestions, and how Udaan supports 10,000+ users with 130 technicians. Explore incident management in Infraon ITSM.
Incident management examples by industry
The process is the same everywhere; priorities and constraints change.
- Banking and financial services. Core banking, ATM and payment outages are P1 by default. Audit trails on every incident and strict change control matter for regulators.
- Telecom and ISPs. Network alarms create most incidents. Linking monitoring events to tickets and grouping duplicate alarms keeps the queue usable.
- Government and public sector. Citizen facing portals have fixed service hours and public visibility, so communication during major incidents is as important as the fix. Some agencies need on premise or in country deployment.
- Manufacturing and energy. Plant systems and shared IT and OT networks raise the stakes of downtime. Field technicians and spare parts often need to be part of the workflow.
How Infraon ITSM supports the incident management workflow
Infraon ITSM covers the full incident lifecycle, with features that map to each step. Plan tiers are as listed on the ITSM pricing page.
- Identify and log. Incident management with automatic time and source recording and email to ticket conversion are in Essential; email threading, incident templates on the self service portal and a native mobile app are also included.
- Categorise and link. Configuration items link to incidents so agents see the impacted asset.
- Prioritise and assign. SLA management with response and resolution targets per priority is in Essential, and multiple SLA profiles in Standard. Rule based auto assignment sends tickets to the right group or technician. GenAI ticket routing and prioritisation is included in the Professional plan.
- Escalate. Escalation matrices per business service, auto escalation by priority, and automatic reassignment when an SLA is breached, with notifications by email, SMS and WhatsApp.
- Diagnose. Contextual knowledge base suggestions when an incident is logged (knowledge management is in Essential). Problem management with a visual timeline for root cause analysis, and event correlation, are in Professional.
- Resolve and close. Work logs with a timer, closure categories, automatic knowledge capture from resolved tickets, and configurable dashboards and KPI and SLA reports you can schedule and export.
Plans start at $19 per user per month (Essential), with Standard at $47 and Professional at $57; yearly billing saves 20%, and Enterprise plans with customisation are available on request. Infraon ITSM runs as SaaS or as the Enterprise edition on premise or hybrid, in the country you need, with Arabic language support. Infraon holds ISO/IEC 27001:2022, ISO 20000-1:2018 and SOC 2 Type 2 certification, and is PinkVERIFY verified for 12 ITIL 4 processes.
In practice: Udaan runs Infraon ITSM for 10,000+ users with 130 technicians and helpdesk agents, handling 500+ tickets a day, and its case study credits knowledge base integration with reducing request load. QLM Life and Medical Insurance Company uses GenAI based automated ticket prioritisation and reported 50% to 75% improvement in customer satisfaction.
Infraon ITSM starts at $19 per user per month. Start a 14 day free trial, or book a demo to see the incident workflow on your own use cases.
Frequently Asked Questions
What are the 8 steps of the incident management process?
Identify, log, categorise, prioritise, assign and escalate, investigate and diagnose, resolve, and close. Each step has an owner and an output, and the priority set in step four decides the SLA targets for the rest.
What is the difference between an incident and a problem?
An incident is a single disruption to a service that needs restoring now. A problem is the underlying cause of one or more incidents. Incident management restores service; problem management finds and removes the root cause so incidents stop recurring.
Who owns the incident management process?
The incident manager owns the process, reporting and major incidents. The service desk logs and routes incidents and resolves known issues; resolver groups fix the rest. Service owners agree the priority rules and SLA targets for their services.
How is incident priority decided?
Priority comes from impact (how many users or services are affected) and urgency (how fast the business needs a fix and whether a workaround exists). A priority matrix maps the two to P1 to P4, and each priority has its own response and resolution targets.
What KPIs measure incident management?
The core set is mean time to acknowledge, mean time to resolve, SLA compliance rate, first contact resolution, reopen rate, backlog age and customer satisfaction. Track them by priority and category, and review monthly.
How does ITIL 4 describe incident management?
In ITIL 4, incident management is a practice focused on restoring normal service quickly and limiting business impact. It works closely with problem management, change enablement and the service desk.
What is the difference between incident management and incident response?
Incident management restores IT services after any disruption. Security incident response deals with suspected breaches: containing the threat and preserving evidence. A security event can start in either process, and teams should agree how they hand over between the two.

