> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.getzendo.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Use a checklist on a request

Some work follows the same steps every time: an onboarding, a launch or a monthly report. A checklist turns those steps into tasks. You add it to a request type in **Settings › Requests › Request types**, and every request of that type starts with the same tasks, so nobody on your team has to remember them.

## Add a checklist to a request type

1. Open **Settings › Requests › Request types** and select a request type.
2. On the **General** tab, go to the **Checklist** section.
3. Select **Add checklist**.

To see every checklist in your workspace, select **Manage checklists**.

## Work through the checklist

1. Open a request of a request type that has a checklist.
2. In the **Request Details** panel, scroll down to the **Checklist** section to see its tasks.
3. To see only the tasks that are left, select **Hide completed tasks**.

![The checklist in Request Details (2), with its progress, and Hide completed tasks (3).](https://getzendo.io/wp-content/uploads/2026/11/kb-q9-checklist.webp =350x439)

## A checklist applies to a whole request type

You write the tasks yourself. The checklist belongs to the request type, so when you change it, you change it for that kind of work, not for one request. Checklists are shared across the workspace, so you can use the same checklist on several request types.

## Track progress

Progress is shown as the number of finished tasks, such as `9/10`. You see it in three places:

- on the request, in the **Checklist** section;
- in the requests list, in the **Tasks** column, so you can see which requests are nearly done;
- on the dashboard and on the client's profile, where requests appear as short rows.

See [Work a request from arrival to done](https://help.getzendo.io/en/article/work-a-request-from-arrival-to-done-jfl1fw/) and [Find requests: views, filters and search](https://help.getzendo.io/en/article/find-requests-views-filters-and-search-lk9az4/).

## Checklist or status

A request shows its status and its checklist side by side, but they answer different questions. The **status** is the stage the request is at. A request has one status at a time. The client sees it, and automations and limits respond to it. The **checklist** is what is left to do in the current stage. It has many tasks, and it is for your team.

So a request can stay in the same status while its checklist moves from `2/10` to `9/10`. See [Understand statuses and the three states](https://help.getzendo.io/en/article/understand-statuses-and-the-three-states-10e4jci/).

## Related

- [Create a request type](https://help.getzendo.io/en/article/create-a-request-type-pucu6t/)
- [Work a request from arrival to done](https://help.getzendo.io/en/article/work-a-request-from-arrival-to-done-jfl1fw/)
- [Add custom fields to a request](https://help.getzendo.io/en/article/add-custom-fields-to-a-request-1qrhajr/)
- [Understand statuses and the three states](https://help.getzendo.io/en/article/understand-statuses-and-the-three-states-10e4jci/)