> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/core-concepts/labeler-performance.md).
# Labeler Performance
Viewing and analyzing labeler performance on Ango Hub
From your project's dashboard, enter the *Performance* tab. You'll be able to see detailed information about your labelers' performance.
## Performance Page Columns
### Completed tasks
**Labels** shows how many labeling tasks an annotator has completed.
**Labeling Time** is how long each annotator has spent on the project.
**Avg. Labeling Time**: How long the annotator has spent, on average, annotating each asset.
**Reviews** is how many reviews a labeler has completed in the project.
**Review Time**: How long the annotator has spent, cumulatively, reviewing.
**Avg. Review Time**: How long the user has spent, on average, on reviewing each task.
### In progress tasks
## Exporting Performance CSV
You may get a CSV of all data in the Performance tab by clicking on the *Download* button in the top-right corner of the table:
---
# 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.imerit.net/core-concepts/labeler-performance.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.
