Skip to content
AOAnnotation Ops Kit

Track annotation operations

Annotation throughput tracker

Connect daily labeling output to hours, rework, and batch cycle time. See where delivery slows down and what to investigate next.

Spreadsheet for Google Sheets · Ops Kit and up · One-time purchase

An annotation throughput tracker gives a team a consistent record of how much work moved through its labeling process. Compare similar tasks and review quality alongside speed so a higher item count does not hide extra correction work.

Start with consistent definitions

Metrics for data labeling operations

Decide what counts as an item, a working hour, and rework before comparing people or vendors. Keep labeling time separate from waiting time.

A practical set of operational measures
MetricDefinitionUse it to ask
Items per hourCompleted items ÷ logged working hoursDid output change for comparable tasks?
Average handling time (AHT)Logged working minutes ÷ completed itemsIs the task taking longer per item?
Rework rateItems needing correction ÷ reviewed itemsIs faster delivery creating more corrections?
UtilizationLogged working hours ÷ scheduled hoursHow much scheduled time was logged as work?
Batch cycle timeTime from defined batch start to completionHow long does the batch spend in the whole process?

Use the same denominator and time definitions in every report. Rework may be measured against reviewed or submitted items; label the choice explicitly and do not mix the two.

Fictional daily-log example

Read output and quality together

A labeler completes 480 items in 6 logged working hours during an 8-hour scheduled day. That is 80 items per hour, an AHT of 45 seconds, and 75% utilization under the definitions above.

If a reviewer checks 100 of those items and sends 8 back for correction, the observed rework rate in that reviewed set is 8%. That is a sample result; it does not tell you that exactly 8% of all 480 items need rework.

Before comparing this day with another, check task complexity, guideline changes, review coverage, and whether the logged hours include correction work. A raw leaderboard can otherwise reward easier assignments.

Find the stage delaying a batch

  1. Log the work. Record items, hours, rework, and scheduled time consistently in the Daily Log.
  2. Review the pattern. Use per-person summaries and weekly reports to spot changes that need an explanation.
  3. Trace batch stages. Check cycle time and the bottleneck view. A batch may be waiting for review even when labeling speed is stable.
  4. Record the action. Clarify an ambiguous rule, resolve a handoff, or revisit capacity assumptions, then check the following reporting period.

For recurring label disagreements, update the annotation guidelines. For a new vendor, put the delivery assumptions into a data annotation RFP. Use the QA sample size calculator to plan quality review separately from throughput reporting.

The downloadable files

Put the workflow into practice

The Throughput Tracker includes a Daily Log, Per-Person Summary, Weekly Report with charts, Cycle Time, and Bottleneck views. It is included in Ops Kit with the QA files and Vendor RFP Kit. Requires Google Sheets: some summary formulas do not update in Excel.

Single-user license. Team plan: $299 for up to 10 people at one company. Sales tax or VAT added where applicable.

The page above is a free guide and preview. The editable kit files are a paid download through Gumroad.

Throughput Tracker bottleneck view showing the share of batch cycle time spent in each stage
Actual Throughput Tracker bottleneck-view preview. Select the image for the full-size view.

Questions about this resource

Does the Throughput Tracker work in Excel?

Use Google Sheets for live results. Some summary formulas are Google-only and will not update in Excel. The other kit files have their own format requirements, listed on the homepage.

Is this an automatic integration with a labeling platform?

The kit is a spreadsheet-based workflow. Your team enters its operational data; the product does not provide a live connection to a labeling platform.

Which plan includes it?

Ops Kit ($199, single user) and Team ($299, up to 10 people at one company). QA Core does not include the Throughput Tracker.

Continue the workflow

Define the labels

Data annotation guidelines template

Define labels, examples, edge cases, and version history.

Read the guide

Compare labeling vendors

Data annotation RFP template

Compare requirements, pilot evidence, and vendor scores.

Read the guide

Planning a QA review? Use the free sample size calculator or download the free sample-size sheet and error taxonomy.