> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/documents-and-library/add-a-checklist-to-a-document.md).

# Add a checklist to a document

Add a checklist anywhere in a document to keep notes and action items together. Insert one with the **To-do list** option in the slash menu, tick items off inline, and nest sub-tasks under a parent item. The checked state is saved with the document, so everyone with access sees the same progress.

## Add a checklist

1. Open the document and place your cursor on the line where the checklist should start.
2. Type **/** to open the slash menu, then start typing **todo** or **checklist** and choose **To-do list**. You can also select existing text and choose **To-do list** from the list dropdown in the formatting toolbar.
3. Type your first item and press **Enter** to start the next one.

Each new line continues the checklist. Press **Enter** on an empty item to end the list and return to normal text.

## Check items off

Click the checkbox to the left of an item to mark it complete. Completed items stay in place so you keep a record of what is done. The state is saved automatically and persists across sessions for everyone who can open the document.

## Nest sub-tasks

To break an item into smaller steps, put the cursor on the line below it and press **Tab** (or use the indent button in the toolbar). The line becomes a sub-task of the item above. Press **Shift+Tab** to move it back out. Each checkbox reflects only its own state: ticking a parent does not tick its children, and vice versa.

| Action             | How to do it                            |
| ------------------ | --------------------------------------- |
| Start a checklist  | Type **/** and choose **To-do list**    |
| Add the next item  | Press **Enter** on the current item     |
| Complete an item   | Click its checkbox                      |
| Create a sub-task  | Press **Tab** on the line below an item |
| Outdent a sub-task | Press **Shift+Tab**                     |
| End the checklist  | Press **Enter** on an empty item        |

## Frequently asked questions

**Where are my checked items stored?** With the document itself, so the state persists across sessions and is visible to anyone with access to that document.

**Can I add more than one checklist to a document?** Yes, as many as you need, anywhere in the document.

**Do sub-tasks roll up to the parent item?** No. Each checkbox is independent.

**Will other people see when I check something off?** Yes. Anyone with access sees the current state when they open the document.

**Can I turn an existing bullet list into a checklist?** Yes. Select the list and choose **To-do list** from the list dropdown in the formatting toolbar.

## Related articles

* [Comment on a document](/documents-and-library/comment-on-a-document.md)
* [View and restore document versions](/documents-and-library/view-and-restore-document-versions.md)
* [Keep a document up to date automatically](/documents-and-library/keep-a-document-up-to-date-automatically.md)
* [Share a document](/documents-and-library/share-a-document.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rhythms.ai/documents-and-library/add-a-checklist-to-a-document.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.