> For the complete documentation index, see [llms.txt](https://intuitem.gitbook.io/ciso-assistant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://intuitem.gitbook.io/ciso-assistant/features/task-analytics.md).

# Tasks analytics

Filter-aware dashboard over your task definitions — status, due dates, assignees, domains, commitments

**Tasks analytics** is to the tasks list what [applied controls analytics](/ciso-assistant/features/applied-controls-analytics.md) is to the controls list: the same rows, aggregated. It answers *how much operational work is on the books, who holds it, and how much of it is late*.

## Where to find it

* **From the tasks table** — the analytics button (`Tasks analytics`) in the toolbar of `/task-templates`. The filters active on the table are carried over, so the dashboard reflects exactly the slice you were looking at.
* **From an audit's action plan** — scoped to the tasks attached to that audit, its requirements, or a finding raised from one.
* **From a findings binder's action plan** — scoped to the tasks attached to that binder or one of its findings.

When filters are in play, a pill above the dashboard says so. The numbers below are not your whole estate.

## What it shows

| Block           | What it answers                                                                                                                                                               |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **By status**   | Counts per status of the next occurrence — the same status the table's column shows, so the chart and the list agree                                                          |
| **Due dates**   | Five buckets — overdue / due within 30 days / due within 90 days / later / no date — matching the applied-control buckets so the two pages read alike                         |
| **Recurrence**  | One-off definitions versus recurring ones                                                                                                                                     |
| **By assignee** | Who holds the most tasks, each broken down by status. Actors you can't see are grouped as *Restricted*; tasks with nobody assigned as *Unassigned*                            |
| **By domain**   | Domains with the most tasks, also broken down by status                                                                                                                       |
| **Commitments** | With [commitment management](/ciso-assistant/concepts/operations/commitments.md) on: tasks per commitment state, plus how many have **slipped** and how many are **breached** |

For a recurring definition the status is read from its next *upcoming* occurrence — past ones are skipped — which is what makes "overdue" mean something on a task that has run fifty times.

## Related

* [Tasks](/ciso-assistant/concepts/operations/tasks.md)
* [Applied controls analytics](/ciso-assistant/features/applied-controls-analytics.md)
* [Action plans](/ciso-assistant/features/action-plans.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 by asking a question.

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

```
GET https://intuitem.gitbook.io/ciso-assistant/features/task-analytics.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 `automate deployments from our CI pipeline` 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.