This article and video explores the different task types available in the Cutover platform, what each of them are and how they can be used in your runbook.
Task Types
When a user creates a task, they must specify the kind of task it is. A number of default task types are made available for all accounts. These task types include:
Task name and icon | Clicks to complete | Task Type Description |
| 2 | A Normal task is an activity assigned to a User or Team(s), with duration. Users start the task with a single click, execute activity, and then complete the task with a single click. |
| 1 | An SMS task has zero duration and can be completed with a single click. When a user has been assigned to an SMS task as a recipient, a message of up to 1600 characters can be created and sent during a run. |
| 1 | A Milestone has zero duration, and is typically used to capture key milestones in your plan. Milestones show up in the runbook dashboard and thus consideration should be given to how you want to make use of this task type for reporting. |
| 2 | A Call task has zero duration and requires the user to click to start and then another click to complete. When a user has been assigned to a Call task as a recipient, a formatted message can be created and spoken over a telephone call |
| 1 | An Email task has zero duration, and can be completed with a single click. When a user, or team, have been assigned to an Email task as a recipient, a formatted message can be created and sent during a run at a specific point in the runbook. Recipients and content are set in the task edit panel, by clicking "Settings". A test message can be sent during the phase if desired. |
| 2 | A Validation task requires a response from the user upon completion that is recorded and enables a result to be captured ie: Pass, Fail, Not Tested, with optional commentary. The Test Summary dashboard captures the result selected for any validation tasks. Users start the task with a single click, execute activity, and then complete the task with a single click, capturing an appropriate response. |
| - | Custom task types can be associated with integrations to over 20 tools. Please reach out to your Customer Success Manager or our Support team, to learn more about this feature. |
| - | Branching tasks allow optional execution of one or more legs, or branches of a runbook. More information can be found here. Note: They are not currently one of the default task types available to users of Cutover. The branching and branch header task types can though be enabled very easily if this is not already available to you. Contact your Customer Success Manager (CSM) or get in touch with our Support team via the in-app chat. Our Support team can also be reached at support@cutover.com. |
| 1 | A Checklist task includes a due date and has zero duration, and is therefore typically used to capture activity such as check-list items you complete before embarking on the core activity of the runbook. |
| - | A Snippet task is a quick way to insert ready-made steps or templates into your runbook. See our Snippets article for more information. |
| - | A linked task type enables you to link runbooks to a parent runbook.
When a linked task type is added to a runbook, it is linked to a template that is then converted to a linked runbook. These runbooks cannot begin until given the command to start from the parent runbook. |
Integration task type Note: Integration tasks display an icon specific to the connected application (e.g., Jira, AWS, Jenkins) so you can easily identify the system being triggered. | - | Integration tasks automatically trigger actions in external systems—such as updating a ServiceNow ticket, starting a Jenkins build, or executing a cloud script—without requiring manual intervention. The task updates its status in real time as the external system completes the work. For more information on integrations, visit our Developer Portal here. |
Changing a task type
Previously, changing a task’s type (for example, from “Normal” to “Validation”) would reset the task duration to the new task type’s default value, overwriting any manually configured duration. This affected both single task edits and bulk edits, particularly in larger runbooks where users needed to change task types without losing time-sensitive duration data.
Manually configured durations are now preserved when switching between non-auto-finish task types. When moving from an auto-finish type to a non-auto-finish type, the duration is reset to the new task type’s default value. Switching to an auto-finish type (such as a Milestone) will set the duration to zero, with a clear informational message explaining why.
Bulk edit now also includes new duration controls:
Unchanged (default) — keeps existing durations as they are
Reset to task type default — applies the new task type’s default duration to all selected tasks
Custom — sets a specific duration across all selected tasks


