ROBOTICS DATA COLLECTION & ANNOTATION
Human demonstration recordings and annotation of your existing data. Start with one task, a clear specification and a pilot your team can evaluate.
Discuss a robotics pilot See an example briefONE TASK. A CLEAR DATA CONTRACT.
The action, setting and evidence your team needs.
New human recordings, existing material, or both.
Agreed labels, documented checks and usable files.
Scope, budget and acceptance criteria agreed before production.
TWO WAYS TO START
For robotics and embodied AI teams with a specific data requirement.
Commission people to perform and record a defined physical task. Agree the environment, camera view, task variations and recording requirements around your intended use.
Equipment, locations, participant requirements and usage rights are scoped for each pilot.
Bring your recordings or other project data. We scope the annotation and review work around the labels, evidence and export format your team needs.
Label definitions and review coverage are agreed on a sample before a larger batch.
AN EXAMPLE PILOT BRIEF
“Move a cup from a marked start position onto a tray.” A simple task still needs a shared definition of the recording and its labels.
Illustrative scope only. This is a proposed brief, not footage from a client project.
FROM BRIEF TO PILOT
The pilot should help you decide whether to expand, revise the specification or stop.
Share the task, intended use and data you already have. Agree deliverables, rights, access, retention, budget and timing.
Review a small sample together. Resolve unclear instructions and settle the acceptance criteria.
Receive the agreed files with review notes and known limitations. Assess their fit in your own workflow before scaling.
BEFORE WE START
Yes. Scope new human recordings and annotation in one pilot, or start with a review of material you already have. The brief defines what is included in each stage.
Human demonstration video shows an action being performed. It does not automatically include robot commands, joint states or sensor measurements. Your research team should confirm how it will use the recordings. Robot teleoperation and instrumented robot collection require a separate capability assessment.
We confirm those against your requirements before committing. Start with the sample structure your pipeline expects, the initial batch size and the decision the pilot should support.
The project agreement specifies source permissions, participant permissions where needed, permitted uses, storage, access and retention. Share a high-level description through the enquiry form; agree a suitable transfer route before sharing project files or sensitive data.
START WITH YOUR TASK
Tell us the task, whether you need new recordings or annotation, and what a useful pilot would deliver.
Discuss your pilot