> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/experiences/checklists.md).

# Checklists

What a checklist is made of, how its tasks end, and how users open, dismiss and reopen it. Then build one in the builder or ask your assistant.

## What checklists are

Checklists help guide users through essential tasks with an on-screen list that tracks progress. Configure task actions, completion conditions, and a final step to enhance user engagement.

**You will have at the end:** a clear picture of what a checklist is made of, how each task ends, and how users open, dismiss and reopen it, before you build one.

***

## What a checklist is made of

A checklist has two fixed steps: the checklist with its tasks, then a completion step. You cannot add or remove steps, but you choose the content of both.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FjRNTmCxRqOqqw0BViOSN%2Fchecklists-01-anatomy.png?alt=media&amp;token=f1914b91-1385-4cc6-b722-41132a02d930" alt="A checklist open on a neutral app page: a header with title, paragraph, control and progress bar, three tasks with checkmarks, and an expanded task with a Start button and a Skip task button. Below, the collapsed float trigger with its label and task count, and the completion step with a Close checklist button."><figcaption><p>A checklist and its completion step.</p></figcaption></figure>

| Part            | What it holds                                                                                       |
| --------------- | --------------------------------------------------------------------------------------------------- |
| Trigger         | The collapsed checklist users click to open it.                                                     |
| Header          | Title, paragraph, progress bar, and the control that minimizes or drags the checklist.              |
| Tasks           | A checkmark and a heading, a primary CTA, and optionally a paragraph, media or a secondary CTA.     |
| Completion step | Shown once every task is completed, with one primary CTA. Its default label is **Close checklist**. |

Each element and its settings: [Components](https://help.usejimo.com/docs/experiences/checklists/components.md).

## When to use a checklist

* **Onboarding in several tasks.** Users work through the tasks in their own time and see their progress.
* **A hub for other experiences.** A task can launch a tour or another experience, and tick itself once users have seen or completed it.
* **Setup steps on several pages.** A task can open the page where the work happens.

For one flow that users follow step by step, use a [tour](https://help.usejimo.com/docs/experiences/tours-and-modals.md) instead, and launch it from a task.

## How users open it

When collapsed, a checklist shows as its trigger, and users click it to expand the checklist. There are two trigger types: **Minimized**, a compact version of the header, and **Float**, a standalone button with its own label.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FAPujNgpNnyM2hgh5uNw9%2Fchecklists-05-trigger-types.png?alt=media&amp;token=204d994a-e24c-4200-8bc9-bef93a65cee6" alt="Two app pages side by side. Left, a Minimized trigger: a compact checklist header with title and progress bar in the top corner. Right, a Float trigger: a floating Get started button with a progress ring and a 1/3 count."><figcaption><p>Minimized and Float triggers.</p></figcaption></figure>

A checklist can also show inside a [Resource Center](https://help.usejimo.com/docs/experiences/resource-center.md), through its checklist block: the user's active checklist, or one you select.

Progress shows in the header as a **Plain Bar** or a **Step-by-Step Bar**, and on a Float trigger as **Circular** or **Count**.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FAkJdx7DcsDJRilnytUwL%2Fchecklists-04-progress-styles.png?alt=media&amp;token=394bc3d5-58f2-4dd0-b23f-c7cdb10c6fff" alt="Four progress styles: in the checklist header, a plain bar and a step-by-step segmented bar, each showing 2 of 5 done; on a float trigger, a circular indicator or a count next to the Get started label."><figcaption><p>Progress styles of the header and the float trigger.</p></figcaption></figure>

## How a task ends: completed or skipped

Clicking a task or its primary CTA runs the task's main action, for example **Launch experience**. A task then ends in one of two ways:

| Outcome   | When                                                                                                                                       | What users see                                          |
| --------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------- |
| Completed | Its completion conditions are met, for example the launched experience is seen or completed, or a CTA set to complete the task is clicked. | The checkmark turns on and the progress moves.          |
| Skipped   | Users click **Skip task**, the default action of the secondary CTA.                                                                        | The task is skipped, a separate outcome from completed. |

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FwYCgY4sFxqsFWIPCqbqM%2Fchecklists-03-task-lifecycle.png?alt=media&amp;token=d20868e2-31f7-410f-83e2-f75cdeb5da1b" alt="A task to do with Start and Skip task buttons leads to two outcomes: Completed, when its completion conditions are met or a CTA completes it, and Skipped, when users click Skip task. A Statistics table below has separate Clicked, Skipped, Completed and Completion rate columns."><figcaption><p>Completed and skipped are two separate outcomes.</p></figcaption></figure>

The checklist Statistics count the two apart, in the **Clicked**, **Skipped**, **Completed** and **Completion rate** columns. The **Completion** setting decides whether users complete tasks **In any order** or **In order**, from top to bottom. Once every task is completed, users see the completion step if Dismissible is set to No. Conditions, actions and order: [Behavior](https://help.usejimo.com/docs/experiences/checklists/behavior.md).

## Dismiss and recurrence

Users can dismiss a checklist only when it has a dismiss button: add the Dismiss element, or set **Dismissible** to **Yes**. Without one, completing every task is the only way to close it for good.

A checklist follows its recurrence like any experience. With **Show once**, the default, a user who dismisses it may not see it again. To bring it back, set a recurrence such as **Show every time** or every N days, weeks or months in [Schedule, recurrence and priority](https://help.usejimo.com/docs/publish/trigger-at-the-right-time-when/planning-your-experience.md).

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FWhP7GCYrsEnnNHwsssKA%2Fchecklists-07-recurrence-dismiss.png?alt=media&amp;token=20b70675-cf99-4f40-b0f5-99795984cba7" alt="Two rows. Show once: users dismiss the checklist on visit 1, and on the next visit it is not shown, marked May not show again. With a recurrence, Show every time or Show every N days, weeks or months: users dismiss it on visit 1 and it comes back on the next occurrence."><figcaption><p>Set a recurrence to bring a dismissed checklist back.</p></figcaption></figure>

***

## The checklist builder

### Accessing the builder

Navigate to the Builder from the dashboard to start crafting your checklist.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FEjEQCVfwcyWHa6g1IsQn%2Fimage.png?alt=media&amp;token=0c7b50c3-5f9b-4f9a-9973-673fef40f9a1" alt="Checklists dashboard"><figcaption><p>Checklists dashboard</p></figcaption></figure>

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FeSJm4BIKG6iq7Wd87BKS%2Fimage.png?alt=media&amp;token=6ae8a9db-c3a3-4c97-a945-72caa0cb4881" alt="Empty state first checklist"><figcaption><p>Empty state first checklist</p></figcaption></figure>

### Main features

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F39g9q28by43UKTV7yaZL%2Fimage.png?alt=media&amp;token=c31bcefa-ea01-4e7c-a3fa-e5e255448f56" alt="Checklist builder"><figcaption><p>Checklist builder</p></figcaption></figure>

* **A (Navigator - Checklist Elements):** This section displays the checklist elements (Header, Task List, Dismiss) within the expanded checklist. You can access their specific parameters and the general checklist options here.
* **B (Trigger):** This area represents the display settings for the collapsed version of the checklist. It controls how and when the checklist is displayed on-screen.
* **C (Tab Selector):** Use this to switch between different tabs. By default, it’s on the **Navigator** tab, but you can also access:
  * [**Element Tab**](https://help.usejimo.com/docs/experiences/checklists/components.md)**:** Manage the addition or removal of checklist elements.
  * [**Theme Tab**](https://help.usejimo.com/docs/build/theme.md)**:** Apply and manage preset styles for consistent design.
  * [**Languages Tab**](https://help.usejimo.com/docs/build/multiple-languages.md)**:** Set up translations for multi-language support.
* **D (Top Bar - Step Switcher):** This bar allows you to switch between the checklist steps, like the **Task List** and **Completion Step**. Note that these are fixed steps, so you cannot add additional steps here.
* **E (Behavior Parameters):** These settings are available for the main checklist element and each task within it. Use this section to configure behavior options, such as task actions and completion conditions.
* **F (Style/Positioning Parameters):** This section lets you customize the appearance, including text, size, colors, and positioning on the screen.
* **G (Live Preview):** Here, you can see an interactive preview of the checklist, allowing you to access and adjust parameters directly by interacting with elements in the preview.
* **H (Action Buttons)**: Here, you'll find multiple actions:
  * The 'Save' button to secure your progress. This button allows you to force save but the builder automatically saves your work regularly.
  * The '[Preview](https://help.usejimo.com/docs/build/preview.md)' to see a full simulation of your checklist.
  * The '[Target & Publish](https://help.usejimo.com/docs/publish/target-and-publish.md)' sets the criteria for who will see the checklist and when.

***

## Best practices

* **Consistent design**: use the themes panel to keep a consistent look across your checklist.

***

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Components</strong></td><td>Header, tasks and dismiss: what a checklist is made of.</td><td><a href="https://help.usejimo.com/docs/experiences/checklists/components.md">Components</a></td><td><a href="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2Fo6xg0zX57QRiK9rp0Tju%2FR241-c01-checklist-components.png?alt=media&amp;token=d175bd26-2934-44ec-b236-7cb0d272fcd0">R241-c01-checklist-components.png</a></td></tr><tr><td><strong>Behavior</strong></td><td>How tasks expand, launch experiences and complete.</td><td><a href="https://help.usejimo.com/docs/experiences/checklists/behavior.md">Behavior</a></td><td><a href="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FfWrxWTN7KyNCK3BteQfd%2FR241-c02-checklist-behavior.png?alt=media&amp;token=05d93d40-9f4a-4521-a2da-b056fe38625c">R241-c02-checklist-behavior.png</a></td></tr></tbody></table>

## From your assistant

Ask: *"Draft a checklist Get set up with two tasks: Take the welcome tour, done when that tour is completed, and Invite a teammate, which opens /settings/team and is done when the URL contains /settings/team."* The assistant drafts the checklist with its header and both tasks, each with its button and completion conditions, and returns a preview link that opens the draft on your app. It also writes the trigger label and the copy of the completion step.

It cannot set **Dismissible**, **In order**, **Auto expand**, the trigger type, a **Launch Agent** action or JavaScript: set those in the builder. More in [What to ask?](https://help.usejimo.com/docs/integrations/mcp/what-to-ask.md)

## Verify

* Preview the checklist on your app: its trigger shows, and clicking it expands the checklist.
* Do what one task asks: its checkmark turns on and the progress moves.
* Complete every task: the completion step shows.

## Go further

* [Show on: trigger at the right moment](https://help.usejimo.com/docs/publish/trigger-on-the-right-spot-show-on.md): when the checklist appears on the page.
* [Who: target the right users](https://help.usejimo.com/docs/publish/target-right-people-who.md): which users get the checklist.
* [Where: target pages and domains](https://help.usejimo.com/docs/publish/target-specific-urls-domains-where.md): the pages it shows on.
* [Schedule, recurrence and priority](https://help.usejimo.com/docs/publish/trigger-at-the-right-time-when/planning-your-experience.md): the recurrence that brings a dismissed checklist back.
* [Goal: measure outcomes](https://help.usejimo.com/docs/publish/mesure-outcomes-goal.md): measure what users do after the checklist.
* [Chain experiences](https://help.usejimo.com/docs/build/actions/chain-experiences.md): show the next experience once the checklist is completed.
* [Experience links](https://help.usejimo.com/docs/build/actions/experience-links.md): how tasks hold the experiences they launch.
* [Available Actions](https://help.usejimo.com/docs/build/actions/available-actions.md): the actions a task or a button can run.
* [Resource Center](https://help.usejimo.com/docs/experiences/resource-center.md): show the checklist inside a Resource Center.
* [Analytics](https://help.usejimo.com/docs/analyze/analytics.md): follow how users engage with your experiences.

**Next page:** [Components](https://help.usejimo.com/docs/experiences/checklists/components.md)
