---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Checklist Task activity

# Checklist Task activity {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Checklist Task activity

The Checklist Task activity in ServiceNow Playbooks prompts agents to complete all items in a task checklist.
It is designed to help manage and track checklist items within tasks, ensuring that essential steps are completed systematically.
Show full answer Show less  
This activity is available as a common activity and can be added to a playbook by users with admin, playbook.admin, or pdauthor roles.

## Key Features

* **Inputs Configuration:** Configure key inputs such as Checklist Owner, Checklist Items, and Checklist Name to define the checklist details.
* **Common Properties:** Set activity properties including the title (Label), description, run conditions, and scheduling rules that determine when the activity or stage runs.
* **Scheduling Options:** Choose start rules for when the stage or activity begins---either when the process or stage starts, or after specific stages or activities finish. Optionally, add delays before running.
* **Advanced Inputs:** Enable users or groups to skip the activity if Can Skip is enabled by specifying Skip Assignment Group or Skip Assigned To.
* **Task Association:** Link the checklist to a specific task record so the checklist appears on that task. When associated, the checklist state persists across playbook runs; otherwise, new private tasks are created each run.
* **Show SLA:** Optionally display SLA countdown details for the task to monitor time-sensitive activities.
* **Outputs:** The activity outputs a Checklist Task reference, providing the associated task record for use in subsequent playbook activities.
* **UI Layouts:** Customize how the activity appears during playbook execution for better user experience.

## Practical Benefits for ServiceNow Customers

* Streamlines task completion by breaking down work into manageable checklist items assigned to a specific user.
* Provides flexibility in workflow design by allowing conditional execution, scheduling, and skip options tailored to organizational needs.
* Ensures visibility of checklist progress directly within task records, improving tracking and accountability.
* Supports integration with SLAs to help meet service commitments.
* Enables seamless data transfer between playbook activities through defined outputs, supporting complex workflows.  
Prompt an agent to complete all items in a task checklist.
The key inputs for this activity are the Checklist Owner, Checklist Items, and Checklist Name fields under the [Inputs](https://www.servicenow.com/docs/e8jPfEDyGd84Hwh1s4DebA#checklist-task-activity__table_cjj_sr3_plb) section.

## Roles and availability {#checklist-task-activity__section_pwq_rb5_kcb}

This activity is available as a common activity. Users with the admin, playbook.admin, or pd_author can add this activity to a playbook.

## Common properties {#checklist-task-activity__section_yb4_zq3_plb}

These properties are common to all to activities in Playbooks.  
Open the activity properties panel and configure your activity to add values for the following inputs. If the input value varies, use the pill-picker to show where to get the value. To learn more about the pill-picker, see [Dot-walking examples](https://www.servicenow.com/docs/access?context=dot-walking-examples&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US). {#checklist-task-activity__table_ajt_sr3_plb__entry__3}

| Input | Type | Description |
|-|-|-|
| Label | String | Title to display as activity and playbook card. |
| Description | String | Information to display about activity usage or outcome. |
| Run condition | Condition Builder | Conditions that must be met to run an activity or stage. You can use data from prior activities to build conditions. Note: Select Show additional options to see this field. |
| Start Rule | Choice | Under ScheduleStart Rule, select a start rule for when your stage should start running: * When process starts: Your stage starts running as soon as the playbook starts. * After specific stages: Your stage starts running after specified stage(s) have finished running. {#checklist-task-activity__ul_f4z_nq1_ppb}Under Schedule \> Start Rule, select a start rule for when your activity should start running: <!-- --> * When stage starts: Your activity starts running as soon as its stage starts running. Your stage starts running when your playbook is triggered. * After specific activities: Your activity starts running after specified activities have finished running. {#checklist-task-activity__ul_zzc_3ls_m1c} |
| Start with delay | True/False | Option to wait for a duration of time before running an activity or stage. When enabled, this input displays the [Start with delay input properties](https://www.servicenow.com/docs/EdInaaLAHZCnrBcJbs96Lw "Specify a duration of time to wait before running an activity or a stage whose start rule and conditions have been met. Give users time to act during automated playbooks. Give users time to wait for a specific date and time to complete actions."). Note: Select Show additional options to see this field. |
[ ]

{#checklist-task-activity__table_ajt_sr3_plb}

## Inputs {#checklist-task-activity__section_bgh_1r3_plb}

After configuring the required inputs for your activity, you can also choose to configure additional inputs. In the side panel, select Show additional options to display these advanced inputs. For more information, see [Activity experience](https://www.servicenow.com/docs/aEvbv54ObgcCjjhXabvx8w#activity-definitions__activity-experience). {#checklist-task-activity__table_cjj_sr3_plb__entry__3}

| Input | Type | Description |
|-|-|-|
| Skip Assignment Group | Reference.Group \[sys_user_group\] | Group that is allowed to skip this activity when Can Skip is enabled. Note: If Can Skip is enabled, and you do not specify a Skip Assignment Groupor Skip Assigned To, all users will be able to skip this activity. |
| Skip Assigned To | Reference.User \[sys_user\] | User that is allowed to skip this activity when Can Skip is enabled. Note: If Can Skip is enabled, and you do not specify a Skip Assignment Groupor Skip Assigned To, all users will be able to skip this activity. |
| Checklist Owner | Reference.User \[sys_user\] | The user who owns this checklist. |
| Checklist Items | String | The items you want display in your checklist. |
| Checklist Name | String | The name to display for the checklist. |
| Task | Reference.Task \[task\] | Reference a record to associate with the checklist activity. The checklist is also displayed in the associated task record. Note: When a specific task record is associated with the checklist, the state of the checklist does not change if you run the playbook again. When you don't provide a specific task record, a new private task record is created for each run. <br /> <br /> |
| Show SLA | True/False | Option to show SLA countdown details for the task. Note: Select Show additional options to see this field. |
| Can Skip | True/False | Option to allow agents to skip the checklist and to continue through the playbook. |
[ ]

{#checklist-task-activity__table_cjj_sr3_plb}

## Additional properties {#checklist-task-activity__section_l44_5dy_m1c}

Move stuff here.

## Outputs {#checklist-task-activity__section_unx_fr3_plb}

These outputs can provide data to other activities in your playbook. You can access this data as activity inputs when you configure your activity: {#checklist-task-activity__table_mv2_rr3_plb__entry__3}

| Output | Type | Description |
|-|-|-|
| Checklist Task | Reference.Task \[task\] | Task record that updates when this activity completes. |
[ ]

{#checklist-task-activity__table_mv2_rr3_plb}

## UI Layouts {#checklist-task-activity__id_xrs_lww_41c}

Set properties for how the activity renders during a playbook run.

*[\>]: and then


