--- title: Create a change task in Service Operations Workspace description: When you need to engage another team or agent for help, create and assign change task. For example, there can be tasks to plan the change, implement the change, and test, and review the work. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-service-management/service-operations-workspace/create-change-task-sow.html release: australia product: Service Operations Workspace classification: service-operations-workspace topic_type: task last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Change Management in Service Operations Workspace, Operating IT services in your organization, Service Operations Workspace for ITSM, IT Service Management] --- # Create a change task in Service Operations Workspace When you need to engage another team or agent for help, create and assign change task. For example, there can be tasks to plan the change, implement the change, and test, and review the work. ## Before you begin Role required: itil or admin ## Procedure 1. Open a change request. 2. On the change record page, Click the more actions icon \(\[Omitted image "more-actions-icon.png"\] Alt text: more actions icon\) and select **Create Change Task**. 3. In the Create Change task dialog box, select the task type. By default, the following task types are available. To create additional task types, see [Create a task type for problem or change in Service Operations Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/service-operations-workspace/create-task-type-sow.md). - Planning - Implementation - Testing - Review 4. Click **Create**. 5. On the form, fill in the fields.
Name Definition
Short description A summary of the task.
Description Detailed description of the task.
Number Auto-generated identification number for the task.
Change request Associated change request.
State State of the change task:- **Pending**: Open and unassigned - **Open**: Open and unassigned - **In progress**: Open and actively being worked on - **Closed**: Inactive and closed. Requires close code and close notes to be provided. - **Canceled**
Configuration item Configuration item \(CI\) or service that the change task applies to.
Type Type of change task, **Planning**, **Implementation**, **Testing**, or **Review**. The default workflow generates tasks in type **Review**.
On hold Option to indicate whether the change task is on hold. Provide an **On hold reason** if a change task is placed on hold.
Assignment
Assignment group Group that the change task is assigned to.
Assigned to User that the change task is assigned to. If an assignment rule applies, the change task is automatically assigned to the appropriate user or group.
Schedule
Planned start date Date you plan to begin working on the task.
Planned end date Date the change task is planned to be completed.If the task type is **Implementation**, the **Planned start date** and **Planned end date** values must fall within the planned start and end dates specified in the change request.
6. Click **Save**. **Parent Topic:**[Change Management in Service Operations Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/service-operations-workspace/change-sow.md) **Related topics** [Create a change request in Service Operations Workspace]() [Work on a change request in Service Operations Workspace]() [Standard change catalog]() [Work on a change task in Service Operations Workspace]() [Create a Change Advisory Board \(CAB\) definition]() [Create a CAB meeting]() [Conduct a CAB meeting in the CAB workbench]()