Home / Data services / Annotation and labeling

Data service 04

annotation and labeling

Action segmentation, affordance masks, language captions, reward signals — at the bar your model deserves.

99.4%
Label accuracy
14
Modality types
1,200/hr
Labels per operator hour
RAW FRAME UNLABELED ANNOTATION PIPELINE 1 Action segmentation DONE 2 Affordance masks DONE 3 Language captions 4 Reward signals QUEUE 5 QA review QUEUE LABELED FRAME GRASP PLACE AVOID PUSH LIFT POLICY-READY 99.4%Label accuracyMulti-pass QA verified 14Label typesActions, masks, captions 1.2KLabels / hrPer trained annotator 2-passQA reviewEvery label checked twice TRAINING-READY

What is annotation and labeling?

Annotation and labeling is the process of adding structured metadata to raw robotics data — action boundaries, affordance masks, natural-language captions, and reward signals — so your model knows what happened, where, and why it mattered.

Typical use cases

  • Imitation learning — action segmentation so policies learn when to grasp, pour, and release
  • VLA pre-training — language captions paired with video for vision-language-action models
  • Reward modeling — success/failure labels and scalar reward signals for RLHF
  • Scene understanding — affordance masks and object-level segmentation

Why teams partner with us

Labeling robotics data requires domain expertise, not just clicking boxes. Our annotators are trained on manipulation, locomotion, and navigation tasks.

  • 99.4% accuracy — multi-pass QA on every label
  • 14 label types — from bounding boxes to free-text captions
  • Your ontology — we label to your taxonomy, not ours

Why outsource labeling?

Your engineers should be iterating on architectures, not drawing masks. We scale annotation teams up and down to match your training cycles.

1,200 labels/hr per trained annotator.

48-hour turnaround on standard batches.

14 modalities supported out of the box.

Where we collect

41+ delivery centers across 12 countries. Every program runs from a Roborax hub near your target time zone.

Asia Pacific
India · Philippines

Americas
USA · Canada · Colombia · Jamaica · El Salvador · Belize

EMEA
UK · Albania · Kosovo · Morocco

Explore all locations →

What we deliver

The annotations a VLA model actually needs

Four label types that bridge raw capture to a training-ready dataset.

Action segmentation

Frame-level action labels with start, end, and class for every clip.

Affordance masks

Pixel-level masks of graspable, pushable, and contact regions.

Language captions

Free-form and templated natural-language descriptions per scene.

Reward signals

Dense or sparse reward per timestep for RL and IRL pipelines.

How we work

Spec, calibrate, annotate, audit

Four stages that lock the bar before billable work and verify it after.

1Step 1

Spec

Acceptance criteria locked with your team. Edge cases documented in writing.

2Step 2

Calibrate

Operators pass a gold-set bar before producing billable labels.

3Step 3

Annotate

Production labeling with daily QA review and same-day rejections.

4Step 4

Audit

Held-out 5% sample re-reviewed by seniors. Accuracy report per batch.

Rigs and tools

Tools we run, formats we ship

Use ours, use yours, or use the open-source standard.

CVAT

OSS, self-host

Labelbox

Enterprise SaaS

Scale Studio

Enterprise SaaS

Encord

Multi-modal

VGG VIA

Lightweight

Custom

Your pipeline

What our partners say
We were burning weeks on labeling iteration. Their gold-set process locks the criteria at week two. We haven’t had a label-spec change since.
Iqbal Ahmed
Head of Eval, OpenLatent

FAQ

Questions about annotation and labeling

COCO, CVAT, YOLO, custom JSON, ROS bag with annotation overlays, and RLDS for trajectory data. If you use an internal format, share the schema and we will build a converter.
Our baseline is 99.4% label accuracy across active programs. We achieve this through multi-pass review, consensus labeling on ambiguous frames, and a dedicated QA team that audits every batch before delivery.
Every label goes through automated validation checks, a human review pass, and a final QA audit. Batches that do not meet your agreed accuracy threshold are re-labeled at no additional cost.
Yes. Send us your label taxonomy, class definitions, and any edge-case guidance before the program starts. We build that into operator training and validation tooling.
Ambiguous frames are flagged in the delivery manifest with a confidence score. You choose whether to include them in training, discard them, or send them back for adjudication.

Further reading

From the blog

Robot Data Annotation: A Practical Guide for ML Teams

Rubrics, workflows, and QA standards for robot annotation programs.

From the blog

The QA Pipeline Every Robotics Data Team Needs

How to build quality assurance into your annotation pipeline.

Run a labeling pilot

Send us a sample batch and the spec. We come back with a calibrated quote in three days.

FROM THE FIELD

Data operations insights