Custom data collection

Tell us the task.
We scope the capture.

Buyer-directed recording programs for human activity data. Specify what your model needs to observe; agree feasibility, access, protocol and acceptance before collection.

Requirements & feasibility

Define the learning or evaluation objective, workflow, objects, target environments, market, participants and intended use. Identify specialist access and whether the required signals can be captured.

Protocol & commercial scope

Agree accepted-hours definitions, equipment, perspectives, resolution, frame rate, annotation, privacy boundaries, licensing, review criteria and re-recording policy.

Pilot & buyer review

Record a representative permitted sample under the proposed setup. Review visibility, task completion, file compatibility and label quality. Resolve gaps before expanding scope.

Collection & quality review

Capture the agreed variations. Track files and decisions against the protocol. Separate accepted footage from rejected footage and any approved re-recordings.

Delivery & documentation

Package accepted footage, agreed annotations, metadata and review records. Include the agreed rights and permission documentation; verify the manifest and delivery method.

06 / What the buyer receives

More useful than
a folder of footage.

Agree the schema and evidence needed to evaluate a batch. The deliverable is defined in the proposal, including what is not captured or measured.

Video, context and a review trail.

Accepted recordings can be paired with task IDs, recording conditions, camera information and review outcomes. Optional annotation layers are scoped against your requirements.

Human RGB video does not automatically include 3D pose, depth, force or executable robot trajectories. Sensor streams and derived labels require a suitable rig and separate validation.

Task boundariesObject labelsOutcome & retry tagsAgreed file schema

Technical scoping for AI teams ↗

collection-example/  # illustrative
  footage/           # accepted video files
  metadata/          # clip and capture records
  annotations/       # if commissioned
  review/            # QA decisions and reasons
  documentation/     # datasheet and agreed rights
  manifest.json      # agreed file index
Technical scoping

Choose the view
that answers the task.

The brief should define what must be visible and what must be measured. More cameras are useful only when they solve a real visibility or synchronization need.

SetupUseful forCheck in the pilot
Egocentric / first-personOperator perspective and tool selectionHead movement, occlusion, field of view and task continuity
Fixed / overheadStable visibility of hands, parts and work surfaceReach boundaries, shadows, tiny objects and obstruction
Multi-viewComplementary coverage of complex interactionsCamera calibration, synchronization and shared identifiers
Additional sensorsSpecific depth, motion or tactile requirementsRig feasibility, measured performance and annotation validity; separately scoped

Scope the deliverable,
then scope the price.

Commercial terms depend on specialist recruitment, site access, rig complexity, accepted hours, annotation depth and review effort. Pilot scope and timing are agreed before collection starts.

Prepare a project brief

Agree the pilot before recording

The buyer defines the task, intended use and test for success. Taktfield assesses the proposed site, permissions, safety, equipment and cost. The parties then agree a written scope or revise the brief.

The pilot agreement defines the unit of delivery, review sample or coverage, feedback window and limits on corrections. Any larger collection is a separate decision after pilot review.