Project Overview
The Overview tab is the first thing you see when you open a project. It answers two questions at a glance: is this project healthy, and how much of it is done.
Prerequisites
You need Project management access in the workspace to open a project at all β that is the Annotation manager, Project manager, Developer, or Admin workspace role. See Roles & permissions. The Project health section has an extra condition. It is only shown to users whose organization role can view productivity data β Team manager or Admin. It is also hidden for every user in organizations that do not have access to productivity statistics, regardless of role. If you do not see it, the rest of the tab still works as described.
Overview
Use this page as the starting point for a project. It gives production managers a quick read on whether a project is on track and provides access to individual requests.
The tab has three collapsible sections, top to bottom:
- Project health β four outcome KPIs for the project as a whole.
- Progress β how many inputs are done, and where the rest are.
- Requests β the list of requests in the project.
Project Health
Four cards, each showing a headline figure and a comparison against an earlier period.
Card | Headline | Comparison |
|---|---|---|
Productivity | Rolling 7-day productivity against the project's AP target | Previous 7 days |
Client acceptance rate | Share of requests accepted in their first round of Client QA. | The same rate over the last 30 days |
Inputs delivered | Inputs delivered in the most recent week | Previous week |
Team health | Share of active annotators within healthy working limits on this project | The same figure a week ago |
Productivity and Inputs delivered also plot a 5-week trend. Hover a point to see that week's value.
A colored chevron next to the headline indicates whether the change since the previous period is positive or negative for that metric. No chevron means the value is flat.
Where a card has no data yet, the headline shows a dash (β) rather than a zero.
Hover the β on any card for its definition and the fine print on what the comparison figure means.
Project health is a quick-scan surface only. When a number looks wrong, use Open detailed metrics to move to the Project Metrics tab, which has the weekly tables, charts, and per-user breakdowns behind it. Each card is also clickable and takes you straight to the matching metrics sub-tab.
Progress
Project completion is the share of inputs that have reached the delivery-ready state, with the absolute counts below it (x out of y inputs).
General project progress is a single horizontal bar covering every input in every request in the project, split by phase:
- Not started β no work has begun on the input.
- Production β the input is being annotated or corrected.
- Client QA β the input is being reviewed by the client.
- Delivery β the input has been delivered.
Input progress breaks the same data down per request. Choose between two views with the radio buttons:
- Across requests (default) β one row per request, each a stacked bar of its phase distribution.
- Across phases β one row per phase, showing how that phase is composed across requests.
Each view has its own toggle, and only that view's toggle is shown:
- In Across requests: Hide requests with only delivery ready inputs removes finished requests from the chart so you can focus on remaining work. It is disabled when there are no such requests.
- In Across phases: Hide Delivery phase drops the Delivery phase from every row.
Requests with no inputs are left out of the chart automatically.
Requests
The requests in the project, with their input batch name, active phase, input count, last update, and Client QA verdict. Filter by status, active phase, and Client QA verdict, and choose whether to include archived requests. The count in the section header reflects the current filter.
This is the way in to an individual request β see Request detailsο»Ώ.
Frequently asked questions
ο»Ώ