Remote capture
Remote capture can support distributed coverage across markets. Participants record on approved devices and follow a defined capture flow.
Video data collection
Collect the video your dataset does not cover
Your model may need footage that does not exist, misses the conditions it will meet in use, or cannot be used under its current licence. YPAI can design and operate a managed video collection project to close that gap.
Your engineers define what the footage must show and how it will be judged. YPAI runs the collection against that brief.
Share the footage gap. A member of the team will review what you send.
A managed video collection project at scale
YPAI manages sourcing and capture across the locations and conditions needed for the required coverage. Accepted footage is handed to engineering with the records needed to verify it before use.
Coverage before volume
Turn a coverage gap into recording instructions
A file count shows volume, not whether the footage covers the conditions the model will meet in use.
Observed gap
Recording instruction
Missing scenario
Locations / conditions / required share
A missing scenario becomes a coverage requirement. If a group or market needs a fixed share, the plan gives it a quota. The resulting instructions tell recorders what must appear in the frame and which conditions to reproduce.
Remote capture and moderated capture suit different tasks
The task determines whether coverage comes from distributed recording, active moderation, a fixed location, supplied hardware or synchronised streams. YPAI confirms the final configuration before commitment.
Moderated capture
A moderator gives instructions and intervenes during recording when the task requires it.
Fixed or synchronised
Some tasks need a fixed location or hardware supplied by YPAI. Others add camera or sensor streams that stay synchronised with the video.
Source to decision to delivery
Each asset keeps its operating trace
YPAI owns the collection platform and its human-review workflow. Each asset carries a source record; any derivative links back to that source. The review record names the reviewer and rubric, then stores the evidence and decision.
SOURCE
DELIVERY
Review follows the project plan
Technical checks follow the project plan. Human reviewers examine recordings selected under the sampling plan. The reviewer applies the rubric and records the evidence, decision and reason. A result that needs another judgement goes to adjudication or escalation.
If the acceptance or change-control path calls for rework or recapture, YPAI returns the recording with the reason.
The return path remains visible
Source, derivative and review records stay connected so the receiving team can inspect what changed, who reviewed it and which decision applies.
Engineering receives a delivery it can verify
The handover groups accepted media in a delivery manifest with the agreed metadata and QA or acceptance record. Engineering uses that package to verify the asset and version before it enters the model workflow.
Accepted mediaDelivery manifestAgreed metadataQA or acceptance record
Decisions before capture
Agree rights and processing before capture
Purpose and permission
The buyer and YPAI identify the purpose and applicable lawful basis before processing personal data. They record any source rights, releases, licences or permitted-use terms separately and keep them with the asset.
CAPTURE
STARTS
AFTER AGREEMENT
STARTS
AFTER AGREEMENT
Processing and requests
The buyer and YPAI set the processing location, retention period and relevant subprocessors before work starts. Standard contractual clauses are available for a customer-directed transfer outside the EEA, while the media stays in the client-specific environment agreed for the work.
YPAI uses separate workflows for data-subject requests and participant withdrawals. A withdrawal carries its own audit trail. Under the standard terms, erasure follows within 30 days after the contract ends.
Verify capacity, then schedule capture
YPAI checks the required coverage and capture setup against available capacity before setting the schedule. Before capture, the buyer and YPAI agree the scope, acceptance terms, change control and price for the work.
Pilot is a method decision
Test the method before production
A pilot tests the proposed method against its own project-specific standard. The buyer reviews the result and its quality measurements, then decides how to respond to any recorded deviation.
After that review, the buyer decides whether to commission production.
The first useful brief
Share the footage gap
Tell us where the current footage falls short and what the new footage must show. The team will review your submission.