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

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Create a Change model

# Create a Change model {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read  
Depending on your requirements, you can create a Change model and configure the
states and transitions for a specific use case.

## Before you begin

Role required: change_manager

## Procedure

1. Navigate to AllChangeAdministrationChange Models.
2. Click New.
3. On the form, fill in the fields.  
   {#create-a-change-model__table_ijj_ytc_xnb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Unique name for the Change model. |
   | Default Change Model | Option for enabling the Change model as a default model on the Change request form. |
   | Active | Option for enabling that this model is available for selection when creating a Change request. |
   | Color | Color that appears on the left side of the Change model bar on the Models tab in the Change landing page. |
   | Available in 'Create New' | Option for enabling that this model is available for selection on the Models tab on the Change landing page. Also, the model will be available to select in the Model field on the Change request form. |
   | Description | Detailed description of the Change model. |
   | Implementation states | Implementation state for the Change model. For more information on states, see [State model and transitions](https://www.servicenow.com/docs/cnxtVt6QhT58mZrAcXD0Vw "Change Management offers a state model to move and track change requests through several states."). If you are using Mass CI Update with Change Models ensure the Implementation states field in the model is set to the state in which you want the changes to take effect. |
   | Record Preset | Preset values for all changes using this model. |
   | Advanced Security | Option to enable role-based access controls and user criteria to tailor the Change creation landing page views. When you enable Advanced Security, Available For, Not Available For, and Can write tabs appear next to Model States tab. |
   | Read Roles | Option to define the roles to view the Change model. |
   | Write Roles | Option to define the roles to edit the Change model. |
   [Table 1. Change Model form]

   {#create-a-change-model__table_ijj_ytc_xnb}
4. Click the form context menu icon (![Form context menu icon.]()) and select Save.  
   The Model States context menu appears. You can select the states for your Change model.
5. Click New.
6. On the form, fill in the fields.  
   {#create-a-change-model__table_ijp_mcv_znb__entry__2}

   | Field | Description |
   |-|-|
   | State | State that you want to include in your model. |
   | Initial State | Option to enable this state as the initial state for your model. This field is automatically selected when you add the first state to your model. |
   [Table 2. Model State form]

   {#create-a-change-model__table_ijp_mcv_znb}
7. To save the state and return to the Change Model form, click Submit.
8. To add a transition between the states, click the display/hide hierarchical lists icon (![Display/hide hierarchical lists icon.]()) for the model state that you want to apply the transition to.  
   The Model State Transitions context menu appears.
9. Click New.
10. On the form, fill in the fields.  
    {#create-a-change-model__table_aq3_n2v_znb__entry__2}

    | Field | Description |
    |-|-|
    | From | State that the Change request is moving from. |
    | To | State that the Change request is moving to. |
    | Automatic Transition | Option for enabling automatic transition to the Change request when the defined conditions are met. Selecting this option also prevents you from manually selecting the State field on the Change request form. |
    [Table 3. Model State form]

    {#create-a-change-model__table_aq3_n2v_znb}
11. Click the form context menu icon (![Form context menu icon.]()) and click Save.  
    The Model State Transition Condition context menu appears.
12. Click New.
13. On the form, fill in the fields.  
    {#create-a-change-model__table_ybk_z2v_znb__entry__2}

    | Field | Description |
    |-|-|
    | Name | Unique name for the condition. |
    | State Transition | State that you're applying the transition condition to. This field is automatically set with the state that you're applying the condition to. |
    | Description | Detailed description of the condition. |
    | Requires | Condition for your transition. You can select a pre-defined condition, such as Mandatory Fields to require that specified fields are populated before the model state transitions, or select Transition Condition to define a more granular condition. To create pre-defined conditions, see [Create predefined conditions](https://www.servicenow.com/docs/5WJJNVu8IuPH3CoK5HAZPw "Create predefined transition conditions to reuse the conditions for your Change models."). |
    | Condition (condition builder) | Condition on the Change request that must be fulfilled to enable the transition. |
    | Condition (script) | Script that must be fulfilled to enable the transition. The script returns a value of True when passed. |
    | Active | Option to make the condition active. |
    [Table 4. Model State Transition Condition form]

    {#create-a-change-model__table_ybk_z2v_znb}
14. Click Submit.
15. Select Available For tab.
16. Select New to add the list of users who can access the Change model
17. On the form, fill the fields.  
    {#create-a-change-model__table_ryj_1mj_bwb__entry__2}

    | Field | Description |
    |-|-|
    | Name | Unique name for the user criteria record. |
    | Active | Option to make the condition active. |
    | Users | Option to select the users who can access the Change model. |
    | Groups | Option to select the groups who can access the Change model. |
    | Roles | Option to select the role who can access the Change model. |
    | Companies | Option to select the companies who can access the Change model. |
    | Locations | Option to select the location of the company who can access the Change model. |
    | Departments | Option to select the departments who can access the Change model. |
    | Match All | Option to use the Change model if it meets all conditions in the user criteria. |
    | Advanced | Option to create a script to meet the condition for user criteria. |
    [Table 5. User Criteria record]

    {#create-a-change-model__table_ryj_1mj_bwb}
18. Select Submit.
19. Manage the users to access the change model by providing the user access in Not Available For, Available For, and Can Write tabs:  
    * Available For -- Provides the access for the change model
    * Not Available For -- Doesn't provide the access for the change model
    * Can Write -- Provides the editable access to the change model

    {#create-a-change-model__ul_ff1_3mf_fwb}

    For more information on user access, refer [Create a user criteria record for Change Management](https://www.servicenow.com/docs/l1gWBIZsV3OjoqLRZwO1Eg "Create a user criteria record to control user access to widgets.").
20. Select Submit.
* **[Create predefined transition condition types](https://www.servicenow.com/docs/5WJJNVu8IuPH3CoK5HAZPw)**   
  Create predefined transition conditions to reuse the conditions for your Change models.
* **[Attach a process for Change model states](https://www.servicenow.com/docs/CGHWKkDsNxSP4tcCKzhJ_w)**   
  You can attach a process with defined conditions to the Change model states to enable state transitions.

*[\>]: and then