On a Normal Change Model what are some examples of the Model Stale Transitions that are defined for the Authorize state?

In the standard ServiceNow Normal Change Model, the 'Authorize' state represents the formal approval stage. From this state, there are three primary transitions defined. If the change is approved, it moves to the 'Scheduled' state to be planned for implementation. If the change is rejected but requires rework, it can be moved back to the 'New' state for the requester to modify and resubmit. If the change is rejected outright or is no longer required, it can be moved to the 'Canceled' state. These transitions represent the key decision outcomes at the authorization phase.

A. The 'Review' state occurs after implementation and cannot be transitioned to directly from 'Authorize'. The 'Draft' state is typically an initial state, not a destination from 'Authorize'.
B. A Normal Change must be scheduled before it can be implemented. Transitioning directly from 'Authorize' to 'Implement' or 'Review' bypasses critical process steps.
D. A change cannot be moved directly to the 'Closed' state from 'Authorize'. The implementation and post-implementation review must be completed first.

1. ServiceNow Product Documentation - Change Management state model and transitions: The official documentation provides a state model diagram and a table detailing the transitions for different change types. For a Normal change

the documented transitions from the 'Authorize' state are to 'Scheduled'

'New'

or 'Canceled'. (ServiceNow Vancouver Release

Doc ID: KB1123423

Section: "Normal change request state model and transitions").

2. ServiceNow Now Learning - ITSM Fundamentals On Demand: The courseware explains the lifecycle of a Normal Change Request. It details that after the 'Assess' state

the change moves to 'Authorize'. Upon approval

it proceeds to 'Scheduled'. If rejected

it can be sent back for rework ('New') or canceled. (Module: Change Management

Topic: Change Models and Lifecycles).