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


---

# Change templates

# Change templates {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Standardize the creation of change requests by creating change templates based on all available change models.

Users with the change_manager roles or with write access to change models can create change templates.

Change templates streamline the process of creating common change records by providing users with predefined data for specific fields in common types of change requests. Templates reduce repetitive manual effort and enforce
consistency and accuracy.

You can create templates for specific change models, add change request fields, define the information in the fields, and set them as read-only or required using field policies.

For more information, see [Create and propose a change template](https://servicenow-prod.fluidtopics.net/kp~dpiwKPH2o8r5cKIH4cw "Create, customize, and then propose for publication a change template aligned to a change model to make change creation faster, and promote data quality and consistency.").

You can create different template categories and group templates under specific parent and child categories. This categorization does not affect existing standard change categories.

View template metrics to analyze the usage and efficiency of the templates created using each model. On the Change Template Overview page, you can view the usage statistics for all active change templates.
**Related concepts**   

* [Enhanced change data model](https://servicenow-prod.fluidtopics.net/lOtKgKypeExydQilr~ldSg "The enhanced Change data model supports better categorization, change model linkage, and role-based access to change templates. This new data model does not impact the existing standard change catalog and no migration of existing standard changes is required.")  
**Related tasks**   

* [Configure template categories](https://servicenow-prod.fluidtopics.net/M5RWCL2wP~Cw_cT14NjWdA "Create template categories and child categories to classify templates based on a change model, template usage, and organizational areas like software or security.")