> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tatara.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Task trackers

> The tracker format: a checklist with per-task tags, priorities, due dates, and completion dates, and how to work one in the app.

A tracker document is a checklist. Tasks are checkbox list items, optionally grouped under `## Section` headings, and each task can carry tags, a priority, a due date, and a completion date. Ask your agent for a task list and it creates the document in the tracker format — see [Document formats](/formats/overview).

Where a [board](/formats/kanban) is about moving cards between stages, a tracker is about the metadata on each task: what it is tagged, how urgent it is, when it is due.

## The markdown underneath

```markdown theme={null}
- [ ] Renew domain 📅 2026-08-01

## Launch

- [ ] Ship pricing page #launch ⏫ 📅 2026-07-20
  Needs sign-off from Angus.
- [x] Write launch email #launch ✅ 2026-07-12

## Later

- [ ] Evaluate CDN options 🔽
```

`- [ ]` is an open task and `- [x]` is done. Tasks can sit loose at the top of the document or under sections, and any indented lines beneath a task are its detail: notes and subtasks that travel with it. The body holds only tasks and section headings — context about the tracker belongs in the document's description field.

## What a task can carry

Task metadata rides inline on the task line, following the task-emoji conventions plain-text task lists have settled on:

| Token           | Written as                                                |
| --------------- | --------------------------------------------------------- |
| Tag             | `#tag`                                                    |
| Priority        | `🔺` highest, `⏫` high, `🔼` medium, `🔽` low, `⏬` lowest |
| Due date        | `📅 YYYY-MM-DD`                                           |
| Completion date | `✅ YYYY-MM-DD`                                            |

<Note>
  These task tags are free text inside the task line. They are not the document's own tags, they are not checked against your tag registry, and they do not count toward the document's tag limit.
</Note>

## Working with a tracker in the app

* **Tick a task.** Each task has a checkbox.
* **Edit inline.** Click a task title to edit it in place.
* **Due dates.** The due date shows as a pill, and editing it opens a date picker. Overdue tasks are highlighted.
* **Priorities.** The glyph is shown with a tooltip naming the level: `🔺 Highest`, `⏫ High`, `🔼 Medium`, `🔽 Low`, `⏬ Lowest`. A completion date shows alongside as `✅ YYYY-MM-DD`.
* **Tags.** Tags in a title render as chips. Click one to filter the list to it. You can add and remove tags per task.
* **Detail.** Tasks with detail lines show a `details` pill that opens a read-only dialog.
* **Toolbar.** The toolbar holds a progress bar counting done tasks out of the total, a `Group by` control offering `By section`, `By due date`, `By priority`, and `By tag`, a `Show completed` toggle, and a chip for the active tag filter with a button to clear it.

<Warning>
  Grouping, filtering, and the show-completed toggle are view state only. They never rewrite the document, and they reset when you reload the page. The order in the document is always the order you wrote.
</Warning>

A tracker document has no properties rail and no width control, and its title is read-only on the document page. Rename it from the sidebar.

<Columns cols={2}>
  <Card title="Kanban boards" icon="columns-3" href="/formats/kanban">
    The other checkbox format: columns of cards you drag between stages.
  </Card>

  <Card title="Agent skills" icon="code" href="/skills">
    Install the skill that teaches your agent the tracker grammar.
  </Card>
</Columns>