State progression for normal, standard, and emergency changes

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.'

Change type progression

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.

For the state values and descriptions, see State model and transitions

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.

Table 1. Normal change state progression

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

Table 2. Standard change state progression

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

Table 3. Emergency change state progression

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