---
title: Checklist Task activity
description: Prompt an agent to complete all items in a task checklist.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/build-workflows/workflow-studio/checklist-task-activity.html
release: australia
product: Workflow Studio
classification: workflow-studio
topic_type: reference
last_updated: "2026-03-12"
reading_time_minutes: 3
breadcrumb: [Interactive activities, Playbooks reference, Playbooks, Workflow Studio, Build workflows]
---

# Checklist Task activity

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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/checklist-task-activity.md) section.

## Roles and availability

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

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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/dot-walking-examples.md).

<table id="table_ajt_sr3_plb"><thead><tr><th>

Input

</th><th>

Type

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Label

</td><td>

String

</td><td>

Title to display as activity and playbook card.

</td></tr><tr><td>

Description

</td><td>

String

</td><td>

Information to display about activity usage or outcome.

</td></tr><tr><td>

Run condition

</td><td>

Condition Builder

</td><td>

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.

</td></tr><tr><td>

Start Rule

</td><td>

Choice

</td><td>

Under **Schedule** &gt; **Start 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.

Under Schedule &gt; 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.

</td></tr><tr><td>

Start with delay

</td><td>

True/False

</td><td>

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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/start-with-delay-properties.md).**Note:** Select **Show additional options** to see this field.

</td></tr></tbody>
</table>## Inputs

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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/activity-definitions.md).

<table id="table_cjj_sr3_plb"><thead><tr><th>

Input

</th><th>

Type

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Skip Assignment Group

</td><td>

Reference.Group \[sys\_user\_group\]

</td><td>

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 Group**or **Skip Assigned To**, all users will be able to skip this activity.

</td></tr><tr><td>

Skip Assigned To

</td><td>

Reference.User \[sys\_user\]

</td><td>

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 Group**or **Skip Assigned To**, all users will be able to skip this activity.

</td></tr><tr><td>

Checklist Owner

</td><td>

Reference.User \[sys\_user\]

</td><td>

The user who owns this checklist.

</td></tr><tr><td>

Checklist Items

</td><td>

String

</td><td>

The items you want display in your checklist.

</td></tr><tr><td>

Checklist Name

</td><td>

String

</td><td>

The name to display for the checklist.

</td></tr><tr><td>

Task

</td><td>

Reference.Task \[task\]

</td><td>

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.

 \[Omitted image "checklist-task-record.png"\] Alt text: Checklist in a task record

</td></tr><tr><td>

Show SLA

</td><td>

True/False

</td><td>

Option to show SLA countdown details for the task.**Note:** Select **Show additional options** to see this field.

</td></tr><tr><td>

Can Skip

</td><td>

True/False

</td><td>

Option to allow agents to skip the checklist and to continue through the playbook.

</td></tr></tbody>
</table>## Additional properties

Move stuff here.

## Outputs

These outputs can provide data to other activities in your playbook. You can access this data as activity inputs when you configure your activity:

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

## UI Layouts

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