Skip to content

Existing Workplace Footage vs Commissioned Demonstration Recording

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

License existing footage when you need volume, real operating conditions and many sites for pretraining or task understanding, and can accept the viewpoints, labels and consent terms it was recorded under. Commission recording when you need a specific viewpoint, calibrated sensors, visible hands, planned task coverage, failure cases or consent written for AI training. Many programs combine them: archives for breadth, commissioned capture for the robot's target tasks.

The decision this page settles

The general choice between existing assets, new collection and specialist partners, across every data type, is covered in existing assets vs new collection vs specialist data. This page narrows it to one asset: video of people doing physical work. Should you license what a business already recorded, or pay to record it again on your terms?

The answer depends less on price than on which properties your training use needs, and whether those properties can be added after the fact.

What each route gives you

FactorExisting footageCommissioned recording
Viewpoint and sensorsWhatever the original purpose needed: overhead, presenter-framed, occasionally head-mountedChosen to match the robot: eye-level head camera, wrist camera, multi-view, depth, IMU
Calibration and clockRarely documentedSpecified: intrinsics, extrinsics, shared timestamps
Task coverageWhat the business happened to record, mostly routine successful workPlanned against a task list, including variations, recoveries and failures
Labels and languageTitles, sometimes procedure IDs; seldom step boundariesDesigned in: narration, step markers, task and outcome IDs
Consent and noticeGiven for training, quality or security purposesWritten for the intended AI use from the start
RealismReal pace, interruptions and sitesReal on live work; less so when staged
Volume and site diversityPotentially large, many sites, many yearsBounded by budget, recruitment and site access
Time to first dataAfter rights review and selectionAfter scoping, recruitment, equipment and a pilot

Properties you can add later, and properties you cannot

This is the test that decides most cases.

PropertyCan it be added to existing footage?Notes
Task and step labelsYesAnnotation cost scales with hours; see annotating existing footage
Language descriptionsYes, after the factPost-hoc captions are weaker than narration recorded during the work
Object masks and tracksWhere objects are visibleOcclusion limits coverage
2D hand keypointsPartlyOnly where hands are visible and ungloved
RedactionYesIt lowers training value and does not settle permission questions
Camera viewpointNoThe archive's angle is fixed
Camera calibrationRarelyOnly if the same cameras are still installed and can be calibrated now
Depth, IMU, gazeNoNever recorded
Multi-sensor synchronizationNoNeeds a shared clock at capture time
Planned failures and rare eventsNoYou can only search for what happens to exist
Consent scope for AI trainingSometimesRe-notice or re-consent may be impractical, especially for former staff

If a property you need sits in a "No" row, no amount of preparation will make the archive provide it. That is the clearest signal to commission.

What designed capture looks like in published datasets

Purpose-built collections show what commissioning buys. Ego-Exo4D recorded skilled activities simultaneously from egocentric and multiple exocentric cameras, with multichannel audio, eye gaze, 3D point clouds, camera poses, IMU and expert commentary (Grauman et al., 2023). Assembly101 used 8 static and 4 egocentric cameras on unscripted assembly that included mistakes (Sener et al., 2022).

Language and failures can also be designed in. EPIC-KITCHENS-100 used head-mounted cameras and "pause-and-talk" narration as its first annotation stage (Damen et al., 2020). CaptainCook4D recorded normal and intentionally erroneous recipe executions under IRB approval with written consent (Peddi et al., 2023).

Designed capture still costs effort after recording. Ego4D worked with consenting participants and de-identification procedures, and reports more than 250,000 hours of annotator effort (Grauman et al., 2021).

Existing video wins on scale. HowTo100M assembled 136 million clips from 1.22 million narrated web videos and used the automatically transcribed narration with no manual annotation (Miech et al., 2019); later work found that much of that narration does not describe what is on screen at the time. Business archives often behave similarly: abundant, weakly labeled and loosely aligned.

Where existing footage usually comes from

What commissioning involves

A commissioned recording needs a task list, a capture specification, demonstrators who consent, site access, equipment, calibration and in-collection QA. Two early choices shape it: whether to record live operations or staged sessions (staged vs live operation recording), and how small a first run should be (pilot collection scoping).

The SourceX site describes a separate physical-world path for new recordings of hands-on work coordinated with businesses, where each opportunity has its own requirements.

A decision procedure

  1. Name the training use: visual pretraining, latent-action pretraining, co-training with tracked hands, step recognition, or evaluation.
  2. List must-have properties for that use, marking any that appear in the "No" rows above.
  3. Request a sample from the archive and audit it against the list.
  4. Commission for any use whose must-have properties fail and cannot be added.
  5. License and budget preparation for uses the archive passes.
  6. Combine where it pays: an archive for breadth, a commissioned set for target tasks and for a held-out evaluation set.

Illustrative: two requests for one task family

# Illustrative only — two ways to source data for shelf restocking
archive_license:
  asset: existing training and quality-audit video, retailer_009, 2021-2025
  use: visual pretraining; step recognition
  must_have: hands visible in sampled frames above a buyer-set share; procedure IDs; constant frame rate
  preparation: selection, step segmentation, face and screen redaction
  rights: notice covered internal training; AI-training permission to be confirmed per video
commissioned_recording:
  sites: store_A, store_B (live operation, off-peak)
  demonstrators: consenting staff with a range of experience (operator_A01 ... operator_A12)
  capture: eye-level head camera + wrist camera, calibrated, shared clock
  coverage: SKU list incl. fragile and heavy items; planned recoveries
  labels: narration during capture; step markers; outcome flag per attempt
  rights: consent written for AI training; license defines redistribution limits

Hidden costs on each side

Existing footage: most hours are irrelevant and must be screened out; rights must be checked video by video; vendor-produced content may not belong to the business; annotation is needed before training; redaction removes useful pixels.

Commissioned recording: recruiting and briefing demonstrators; disruption to live work; equipment and calibration; consent administration; QA and re-shoots; repeat visits to cover variation.

Neither route has a universal minimum volume. What you need depends on architecture, task, embodiment and intended use.

Permissions and provenance

Existing footage was recorded under a notice that described some purpose. Ask what that purpose was, whether licensing for AI training falls within it, and who appears on camera: employees, contractors, customers or members of the public.

Commissioned recording lets consent be written for the intended use, but it still needs site access and the agreement of everyone recorded. Worker consent and identifiable people covers the diligence questions. This is not legal advice.

Questions to ask suppliers

  1. Why was this footage recorded, and what notice did the people in it receive?
  2. Which cameras, mounts and frame rates were used, and are any of those cameras still installed?
  3. Can clips be linked to task, procedure or work-order IDs?
  4. What share of the archive shows hands and handled objects up close?
  5. Are failed, interrupted or corrected attempts included, or edited out?
  6. Who produced the footage: in-house staff or an outside vendor?
  7. For new recording: which sites could host it, during which hours, and with how many willing demonstrators?
  8. For new recording: can consent be written to cover model training, licensing and retention?

Discuss your requirements

If you have worked out which properties your use needs, send SourceX the task list and must-have properties. SourceX looks for US businesses that hold suitable footage, checks the data and the supplier's licensing permissions, and coordinates the license and delivery. If no existing asset fits, SourceX can scope a commissioned collection of new recordings. SourceX reviews each request and follows up about potential sources; a request does not guarantee a match.

For background, see what human demonstration video can and cannot do for robot learning, the workplace task demonstration hub and the humanoid training data guide. The catalog page on licensing video recordings covers record-level terms.

Describe the workplace demonstration data your robotics project needs

Sources

Frequently asked questions

When should a team license existing workplace footage instead of commissioning recording?

Licensing existing footage suits teams that need volume, real operating conditions and many sites for pretraining or task understanding, and that can accept the viewpoints, labels and consent terms it was recorded under. Many programs combine archives for breadth with commissioned capture for target tasks.

Which properties of workplace video can be added after recording, and which cannot?

Task and step labels, language descriptions and redaction can be added afterwards, but camera viewpoint, depth, IMU and gaze cannot. Multi-sensor synchronization and planned failures cannot be added either, so a missing property of that kind points toward commissioned recording.

Does consent for existing footage cover licensing it for AI training?

Existing footage was recorded under a notice for some purpose, so consent may not extend to AI training. Buyers should ask what that purpose was and who appears on camera. Re-notice or re-consent may be impractical for an archive, especially for former staff.

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