> For the complete documentation index, see [llms.txt](https://documentation.taskmaverick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.taskmaverick.com/analytics-and-monitoring/dashboards/performance-dashboards.md).

# Performance Dashboards

Three dashboard tabs — **Team**, **Unit**, and **Personal** — give you performance metrics for different organizational levels. They share the same core metrics but viewed from different angles.

## Why use Performance Dashboards?

You need to know not just *what* was done, but *how well* and *how efficiently*. These dashboards combine multiple metrics into one view so you can compare teams, evaluate individuals, and track trends over time — all without building a custom report.

## Core metrics

All three dashboards display these metrics:

<table><thead><tr><th width="222">Metric</th><th>What it measures</th></tr></thead><tbody><tr><td><strong>Missions/Hour</strong></td><td>How many Missions an employee (or team) completes per working hour</td></tr><tr><td><strong>Ratings/Hour</strong></td><td>How many peer ratings are given per working hour</td></tr><tr><td><strong>Points/Hour</strong></td><td>How many reward points are earned per working hour</td></tr><tr><td><strong>Work Quality</strong></td><td>Average rating score received on completed Missions</td></tr><tr><td><strong>Objectivity Rating</strong></td><td>How consistent and fair a person's ratings are when evaluating others</td></tr></tbody></table>

{% hint style="info" %}
Time-based metrics (Missions/Hour, Ratings/Hour, Points/Hour) depend on **logged working hours** in the [Timesheet](/your-organization/people/time-timesheet.md). Missing timesheet data = lower or zero values.
{% endhint %}

{% tabs %}
{% tab title="Personal" %}
Go to **Dashboard → Personal**. Select a person to see their individual performance over time.

* Filter by **date range**
* Shows the same core metrics for the selected individual
* Useful for 1:1 reviews, performance conversations, and identifying training needs
  {% endtab %}

{% tab title="Team" %}
Go to **Dashboard → Team**. Select a team to see aggregated metrics for all members.

* Filter by **date range** and **specific people**
* View includes a **bar graph** for visual comparison and a **detail table** with individual scores
* Shows **"This Team"** vs. **"All Teams"** averages for benchmarking
  {% endtab %}

{% tab title="Unit" %}
Go to **Dashboard → Unit**. Select a unit to see performance across all teams at that location.

* Filter by **team** (multi-select) and **time period** (1W, 4W, 12W, 52W, All-time)
* **Unit Stats** table + **bar graph** on top, **Team Stats** table below
* Shows **"This Unit"** vs. **"All Units"** averages for cross-location comparison
* Also available on mobile via **Unit Board → Statistics / Leaderboard**
  {% endtab %}
  {% endtabs %}

## Good to know

* Only **one unit** or **one team** can be viewed at a time — no cross-unit side-by-side comparison
* Personal Missions and Team Missions assigned to Personal Boards are **excluded** from Unit/Team calculations
* Each user is counted **once,** even if linked to multiple teams
* Web only — mobile users see a simplified version via the Unit Leaderboard


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.taskmaverick.com/analytics-and-monitoring/dashboards/performance-dashboards.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.