Project Metrics

the metrics page is under active development and the components below may evolve the metrics tab is split into five sub tabs, selectable from the chip row at the top each chip writes a ?metricstab=… parameter to the url, so individual tabs can be deep linked or shared the default tab is productivity productivity the productivity tab is the default landing view it surfaces a 7 card kpi row in playbook diagnostic order when productivity is below target, you walk these ratios left to right to find where to look first the cards, in order productivity ap / (apt x reported hours) 100% = on target, >100% = ahead, <100% = behind time allocation ratio (was "time allocation") time spent in task view (annotate + review + correction) / reported time healthy band 75 90% color green 75 90%, red otherwise annotate speed ap produced in annotate tasks / time in annotate tasks "pure speed" during the annotate phase color thresholds red below 1 3x apt, yellow 1 3 1 4x apt, green >= 1 4x apt correction ratio correction time / annotate time color thresholds green <5%, yellow 5 10%, red >10% review ratio review time / time spent in task view shows the share of tool time consumed by review activities color thresholds green <10%, yellow 10 15%, red >15% reported time total team hours over seven days active users count of users with reported work time each card displays the headline value, a comparison against the previous 7 days (with a coloured chevron indicating whether the change is good or bad for that metric), and a 5 week graph with per dot tooltips the most recent graph point may differ slightly from the headline number, because the headline is a rolling 7 day value while the graph shows weekly buckets apt calibration warning a banner appears above the kpi row when the project's effective ap target looks miscalibrated — for example, when no annotator has reached 100% productivity in the available data the playbook is when nobody is hitting target, the target itself is likely wrong — recalibrate the project's apt before reading the diagnostic ratios, since they all assume a realistic benchmark productivity vs target a weekly distribution chart showing how the team splits across three fixed bands above target, approaching target, and below target weekly ap produced a bar chart of total annotation points produced per week, with value labels on each bar tables below the charts a weekly summary table and a per user breakdown table clicking a user opens their full productivity report; the originating project is preserved via ?projectid=\<id> so the breadcrumb back button returns to this metrics view efficiency the efficiency tab focuses on the drivers behind the productivity headline it contains efficiency drivers table — per user efficiency breakdown ap/h trend — weekly ap/h over time productivity spread — distribution of productivity across the team qa ratio trend — review + correction time as a share of tool time, over time active users trend — weekly active user counts productivity vs target bucket trend — how the distribution across the three target bands has shifted week over week delivery delivery groups the throughput oriented charts weekly counts — inputs delivered per week weekly detailed counts — same data broken down by phase or status turnaround time — average time from request creation to delivery composition composition tracks what is in the data — shapes per input, objects per input, and geometry type density across requests the data source toggle and shape prediction overlay still apply here quality quality kpis are split out into their own tab the headline cards cover review quality (share of annotated objects accepted by quality reviewers without changes) and expert verification (share of qr approved objects also accepted by experts) a sub metric breakdown table covers precision, recall, geometry accuracy, property accuracy, and the count of reviewed scenes learning curve the learning curve tab tracks how quickly new annotators ramp up their annotation speed during their first weeks in a project each user's timeline is aligned so that week 0 is their first day in the project, making it easy to compare onboarding progress regardless of start date chart the main chart displays one line per user, plotting annotation speed (ap/hour) against onboarding weeks reference lines provide context annotation speed target — 140% of the configured annotation points target (apt), representing the speed needed for 100% productivity p90 and p50 — percentile lines across all displayed users expected learning curve — a shaded band showing the configured min/max speed range per week (see annotation points and target for configuration) you can brush select a region on the chart to filter the summary table to only the users whose lines pass through the selection kpi cards three kpi cards summarize onboarding health above expected learning curve — percentage of onboarding users performing above the configured learning curve band reached target speed — number of users who have reached the annotation speed target avg days to target — average number of active days it took users to reach the target (among those who have) if the expected learning curve is not yet configured, the first kpi card displays a link to project settings where it can be set up filters max active weeks — slider to limit the chart to users with at most n active weeks hide users above annotation speed target — checkbox to focus on users still ramping up user filter — search by name or email supports pasting comma separated email lists summary table displays a row per onboarding user with columns for days active, current speed, speed delta (weekly and bi weekly), productivity percentage, and curve deviation actions csv export — download the table data copy emails — copy selected user emails to clipboard who sees what access controls are applied per tab productivity, quality and learning curve require the team overview permission productivity is also hidden when time spent is hidden efficiency requires the team overview permission delivery and composition are visible to all users with access to the metrics tab when a user lacks permission to see a tab, the chip is hidden from the row