> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/intelligence/heart/task-success.md).
# Task Success
What the Task Success dimension measures, how the aggregate completion ratio works, and when it activates.
Task Success is the HEART[^1] dimension that measures whether users complete what they set out to do. It is the simplest dimension: one metric, one formula.
## What Task Success measures
Task Success answers three questions about an application:
* What share of started tasks are completed?
* Which specific tasks are failing, and where is the drop-off?
* Is task performance improving after changes to content, training, or process?
The score is one signal across all tasks in the application. Per-task detail, such as which tasks fail and where people drop off, appears on the Tasks page and in AI Insights, not in the dimension score.
Efficiency measures the speed and consistency of completions. Task Success measures whether completions happen at all. Risk measures whether the right data is entered. Together they cover different aspects of task performance.
The Task Success dimension detail in the HEART scorecard.
## How the score is calculated
The Task Success score is the completion ratio across all defined Tasks in the application: total completions divided by total starts, on a scale of 0 to 100.
This is one ratio across all tasks, not an average of each task's completion rate. Averaging would give a task with ten starts the same influence as a task with ten thousand starts. The ratio reflects actual usage, so high-traffic tasks carry proportional weight.
When Task Success is inactive, for example because no Tasks are configured or there is not enough data yet, HEART handles it as described in [How the score is calculated](/intelligence/heart.md#how-the-score-is-calculated).
### Activation
Task Success activates once the application has collected enough task completions over a sufficient period. Tasks must be configured first.
## Relevant articles
{% content-ref url="/pages/TBF4QYHDMWQghy26u8xI" %}
[HEART](/intelligence/heart.md)
{% endcontent-ref %}
{% content-ref url="/pages/nJSkeXwSmCTopscQ7Fmx" %}
[Tasks](/intelligence/tasks.md)
{% endcontent-ref %}
{% content-ref url="/pages/iSW1aAIFYuiVThZ8DMfM" %}
[Create a task in the Editor](/intelligence/tasks/create-a-task-in-the-editor.md)
{% endcontent-ref %}
{% content-ref url="/pages/H0TpAAVoypgUSRX7TiLj" %}
[Efficiency](/intelligence/heart/efficiency.md)
{% endcontent-ref %}
## FAQ
What happens if no Tasks are configured?
Task Success does not activate, and HEART is calculated from the remaining active dimensions. [Create a task](/intelligence/tasks/create-a-task-in-the-editor.md) to start scoring Task Success.
Are all Tasks included, or can specific tasks be selected?
All Tasks defined for the application are included. You cannot select or exclude individual tasks from the score.
Why one ratio instead of averaging each task's rate?
Averaging would give low-volume tasks too much influence. One ratio across all tasks reflects actual usage and gives a more reliable signal for the application.
What is the difference between Task Success and Efficiency?
Task Success measures whether tasks complete at all. Efficiency measures the speed and consistency of those completions.
[^1]: HEART is Userlane's five-dimension model for scoring how well an application works for the people using it, on a scale of 0 to 100.
---
# 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://docs.userlane.com/intelligence/heart/task-success.md?ask=&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.
