---
title: Create a Change model
description: Create change models to configure the states and transitions to match your organization's change processes.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/it-service-management/change-management/create-a-change-model.html
release: brazil
product: Change Management
classification: change-management
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 4
breadcrumb: [Configure, Change Management, IT Service Management]
---

# Create a Change model

Create change models to configure the states and transitions to match your organization's change processes.

## Before you begin

Role required: change\_manager

## Procedure

1.  Navigate to **All** > **Change** > **Administration** > **Change Models**.

2.  Select **New**.

3.  On the form, fill in the fields.

<table id="table_ijj_ytc_xnb"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Name

</td><td>

Name of the change model, based on the process that the model represents. For example, you can create the following change models:-   Normal
-   Standard
-   Emergency


</td></tr><tr><td>

Default Change Model

</td><td>

Option for enabling the change model as a default model on the change request form.

</td></tr><tr><td>

Active

</td><td>

Option for making the model available for selection when creating a change request.

</td></tr><tr><td>

Color

</td><td>

Color that appears on the side of the change model bar on the **Models** tab in the change landing page.

</td></tr><tr><td>

Available in 'Create New'

</td><td>

Option for making this model available for selection on the **Models** tab on the change landing page and in the **Model** field on the change request form.

</td></tr><tr><td>

Description

</td><td>

Detailed description of the change model.

</td></tr><tr><td>

Implementation states

</td><td>

Implementation state for the change model. For more information on states, see [State model and transitions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/c_ChangeStateModel.md).If you are using Mass CI Update with change models, verify that the **Implementation states** field in the model is set to the state in which you want the changes to take effect.

</td></tr></tbody>
</table>4.  On the **Security** tab, fill in the fields.

<table id="table_dyx_l11_g3c"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Advanced Security

</td><td>

Option to enable role-based access controls and user criteria to tailor the Change creation landing page views. When you enable Advanced Security, the **Not Available For**, **Available For**, and **Can Write** tabs appear next to the **Model States** tab in the related lists.For more information on managing user access to the change model, see [Create a user criteria record for Change Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/create-user-criteria.md).

</td></tr><tr><td>

Available For

</td><td>

Users with access to the change model.

</td></tr><tr><td>

Not Available For

</td><td>

Users with no the access to the change model

</td></tr><tr><td>

Can Write

</td><td>

Users with write access to the change model.

</td></tr><tr><td>

Read Roles

</td><td>

Roles that can view the change model.

</td></tr><tr><td>

Write Roles

</td><td>

Roles to edit the change model.

</td></tr></tbody>
</table>5.  Provide standard information for specific fields to be available for a new change request created using the model.

    If you set a preset for the model, the value becomes read-only for change records created using the model.

    1.  On the **Preset Management** tab, select the **Apply record preset** check box.

    2.  Select the record preset from the list, and then select the relevant option for the chosen preset.

    3.  Select the fields from the list, and then select the relevant value for the chosen field.

    4.  Select **Submit**.

6.  On the **Template Management** tab, fill in the fields.

<table id="table_wr2_xb1_g3c"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Who can propose Templates

</td><td>

Users allowed to propose templates using this change model. The available options are:-   Anyone who can modify this model
-   Anyone who can read this model


</td></tr><tr><td>

Template approval users

</td><td>

Users who can approve templates proposed using this change model.

</td></tr><tr><td>

Template approval groups

</td><td>

User groups that can approve templates created using this change model.

</td></tr></tbody>
</table>7.  Select **Submit** to save the change model with the details provided.


## What to do next

Configure states for the change model you create. For more information, see [Configure change model states](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/configure-change-model-states.md).

Manage the templates created using the change model through options in the **Change Templates** tab. For more information, see [Create and propose a change template](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/create-change-template.md).

Configure categories that help classify available templates on the Create a change request page. For more information, see [Configure template categories](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/configure-template-categories.md).

-   **[Configure change model states](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/configure-change-model-states.md)**  
Configure states for change models and define transition between multiple states.
-   **[State field policies for change models](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/state-field-policies-change-models.md)**  
Use state field policies to make change request fields mandatory or read-only at each state in a change model. Policies are enforced on the form when a change request is created or updated.
-   **[Change model attributes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/change-model-attributes.md)**  
Change model attributes are tags that you assign to states in a change model. Scripts can check which attributes are present in the current state of a change and turn functionality on or off for that state.
-   **[Create predefined transition condition types](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/create-predefined-transition-condition-type.md)**  
Create predefined transition conditions to reuse the conditions for your change models.
-   **[Model script editor role](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/model-script-editor-roles.md)**  
This role grants write access to the scripted condition fields on model state transition conditions and model condition types.
-   **[Attach a process for Change model states](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/attach-process-change-model.md)**  
You can attach a process with defined conditions to the change model states to enable state transitions.
-   **[Create and propose a change template](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/create-change-template.md)**  
Create, customize, and then propose a change template for any change model to standardize common change requests so that users don't have to create them manually.

**Parent Topic:**[Configuring Change Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/configure-change-management.md)