---
title: Change Management considerations
description: Consider these points while implementing the CSDM framework.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-service-management/change-management/itsm-change-use-case-trouble.html
release: australia
product: Change Management
classification: change-management
topic_type: concept
last_updated: "2026-03-12"
reading_time_minutes: 1
breadcrumb: [Applying CSDM guidelines to Change Management, Configure, Change Management, IT Service Management]
---

# Change Management considerations

Consider these points while implementing the CSDM framework.

-   Business applications not referenced in the Change Management use case: Business applications are portfolio objects you can use for designing and planning an Enterprise Architecture. Business application portfolio objects don't contain version, environment, and localization details for deployments using one or more applications.
-   Change approval process: It depends on how you implement Change Management. After you populate the CIs on the Change form \(if there's a relationship between the CI and the impacted services and service offerings\), the Approval group approves the change.
-   CI attributes used for routing changes: If you are initiating the change or the change task, use the Assignment Group attribute CI. If you are using build run teams, you could use the Support Group attribute CI for the team assignments.

## For more information

[See the video: How Change Management leverages the CSDM](https://www.youtube.com/watch?v=3iCxTeU4ZTA&list=PLkGSnjw5y2U7QNr9jL6TAgwQvYBI_LEtK&index=43)

**Parent Topic:**[Applying CSDM guidelines to Change Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/itsm-change-use-case-product-view.md)