> 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/execution-dashboard.md).

# Execution Dashboard

The Execution Dashboard shows how long employees actually spend [completing Missions](/mobile-app/perform-a-mission.md) — measured from the moment they **claim** a Mission to when they **close** it.

## Why use the Execution Dashboard?

Completion metrics tell you *if* work was done. Execution metrics tell you *how* it was done. If a 30-minute cleaning checklist is being closed in 15 seconds, something is wrong. If a simple task consistently takes 3 hours, the process needs rethinking.

**Example:** A manager notices one employee closes "Room Inspection" Missions in under 30 seconds while others take 8–12 minutes. The data triggers a quality review.

## How to use it

Go to **Dashboard → Execution**.

1. Select a **Unit** (required before any data appears)
2. Filter by **Team**, **Person**, **Mission**, and/or **Date Range**
3. Choose **Group By**: Person (who takes how long) or Mission (which Mission takes how long)

The dashboard displays execution duration in bands: 0–30s, 31–60s, 61–90s, 91–120s, 2–5m, 5–10m, 10–15m, 15–30m, 30–45m, 45–60m, 60–90m, 90–120m, 2–6h, 6–12h, 12–18h, 18h+.

### Auto-Refresh

Enable Auto-Refresh to update the dashboard every 30 seconds — useful for displaying on a wall-mounted screen. Off by default. Only refreshes when the date range includes the current day.

## Good to know

* Execution time = **Claimed to Closed** only (not Open to Closed)
* Interpret durations in context — a 30-second close for a Task is normal; for a 50-question Checklist, it's suspicious
* Web only — not available on mobile


---

# 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/execution-dashboard.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.