Jump to the comparison
Data Annotation Services

Data annotation QA workflow

Good labels come from a process with checks at each step, not from a promise. This workflow runs from the label guide to an accepted batch, and shows what to test when you choose a vendor.

The QA workflow, step by step

  1. Write the label guide. Every class, with pictures of edge cases, what to skip and what to do when unsure.
  2. Build a gold set. Items an expert labels and a second person checks. These are the answers you score against.
  3. Run a pilot. A small batch scored against the gold set. Read every error and fix the guide before going further.
  4. Hide gold items in the work. Mix gold items into normal batches without marking them, so scores reflect everyday work.
  5. Label some items twice. A share of items goes to two labelers, so you can measure agreement between them.
  6. Review each batch. A second person checks a sample; rule checks catch boxes off the image or missing classes.
  7. Accept or return the batch. Compare the scores with the pass marks agreed in advance, and return batches that miss.
  8. Feed back. Update the guide with each new edge case and tell labelers about the classes they get wrong.

The numbers behind steps 2 to 7 (accuracy, IoU and agreement) are explained in annotation quality metrics.

Review levels: who checks what

Review levels in an annotation QA workflow
Who checksWhat they doWhat it catches
The labelerChecks their own work before sending itSlips: a missed object, a wrong class picked
A second labelerLabels the same items, or checks another'sUnclear rules, where two people read the guide differently
A reviewer or QA leadChecks a sample of each batch against the guideErrors repeated across a whole batch or one labeler
Rule checks in the toolRuns on every labelBoxes outside the image, empty labels, duplicate shapes
Your own teamSpot-checks delivered batches against the gold setDrift from what your model needs

How companies and tools describe their checks

Most of the 15 companies we compare do not describe their checks on their own pages. Ask each one to show you a batch report from a past project: the scores, the sample size and what happened to batches that missed.

Data labeling vendor selection: what to test in the pilot

  • Send every vendor the same small batch of items, with the same label guide, and keep a gold answer for each.
  • Score accuracy, IoU and missed objects yourself; do not rely on the vendor's own score.
  • Note the questions they ask about the guide. Good questions early mean fewer errors later.
  • Time the turnaround, and ask how they would staff the full volume.
  • Ask for their audit reports before any real data moves (see data annotation security).
  • Compare the price per label after rework, not the headline rate.

These companies publish a free or paid test on their own pages:

Batch rules for the contract

  • How many items are checked per batch, and who picks them.
  • The pass marks: accuracy on gold items, IoU for shapes, agreement on items labeled twice.
  • A batch below the mark is relabeled at the vendor's cost and scored again.
  • The guide is the reference: changes to it are dated, and older batches are judged by the version they were labeled under.

More buyer guides

Want companies to quote against these rules? Describe the job once, and up to three annotation companies reply with prices.

Get quotes from three companies