Change flows

---
title: Change flows
description: Change Management change flows provide a library of reusable actions and end-to-end implementations of the change models in the base system.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-service-management/change-management/change-flows.html
release: australia
product: Change Management
classification: change-management
topic_type: concept
last_updated: "2026-09-10"
reading_time_minutes: 2
keywords: [Workflow Editor, Workflow, Flow]
breadcrumb: [Reference, Change Management, IT Service Management]
---

# Change flows

Change Management change flows provide a library of reusable actions and end-to-end implementations of the change models in the base system.

Starting with the Yokohama release, the new base system flows replace the existing workflows for Change Management. However, you can continue to create custom workflows or use the existing ones. To migrate your existing workflows to flows, check the new base system flows available in Workflow Studio for guidance. For any new requirements, use flows.

You can use ServiceNow® Workflow Studio to create, operate, and troubleshoot flows. Workflow Studio is a single interface that provides:

-   Natural language descriptions.
-   Runtime information.
-   Consolidated configuration.

The provided flows are read-only so that they can be upgraded. To change the behavior of these flows, copy the read-only flow and then deactivate it. You do not need to contact Support to deactivate an base system change flow. After you deactivate the read-only flow, only the copied flow is triggered.

You can deactivate an base system change flow directly after you copy it, without logging a support case. To activate the change flows in the base system, contact Support to request activation. For more information on the plugin activation, see [Activate Change Management - Change Flows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/activate-change-flows.md)

.

The following table lists the default change flows.

|Flow|Description|
|----|-----------|
|Change - Cloud Infrastructure - Authorize|Process cloud infrastructure changes for approvals.|
|Change - Emergency - Authorize|Process an emergency change that is in authorize state and is not on hold.|
|Change - Emergency - Implement|Process an emergency change that is in the implement state.|
|Change - Emergency - Review|Process an emergency change in the review state.|
|Change - Normal - Assess|Process a normal change that is in the assess state and is not on hold.|
|Change - Normal - Authorize|Process a normal change that is in the authorize state and is not on hold.|
|Change - Normal - Implement|Process a normal change that is in the implement state.|
|Change - Standard|Process a standard change.|
|Change - Standard - Implement|Process a standard change that is in the implement state.|
|Change - Standard - Proposal|Propose a new standard change template. Handles approvals from draft to published state.|
|Change - Unauthorized - Authorize|Process an unauthorized change for approvals.|
|Change - Unauthorized - Review|Review an unauthorized change.|

-   **[Change Management Workflow Studio actions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/change-flow-actions.md)**  
Use Workflow Studio actions as building blocks to handle the change models and types. The flow actions are available under the ITSM spoke in Workflow Studio.

**Parent Topic:**[Reference section for Change Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/reference-change-management.md)