Skip to content

Hand-Object Interaction Annotation for Workplace Demonstrations

By Noah Loul · Reviewed by Noah Loul · Updated

  1. 01Your data spec
  2. 02Matched to businesses
  3. 03Rights and samples reviewed
  4. 04Licensed delivery
How it works with SourceX: Your data spec → Matched to businesses → Rights and samples reviewed → Licensed delivery.Illustrative

Short answer

Hand-object interaction annotation records, at key frames or every frame, where each hand is, which object it touches, when contact starts and ends, the grasp type, and which object is the active tool or target. A specification should fix hand and object classes, the contact rule, a grasp vocabulary, the sampling rate and how occlusion and gloves are marked, then test agreement on a gold set before scaling.

What these labels are for

Hand-object interaction (HOI) labels teach a perception model to find hands, tell left from right, detect contact, pick out the object being manipulated, recognize the grasp and relate a tool to its target. Robotics teams use them to train and evaluate those perception components, to build object-centric representations, and as an input to hand-pose and retargeting pipelines when combined with 3D data.

This page covers spatial labels. When steps begin and end is a temporal question, specified in step segmentation and task boundary annotation. Masks and tracks for every object in the scene are covered in object tracks and segmentation masks, and metric 3D hands in 3D hand pose data from workplace recordings.

Label layers

LayerGeometryTypical samplingWhat it supports
Hand box and sideOne box per hand, left or rightKey frames plus interpolationHand detection and tracking
2D hand keypointsWrist and finger jointsSampled framesPose priors, grasp recognition
Contact statePer hand: free, touching, holding, unknownEvery transitionContact prediction, grasp phases
Active objectBox or mask of the object in handTransitions plus key framesActive-object detection
Object identityClass or instance ID from a fixed listPer active objectLinks to product and part data
Grasp typeClass from a fixed vocabularyOnce per graspGrasp recognition, pre-shape priors
Tool-target relationTool ID, target ID, verbPer tool useTool-use understanding
Visibility and PPEVisible, partial, hidden; glove typePer segmentFiltering and robustness analysis

Choose the layers your models consume. Keypoints and masks cost far more per frame than boxes and contact states.

Published precedents

MECCANO, recorded in an industrial-like assembly setting, labels temporal action segments and active-object bounding boxes and defines an egocentric human-object interaction detection task (Ragusa et al., 2020). HA-ViD provides 3,222 multi-view assembly videos with 96K temporal labels and 2M spatial labels (Zheng et al., 2023), a reminder that spatial labels can far outnumber temporal ones. IKEA ASM adds object segmentation and human pose to furniture-assembly video (Ben-Shabat et al., 2020), and Assembly101 includes 18M 3D hand poses alongside its action segments (Sener et al., 2022).

When 2D labels are not enough, 3D ground truth comes from instrumented capture. HOT3D obtained 3D poses of hands and objects from optical-marker motion capture and released hand annotations in UmeTrack and MANO formats (Banerjee et al., 2024). Third-person HOI images are also useful on their own: affordance grounding has been learned from exocentric interaction images and transferred to egocentric views of objects (Luo et al., 2022).

The contact rule

Write contact down as a visible test, not an intuition:

  • Touching — the hand visibly meets the object, but the object does not move with it.
  • Holding — the object moves rigidly with the hand, or is clearly enclosed by it.
  • Free — no contact with any annotated object.
  • Unknown — the contact region is hidden. Annotators must use this rather than guess.

Label the frame of each transition, and set a tolerance in frames for agreement checks. For tools, record two relations: hand holds tool, and tool contacts target.

The grasp vocabulary

Start from a published classification such as the GRASP taxonomy, which merges earlier taxonomies into 33 static one-handed grasp types, reducible to 17 general grasps if object shape and size are ignored (Feix et al., 2016). Then collapse it to the classes annotators can reliably tell apart at your resolution and that matter to your robot hand.

An illustrative reduced workplace set might contain power wrap, precision pinch, lateral pinch, tripod, hook, flat-palm push and tool grip. Fine distinctions that collapse in low-resolution or gloved footage only add noise. Report a confusion matrix from the gold set before freezing the list.

Illustrative annotation records

{
  "_comment": "Illustrative only — synthetic IDs and values",
  "clip_id": "clip_site024_0217",
  "frame": 3810,
  "hands": [
    {"side": "right", "box": [612, 404, 781, 560], "visibility": "visible",
     "glove": "nitrile", "contact": "holding", "active_object": "obj_0031",
     "grasp_type": "precision_pinch"},
    {"side": "left", "box": [402, 455, 540, 590], "visibility": "partial",
     "glove": "nitrile", "contact": "touching", "active_object": "obj_0007",
     "grasp_type": null}
  ],
  "objects": [
    {"object_id": "obj_0031", "class": "connector_housing", "box": [690, 470, 742, 515]},
    {"object_id": "obj_0007", "class": "wire_harness", "box": [380, 500, 610, 640]}
  ],
  "events": [{"type": "contact_start", "hand": "right", "object": "obj_0031", "frame": 3794}],
  "annotator_id": "ann_12",
  "guideline_version": "hoi_guide_v1.1"
}

Sampling strategy

Annotate key frames at a fixed interval plus every contact transition, and interpolate hand and object boxes between them; CVAT, for example, supports interpolation for video annotation (CVAT.ai). Interpolation drifts during fast motion, so require human review of interpolated stretches around grasps and releases.

Model pre-labeling is reasonable if it is disclosed. Record which frames were pre-labeled and measure how often reviewers correct them; a low correction rate on difficult frames is a warning sign, not a success.

Gloves, tools and occlusion

Workplace hands are often gloved, which changes appearance and hides finger joints; mark glove type on every hand, and accept that keypoints may be impossible on thick gloves. The effects on tracking and transfer are covered in gloved hands and PPE in workplace video. Mark the other hand, the object and the worker's body as occluders where they hide contact, so that "unknown" contact can be traced to a cause.

Quality and acceptance

CheckExample pass criterion (buyer sets)
Hand box accuracyMean IoU against the gold set above threshold
Side assignmentLeft/right accuracy above threshold
Contact timingTransitions within a set number of frames of gold
Grasp-type agreementChance-corrected agreement per class above threshold
Active-object identityCorrect object ID on sampled contacts
Use of "unknown"Rate consistent with measured occlusion, not used as a shortcut

Audit procedures and metric definitions for video labels are covered in measuring annotation quality in task video.

Limitations

  • 2D boxes and keypoints carry no depth; contact is inferred from appearance, and no force is measured.
  • Human grasp types do not map one-to-one onto robot hands with fewer degrees of freedom.
  • Existing footage often lacks the resolution for reliable finger keypoints.
  • Labels describe what an object looks like when handled, not how it behaves; the distinction is explained in object recognition vs manipulation data.
  • Detailed hand data can raise biometric-privacy questions in some jurisdictions; review them with counsel. This is not legal advice.

Questions to ask annotation vendors

  1. Which layers will you label, and at what sampling rate for each?
  2. What contact rule will annotators apply, and how is hidden contact recorded?
  3. Which grasp vocabulary do you propose, and what confusion did the gold set show between classes?
  4. Do you pre-label with models, and how are corrections tracked and reported?
  5. How do you handle gloved hands, tools held in the hand and two-handed grasps?
  6. How are object identities linked to our object list or the supplier's catalog?
  7. What share of frames is double-annotated, and what agreement did you reach on the last comparable project?
  8. Which export formats do you support for boxes, masks, keypoints and events?

Discuss your requirements

If you need HOI labels on footage you plan to license or commission, tell SourceX which layers, objects and permitted uses you need. SourceX's role is sourcing, rights review, licensing and delivery coordination; it can also arrange annotation, scoped case by case. SourceX reviews the requirement and follows up about potential sources, and a request does not guarantee a match. Related capture and labeling topics are on the workplace task demonstration hub and the humanoid training data guide, and the catalog page on expert annotations and labels describes labeled business assets.

Explore sourcing and licensing options with SourceX

Sources

Frequently asked questions

What do hand-object interaction labels record in workplace video?

They record where each hand is, which object it touches, when contact starts and ends, the grasp type and which object is the active tool or target. Robotics teams use these labels to train and evaluate perception components and, combined with 3D data, as input to retargeting pipelines.

How should annotators define contact between a hand and an object in video?

Contact is written as a visible test. Touching means the hand meets the object without moving it, holding means the object moves rigidly with the hand, and free means no contact. Annotators record unknown when the contact region is hidden rather than guessing.

How should a buyer choose a grasp vocabulary for hand-object labels?

A buyer should start from a published grasp classification such as GRASP, which has 33 static one-handed types, then collapse it to classes annotators can reliably tell apart. Reporting a confusion matrix from a gold set before the list is frozen shows whether the reduced vocabulary works.

Describe the data your robots need

Describe the tasks, modalities and permitted uses you need. SourceX reviews the requirement and follows up about potential sources; a request does not guarantee a match.

Discuss your humanoid training-data requirements with SourceX
See if you qualify