---
sourceDocument: Brazil IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Incident life cycle

# Incident life cycle {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Incident Management manages incidents through a defined set of states, from creation to closure, so you can track where each incident is in its life cycle.  
Each incident moves through a set of states in the Incident Management process, as shown in the following diagram:Figure 1. Incident management state model flow  
Note:  
The state names in the diagram correspond to the states described in the following table.  
{#c_IncidentManagementStateModel__table_t51_21c_b5__entry__2}

| State | Description |
|-|-|
| New | Incident is logged but not yet investigated. |
| In Progress | Incident is assigned and is being investigated. |
| On Hold | The responsibility for the incident shifts temporarily to another entity to provide further information, evidence, or a resolution. When you select the On Hold option, the following On hold reason list appears. * Awaiting Caller * Awaiting Change * Awaiting Problem * Awaiting Vendor {#c_IncidentManagementStateModel__ul_ixw_vbx_5zb} If the On hold reason is Awaiting Caller, the Additional comments field becomes required. Note: If the caller updates the incident, the On hold reason field is cleared and the state of the incident is changed to In Progress. An email notification is sent to the user whose name is mentioned in the Assigned to field and to the users in the Watch list. An incident can be placed in the On Hold state one or more times before being closed. |
| Resolved | A satisfactory fix is provided for the incident to help keep it from recurring. |
| Closed | Incident is marked Closed after it is in the Resolved state for a specific duration and it is confirmed that the incident is satisfactorily resolved. |
| Canceled | Incident is triaged but found to be a duplicate incident, an unnecessary incident, or not an incident at all. |
[Table 1. Incident states]

{#c_IncidentManagementStateModel__table_t51_21c_b5}

