> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/how-to-and-best-practices/optimizing-productivity-and-focus/smart-productivity-goals.md).

# Smart Productivity Goals

Set employee productivity benchmarks with We360.ai goal tracking — configure minimum active or productive time targets.

Move beyond simple time tracking — use We360.ai's goal system to set meaningful productivity benchmarks for your teams.

## Types of Goals

{% columns %}
{% column %}

#### Active Time Goal

Set a minimum number of active hours per day that employees should meet. This measures overall engagement based on system activity.
{% endcolumn %}

{% column %}

#### Productive Time Goal

Set a minimum number of productive hours per day. This measures time spent on applications and websites categorized as "productive" for the employee's role.
{% endcolumn %}
{% endcolumns %}

## Setup Steps

{% stepper %}
{% step %}

#### Access Goal Settings

Navigate to the **Goals** section. Select the goal type — **Active Time** or **Productive Time** — and set the minimum hours per day.
{% endstep %}

{% step %}

#### Review Goal Achievement

The Goals dashboard provides:

* **Goal Achievement Status** — Overview of how employees are tracking against targets.
* **Team-wise Comparison** — Compare goal achievement across different teams.
* **Achievement Distribution** — See the spread of goal attainment across your workforce.
* **User-wise Goal List** — Drill into individual employee goal performance with activity and productivity percentages.
  {% endstep %}
  {% endstepper %}


---

# 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.we360.ai/how-to-and-best-practices/optimizing-productivity-and-focus/smart-productivity-goals.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.
