---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# State progression for change models

# State progression for normal, standard, and emergency changes {#ariaid-title1}

Release version: Australia  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Each change request model progresses through a number of state values in a specific order.

To enable state transitions, you can attach a process with defined conditions to the change model states. For more information, see [Attach a process for Change model states](https://servicenow-prod.fluidtopics.net/zVM1WVPIJYpEGRaFwR_DVw "You can attach a process with defined conditions to the Change model states to enable state transitions.").'

## Change type progression {#normal-standard-emergency-states__section_state_progression_overview}

Each change type progresses through the same states in a different sequence:

* Normal changes progress through all states: New, Assess, Authorize,Scheduled, Implement, Review, and Closed.
* Standard changes are pre-authorized, so they bypass the Assess and Authorize states and move from New to Scheduled.
* Emergency changes bypass the Assess state but still require the Authorize state before scheduling.
{#normal-standard-emergency-states__ul_state_progression_overview}

For the state values and descriptions, see [Legacy: State model and transitions](https://servicenow-prod.fluidtopics.net/eEnXKkuIAPsBuC6J~pHW6A "Change Management offers a state model to move and track change requests through several states.")

## State transition triggers {#normal-standard-emergency-states__section_state_transition_triggers}

A change request moves between states based on defined conditions, user actions, and approval outcomes and not on elapsed time. A change manager attaches a process with the change model states using Workflow Studio or business rules. When the conditions for a state are met, the change request progresses to the next state. For example, when a required approval is granted, or a user submits the change. For
more information on configuration details, see [Attach a process for Change model states](https://servicenow-prod.fluidtopics.net/zVM1WVPIJYpEGRaFwR_DVw "You can attach a process with defined conditions to the Change model states to enable state transitions.").
{#normal-standard-emergency-states__table_bls_cnj_11b__entry__4}

|   | State | Can be canceled? | Diagram |
|-|-|-|-|
| 1. | New | Yes | Figure 1. Normal change state model |
| 2. | Assess | Yes | Figure 1. Normal change state model |
| 3. | Authorize | Yes | Figure 1. Normal change state model |
| 4. | Scheduled | Yes | Figure 1. Normal change state model |
| 5. | Implement | Yes | Figure 1. Normal change state model |
| 6. | Review | No | Figure 1. Normal change state model |
| 7. | Closed | No | Figure 1. Normal change state model |
[Table 1. Normal change state progression]

{#normal-standard-emergency-states__table_bls_cnj_11b} {#normal-standard-emergency-states__table_zfv_rfl_b1b__entry__4}

|   | State | Can be canceled? | Diagram |
|-|-|-|-|
| 1. | New | Yes | Figure 2. Standard change state model |
| 2. | Scheduled | Yes | Figure 2. Standard change state model |
| 3. | Implement | Yes | Figure 2. Standard change state model |
| 4. | Review | No | Figure 2. Standard change state model |
| 5. | Closed | No | Figure 2. Standard change state model |
[Table 2. Standard change state progression]

{#normal-standard-emergency-states__table_zfv_rfl_b1b} {#normal-standard-emergency-states__table_imz_sgl_b1b__entry__4}

|   | State | Can be canceled? | Diagram |
|-|-|-|-|
| 1. | New | Yes | Figure 3. Emergency change state model |
| 2. | Authorize | Yes | Figure 3. Emergency change state model |
| 3. | Scheduled | Yes | Figure 3. Emergency change state model |
| 4. | Implement | Yes | Figure 3. Emergency change state model |
| 5. | Review | No | Figure 3. Emergency change state model |
| 6. | Closed | No | Figure 3. Emergency change state model |
[Table 3. Emergency change state progression]

{#normal-standard-emergency-states__table_imz_sgl_b1b}