How it works
Specification to delivery.
Task specification, consented collection, quality review, and licensed demonstrations.
The workflow
From robot tasks to training data.
Catalog datasets and custom collections follow the same steps.
- 01
Define the specification
We define what the data must contain: modalities, tasks, labels, environments, and the acceptance criteria.
- 02
Source consented contributors
We recruit contributors who fit the specification and collect explicit consent and licensing at the point of contribution, so rights are established before any data is captured.
- 03
Collect at the origin
Contributors capture egocentric task video, human manipulation, or robot teleoperation to the specification. Timestamps, actions, sensor records, and labels are captured alongside the demonstrations.
- 04
Review and QA
Submissions are reviewed against modality-specific signal, metadata, and labeling criteria, with redaction applied where the specification requires it.
- 05
Package and pilot
We assemble a review package, then run a pilot before scaling the program.
- 06
Deliver with rights attached
Accepted data is delivered with the provenance and license records defined for the engagement, through the agreed access channel.
Questions
Working with us
- Can we start from an existing dataset?
- Yes. Every catalog entry publishes a buyer datasheet with capture specifications and review access. If an existing dataset fits, evaluation can begin from those records.
- What if the data we need does not exist yet?
- That is the common case. A build-to-spec collection program is run against the stated requirements, with QA and acceptance criteria agreed before collection begins.
- How do we evaluate quality before buying?
- Start with the published datasheet. Review packages provide schema details and sample metadata, with representative media, QA summaries, and licensing documentation available in a buyer review package.
- How is delivered data accessed?
- Request a review package from the dataset page. Production delivery format and transfer method are confirmed for the engagement.
Continue
Related pages
Data rights & provenance
How consent, licensing, and origin are defined and reviewed.
Quality methodology
Capture, synchronization, annotation, and outcome checks for robotics data.
Security & privacy
Request-based access, privacy handling, and program safeguards.
Licensing
Commercial license scope and the terms buyers review.
Solutions
Robotics training data and custom collection.
About Datoric
Robotics data programs, company identity, and contacts.