Skip to content

Workplace Task Demonstration Data for Humanoid Robots

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

Workplace task demonstration data is recorded human work, meaning video with optional hand pose, IMU and audio, plus labels and linked procedures, that shows how real tasks are done. It supports visual pretraining, task and step understanding, latent-action and reward learning, and co-training when hands are tracked in 3D. It contains no robot actions or forces, so humanoid control still needs robot data.

What this cluster covers

This is the largest cluster in the humanoid training data guide because demonstrations are where business supply and robot learning overlap most. It covers four things: deciding what demonstration data your model can use, finding existing footage, specifying new capture, and turning raw recordings into labeled, accepted deliveries. Task pages then apply those decisions to specific work such as garment folding, room turnover or shelf restocking.

The cluster treats demonstrations as human data. Teleoperated robot episodes and handheld-gripper data are robot-format data and sit in the procurement and specialist collection cluster.

What demonstration data looks like

At one end are archives recorded for other reasons: onboarding videos, practical-assessment recordings, technician body-camera sessions and fixed process cameras. At the other end are corpora designed for machine learning. Their design choices show what purpose-built capture can include:

  • Scale and consent by design. Ego4D gathered 3,670 hours of daily-life video from 931 consenting camera wearers, under de-identification procedures (Grauman et al., 2021).
  • Synchronized viewpoints and sensors. Ego-Exo4D recorded skilled activities, including bike repair, with an egocentric camera plus several exocentric cameras, eye gaze, IMU, 3D point clouds and expert commentary (Grauman et al., 2023).
  • Tracked hands. EgoDex paired 829 hours of egocentric video with 3D hand and finger tracking across 194 tabletop tasks (Hoque et al., 2025).
  • Language at capture time. EPIC-KITCHENS-100 used "pause-and-talk" narration as its first annotation stage, then transcribed, parsed and segmented it (Damen et al., 2020).

Business archives rarely have any of these properties out of the box. Most of the work in this cluster is about closing that gap, either by adding labels to existing footage or by commissioning recording that builds them in.

What it can support, and what it cannot

Use in a humanoid stackWhat the data must haveUsual route
Visual representation pretrainingVolume, diversity, hands and objects in viewExisting footage
Task and step understanding, evaluationTask names, step boundaries, outcomesExisting footage plus annotation
Video-language trainingNarration, instructions or aligned SOP stepsNarrated footage, SOP pairing
Latent-action or world-model pretrainingClean segments, constant frame rate, broad task coverageExisting footage
Co-training with robot data3D hand pose, calibrated cameras, tasks matching the robot'sCommissioned capture
Progress and reward estimationComplete episodes with outcome labelsEither, with annotation

Representation learning from human video is well established: R3M pretrained on Ego4D and served as a frozen perception module for downstream robot learning (Nair et al., 2022). Foundation-model data mixes put human video at the base and label it with latent or pseudo-actions (NVIDIA, 2025). Co-training needs more: EgoMimic captured its human demonstrations with Project Aria glasses so hand and head trajectories could share a space with the robot's (Kareer et al., 2024).

What the data cannot supply is the robot side: joint states, commanded actions, contact forces, the robot's own viewpoint and its kinematics. The detailed account is in what human demonstration video can and cannot do and the human-to-humanoid embodiment gap. Tasks that depend on touch or force need the data described in when video is not enough.

Where demonstration data comes from

Existing footage. Corporate learning teams, trade schools and certification bodies, field-service organizations, franchise networks and facility contractors hold recordings of real work. The most plausible starting point is corporate training video archives. Fixed cameras are the most common and least useful source for manipulation; see what CCTV footage can and cannot support. Before buying, check that public instructional video would not do the job; public instructional video vs licensed footage compares the two.

Commissioned recording. New capture lets you choose camera placement, sensors, task scripts, operator mix and consent wording. It costs time and money and still needs willing businesses and site access. The site describes a separate physical-world path for new recordings of hands-on work coordinated with businesses, where each opportunity has its own requirements, and the catalog entry for first-person video of skilled manual work describes that collection program. The decision itself is covered in existing footage vs commissioned recording.

Annotation on either. Step segments, hand-object labels, language and outcome flags can be added after the fact, within limits set by what the camera saw. SourceX's role is sourcing, rights review, licensing and delivery coordination; it can also arrange annotation and engage specialist capture partners, scoped case by case.

How to evaluate demonstration supply

Ask for evidence on each of these before you license anything. The thresholds are yours to set; the examples are illustrative.

  1. Hands in view. Share of sampled frames with both hands and the manipulated object visible (for example, a buyer might require 70% for co-training use).
  2. Viewpoint. Camera type, mount and lens per recording, and whether it changes across the archive. Egocentric and fixed views serve different uses.
  3. Segmentability. Whether recordings map to job, work-order or procedure IDs that make step labeling tractable.
  4. Coverage. Counts by site, operator, object type and condition, including failures and recoveries.
  5. Capture quality. Frame rate, motion blur at production pace, lighting, gloves and PPE.
  6. Language. Narration, captions or linked SOPs. Automatic transcripts are cheap but loose: HowTo100M's captions are ASR narrations with no extra manual annotation (Miech et al., 2019), and narration often runs ahead of or behind the action.
  7. Permissions. Who appears, what they were told, and who can license the footage. See worker consent and identifiable people.

The delivery-level version of this list is acceptance criteria for demonstration video.

Illustrative triage of three candidate assets

Candidate (synthetic)What it offersMain gapNext step
archive_LD_01: onboarding videos, tripod-mounted, narratedTask and step understanding; video-language pairsThird-person view; hands often occluded by the bodySample 20 clips for hand visibility; confirm the course vendor does not own them
bodycam_FS_02: technician body-camera sessionsFirst-person repair footage with expert talkCustomer premises; inconsistent framingCheck customer contract terms and premises permissions
fixedcam_PK_03: ceiling cameras over pack stationsCoverage and task timing at volumeNo hand detailUse for activity timing and task-recognition evaluation only

None of the three gives co-training data. If that is the goal, plan commissioned capture with tracked hands from the start.

Key pages in this cluster

GroupPageWhat it answers
Foundations and limitsHuman demonstration video for robot learningWhich parts of the stack human video can feed
Foundations and limitsThe human-to-humanoid embodiment gapWhy human motion does not transfer directly
Foundations and limitsHuman demonstrations vs teleoperationWhere business data ends and robot data begins
Foundations and limitsWhen video is not enoughTasks that need force or tactile data
Foundations and limitsDemonstrations for imitation vs pretrainingDifferent data requirements for the two uses
Foundations and limitsHow many demonstrations do you need?What published work reports, without universal minimums
Foundations and limitsUnlabeled video for latent-action pretrainingSourcing volume and diversity for VLA pretraining
Existing footageExisting footage vs commissioned recordingThe core license-or-record decision
Existing footageCorporate training video archivesChecklist for the most plausible existing asset
Existing footageInstruction-paired demonstration datasetsVideo that comes with matching written procedures
Existing footagePublic instructional video vs licensed footageWhen web video suffices and when it does not
Existing footageFixed-camera and CCTV footageWhat ceiling cameras can and cannot support
Existing footageAnnotating existing footageWhich labels can be added after the fact
Commissioned captureEgocentric vs exocentric workplace videoChoosing the viewpoint for your use
Commissioned captureStaged workcells vs live operationsWhere to record demonstrations
Commissioned captureHead-mounted camera capture specificationAn adaptable spec for egocentric capture
Commissioned captureScoping a pilot collectionTesting assumptions before full capture
Commissioned captureDemonstration coverage planOperators, sites, objects and conditions to cover
Commissioned capture3D hand pose dataGetting hand pose from workplace recordings
Annotation and acceptanceStep segmentation annotationTask boundaries and step labels
Annotation and acceptanceHand-object interaction annotationContacts, grasps and active objects
Annotation and acceptanceLanguage annotations for demonstrationsInstructions, captions and narrations
Annotation and acceptanceClip metadata schemaFields every clip should carry
Annotation and acceptanceRedaction without destroying training valueFace and bystander redaction trade-offs
Annotation and acceptanceAcceptance criteria for demonstration videoPass/fail checks on a delivery
Task pagesBimanual task demonstrationsTwo-handed work for two-armed robots
Task pagesGarment folding and textile handlingDeformable-object demonstrations from laundries
Task pagesHotel housekeeping room turnoverLong-horizon service work in guest rooms
Task pagesCommercial kitchen food prepCutting, portioning and plating
Task pagesRetail shelf restockingRestocking and facing in stores

Neighboring clusters

Demonstrations rarely stand alone. Written procedures supply the step names and success criteria that make video usable; see SOP-to-video step alignment and the procedures hub. Tool use and repair footage lives in maintenance and tool use; picking, packing and unloading in warehouse and fulfillment; assembly and machine tending in manufacturing and assembly.

Discuss your requirements

If you know the tasks, viewpoints and labels you need, describe them to SourceX, along with the uses you need licensed and how you will hold out evaluation data. SourceX investigates whether US businesses hold suitable footage, checks the supplier's licensing permissions and coordinates the license and delivery. It reviews each requirement and follows up about potential sources; a request does not guarantee a match.

Describe the workplace demonstration data your robotics project needs

Sources

Frequently asked questions

What is workplace task demonstration data, and what does it leave out?

Workplace task demonstration data is recorded human work, meaning video with optional hand pose, IMU and audio, plus labels and linked procedures. It contains no robot actions or forces, so humanoid control still needs robot data.

Which uses can demonstration video support, and which need tracked hands?

Visual pretraining and latent-action pretraining usually draw on existing footage. Co-training with robot data needs 3D hand pose, calibrated cameras and tasks that match the robot's, which usually means commissioned capture.

How should a buyer check who appears in workplace demonstration footage?

Ask who appears, what they were told and who can license the footage. Workplace recordings show employees, contractors, customers and bystanders, so buyers should check what notice or consent existed at recording, whether it covers AI training and transfer, and how withdrawal is handled.

Pages in this section

Technical procurement guides

Evaluation checklists

Sourcing guides

Collection specifications

Task data

Licensing and delivery

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